1. ARC-SC-agenda-July-2018 Date: 2018-07-10 Authors: July 2009
doc.: IEEE /0840r0
ARC-SC-agenda-July-2018
Date:
Authors:
David Bagby, Calypso Ventures, Inc.

2. Agenda for: ARC SC, July 2018, San Diego, California, USA
Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: ARC SC, July 2018, San Diego, California, USA
David Bagby, Calypso Ventures, Inc.

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

4. Tuesday, July 10th, 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 – July 2018 (1 of 2) Tuesday, July 10, PM2
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – July 2018 (1 of 2)
Tuesday, July 10, PM2
Administrative: Minutes
IEEE 1588 mapping to IEEE /802.1ASrev use of FTM update /1086r4
802 (and 802.1) activities: 802c, 802.1CQ
IETF/802 coordination
Continued review of TGax approach to subclause 10.2 and Figure 10-1: 11-18/0362r1
YANG/NETCONF modeling discussions – TIG formation discussion
“What is an ESS?”: 11-18/1051r0
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)
MLME-RESET, versus MLME-JOIN and MLME-START
Wednesday, July 11, AM1
TGba joint meeting preparation: 11-18/0884r1, 11-18/1016r0, 11-18/1017r0, 11-18/1020r0
Continue the others, above, as needed
David Bagby, Calypso Ventures, Inc.

12. ARC Agenda – July 2018 (2 of 2) Thursday, July 12, AM2
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – July 2018 (2 of 2)
Thursday, July 12, AM2
Future sessions / SC activities
Continue the other items (previous slide), as needed
TGba joint meeting preparation: 11-18/0884r1, 11-18/1016r0, 11-18/1017r0, 11-18/1020r0
Joint session with TGba – Thursday, July 12, PM2
Investigation of WUR architecture topics; eventually may lead into “split” PHYs (LC, 28 GHz (Phazr)): 11-17/1025r0, 11-18/0884r1, 11-18/1016r0, 11-18/1017r0, 11-18/1020r0
David Bagby, Calypso Ventures, Inc.

13. Prior ARC Minutes May face-to-face minutes:
Jan 2009
doc.: IEEE /1455r0
Prior ARC Minutes
May face-to-face minutes:
11-18/0942r0
11-18/0999r0 (TGba minutes, capturing Thursday PM2 joint meeting)
May teleconference minutes:
11-18/1021r0
June teleconference minutes:
11-18/1098r0
David Bagby, Calypso Ventures, Inc.

14. Egyptian architecture picture allocations
Jan 2009
doc.: IEEE /1455r0
Egyptian architecture picture allocations
David Bagby, Calypso Ventures, Inc.

15. IEEE 1588 mapping to IEEE 802.11/ 802.1ASrev use of FTM update
Update (Ganesh Venkatesan)
IEEE 1588/802.1AS
WG LB on D7.0 closed May 7
802.1ASrev use of FTM:
11-17/1086r4 (Ganesh Venkatesan)

16. IEEE 802 activities directly related to IEEE 802.11 ARC
Update (Mark Hamilton)
802.1Q-2018 is now published (available at no charge to WG members for a limited time)
802c, and 802.1CQ
802.1CQ in PAR process
Relation to aq
Other correlations or implications?

17. IETF/802 coordination Peter Yee present topics of interest:
Consider IETF DetNet/time-sensitive networking input?
FC-CoDel?
TLS v1.3?

18. TGax architecture topics
TGax approach to subclause 10.2 and Figure 10-1: 11-18/0362r1
Concepts initially discussed in Sep, 2017 (see 11-17/1220r2 and 11-17/1396r1)
In March, reviewed 11ax D2.0 comments received, and resolutions first proposed (11-18/0362r0)
Review/discuss updates, formulate response

19. Discussion on YANG/NETCONF models
Next steps? (Are any underway, already?)
TIG?

20. What is an ESS?
See 11-18/1051r1

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

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.?

23. Wednesday, July 11th, AM1

24. Thursday, July 12th, AM2

25. 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
Consider YANG/NETCONF next steps
Investigation of WUR architecture topics; may lead into “split” PHYs (LC, 28 GHz (Phazr))
Will also follow 802.1/ activities on links, bridging, and MAC Service definition – “What is an ESS?”, for example
MLME-RESET, versus MLME-JOIN and MLME-START
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.

26. Planning for September 2018
Plan for three individual meeting slots
Usual slot on Wed AM1
Another 2 slots for standalone ARC work (Monday/Tuesday?)
Plus Joint sessions: Another with TGba?
Individuals interested in ARC work are encouraged to also attend AANI SC sessions
Teleconferences:
Schedule with 10 days notice

27. Prep for TGba joint session
Suggest:
Review of slides (in this deck)
Review of “802.11ba Architecture discussion” (Ganesh Venkatesan) 11-18/0884r1
Review of “Definition of WUR Mode” ( r2)
Review of Specification Framework (11-17/0575r11)
Review of inputs from teleconferences: 11-18/1016r0, 11-18/1017r0, 11-18/1020r0

28. Thursday, July 12th, PM2 Joint session with TGba and ARC

29. TGba architecture topics
Investigation of TGba (WUR) architecture topics
may lead into discussion of other “split” PHYs (LC, 28 GHz (Phazr))
Presentations:
“802.11BA topics related to ARC” (Ganesh Venkatesan) 11-18/0533r2
“11BA Arch Discussion” (Mark Hamilton) 11-17/1025r0
Review of “802.11ba Architecture discussion” (Ganesh Venkatesan) 11-18/0884r1
Review of “Definition of WUR Mode” ( r2)
Review of Specification Framework (11-17/0575r11)
Review of inputs from ARC teleconferences: 11-18/1016r0, 11-18/1017r0, 11-18/1020r0
Also see following slides
TGba is still maturing, through the SFD process. Started in March session with substantive discussions

30. TGba architecture comments/answers to questions in 11-17/1025 (from July 10, 2017 TGba)
Yes, fully independent PHY
Probably independent MAC?
Always co-located with AP or non-AP STA – a “companion” radio
No MAC Address (?)
WUR MAC (assuming it is independent) does need to coordinate with the main MAC. Main MAC negotiates a WUR ID on WUR’s behalf, for example. And, power on/off needs to be coordinated between them – might be through higher layer entity, though (?)
WUR does not associate to the BSS (it doesn’t have a MAC Address)
WUR only runs in 2.4/5 GHz. But, can work with all PHYs (maybe?)
Mesh, IBSS, OCB uses are TBD in the future, not now

31. TGba architecture new questions (from July 12, 2017 ARC)
Does every WUR stack have an individual “ID” (“WUR address”)? Or, could a given WUR stack be only addressed using a “group ID” in some scenarios?
How are WUR ID’s made globally unique, or are they? What about overlapping WUR coverage? Prevented using the same solution as security protections? Prevented through selection of different sub-carriers?
How does the WUR stack become aware of ongoing NAV protections? RX doesn’t need to know. What about the TXr?
For protection – how much of a legacy frame header is sent? Just PHY header? Some MAC header (addresses? NAV? Etc)
Is there any sharing (necessarily, as part of the design, not implementation choice) of RF front-end?
What happens when the Main stack wakes up? Does it still have an association? Is it in some power save state (which)?
“Yes, fully independent PHY” – is that for the RX side, or the TX side?
What about error recovery? STA goes out of range? What if the AP changes (DFS, ITS, etc)?

32. TGba architecture potential assumptions (from July 12, 2017 ARC)
How does the WUR stack become aware of ongoing NAV protections? RX doesn’t need to know. The master’s Main stack runs the usual medium access, and wait until it has a TXop, then triggers the WUR to TX.
On the RXr, only one stack (WUR or Main) are active at a given point in time.
When the Main stack wakes up, it still has an association and is in a power save state (a new “WUR” power save state). The Main stack TXs, which is the indication that the wakeup was successful and completed.
There are 100% RX WURs, at the sleeping node. There are TXrs, on the master node, and these are therefore (potentially) different architecturally.
The WUR “wakeup” frame does not NAV protect to cover the sleeping device’s Main radio waking up and TXing.
Review 11-17/972 to confirm/before proceeding on the above