Minutes of Meeting Ontue-Wedpm1, 18-19Mar 2014

Minutes of Meeting Ontue-Wedpm1, 18-19Mar 2014

Mar 2014doc.: IEEE 802.11-14/0xxxr0

IEEE P802.11
Wireless LANs

Minutes of IEEE 802 JTC1 Standing Committee
in Beijing, USA
in March 2014
Date: 20150507
Author(s):
Name / Affiliation / email
Andrew Myles / Cisco /

Minutes of Meeting onTue-WedPM1, 18-19Mar 2014

Agenda

  • The standing committee agenda is found in 11-14/0228r0 (updated to 11-14/0228r1).\
  • The agenda was approved by unanimous consent.
  • Paul Nikolich (multiple affiliations) made the necessary motion, while Bruce Kraemer (Marvell Semiconductor) seconded the motion.

Minutes

  • Minutes of the Los Angeles meeting (11-14/0208r0) were approved without dissent.
  • Bruce Kraemer offered the motion; Donald Eastlake (Huawei) seconded it.

Goals

  • Andrew Myles (SC chair, Cisco) reviewed, for the nth time, the goals of the standing committee.
  • The status of the JTC1 SC within IEEE 802 has been rectified as of this Monday, so that it is now formally a standing committee of IEEE 802, not IEEE 802.11.

SC6 meeting summary

  • A large part of the agenda is dedicated to reporting on the outcome of last month’s ISO/IEC JTC1/SC6/WG1 meeting in Ottawa.
  • There were 7 of 19 member national bodies represented: USA, China, Switzerland, South Korea, Canada, United Kingdom, and Austria.
  • The meeting agenda was not particularly packed, reflective of few items before WG1 that were of interest to more than 2 national bodies.
  • The current plan of work between now and the next meeting are mostly Korean proposals that don’t appear to have a lot of traction.
  • Proposals from the China NB (via representatives from IWNCOMM) for TePA-related standards remain possible, but are not currently on the docket.
  • As the agenda was so light, the US NB proposed replacing the next WG1 meeting with a teleconference, but that proposal was not adopted.
  • Less strongly worded proposals from the US and Swiss NBs for more use of teleconferences within WG1 were then accepted, but these proposals were shot down at the SC6 level.

IEEE 802 activities in SC6

  • The IEEE 802 delegation briefed the status of various IEEE 802 activities to WG1.
  • No new draft documents have been liaised to WG1 since the last IEEE 802 interim meeting in January.
  • IEEE 802.1’s plan for which draft specifications to submit to WG1 needs to be reviewed to determine what, if any, documents are now ready to be liaised to WG1.
  • There’s some question within the SC as to whether the IEEE 802 O&A document that is currently under sponsor ballot should be liaised now or upon its ratification by IEEE 802.
  • Glen Parsons (Ericsson, IEEE 802.1 vice chair) will consider the matter and update the SC during the Wednesday time slot.
  • Parsons will verify the statuses of IEEE 802.1Xbx and 802.1Q to see if they have moved on.
  • Geoff Thompson noted that IEEE 802.3-2012 had been liaised to SC6 and was approved without comment.
  • IEEE 802.3 has a major update to IEEE 802.3 in the pipeline.
  • IEEE 802.3 seems likely to only send major rollups to SC6 under the PSDO rather than individual amendments.
  • IEEE 802.15 has submitted an IEEE 802.15.4 draft to SC31 (at their request).
  • Jodi Haasz (IEEE staff) is going to have a discussion with Henry Couchieri (ISO staff) to move the liaison to SC6.
  • Andrew Myles will check with Bob Heile (ZigBee Alliance) on IEEE 802.15’s plan for future submissions to SC6.
  • IEEE 802.22 has agreed to submit to their specification under the PSDO
  • IEEE 802 itself has notified SC6 of newly started projects.

Status of IEEE 802 standards in SC6

  • IEEE 802 has pushed IEEE 802.11, IEEE 802.1X, IEEE 802.1AE, and IEEE 802.3 through the PSDO ratification process.
  • Nine other standards/amendments remain in the ratification process under the PSDO. IEEE 802.22 is the latest document to be sent and will close its 60-day pre-ballot in May.
  • Some of the documents have completed their 5-month FDIS ballots and now require comment resolution.
  • IEEE 802.1AB passed its FDIS ballot, collecting ballot comments from Switzerland and China.
  • China actually cast the sole vote against approval during the FDIS ballot.
  • IEEE 802.1AS also passed with a similar result.
  • IEEE 802.11ae passed with a ‘no’ vote from the China NB, which reserved the right not recognize the result of the ballot.
  • IEEE 802.11aa is in the same boat.
  • IEEE 802.3 passed with comments.
  • Geoff Thompson raised the point that the title of IEEE 802.3 has changed since the last time that SC6 ratified it.
  • Jodi Haasz will send out a PDF of the proposed ISO/IEC cover page for the specification to make sure that it reads correctly.
  • IEEE 802.1AEbw passed with a negative vote from China, which again refused to recognize the result.
  • IEEE 802.1AEbn also has the same status.

Comments in PSDO

  • The Swiss and Chinese NBs have been complaining in ballot comments that IEEE 802 standards refer to Proposed and Informational RFCs.
  • They want to see references that are only to full, standards-track RFCs.
  • This would seem to be an inconsistent position given that ISO/IEC itself has made such references, both to IETF RFCs and to ISO/IEC draft specifications.
  • Despite that, a strong argument in favor of IEEE 802 standards referencing IETF RFCs of any type is that IEEE standards are developed under IEEE rules, not ISO/IEC rules.
  • China’s refusal to recognize the ratification of some of the IEEE standards is probably moot, whether they have standing to do so.
  • Market forces may very well overcome China’s position even if it’s not entirely clear that China had the right to refuse cognizance of an approved ISO/IEC standard.
  • Jodi Haasz will check on if and how IEEE and ISO might respond to the Chinese refusal.
  • In the meantime, IEEE 802 has generated responses to all technical comments submitted on the ballots for IEEE 802.11aa, IEEE 802.11ad, and IEEE 802.11ae.
  • Myles briefed those responses, which mainly deal with the submitted comments regarding IEEE use of IETF Informational and Proposed standard references.
  • Donald Eastlake pointed out IETF RFC 7127, which clarifies the characterization of IETF Proposed Standards

Submissionpage 1Andrew Myles (Cisco)