1. ARC-SC-agenda-Mar-2019 Date: 2019-03-12 Authors: July 2009
doc.: IEEE /0840r0
ARC-SC-agenda-Mar-2019
Date:
Authors:
David Bagby, Calypso Ventures, Inc.

2. Agenda for: ARC SC, March 2019, Vancouver, BC, Canada
Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: ARC SC, March 2019, Vancouver, BC, Canada
David Bagby, Calypso Ventures, Inc.

3. IEEE 802.11 Architecture Standing Committee
July 2009
doc.: IEEE /0840r0
IEEE Architecture Standing Committee
Agenda
March 2019 session
Chair: Mark Hamilton (Ruckus/ARRIS)
Vice Chair: Joe Levy (InterDigital)
David Bagby, Calypso Ventures, Inc.

4. Tuesday, March 12th, PM2

5. Attendance, etc. Reminders to attendees:
July 2009
doc.: IEEE /0840r0
Attendance, etc.
Reminders to attendees:
Sign in for .11 attendance credit
Noises off
No recordings
David Bagby, Calypso Ventures, Inc.

6. Participants, Patents, and Duty to Inform
July 2009
doc.: IEEE /0840r0
Participants, Patents, and Duty to Inform
All participants in this meeting have certain obligations under the IEEE-SA Patent Policy.
Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2]:
“Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents
“Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents)
The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group
Early identification of holders of potential Essential Patent Claims is strongly encouraged
No duty to perform a patent search
David Bagby, Calypso Ventures, Inc.

7. July 2009
doc.: IEEE /0840r0
Patent Related Links
All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development.
Patent Policy is stated in these sources:
IEEE-SA Standards Boards Bylaws
IEEE-SA Standards Board Operations Manual
Material about the patent policy is available at
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit
This slide set is available at
David Bagby, Calypso Ventures, Inc.

8. Call for Potentially Essential Patents
July 2009
doc.: IEEE /0840r0
Call for Potentially Essential Patents
If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance:
Either speak up now or
Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or
Cause an LOA to be submitted
David Bagby, Calypso Ventures, Inc.

9. Participation in IEEE 802 Meetings
November 2016
doc.: ec EC
Participation in IEEE 802 Meetings
Participation in any IEEE 802 meeting (Sponsor, Sponsor subgroup, Working Group, Working Group subgroup, etc.) is on an individual basis
•     Participants in the IEEE standards development individual process shall act based on their qualifications and experience. ( section 5.2.1)
•    IEEE 802 Working Group membership is by individual; “Working Group members shall participate in the consensus process in a manner consistent with their professional expert opinion as individuals, and not as organizational representatives”. (subclause “Establishment”, of the IEEE 802 LMSC Working Group Policies and Procedures)
•    Participants have an obligation to act and vote as an individual and not under the direction of any other individual or group. A Participant’s obligation to act and vote as an individual applies in all cases, regardless of any external commitments, agreements, contracts, or orders.
•    Participants shall not direct the actions or votes of any other member of an IEEE 802 Working Group or retaliate against any other member for their actions or votes within IEEE 802 Working Group meetings, see section and the IEEE 802 LMSC Working Group Policies and Procedures, subclause “Chair”, list item x.
By participating in IEEE 802 meetings, you accept these requirements. If you do not agree to these policies then you shall not participate.
(Latest revision of IEEE 802 LMSC Working Group Policies and Procedures:
Dorothy Stanley, HP Enterprise

10. Other Guidelines for IEEE WG Meetings
All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws.
Don’t discuss the interpretation, validity, or essentiality of patents/patent claims.
Don’t discuss specific license rates, terms, or conditions.
Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings.
Technical considerations remain primary focus
Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets.
Don’t discuss the status or substance of ongoing or threatened litigation.
Don’t be silent if inappropriate topics are discussed … do formally object.
See IEEE-SA Standards Board Operations Manual, clause and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.

11. ARC Agenda – March 2019 (1 of 2) Tuesday, March 12, PM2
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – March 2019 (1 of 2)
Tuesday, March 12, PM2
Administrative: Minutes
IEEE 1588 mapping to IEEE /802.1ASrev and use of FTM
MAC randomization – follow-ups for
Consider formation of a TIG: 11-19/0483r0
IETF/802 coordination
IETF SAVI draft:
New topic (from REVmd)?: “What is a STA?” (See: 11-19/0106r0)
Wednesday, March 13, AM1
“What is an ESS?”: 11-18/1051r5
MLME-RESET, versus MLME-JOIN and MLME-START (and MLME-SCAN?)
David Bagby, Calypso Ventures, Inc.

12. ARC Agenda – March 2019 (2 of 2) Wednesday, March 13, PM2
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – March 2019 (2 of 2)
Wednesday, March 13, PM2
Future sessions / SC activities
IEEE 802 activities relevant to : aq, 802.1CQ and LAAP: 11-18/1934r0
Consider IETF DetNet/time-sensitive networking input (potential relationship to RTA TIG?)
Multiple MAC Addresses (and IPv6), “Multiple radios”
System architecture views for common use scenarios
AP/DS/Portal architecture and 802 and GLK concepts /0136r2, 11-16/1512r0, 11-16/0720r0, 11-15/0454r0, 11-14/1213r1 (slides 9-11)
Continue the other items (previous slide), as needed
David Bagby, Calypso Ventures, Inc.

13. Prior ARC Minutes January face-to-face minutes: 11-19/0165r0 Jan 2009
doc.: IEEE /1455r0
Prior ARC Minutes
January face-to-face minutes:
11-19/0165r0
David Bagby, Calypso Ventures, Inc.

14. IEEE 1588 mapping to IEEE 802.11/ 802.1ASrev use of FTM update
Update (Ganesh Venkatesan)
IEEE 1588/802.1AS
Results from first Sponsor Ballot of IEEE 1588 revision, Sep 17 – Oct 28: (84%), 359 comments received.
In comment resolution process.
802.1ASrev use of FTM:
Results of first Sponsor Ballot of 802.1ASrev D8.0, Jan 24 – Feb 23?

15. IEEE 802 activities directly related to IEEE 802.11 ARC
802.11aq, 802.1CQ and LAAP: 11-18/1934r0
Clear(er) problem statement from 802.1?
Proxy IPv6 Neighbor Discovery: 11-18/1920r2
Updates?

16. MAC Address randomization
Background:
Incoming liaison from WBA is here: 11-18/1579r1
response: 11-18/1988r2
Consider formation of a TIG: 11-19/0439r0
Note Submissions on this topic (in REVmd):
MAC randomization - IDQuery: 11-19/0179r0
Address policy ANQP: 11-19/0286r3

17. IETF/802 coordination
Peter Yee present topics of interest:

18. Source Address Verification Improvements
IETF SAVI draft:

19. What is a STA?
See: 11-19/0106r0
Related: What is the (“STA(s)”) architecture of off-channel TDLS?

20. Wednesday, March 13th, AM1

21. What is an ESS?
See 11-18/1051r5
Related, new topic from REVmd, “What is a STA?”
See: 11-19/0106r0
Related: What is the (“STA(s)”) architecture of off-channel TDLS?

22. MLME-RESET, versus MLME-JOIN and MLME-START
Topic out of REVmd:
No apparent requirement for an “initial” MLME-RESET, in So, what is the initial state?
Many MIB attributes describe taking effect at next MLME-JOIN or MLME-START.
MLME-JOIN occurs at each BSS transition
MLME-START occurs at less well-defined points, seems to require an MLME-RESET first
Do these attributes really take effect at these points, or at the MLME-RESET?
How about other state information, such as security association, block ack agreements, etc., etc.?
Maybe need to consider MLME-SCAN, too?
Is correct information provided at these primitives (and not more than needed information)?

23. Wednesday, March 13th, PM2

24. ARC Future Activities & sessions
ARC SC meets when a specific focused task is requested of the SC for which the is sufficient volunteer interest.
Continue work on architectural models, and liaison with TGs in development of their architecture as appropriate
Investigation of “split” PHYs (LC, 28 GHz (Phazr))
Investigation of as part of a Deterministic Network
Multiple MAC Address discussion (IPv6) – perhaps “multiple radios” too
System architecture(s) for common use scenarios
Will also follow 802.1/ activities on links, bridging, and MAC Service definition – “What is an ESS?”, for example
“What is a STA?” (11-19/0106) Related: What is the (“STA(s)”) architecture of off-channel TDLS?
MLME-RESET, versus MLME-JOIN and MLME-START (and MLME-SCAN?)
Monitor/report on IETF/802 activities, as needed
Monitor/report on IEEE 1588 activities and 802.1ASrev use of FTM, as needed
If you have ANY other topic that you would like ARC SC to consider, contact the SC chair.

25. Planning for May 2019 Plan for three individual meeting slots
Usual slot on Wed AM1
Another 2 slots for standalone ARC work
Teleconferences:
None planned.

26. DetNet and other time-sensitive networking, (IETF, RTA TIG, etc.)
IETF TSN use case document declares inappropriate for deterministic networking. But, TSCH appears to be appropriate.
Can be used?
If not, can/should be “improved” so that it can be used?
PAW BOF formed, scheduled for ~ March 25
Does 11ax scheduling/trigger-based fit into this?
What are the requirements coming from the RTA TIG, and do those change the above?

27. AP/DS/Portal architecture and 802 concepts
Presentations on architectural description(s)
Reference presentations (previously reviewed, current status of thinking):