1 / 27

Supplementary Materials for May 2015 802.11 Plenary Meetings

This report provides supplementary materials related to the May 2015 802.11 plenary meetings, including liaisons, joint meetings, and decisions made.

troia
Download Presentation

Supplementary Materials for May 2015 802.11 Plenary Meetings

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. May 2015 802.11 SessionSupplementary Material Authors: Date: 2015-05-10 Adrian Stephens, Intel Corporation

  2. This report provides supplementary material related to attending the May 2015 802.11 plenary meetings. • Refer to the agenda: 11-15/482r<latest> Introduction Adrian Stephens, Intel Corporation

  3. Monday Adrian Stephens, Intel Corporation

  4. Ongoing • NGMN Liaison and Whitepaper - Owned by REG SC • Liaison from 3GPP (March 2015), Regarding Coexistence of Licensed Assisted Access (LAA) and IEEE 802 – Owned by REG SC • Liaison from 3GPP, Regarding Study on LTE Support for V2X Services • “3GPP TSG SA would like to inform ETSI ITS, US SAE, US ITSA, Korean Ministry of Land, Infrastructure and Transport, GSMA Connected Living and IEEE that V2X study has been started in SA WG1 to identify use cases and requirements for LTE V2X (V2V, V2I, and V2P).” M2.3.1 Summary of new and ongoing Liaisons and Status Adrian Stephens, Intel Corporation

  5. Invitation from 802.19 Chair to 3GPP to present on LTE-LAA Havish Koorapaty (Ericsson), from 3GPP, will be coming to give a presentation on this topic The timeslot is Tuesday pm2 in Georgia B (2nd Floor). Room will hold 50. M2.3.1 – Liaison in person from 3GPP in 802.19 Adrian Stephens, Intel Corporation

  6. Joint Meetings • Thu am1: TGak, 802.1Qbz, 802.1AC, and ARC • Reciprocal credit is provided to 802.11 voters for attendance at: 802.18, 802.19, 802.24, 802.1 and Privacy ECSG • Reciprocal credit for 802.19 is for Coexistence in Unlicensed Bands Study Group • Reciprocal credit for 802.1 is for 801.1Qbz, 802.1CF and 802c (Local MAC address) Study Group M3.2 Joint meetings and Reciprocal Credit Adrian Stephens, Intel Corporation

  7. Response from the IEEE-SA Standards Board on request sent by WG related to 802.11ah Edgar Figueroa, CEO of the Wi-Fi Alliance will address us Discussion on how TG chairs should be determined Information on Email exchange with the RAC on ANA M3.10 Topics for Wednesday plenary Adrian Stephens, Intel Corporation

  8. PARS • P802.11ay (http://www.ieee802.org/11/PARs/P802.11ay.pdf) was approved at the March IEEE SASB meeting. • Approval of draft standards • None M3.11 802 EC and IEEE-SA Standards Board decisions Adrian Stephens, Intel Corporation

  9. Wednesday Adrian Stephens, Intel Corporation

  10. 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 W2.2 Call for Potentially Essential Patents Adrian Stephens, Intel Corporation

  11. Leaders of 802.11 Task Groups, Study Groups and Standing Committees (or their nominee) should attend the Thursday CAC at 7:30pm. • The purpose of the CAC is: • To prepare the agenda and material for the closing WG plenary • To create room requests for the next session • To advise and support the chair in his responsibilities as an EC member W2.3 – Thursday CAC reminder Adrian Stephens, Intel Corporation

  12. There is a conflict between what the rules say and what I perceive to be our recent practice. • The 802 WG P&P states: “7.3 Subgroups of the WG The WG may, from time to time, form subgroups for the conduct of its business. … The WG Chair shall appoint the chair of the subgroup. “ • The 802.11 OM states: “4.2 Task Group Chair The TG Chair shall be appointed by the WG Chair and confirmed by a WG majority approval. The TG Chair is re-affirmed every 2 years: one session after the WG Chair is elected.” • What we actually do: Each TG holds an election, and the WG affirms the TG’s choice W5.2 – How the TG chair should be determined Adrian Stephens, Intel Corporation

  13. This is part of continuous process improvement – managing the WG effectively is the primary job responsibility of the WG chair. I have consulted with other WG chairs, the 802.11 officers and the CAC to determine what is best practice and how we should respond. I will in future ask TGs to produce a recommendation for TG chair, and will share the qualifications I am looking for with the TG. Why change anything / what will change? Adrian Stephens, Intel Corporation

  14. The prospective TG chair should indicate that their employer will support their attendance at all 802.11 sessions, and that they will normally be present to run TG meetings at those sessions. • The main qualification sought is demonstrated competency in a job carrying a management responsibility in 802.11; such as: Task or study group chair or vice chair, ad-hoc chair • Note, we are looking for a manager, not a leader. TG chair qualifications Adrian Stephens, Intel Corporation

  15. The IEEE “RAC” is the registration authority for IEEE standards They coordinate use of resources created in IEEE standards They are a significant source of income for IEEE-SA The following was an enquiry from the RAC on entry of P802.11 (Revision MC) to sponsor ballot, prompted by the existence of <ANA> flags and explanatory editors notes. W5.3 – Exchange with IEEE RAC Adrian Stephens, Intel Corporation

  16. "IEEE Std 802.11, front matter, p. v, Participants — Per IEEE-SA rules, the Registration Authority has right of first refusal for all registration activities.  Please explain why the WG has (or had) an Assigned Number Authority, and what numbers that authority was administering, and why those numbers are not appropriate as an IEEE RA registry.  (Other standards have code points in various protocols that they specify (and reserve for future specification) without objection of the RAC, so this is just a request for additional information.  (That title for a WG responsibility acted as a red flag.)" W5.3 – Email from RAC 2015-04-28 Adrian Stephens, Intel Corporation

  17. The 802.11 ANA is an organizational convenience for 802.11 standards.  We have had times when there were 6 simultaneous amendments all amending the same table specifying things like Element IDs.   We needed a mechanism to take control of this situation.  We have done that by creating a database identifying controlled resources (those likely to be updated by more than one amendment at a time).   A controlled resource can only be used by requesting assignment from the 802.11 ANA.  We have a review process that checks that an amendment uses only numbers assigned to it from the 802.11 ANA.  W5.3 – Reply from WG chair 2015-04-28 Adrian Stephens, Intel Corporation

  18. Notwithstanding this,  it is the published standard or amendment that is definitive.  For example,  we had an amendment that published an value of a controlled resource that had not been assigned to it,  and we therefore had to shuffle up previously assigned resources in in-development amendments to make room for it. The flag “<ANA>” is not allowed in the published standard or amendment,  it is a placeholder during development of the document only.  There have been two exceptions to the “internal to 802.11” purpose.   Firstly,  we record the use of controlled resources by third parties without the consent of 802.11 in order to avoid collision.  Examples are various manufacturers,  and the Chinese in their WAPI protocol.  Secondly,  we have allocated a number to 802.15 because they have chosen to adopt a ciphersuite identifier table from 802.11,  but wanted to make an addition of their own.  [snip] W5.3 – Reply from WG chair 2015-04-28 - II Adrian Stephens, Intel Corporation

  19. (From RAC IEEE-SA staff administrator) I have received confirmation from Bob Grow that he is satisfied with your response and that the RAC has no problems with the WG defining and reserving unused protocol code points, handling management arcs under their assignments, and defining appropriate for them structures for coordination between multiple projects.  The RAC years ago passed on managing 802.3 selector field values used in Ethernet auto negotiation even though they were being allocated to other standards (and even in one case appropriated).  The cyber suite number seems to be similarly acceptable for WG management, even if it bridges a few standards.  If the RAC can be of assistance in management of any of the external number issues, we are available to help, but see no reason why this would be a registry issue of concern to the IEEE-SA BOG. W5.3 – Response from RAC 2015-04-29 Adrian Stephens, Intel Corporation

  20. friday Adrian Stephens, Intel Corporation

  21. 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 F2.2 Call for Potentially Essential Patents Adrian Stephens, Intel Corporation

  22. Next Full WG Session: July 12-17 • 1st CAC telecon – June 8th at noon ET (-5 weeks) • Initial objectives/agendas should be uploaded as mentor documents (.ppt format) or send to chair (.xls tab format) before the telecon. • Meeting date set to meet 30-day agenda submission deadline. • 2nd CAC telecon – June 29th at noon ET (-2 weeks) • Snapshots to be send to Dorothy Stanley before this telecon. • This meeting is being held a week early to avoid clash with USA holday F2.4 Administrative Reminders Adrian Stephens, Intel Corporation

  23. F2.5 Letters of Assurance Database is here • 5 requests for LoA pending**: • Qualcomm (802.11ah), • Broadcom (802.11ai), • Texas A&M University System (802.11n, .11ac, .11ad) • Intel Corporation (REVmc) • Key: New this session Data as of 2015-03-12 ** i.e. Chair has not received a substantive response Adrian Stephens, Intel Corporation

  24. F2.6 Availability of documents- Jan 2015 Last updated: 2014-10 Adrian Stephens, Intel Corporation

  25. Drafts are sent to ISO during sponsor ballot to solicit comments. Approved drafts may also be sent during working group ballot. Any comments received from ISO are processed by the comment resolution committee No comments outstanding F2.7 802.11 drafts to ISO/IEC JTC1/SC6 Adrian Stephens, Intel Corporation

  26. The wireless chairs meeting makes decisions related to the operation of the wireless interim meetings, such as location and cost. The meeting is open to all. If you are interested in these topics, please attend. The wireless chairs meeting takes place at 4:00pm local time on the Sunday of 802 Plenary and 802 Wireless Interim sessions. F7.1 802 Wireless Chairs meeting Adrian Stephens, Intel Corporation

  27. July 12-17, Hilton Waikoloa, HI, USA • IEEE 802 Plenary • All 802.11 groups meeting • Will include a our 25thanniversary celebration • Meeting Registration and Hotel Registration are Open For information and registration links, see http://www.ieee802.org/11/Meetings/Meeting_Plan.html F7.2 Next Meeting – 802 Plenary Adrian Stephens, Intel Corporation

More Related