March 2017 doc IEEE 802 11 170202 r

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 ARC-SC-agenda-March-2017 Date: 2017 -03 -14 Authors: Agenda Slide 1 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Abstract Agenda for: ARC SC, March 2017, Vancouver, British Columbia, Canada Agenda Slide 2 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 IEEE 802. 11 Architecture Standing Committee Agenda March 2017 session Chair: Mark Hamilton (Ruckus/Brocade) Vice Chair: Joe Levy (Inter. Digital) Agenda Slide 3 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Tuesday, March 14 th, PM 2 Agenda Slide 4 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Attendance, etc. • Reminders to attendees: – Sign in for. 11 attendance credit – Noises off – No recordings Agenda Slide 5 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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 Agenda Slide 6 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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 http: //standards. ieee. org/develop/policies/bylaws/sect 6 -7. html#6 IEEE-SA Standards Board Operations Manual http: //standards. ieee. org/develop/policies/opman/sect 6. html#6. 3 Material about the patent policy is available at http: //standards. ieee. org/about/sasb/patcom/materials. html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee. org or visit http: //standards. ieee. org/about/sasb/patcom/index. html This slide set is available at https: //development. standards. ieee. org/myproject/Public/mytools/mob/slideset. ppt Agenda Slide 7 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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 Agenda Slide 8 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Participation in IEEE 802 Meetings • All participation in IEEE 802 Working Group meetings is on an individual basis • • Participants in the IEEE standards development individual process shall act based on their qualifications and experience. (https: //standards. ieee. org/develop/policies/bylaws/sb_bylaws. pdf 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”. (http: //ieee 802. org/PNP/approved/IEEE_802_WG_Pand. P_v 19. pdf section 4. 2. 1) You have an obligation to act and vote as an individual and not under the direction of any other individual or group. Your obligation to act and vote as an individual applies in all cases, regardless of any external commitments, agreements, contracts, or orders. You 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 https: //standards. ieee. org/develop/policies/bylaws/sb_bylaws. pdf section 5. 2. 1. 3 and http: //ieee 802. org/PNP/approved/IEEE_802_WG_Pand. P_v 19. pdf section 3. 4. 1, 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. Agenda Slide 9 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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 5. 3. 10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Agenda Slide 10 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 ARC Agenda – March 2017 Tuesday, March 14, PM 2 • • Administrative: Minutes IEEE 1588 mapping to IEEE 802. 11 802 activities IETF/802 coordination TGak update MIB attributes Design Pattern - 11 -15/0355 r 4, 11 -17/0475 r 0 , 11 -09/0533 r 1 YANG/NETCONF modeling discussions – 11 -16/1436 r 1 “What is an ESS? ” Wednesday, March 15, AM 1 • • • MIB attributes Design Pattern (cont) AP/DS/Portal architecture and 802 and GLK concepts - 11 -17/0136 r 2, 11 -16/0720 r 0, 1115/0454 r 0, 11 -14/1213 r 1 (slides 9 -11) “What is an ESS? ” (cont) Thursday, March 16, AM 1 • • MIB attributes Design Pattern (cont) AP/DS/Portal architecture and 802 and GLK concepts (cont) “What is an ESS? ” (cont) Future sessions / SC activities Agenda Slide 11 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 ARC Minutes • January Minutes: https: //mentor. ieee. org/802. 11/dcn/17/11 -17 -0201 -000 arc-sc-meeting-minutes-january-2017. docx Agenda Slide 12 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 IEEE 1588 mapping to IEEE 802. 11 • Update (Mark Hamilton) Agenda Slide 13 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 IEEE 802 activities directly related to IEEE 802. 11 ARC • Update (Mark Hamilton) • 802. 1 Q revision underway, target Sept 2017. Roll-in: – – – IEEE Std 802. 1 Qcd-2015, IEEE Std 802. 1 Qca-2015, IEEE Std 802. 1 Q-2014 Cor 1 -2015, IEEE Std 802. 1 Qbv-2015, IEEE Std 802. 1 Qbu-2016, IEEE Std 802. 1 Qbz-2016 • 802. 1 AC-2016 published Agenda Slide 14 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 IETF/802 coordination • Dorothy Stanley present topics of interest: – Multicast traffic features of 802. 11 – status quo is stable – Other? • Last IETF meeting: 13 -18 Nov 2016. Next meeting: 26 -31 March • EC Standing Committee, next meeting: March plenary Agenda Slide 15 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 802. 11 General Links • Donald Eastlake present topics of interest from TGak and 802. 1’s parallel work (802. 1 Qbz-2016 published) • Any open issues/concerns? Agenda Slide 16 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Design Pattern for MIB attributes • The WG 11 Chair has requested that the ARC SC investigate and create a Design Pattern for MIB attributes of the form “*Implemented” and “*Activated” • Background: – https: //mentor. ieee. org/802. 11/dcn/14/11 -14 -1068 -00 -0 arc-mib-attributes-designpattern-background. docx – https: //mentor. ieee. org/802. 11/dcn/14/11 -14 -1281 -04 -0 arc-mib-attributesanalysis. docx • https: //mentor. ieee. org/802. 11/dcn/15/11 -15 -0355 -04 -0 arc-mibtruthvalue-usage-patterns. docx • https: //mentor. ieee. org/802. 11/dcn/17/11 -17 -0475 -00 -0 arc-mibpattern-analysis. xlsx Agenda Slide 17 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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: – https: //mentor. ieee. org/802. 11/dcn/16/11 -16 -1436 -00 -0 arc-yang-modelling-andnetconf-protocol-discussion. pptx • Session on Thurs PM 1 will have 802. 1 experts/interested individuals in attendance, to provide some background and perspective Agenda Slide 18 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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 802. 1 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 802. 11 MAC – and other entities, necessary to accomplish this? ESS == demarcation of this transparency? ? Is it: – Transparent to whatever upper layer is above 802. 11? – Includes entities beyond (above? ) 802. 11? (Like bridges in the 11 ak 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”? Agenda Slide 19 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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 802. 11 MAC 802 Services – includes other entities, necessary to accomplish this? (EAP Auth Service? Bridges (11 ak)? 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 802. 11? No, boundary may be higher than that – Includes entities beyond (above? ) 802. 11? (Like bridges in the 11 ak 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”? Agenda Slide 20 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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. Agenda Slide 21 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Wednesday, March 15 th, AM 1 Agenda Slide 22 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 AP/DS/Portal architecture and 802 concepts • Presentations on architectural description(s) – https: //mentor. ieee. org/802. 11/dcn/17/11 -17 -0136 -02 -0 arc-bridging-architectureconsiderations. docx • Reference presentations (previously reviewed, current status of thinking): Agenda – https: //mentor. ieee. org/802. 11/dcn/14/11 -14 -1213 -01 -0 arc-ap-arch-concepts-anddistribution-system-access. pptx – https: //mentor. ieee. org/802. 11/dcn/13/11 -13 -0115 -15 -0 arc-considerations-on-aparchitectural-models. doc – https: //mentor. ieee. org/802. 11/dcn/14/11 -14 -0497 -03 -0 arc-802 -11 -portal-and-8021 ac-convergence-function. pptx – https: //mentor. ieee. org/802. 11/dcn/14/11 -14 -0562 -05 -00 ak-802 -11 ak-and-802 -1 acconvergence-function. pptx – https: //mentor. ieee. org/802. 11/dcn/15/11 -15 -0454 -00 -0 arc-some-more-dsarchitecture-concepts. pptx – https: //mentor. ieee. org/802. 11/dcn/16/11 -16 -0720 -00 -0 arc-stacked-architecturediscussion. pptx Slide 23 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Thursday, March 16 th, AM 1 Agenda Slide 24 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 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 • Will also follow 802. 1/802. 11 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. Agenda Slide 25 Mark Hamilton, Ruckus/Brocade

March 2017 doc. : IEEE 802. 11 -17/0202 r 2 Planning for May 2017 • Plan for two individual meeting slots – – Usual slot on Wed AM 1 Another slot for standalone ARC work (Monday/Tuesday? ) Another slot (Thursday’s slot)? Joint sessions: TGak? TGaq? • Individuals interested in ARC work are encouraged to also attend other TGak sessions, and AANI SC sessions • Teleconferences: – None planned – May schedule with 10 days notice if discussion warrants Agenda Slide 26 Mark Hamilton, Ruckus/Brocade