1 / 25

ARC-SC-agenda-Mar-2016

ARC-SC-agenda-Mar-2016. Authors:. Date: 2016-03-16. Abstract. Agenda for: ARC SC, March 2016, Macau SAR, China. IEEE 802.11 Architecture Standing Committee. Agenda March 2016 session Chair: Mark Hamilton (Ruckus Wireless). Monday, March 14 th , PM2. Attendance, etc.

kgoebel
Download Presentation

ARC-SC-agenda-Mar-2016

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-Mar-2016 Authors: Date: 2016-03-16

  2. Abstract Agenda for: ARC SC, March 2016, Macau SAR, China

  3. IEEE 802.11 Architecture Standing Committee Agenda March 2016 session Chair: Mark Hamilton (Ruckus Wireless)

  4. Monday, March 14th, PM2

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

  10. ARC Agenda – March 2016 Monday, Mar 14, PM2 • Administrative: Minutes • 802.11 as a component in a (larger) system/5G/IMT-2020:11-15/0757r1, 11-15/0593r2, 11-15/0842r1, 11-15/1133r0, 11-15/1266r1, 11-15/1376r2 Wednesday, Mar 16, AM1 • TGaqarchitecture discussion update • 802.11 as a component in a (larger) system/5G/IMT-2020:11-15/0757r1, 11-15/0593r2, 11-15/0842r1, 11-15/1133r0, 11-15/1266r1, 11-15/1376r2 Wednesday, Mar 16, PM1 • Updates, no action expected: IEEE 1588 mapping to IEEE 802.11 • IETF/802 coordination: update on multicast over 802.11: 11-15/1261r2 • 802.1AC status update • AP/DS/Portal architecture and 802 concepts -11-15/0454r0, 11-14/1213r1 (slides 9-11) • MIB attributes Design Pattern - 11-15/0355r3, 11-15/0891r0 • Future sessions / SC activities Joint session with TGak and 802.1, Thursday, Mar 17, AM1

  11. ARC Minutes January Minutes: https://mentor.ieee.org/802.11/dcn/16/11-16-0157-00-0arc-arc-sc-and-joint-meetings-minutes-january-2016.docx

  12. 802.11 as a “component” } Are these all aligned, in reality? Is 802.11 usable as a component in a (larger?) system, or should it be: • “It should be possible to swap implementations of the component from different sources provided those implementations are compliant to the defined functions and external interfaces.” • How to capture data/control/management models, so 802.11 is usable as a component • What is the goal/who is the customer, for this effort? • Start with requirements… Analyze current situation, gap… Then go! • 802.11 as a “generic” component • 802.11 as a 3GPP component • 802/802.11 as a RIT/SRIT in IMT-2020 • Process/organization/structure discussions • Management of an ESS (as a ‘black box’)? • Especially incorporation of a locally managed ESS into a larger 5G system (management of quality, and timeliness; and tested)

  13. 802.11 as a “component” discussion • Broad use cases potentially, and/or focus on 3GPP/5G/IMT-2020 • Relate to IEEE-SA work on ‘IEEE role in 5G’ • Relate to IEEE ComSoc work on ‘IEEE role in 5G’ • 802 EC has kicked off a Standing Committee to discuss • If 802 doesn’t do a (joint) submission, 802.11 could independently • Discussion of Joe Levy’s brainstorming presentation (11-16/376)

  14. Wednesday, March 16th, AM1

  15. Wednesday, March 16th, PM1

  16. IEEE 1588 mapping to IEEE 802.11 • Update (?)

  17. IETF/802 coordination • Dorothy Stanley present topics of interest: • Multicast traffic features of 802.11 • Any update, or further action needed? – none • Draft will be made available, for March 2016 at the earliest • CAPWAP • Draft for 802.11n has expired • Draft alternate tunnel - is unchanged and active. • No actions requested at this time • Other? • Next meeting IETF 3-8 April 2016 • Request to update 802.11/.15 IETF Tutorial and projects underway and work of joint interests – Dorothy and Charlie will be generating the document. - Will ask for ARC feedback/review for March meeting

  18. 802.1AC revision • Current Status: • There hasn't been a new ballot. • Waiting on the RAC to approve the Ethertype. • Current ballot status: rejected for the second time.  • Presentations for discussion (to be updated, if/as presentations come in): • None

  19. AP/DS/Portal architecture and 802 concepts • Presentations on architectural description(s) • None? • 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

  20. 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” 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-03-0arc-mib-truthvalue-usage-patterns.docx https://mentor.ieee.org/802.11/dcn/15/11-15-0891-00-0arc-delta-r2r3-of-mib-truthvalue-usage-patterns.docx

  21. 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-15-0454-00-0arc-some-more-ds-architecture-concepts.pptx

  22. 802.11aq (PAD) • Any updates, or further collaboration suggested?

  23. 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 • How to capture data/control/management models, so 802.11 is usable as a component; consider standardized mgmt. accesses • Participate in 5G/IMT-2020 activities • Design Pattern for “*Implemented” and “*Activated” MIB attributes • Will also follow 802.1/802.11 activities on links, bridging, and MAC Service definition, Comment on 802.1AC revision project changes/proposals • 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.

  24. Planning for May 2016 • 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) • Individuals interested in ARC work are encouraged to also attend other TGak or TGaq sessions, and monitor 5G/IMT-2020 activities • No teleconferences – will schedule with 10 days notice if an 802.1 ballot happens that needs a response/discussion

  25. Thursday, March 17th, AM1 • Joint session with TGak, 802.1 • See TGak for detailed agenda

More Related