1 / 8

IEEE 802 JTC1 SC closing report (July12)

IEEE 802 JTC1 SC closing report (July12). Authors:. Date: 2012-07-19. Abstract. Closing report for IEEE 802 JTC1 SC for July 2012 in San Diego. JTC1 SC focused on preparation for SC6 meeting in September. General update in San Diego Reviewed latest liaisons to SC6 of Sponsor Ballot drafts

wallis
Download Presentation

IEEE 802 JTC1 SC closing report (July12)

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. IEEE 802 JTC1 SC closing report (July12) Authors: Date: 2012-07-19 Andrew Myles, Cisco

  2. Abstract Closing report for IEEE 802 JTC1 SCfor July 2012 in San Diego Andrew Myles, Cisco

  3. JTC1 SC focused on preparation for SC6 meeting in September • General update in San Diego • Reviewed latest liaisons to SC6 of Sponsor Ballot drafts • 802.11ac D3.0 & 802.11ad D8.0 • Reviewed status of JTC1 ballot on IEEE 802.11-2012 • Opened 18 May, closes 18 Oct • Reviewed agenda for SC6 meeting in Sept • Recommended to EC that Bruce Kraemer be empowered as HoD • Reviewed status in SC6 of proposals of interest to IEEE 802 • Good news is that there is no news on WAPI, TePA-AC, UHT, … • Discussed Switzerland NB suggestions for SC6 process changes as a result of “WAPI experience” • May result in more IEEE 802 collaboration with SC6 Andrew Myles, Cisco

  4. JTC1 SC focused on preparation for SC6 meeting in September • General update in San Diego • Developed responses to questions from SC6 NBs related to proposed agreement on extensions to IEEE 802 standards • Overall goal is agreement that IEEE 802 will have responsibility for all maintenance of ISO/IEC 8802 standards • This is a prerequisite for 802.1/3 to be submitted for ratification by ISO/IEC • Documents for approval by EC (subject to editing) are • 11-12-767r4 – a response to the China NB • 11-12-768r4 – a response to the Switzerland NB • 11-12-769r2 – the proposed agreement between SC6 and IEEE 802 • Will be considered by EC this afternoon Andrew Myles, Cisco

  5. Proposed agreement with SC6: • Best practice indicates a single SDO should have responsibility for developing or maintaining a standard, albeit in cooperation with all relevant stakeholders. • IEEE 802 will have sole responsibility for maintaining, altering and extending all ISO/IEC 8802 standards adopted from IEEE 802. • An extension is defined as functionality that makes use of internal interfaces in an ISO/IEC 8802 standard (and the corresponding IEEE 802 standard); internal interfaces are designed solely for the use of IEEE 802 participants developing IEEE 802 standards within the context of approved IEEE 802 projects. • … 11-12-769r2 contains the “proposed agreement” text Andrew Myles, Cisco

  6. Proposed agreement with SC6: • … • SC6 may request clarification from IEEE 802 as to whether a particular interface in an ISO/IEC 8802 standard (and the corresponding IEEE 802 standard) is an internal interface. • SC6 may request that IEEE 802 develop new external interfaces in an ISO/IEC 8802 standard (and the corresponding IEEE 802 standard) required to enable SC6 to define additional functionality beyond the ISO/IEC 8802 standard. • IEEE 802 will continue to consult with SC6 during the IEEE 802 standards development process to ensure the development of standards that reflect the needs of a broad range of stakeholders. 11-12-769r2 contains the “proposed agreement” text Andrew Myles, Cisco

  7. The proposed “agreement” document is between SC6 and IEEE 802 It is doubtful that either group have the legal authority to sign such a document Instead, it is envisaged that both groups will pass motions approving the agreement This of course leaves open the risk that either group will reneg in the future The only thing stopping this is the “moral imperative” Is that enough comfort for 802.1 WG and 802.3 WG? It is likely that the “proposed agreement” will not be a signed legal document Andrew Myles, Cisco

  8. JTC1 SC will not meet in Indian Wells in September 2012 • Plans for Indian Wells (Sept 2012) • No meeting because clashes with SC6 meeting in Graz, Austria • Plans for San Antonio (Nov 2012) • Report on SC6 meeting in Sept • Review results of JTC1 ballot on IEEE 802.11-2012 Andrew Myles, Cisco

More Related