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

2. Agenda for: ARC SC, July 2017, Berlin, Germany
Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: ARC SC, July 2017, Berlin, Germany
David Bagby, Calypso Ventures, Inc.

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

4. Tuesday, July 11th, 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 2017 Tuesday, July 11, PM2 Wednesday, July 12, AM1
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – July 2017
Tuesday, July 11, PM2
Administrative: Minutes
IEEE 1588 mapping to IEEE
802 activities
IETF/802 coordination
802.1ASrev use of FTM
Investigation of WUR architecture topics; may lead into “split” PHYs (LC, 28 GHz (Phazr)): 11-17/1025r0
MIB attributes Design Pattern /1281r4, 11-15/0355r4, 11-17/0475r3, 11-09/0533r1
YANG/NETCONF modeling discussions – 11-16/1436r1
AP/DS/Portal architecture and 802 and GLK concepts /0136r2, 11-16/0720r0, 11-15/0454r0, 11-14/1213r1 (slides 9-11)
“What is an ESS?”
Wednesday, July 12, AM1
Investigation of WUR architecture topics; may lead into “split” PHYs (LC, 28 GHz (Phazr)): /1025r0
MIB attributes Design Pattern (cont)
AP/DS/Portal architecture and 802 and GLK concepts (cont)
“What is an ESS?” (cont)
Future sessions / SC activities
David Bagby, Calypso Ventures, Inc.

12. Jan 2009
doc.: IEEE /1455r0
ARC Minutes
May face-to-face minutes:
May 30 teleconference minutes:
June 27 teleconference minutes: 11-17/1125
David Bagby, Calypso Ventures, Inc.

13. IEEE 1588 mapping to IEEE
Update (Mark Hamilton)

14. IEEE 802 activities directly related to IEEE 802.11 ARC
Update (Mark Hamilton)
802.1Q revision underway, target Sept Roll-in:
IEEE Std 802.1Qcd-2015,
IEEE Std 802.1Qca-2015,
IEEE Std 802.1Q-2014 Cor ,
IEEE Std 802.1Qbv-2015,
IEEE Std 802.1Qbu-2016,
IEEE Std 802.1Qbz-2016
802.1AC-2016 published

15. IETF/802 coordination
Dorothy Stanley present topics of interest:

16. 802.1ASrev use of FTM Presentations:

17. TGba architecture topics
Investigation of TGba (WUR) architecture topics
may lead into discussion of other “split” PHYs (LC, 28 GHz (Phazr))
Presentations:
11-17/1025r0
Also see following slides

18. TGba architecture comments/answers to questions in 11-17/1025 (from Mon AM1)
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

19. TGba architecture new questions (from Wed AM1 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)?

20. TGba architecture potential assumptions (from Wed AM1 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

21. Design Pattern for MIB attributes
The WG11 Chair has requested that the ARC SC investigate and create a Design Pattern for MIB attributes of the form “*Implemented” and “*Activated”
Background:

22. Discussion on YANG/NETCONF models
We have a likely window now to make a change, if any, as we transition from REVmc to REVmd maintenance activities
Submissions:

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

24. What is an ESS? Current definition depends on the relationship to LLC
“A set of one or more interconnected basic service sets (BSSs) that appears as a single BSS to the logical link control (LLC) layer at any station (STA) associated with one of those BSSs.”
That would mean a Bridged LAN (for example) creates an ESS. Probably not what we (802.11) meant.
We probably meant something about transparency of “location of attachment”/”mobility”, from whatever is using the MAC
and other entities, necessary to accomplish this? ESS == demarcation of this transparency??
Is it:
Transparent to whatever upper layer is above ?
Includes entities beyond (above?) ? (Like bridges in the 11ak scenario?)
The APs have to have some common/similar configuration settings? (SSID, at least. Probably other facilities (security, etc.) and policies?)
Changes to Figure 4-1: ‘BSS’s are just STAs. These ovals are BSAs. Also, should we be saying “OBSA”?

25. What is an ESS? (Continued)
Current definition depends on the relationship to LLC
“A set of one or more interconnected basic service sets (BSSs) that appears as a single BSS to the logical link control (LLC) layer at any station (STA) associated with one of those BSSs.”
We probably meant something about transparency of “location of attachment”/”mobility”, from whatever is using the MAC 802 Services
includes other entities, necessary to accomplish this? (EAP Auth Service? Bridges (11ak)? ANQP, etc?) ESS boundary == demarcation of this transparency?? Yes, + common domain of “mobility” that works, including security, policy, etc., necessary for mobility that actually works.
Is it:
Transparent to whatever upper layer is above ? No, boundary may be higher than that
Includes entities beyond (above?) ? (Like bridges in the 11ak scenario?) Yes, as needed
The APs have to have some common/similar configuration settings? (SSID, at least. Probably other facilities (security, etc.) and policies?) Yes.
Changes to Figure 4-1: ‘BSS’s are just STAs. These ovals are BSAs. Also, should we be saying “OBSA”?

26. What is an ESS? – Direction?
Straw proposal - ESS is: [Edit this list, per discussion]
Set of one of more basic services sets (BSSs)
Appears as a single logical network, to layers above the ESS boundary
The boundary might be above 802 (above Layer 2), or might be within Layer 2 (the MAC SAP, etc.)
The boundary must exist/be clear for participating end stations (see 802 O&A), and external devices that can interwork with the participating end stations
Provides transparency of “location of attachment” / “mobility”, as seen by layers above the ESS boundary, on both participating end stations and external end stations.
Includes all entities necessary to provide the services and transparency required.
Has a common domain of mobility and a common security and policies and configuration necessary to deliver the transparency from mobility.

27. Wednesday, July 12th, AM1

28. 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
Design Pattern for “*Implemented” and “*Activated” MIB attributes – Impacts of YANG/NETCONF decision?
Consider YANG/NETCONF
802.1ASrev use of FTM
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
Monitor/report on IETF/802 activities, as needed
Monitor/report on IEEE 1588 activities, as needed
If you have ANY other topic that you would like ARC SC to consider, contact the SC chair.

29. Planning for September 2017
Plan for three individual meeting slots
Usual slot on Wed AM1
Another slot for standalone ARC work (Monday/Tuesday?)
Another slot (Thursday’s slot)?
Plus Joint sessions: TGak? TGaq? 802.1? TGba
Individuals interested in ARC work are encouraged to also attend AANI SC sessions
Teleconferences:
Schedule discussion of TGba, try to get to a block diagram
Schedule discussion of MIB
Schedule with 10 days notice