1 / 27

ARC-SC-agenda-January-2017

ARC-SC-agenda-January-2017. Authors:. Date: 2017-01-17. Abstract. Agenda for: ARC SC, January 2017, Atlanta, Georgia, USA. IEEE 802.11 Architecture Standing Committee. Agenda January 2017 session Chair: Mark Hamilton (Ruckus/Brocade) Vice Chair: Joe Levy ( InterDigital ).

angus
Download Presentation

ARC-SC-agenda-January-2017

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ARC-SC-agenda-January-2017 Authors: Date: 2017-01-17

  2. Abstract Agenda for: ARC SC, January 2017, Atlanta, Georgia, USA

  3. IEEE 802.11 Architecture Standing Committee Agenda January 2017 session Chair: Mark Hamilton (Ruckus/Brocade) Vice Chair: Joe Levy (InterDigital)

  4. Wednesday, January 18th, AM1

  5. Attendance, etc. • Reminders to attendees: • Sign in for .11 attendance credit • Noises off • No recordings

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

  7. 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/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/develop/policies/opman/sect6.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

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

  9. 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://ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.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://ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.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.

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

  11. ARC Agenda – January 2017 Wednesday, January 18, AM1 • Administrative: Minutes • IEEE 1588 mapping to IEEE 802.11 • 802 activities • IETF/802 coordination • TGak update • MIB attributes Design Pattern - 11-15/0355r4 • YANG/NETCONF modeling discussions – 11-16/1436r1 • AP/DS/Portal architecture and 802 and GLK concepts - 11-17/0136r0, 11-16/0720r0, 11-16/0457r1,11-15/0454r0, 11-14/1213r1 (slides 9-11) Wednesday, January 18, PM1 • MIB attributes Design Pattern (cont) • YANG/NETCONF modeling discussions (cont) • Future sessions / SC activities • “What is an ESS?” Joint session with TGak, Thursday, January 19, AM1 Session with 802.1 YANG experts, Thursday, January 19 PM1

  12. ARC Minutes November Minutes: https://mentor.ieee.org/802.11/dcn/16/11-16-1594-00-0arc-arc-sc-meeting-minutes-november-2016.docx

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

  14. IEEE 802 activities directly related to IEEE 802.11 ARC • Update (Mark Hamilton) • 802.1Q revision under consideration. Roll-in: • IEEE Std Qcd-2015, • IEEE Std 802.1Qca-2015, • IEEE Std 802.1Q-2014 Cor 1-2015, • IEEE Std 802.1Qbv-2015, • IEEE Std 802.1 Qbu-2016, • IEEE Std 802.1Qbz-2016 • 802.1AC published? (TBC) • 802.11’s “up-down” view of “baggy pants” diagram: 11-17/0136r0, 11-16/1512r0

  15. IETF/802 coordination • Dorothy Stanley present topics of interest: • Multicast traffic features of 802.11 • From Dorothy’s IETF liaison report, Nov-2016 (11-16/1315r1): • See https://mentor.ieee.org/802.11/dcn/15/11-15-1261-02-0arc-mulicast-performance-optimization-features-overview-for-ietf-nov-2015.ppt • Further actions: ietf mailing list has been established for ongoing discussion, will include additional 802. wireless groups, see http://www.ieee802.org/11/email/stds-802-11/msg01838.html • Multicast considerations Internet draft describing use cases, issues, etc. under development, see https://tools.ietf.org/html/draft-perkins-intarea-multicast-ieee802-01 • Any update, or further action needed? • IPv6 and IoT may add additional pressure: RFC 6775, Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) defines a registration mechanism for accomplishing proxy ND: IoT and other applications motivating registration over discovery • Other? • Last IETF meeting: 13-18 Nov 2016. Next meeting: 26-31 March • EC Standing Committee, next meeting: March plenary • Updates of 802.11/.15 IETF Tutorial underway, joint work of Dorothy and Charlie: 11-16/0500r1

  16. 802.11 General Links • Donald Eastlake present topics of interest from TGak and 802.1’s parallel work (802.1Qbz) • Topics for joint session on Thursday • 11-17/0136r0

  17. 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: • https://mentor.ieee.org/802.11/dcn/14/11-14-1068-00-0arc-mib-attributes-design-pattern-background.docx • https://mentor.ieee.org/802.11/dcn/14/11-14-1281-04-0arc-mib-attributes-analysis.docx • https://mentor.ieee.org/802.11/dcn/15/11-15-0355-04-0arc-mib-truthvalue-usage-patterns.docx

  18. 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-0arc-yang-modelling-and-netconf-protocol-discussion.pptx • Session on Thurs PM1 will have 802.1 experts/interested individuals in attendance, to provide some background and perspective

  19. Wednesday, January 18th, PM1

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

  21. Planning for March 2017 • Plan for two individual meeting slots • Usual slot on Wed AM1 • Another slot for standalone ARC work (Monday/Tuesday?) • Another slot joint with 802.11ak (Thursday’s slot)? • Another slot (joint with 802.1?) on YANG/NETCONF? • Individuals interested in ARC work are encouraged to also attend other TGak sessions, and AANI SC sessions • Teleconferences: • May schedule with 10 days notice if discussion warrants

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

  23. 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 (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 802.11? No, boundary may be higher than that • Includes entities beyond (above?) 802.11? (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”?

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

  25. AP/DS/Portal architecture and 802 concepts • Presentations on architectural description(s) • https://mentor.ieee.org/802.11/dcn/16/11-16-0457-01-0arc-802-11ak-802-1ac-stas-aps-dses-and-convergence-functions.pptx • https://mentor.ieee.org/802.11/dcn/16/11-16-0720-00-0arc-stacked-architecture-discussion.pptx • Reference presentations (previously reviewed, current status of thinking): • https://mentor.ieee.org/802.11/dcn/14/11-14-1213-01-0arc-ap-arch-concepts-and-distribution-system-access.pptx • https://mentor.ieee.org/802.11/dcn/13/11-13-0115-15-0arc-considerations-on-ap-architectural-models.doc • https://mentor.ieee.org/802.11/dcn/14/11-14-0497-03-0arc-802-11-portal-and-802-1ac-convergence-function.pptx • https://mentor.ieee.org/802.11/dcn/14/11-14-0562-05-00ak-802-11ak-and-802-1ac-convergence-function.pptx • https://mentor.ieee.org/802.11/dcn/15/11-15-0454-00-0arc-some-more-ds-architecture-concepts.pptx

  26. Thursday, January 19th, AM1 • Joint session with Tgak • Review of “up-down” view of “baggy pants” diagram (TBC) • See TGak for detailed agenda

  27. Thursday, January 19th, PM1 • Session with 802.1 experts • Discussion of YANG/NETCONF • Look at 11-16/1436 • Pro/Con considerations – Cost/Benefit? • Tools? (including “mapping” tools?) • Replace MIB or not? • How do you manage the transition? • Github publication, or published document? • Examples of real-world use? • Separate project, or in REVmd?

More Related