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).”
Invitation from 802.19 Chair to 3GPP to present on LTE-LAA
Invitation from 802.19 Chair to 3GPP to present on LTE-LAA
P802.11ay (http://www.ieee802.org/11/PARs/P802.11ay.pdf) was approved at the March IEEE SASB meeting.
Approval of draft standards
None
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:
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
Leaders of 802.11 Task Groups, Study Groups and Standing Committees (or their nominee) should attend the Thursday CAC at 7:30pm.
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 advise and support the chair in his responsibilities as an EC member
There is a conflict between what the rules say and what I perceive to be our recent practice.
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
This is part of continuous process improvement – managing the WG effectively is the primary job responsibility of the WG chair.
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.
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 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.
The IEEE “RAC” is the registration authority for IEEE standards
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 flags and explanatory editors notes.
"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.)"
"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.)"
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.
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.
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 “” is not allowed in the published standard or amendment, it is a placeholder during development of the document only.
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 “” 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]
(From RAC IEEE-SA staff administrator)
(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.
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:
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
Next Full WG Session: July 12-17
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
Database is here
Database is here
5 requests for LoA pending**:
Qualcomm (802.11ah),
Broadcom (802.11ai),
Texas A&M University System (802.11n, .11ac, .11ad)
