JTC1 Ad Hoc January 2012 agenda

JTC1 Ad Hoc January 2012 agenda
July 2010 doc.: IEEE /0xxxr0 JTC1 Ad Hoc January 2012 agenda 16 January 2102 Authors: Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 This presentation will be used to run the JTC1 Ad Hoc meetings in Jacksonville in Jan 2012 This presentation contains a proposed running order for the IEEE JTC1 Ad Hoc committee meeting in January 2011, including Proposed agenda Other supporting material It will be modified during the meeting to include motions, straw polls and other material referred to during the meeting Andrew Myles, Cisco Andrew Myles, Cisco

Participants have a duty to inform in relation to patents
July 2010 doc.: IEEE /0xxxr0 Participants have a duty to inform in relation to patents All participants in this meeting have certain obligations under the IEEE-SA Patent Policy (IEEE-SA SB Bylaws subclause 6.2). Participants: “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 “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such 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; there is no duty to perform a patent search Andrew Myles, Cisco Andrew Myles, Cisco

There are a variety of patent related links
July 2010 doc.: IEEE /0xxxr0 There are a variety of 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 IEEE-SA Standards Board Operations Manual Material about the patent policy is available at If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit This slide set is available at Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 A call for potentially essential patents is not required in the JTC1 Ad Hoc 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 Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The JTC1 Ad Hoc will operate using general guidelines for IEEE-SA 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 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Andrew Myles, Cisco Andrew Myles, Cisco

Links are available to a variety of other useful resources
July 2010 doc.: IEEE /0xxxr0 Links are available to a variety of other useful resources Link to IEEE Disclosure of Affiliation Links to IEEE Antitrust Guidelines Link to IEEE Code of Ethics Link to IEEE Patent Policy Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The JTC1 Ad Hoc will operate using accepted principles of meeting etiquette IEEE 802 is a world-wide professional technical organization Meetings are to be conducted in an orderly and professional manner in accordance with the policies and procedures governed by the organization. Individuals are to address the “technical” content of the subject under consideration and refrain from making “personal” comments to or about the presenter. Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 Ad Hoc has three slots at the Jacksonville meeting
July 2010 doc.: IEEE /0xxxr0 The JTC1 Ad Hoc has three slots at the Jacksonville meeting Tuesday PM1 Wednesday PM1 Thursday PM1 Call to Order Select recording secretary <- important! Approve agenda Details on next page Conduct meeting according to agenda Recess Call to Order Select recording secretary <- important! Conduct meeting according to agenda Recess Call to Order Select recording secretary <- important! Conduct meeting according to agenda Adjourn Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 Ad Hoc has a detailed list of agenda items to be considered
July 2010 doc.: IEEE /0xxxr0 The JTC1 Ad Hoc has a detailed list of agenda items to be considered Approve minutes from November in Atlanta Review extended goals Review liaisons to SC6 Review status of WAPI in SC6 (802.11i replacement) Review status of 802.1X/AE and security replacements Review status of N-UHT (802.11ac replacement) Discuss IPSec replacement proposal Discuss proposing ISO/IEC ratifications of Review plan for renewal of ISO/IEC 8802 standards Discuss SC6 “best practices” Consider any motions Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 Ad Hoc will consider approving its agenda
July 2010 doc.: IEEE /0xxxr0 The JTC1 Ad Hoc will consider approving its agenda Motion to approve agenda The JTC1 Ad Hoc approves the agenda for its meeting in Jacksonville in January 2012, as documented on pages 9-10 of <this slide deck> Moved: Seconded Result Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 Ad Hoc will consider approval of previous minutes
July 2010 doc.: IEEE /0xxxr0 The JTC1 Ad Hoc will consider approval of previous minutes Motion to approve minutes The JTC1 Ad Hoc approves the minutes for its meeting in Atlanta in Nov 2011, as documented in Moved: Seconded: Result: Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The JTC1 Ad Hoc reaffirmed its general goals in Sept 09, but they were extended in Nov 2010 Agreed (with changes from Nov 2010) goals Provides a forum for 802 members to discuss issues relevant to both: IEEE 802 ISO/IEC JTC1/SC6 Recommends positions to ExCom on ISO/IEC JTC1/SC6 actions affecting IEEE 802 Note that 802 LMSC holds the liaison to SC6, not WG Participates in dialog with IEEE staff and 802 ExCom on issues concerning IEEE ’s relationship with ISO/IEC Organises IEEE 802 members to contribute to liaisons and other documents relevant to the ISO/IEC JTC1/SC6 members Extensions The extensions to our goals came out of the 802 ExCom ad hoc held in November 2010 on the Friday evening Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 ISO/IEC JTC1/SC6 met in San Diego in June 2011 and will meet in Guangzhou, China in Feb 2012 SC6 has a F2F meeting every 9 months or so The last meeting was held on June 2011 in San Diego All WGs met in San Diego WG1: Physical and data link layers WG7: Network and transport layers (also known as Future Network) WG8: Directory WG9: ASN.1 and registration The next meeting is in Guangzhou, China in February 2012 Now confirmed for week of 20 Feb 2012, which is the same week as the Wi-Fi Alliance meeting in Vienna Only two WGs are planning to meet WG7: Network and transport layers Andrew Myles, Cisco Andrew Myles, Cisco

IEEE 802 empowered Bruce Kraemer as HoD for the SC6 meeting in February 2012
In November 2011 in Atlanta, Bruce Kraemer was appointed as HoD to the SC6 meeting in Feb 2012 and was authorised to: Appoint the IEEE 802 delegation Approve any necessary submissions Call any necessary preparation teleconferences Possible delegates include: Bruce Kraemer (HoD) Jodi Haaz (IEEE staff) Who? (WAPI) Who? (802.11ac) Who? (802.1X/AE) The actual delegation will depend on what is on the final agenda Andrew Myles, Cisco

The agenda for the Guangzhou, China meeting has not yet been published
IEEE 802 and the National Bodies were required to submit agenda items by 10 Jan 2012 The SC6 secretariat has not yet published a detailed agenda, although there is a draft agenda Likely/possible items of interest to IEEE 802 include: 8802 standards SC6 best practice document WAPI 802.1X/AE replacement 802.11ac replacement ... Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The WG has liaised various Sponsor Ballot drafts to ISO/IEC JTC1/SC6 Task Group After Hawaii After Dallas After LA Sing. After Palm Sp After SanFran After Okinawa After Atlanta Sept 10 Nov 10 Jan 11 Mar 11 May 11 July 11 Sept 11 Nov 11 TGae - D5.0 D7.0 TGaa D6.0 TGac TGmb D8.0 D10.0 D12.0 TGs Ratified TGu D13.0 TGv D15.0 TGz The latest set of documents were liaised on 24 Nov 2011 The WG has told SC6 it will liaise ac as soon as it passes a LB Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 It was recognised by the ad hoc in September 2009 that WAPI is of vital interest to the JTC1 Ad Hoc It was agreed by the JTC1 ad hoc in Hawaii in Sept 09 that WAPI remains an important and constant issue for consideration This is the case for a variety of reasons, possibly including: WAPI appears to duplicate functionality of i The promoters of WAPI continue to assert that i is insecure It is unclear how or whether i and WAPI can coexist The issues related to WAPI are similar to those for the proposed 802.1X/AE and security replacements … Andrew Myles, Cisco Andrew Myles, Cisco

The formal WAPI NP process started in October 2009 …
July 2010 doc.: IEEE /0xxxr0 The formal WAPI NP process started in October 2009 … N14123 Text for NP ballot … for use with ISO/IEC Multiple NBs submitted comments 9-Oct-09 N14228 Summary of Voting on 6N14123, …for use with ISO/IEC IEEE 802 submitted comments (N14142) 1-Feb-10 Renumbered draft responding to UK NB comment 10 of 18 NB’s voted “yes” (10 required) & 5 NB’s stated they would participate (5 required) N14435 ISO/IEC WD Alternative security mechanism for use with ISO/IEC N14436 Disposition of Comments on the ISO/IEC NP 20011 6-Oct-10 6-Oct-10 IEEE 802 comments ignored in proposed disposition  Invited NBs to submit comments on proposed disposition (closing Jan 11) Andrew Myles, Cisco

… and the WAPI NP process was still continuing in Nov 2011 …
July 2010 doc.: IEEE /0xxxr0 … and the WAPI NP process was still continuing in Nov 2011 … IEEE 802 submitted comments on proposed disposition (N14551) USNB submitted comments on proposed disposition (N14549) Inappropriately changed title so document is no longer a disposition of NP ballot comments  N14620 Disposition of Comments on 1st WD 20011 17-Mar-11 Dismisses all substantive USNB comments on basis the process is beyond the NP stage  US NB asserts NP process incomplete & summarizing situation (N14742, N14743) Responds to most comments with assertions & false statements rather than reasoned arguments  IEEE 802 submits document asserting security of i (N14778) Dismisses all (but one) substantive IEEE 802 comments on basis the process is beyond the NP stage  N14770 Revised disposition of Comments on 1st WD 20011 8-Jun-11 Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 SC6 decided in June 2011 that an approved DoC on the WAPI NP comments was required Most discussion at the SC6 meeting in San Diego related to WAPI was focused on process Was the WAPI project at New Project or Working Draft stage? US NB asserted that the WAPI project was still at NP stage because the comments on the ballot had not been resolved and approved by SC6 China/Swiss NB asserted the WAPI project was at WD stage because the ballot passed and that SC6 had sent a working draft out for comment in Sept 10 It was ultimately determined the WAPI project was required to complete a DoC on the NP comments before the NP process was complete Based on ruling by SC6 Chair that was confirmed by JTC1 Secretariat China NB indicated at the time that they would be appealing There apparently was some sort of appeal relating to “bias”, but no outcome of the appeal has been published The China NB participated in the comment resolution process after the San Diego meeting, although under informal protest Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 A series of teleconferences were held to resolve comments on the WAPI NP proposal The ruling in San Diego meant the comments made during the NP ballot process (back in Jan 2010!) needed to be resolved and agreed by SC6 before the WAPI project could formally progress There were a series of teleconferences that attempted to resolve the comments Four teleconferences were held The first teleconference was held on 10 Aug 2011 The last teleconference was held on 21 Nov 2011 Andrew Myles, Cisco Andrew Myles, Cisco

At the last WAPI CRM, the China NB announced that they had withdrawn the WAPI project
The China NB announced they were withdrawing the WAPI project on 21 November 2011 See embedded document It was stated that the China NB withdrew the project because: The project has “experienced and still been suffering many unreasonable obstacles” It is likely the project will not complete within required time limits because of an “unfair and unjustified environment,” The China NB suggested they may resubmit the project “when a more favorable standardization environment is available” Andrew Myles, Cisco

The ISO Project portal now lists the WAPI project as “deleted”
July 2010 doc.: IEEE /0xxxr0 The ISO Project portal now lists the WAPI project as “deleted” The WAPI project is listed as “deleted” Document title: Information technology -Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements- Part XX: Alternative security mechanism for use with ISO/IEC Registration date of project: 6 Oct 2010 Current stage of project: (deleted) <- changed from previously Date of current stage: 22 Nov 2011 <- changed from previously Limit date for next stage: 6 Apr 2012 Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 ad hoc will discuss the likely result of the WAPI project cancellation
The cancellation of the WAPI project “came out of the blue” The real reasons for the cancellation are unclear The JTC1 ad hoc will have a brief discussion relating to this situation What are possible next steps for WAPI standardisation? Will i be allowed in products in China without WAPI? Is there any evidence of waning support for WAPI in China? ... Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The Chair would like to thank various individuals for representing IEEE 802 at the CRMs 10 August 31 August 15 September 21 November Bruce Kraemer Dan Harkins Dorothy Stanley Jodi Haaz Brian Weis Bruce Kraemer Dan Harkins Dorothy Stanley Jodi Haaz Brian Weis Bruce Kraemer Dan Harkins Dorothy Stanley Jodi Haaz Bruce Kraemer Dan Harkins Dorothy Stanley Jodi Haaz Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The WAPI situation highlights the need for IEEE 802 members to get involved in their SC6 NBs IEEE 802 members are important stakeholders in the WLAN industry around the world You are encouraged to participate in the NB activities in whatever country your employer operates and ensure your view is reflected in the NB position Usually NB positions are set by a “mirror committee” of some sort In the US there is a Project 5 TAG that covers the MAC/PHY activities of JTC1/SC6/WG1 In the UK there is also a mirror committee – at least one IEEE member participates Does anyone plan to join any of the NB mirror committees mentioned on the next page? Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 IEEE 802 members are eligible to participate in the activities of many SC6 NBs SC6 P-Members Korea - KATS Spain – AENOR USA – ANSI UK – BSI Germany – DIN Greece – ELOT Russia - GOST R Luxemburg – ILNAS Tunisia – INNORPI Japan - JISC Kazakhstan – KAZMEMST Kenya – KEBS Belgium - NBN Netherlands – NEN China – SAC Canada – SCC Finland – SFS Switzerland – SNV Czech Republic - UNMZ Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The other security related proposals based on TePA will be discussed in SC6 The China NB (really IWNCOMM) have previously proposed two other security related protocols to SC6 An 802.1X/AE replacement An security replacement Both these proposals are based on TePA, the three part authentication protocol underlying WAPI The Chinese NB have submitted documents related to these topics for the SC6 meeting in February 2012 N TePA-AC (802.1X replacement) N TLSec (802.1AE replacement) N MAC Security Requirements for LRWN ( security replacement) Andrew Myles, Cisco Andrew Myles, Cisco

There is some evidence of new activities related to TePA in other SDOs
BWIPS have applied to IESG for a protocol number for a protocol called TISec TISec is a “IP security framework for data communication between network nodes which is based on a Tri-element Peer Authentication[1] mechanism and IP data security methods” It includes an authentication protocol TAI, which “provides network node authentication, key management, credential management, and provides a combination employment of different cryptographic algorithms” It includes a data encapsulation protocol TUE, which “works for the IP layer data integrity and confidentiality of the IP packet” It appears that the proposal forTISec is an alternative to IPsec ESP + IKEv2 where TePA is the authentication component, and the key management piece is unspecified TISec is not of direct relevance to the JTC1 ad hoc but it does indicate a continuing interest in TePA by some stakeholders in China Andrew Myles, Cisco

SC6 will discuss how to handle the new TePA based contributions
The IEEE 802 delegation presented on these topics in June 2011 at the last SC6 meeting However, the China experts were not in attendance because they applied for visas too late This time it appears the Chinese experts will be attendance but no IEEE 802 security experts will be there It is possible the security experts will provide material for the meeting for presentation by Bruce Other options include: IEEE 802 invite Chinese to an IEEE meeting Ignore the SC6 activities ... Discussion? Andrew Myles, Cisco

N-UHT was a “hot topic” at the SC6 meeting in San Diego
July 2010 doc.: IEEE /0xxxr0 N-UHT was a “hot topic” at the SC6 meeting in San Diego Rolf DeVegt presented a discussion of ac and N-UHT at the SC6 meeting in San Diego N IEEE ’s perspectives on document 6N14746 The China NB responded with a presentation at the end of the last day The presentation did not get an official document number, and the version sent to the IEEE 802 delegation was modified from that presented The Nufront rep wrote in an accompanying note I think both MSR and 11 are good at data access applications, but only optimized for different scenarios. So, we are also open to discuss and communicate. Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 It is feared that N-UHT could be linked to the opening up of 5GHz spectrum in China Most of the 5GHz band in China is not currently open for WLAN However, there was an effort led by Chinese SPs & supported by MIIT State Radio Regulatory Commission (SRRC) to open up 5GHz in China This effort had been going very well, until recently when it was claimed that the band may be opened up for N-UHT only The recently published 12th Five Year Plan for Wireless Radio Development provides support for an N-UHT only approach The plan calls for China to make strategic use of its wireless spectrum resources to support broadband, cloud computing, and IoT development It also calls for allocation of spectrum to indigenous Chinese technologies, and that it increase the amount of domestic IP in wireless radio equipment used in China Andrew Myles, Cisco Andrew Myles, Cisco

The standardisation status of UHT & N-UHT within China is slow
July 2010 doc.: IEEE /0xxxr0 The standardisation status of UHT & N-UHT within China is slow A meeting of CCSA before the SC6 meeting in San Diego considered the standardisation of N-UHT in China, and a vote indicated little support Nufront voted “yes”; a number of Chinese companies abstained; a number of Chinese and non Chinese companies voted “no” The Nufront rep informed the SC6 meeting in San Diego in June 2011 that N-UHT would use an “alternate” process within CCSA UHT (an 11n extension) also used this “alternate” process It appears “alternate” means a group of specially selected “experts” It now appears CCSA has approved both UHT & N-UHT and forwarded them to MIIT for final ratification CCSA ran a final 15 day comment period on N-UHT a few months ago Andrew Myles, Cisco Andrew Myles, Cisco

It appears that UHT & N-UHT are still in final review by MIIT ...!
July 2010 doc.: IEEE /0xxxr0 It appears that UHT & N-UHT are still in final review by MIIT ...! MIIT ran a 15 day comment period, closing on 4 Oct It is believed that various organisations made submissions, including: USITO European Union Chamber of Commerce in China Digital Europe Japanese trade asscoiation ... some companies Most of the submissions focus on procedural issues, some of the submissions also raise technical issues UHT/EUHT are incompatible with current WLAN products & EUHT EUHT systems require interference free spectrum bands There is only one 80MHz channel available in China UHT & EUHT have significantly higher sensitivity to frequency error and phase noise compared to the 802. UHT & EUHT introduces new techniques that add significant complexity Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 MIIT has not yet provided a timeline for the next steps for NUHT completion ... whatever they are It is reported that MIIT (S&T Dept) has stated that they are in the process of reviewing the relatively large amount of comment feedback received MIIT were surprised by the number of comments received MIIT have not provided a timeline for any standard being approved. MIIT have expressed frustration with the process, and claimed foreign industry were not fully engaged enough on the issue through local standards groups. It was pointed out to MIIT that foreign enterprises were actually overridden by MIIT and CCSA; … Andrew Myles, Cisco Andrew Myles, Cisco

Recent reports suggest that the risk to 5GHz in China might be overstated
It is reported that: MIIT have indicated they WERE looking at opening up the lower 5 GHz band (e.g GHz) to WLAN in 2012. China still has unresolved issues regarding radio interference from radar, but MIIT will use experience with radar in US & Europe MIIT have made clear that it would NOT grant exclusive access to any specific technology for access to the 5ghz band, MIIT have made clear all internationally standardized products were eligible for use in China Of course, this does not include ac which has not been standardised, even by the IEEE. Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 Nufront have now sent a letter to the IEEE WG Chair suggesting some sort of interaction Nufront have sent a letter (in Chinese!) to the IEEE WG Chair, asking: What is IEEE ’s view towards China developing EUHT? Does an opportunity exist for cooperation between IEEE 802 and EUHT promoters? The IEEE WG Chair responded (in Chinese!) noting: He does not know the opinion of the WG yet The WG is interested in discussions, and learning about EUHT The WG members are likely to have a variety of technical questions, particularly in relation to coexistence of CSMA/CA and TMDA systems Nufront is invited to present to , or alternatively a meeting could be arranged in Beijing next February for a limited audience Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 ad hoc will discuss the letter from Nufront relating to EUHT
Some possible questions for discussion include: What is IEEE ’s view towards China developing EUHT? Does cooperation on EUHT make sense? What are the goals? How could and Nufront cooperate? Does competition make more sense, as long as there is a “level playing field”? ie LBT in open 5GHz bands Does EUHT satisfy the regulations for unlicensed spectrum? LBT probably required in Europe in 5GHz in future ... Note: we will avoid more technical issues, eg EUHT/ coexistence Andrew Myles, Cisco

The JTC1 ad hoc may develop a response to the letter from Nufront relating to EUHT
Contents could include: ... Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 Approval of is important so we can submit it to ISO/IEC for “International” ratification One of the issue that comes up continuously is claims that IEEE is not “International” This repeated continuously by various Chinese stakeholders, particularly in relation to the amendments that have not been sent to ISO/IEC Interestingly, the Swiss NB rep (who is a consultant to IWNCOMM) recently agreed that is “international” in practice One way of resolving this issue is to submit IEEE to ISO/IEC as soon as possible Currently is scheduled for ratification in late Jan 2012, and publication sometime in February Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 ad hoc will discuss formally submitting 802
The JTC1 ad hoc will discuss formally submitting for ratification The WG has previously told SC6 that we intend submitting for ratification by ISO/IEC If the IEEE submits under the PSDO agreement then a 60 day ballot of SC6 is required, followed by a five month approval ballot If SC6 invites IEEE to submit under the PSDO agreement then only a five month approval ballot is required It is hoped that a SC6 NB will make a request for IEEE to submit under the PSDO agreement Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The SC6 meeting in San Diego discussed a proposal from UK NB to withdraw the ISO/IEC 8802 series At the SC6 meeting in San Diego the UK NB made a proposal to withdraw a number of standards including the 8802 series :1997 (based on 802.1H-1997) :1995 (based on 802.1D-1998) 8802-2:2001 (based on IEEE ) 8802-3:2000 (based on IEEE ) 8802-5:1998 (based on IEEE ) :2005 (based on IEEE g-2003, .11h-2004, .11i-2004) The proposal was based on the observation that the ISO versions of these standards are either obsolete or significantly out of date This is less true for the series The proposal also noted that IEEE WG has explicitly requested that :2000 be withdrawn After some discussion, it was agree to postpone any decisions on this proposal until Feb 2012 to give IEEE 802 an opportunity to consider associated issues Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The Chair of the IEEE International ad hoc provided a “discussion starter” in San Francisco Phil Wennblom (Intel) is the Chair of the IEEE International ad hoc This committee has been considering similar issues Phil provided a presentation that: Described the importance of international standards Provided an overview of the PSDO Summarized the IEEE experience with the PSDO Afterwards the IEEE 802 JTC1 ad hoc has a discussion with participation by representatives from: 802.1 WG 802.3 WG WG WG Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The IEEE 802 JTC1 ad hoc put together a liaison that was refined by the IEEE 802 EC after Atlanta The IEEE 802 JTC1 ad hoc developed a draft liaison in November 2011 It was further refined and subsequently approved by the IEEE 802 EC The liaison was approved and submitted to SC6 as N15075 It is likely that Bruce Kraemer will make minor tweaks to this liaison based on: Input from the IEEE 802 EC Any input from this meeting Andrew Myles, Cisco Andrew Myles, Cisco

The JTC1 ad hoc will review the liaison to SC6
N15075 contents (para 1-3) IEEE 802 thanks ISO/IEC JTC1/SC6 for the opportunity to comment on the proposal by the UK NB (in 6N14713) to change the status in ISO/IEC of various ISO/IEC JTC1/SC6 standards and technical reports. IEEE 802 agrees with the UK NB that many of the standards and technical reports highlighted in 6N14713 are out of date. IEEE 802 recommends that IEEE 802 and ISO/IEC JTC1/SC6 work together to address this situation using a variety of mechanisms. IEEE 802 values the review of proposed standards by ISO/IEC NBs. We propose to enhance the PSDO process by enabling review of revisions of certain IEEE 802 standards by ISO/IEC JTC1/SC6 NBs during the IEEE Sponsor Ballot phase, using a process similar to that has already been put in place for the review of IEEE standards by SC6 NBs (e.g. 6N14979). Andrew Myles, Cisco

N15075 contents (para 4-5) IEEE 802 intends to resume submitting revisions of selected IEEE 802 standards to ISO/IEC for international standardisation, using the PSDO agreement, pending a process refinement to meet the particular needs of IEEE 802 and ISO/IEC JTC1/SC6. IEEE 802 is proposing to submit a subset of its standards to ISO/IEC for ratification because it values the status and reputation of ISO/IEC. IEEE 802 subscribes to the principles of ISO (e.g. “one standard, one test, accepted everywhere”). In support of these principles, it is essential that ISO/IEC JTC1/SC6 agrees that the responsibility to maintain, alter or extend the functionality of IEEE 802 standards ratified by ISO/IEC remains solely with IEEE 802. IEEE 802 is prepared to meet with officers of SC6 as soon as possible to develop the formal agreement. The agreement should be ready for consideration by SC6 and IEEE 802 by mid 2012. Andrew Myles, Cisco

N15075 contents (para 6) 6N14713 proposes the withdrawal of a variety of documents. IEEE 802 understands the underlying reasons for this proposal. However, given IEEE 802’s proposed plan to restart submission of IEEE 802 standards for ratification by ISO/IEC, we suggest that most of the existing standards and technical reports identified in 6N14713 not be formally withdrawn until new standards are in place and ratified. This approach minimises any difficulties for those countries and organisations that prefer to reference an ISO/IEC document over an IEEE document. It also avoids any difficulties related to the MAC address registry agreements between IEEE, ISO and IEC, which rely on a number of the documents identified in 6N14713. Andrew Myles, Cisco

N15075 contents (para 7) 6N14713 suggests that ISO/IEC and ISO/IEC , and their amendments, be withdrawn on the basis that the IEEE has withdrawn the IEEE 802 equivalents. We note that the IEEE 802 Executive Committee agreed to their withdrawal in IEEE partially based on the knowledge that these standards would continue to have a formal “stabilized” status in ISO/IEC, which would allow them to be referenced by the IEEE, ISO/IEC and other organisations when necessary. We note that the ISO/IEC “stabilized” status is beneficial to stakeholders because the IEEE has no equivalent status that does not require ongoing maintenance. Therefore, IEEE 802 requests that ISO/IEC and ISO/IEC , and their amendments, remain in “stablized” state in ISO/IEC. IEEE intends to change all references to IEEE and IEEE in our documents to reference the ISO/IEC versions. Andrew Myles, Cisco

N15075 contents (para 8) IEEE 802 agrees with the proposal in 6N14713 to cancel the project ( ) to update ISO/IEC and further recommends withdrawing the draft. The functions of ISO/IEC will be taken over by PSDO agreement, along with the ratification of the IEEE 802 standards that IEEE 802 intends to submit to ISO/IEC for ratification. Andrew Myles, Cisco

N15075 contents (para 8-10) IEEE 802 agrees with the proposal in 6N14713 to cancel the project ( ) to update ISO/IEC and further recommends withdrawing the draft. The functions of ISO/IEC will be taken over by PSDO agreement, along with the ratification of the IEEE 802 standards that IEEE 802 intends to submit to ISO/IEC for ratification. The IEEE 802 recommendations in response to 6N14713 are summarised in the following table. <see next page> IEEE 802 reaffirms its commitment to updating the ISO/IEC 8802 series of standard, pending the development of a refined process for the submittal of standards under the PSDO agreement. IEEE 802 is prepared to meet with the officers of ISO/IEC JTC 1/SC 6 to collaborate on such an agreement to the mutual benefit of both organizations. Andrew Myles, Cisco

Project Number Year Name Recommendation 8802-1 2001 SPECIFIC LANS Overview Retain. IEEE 802 will provide text for a replacement when the current 802 O&A revision project is complete. SPECIFIC LANS Cooperative agreement w IEEE 802 Cancel project. Delete the draft. 8802-2 1998 SPECIFIC LANS Logical Link Control 90.93 Retain in stabilized state 8802-3 2000 SPECIFIC LANS CSMA/CD Edn 6 Retain. Will be superseded as soon the next revision of IEEE is ratified by ISO/IEC 8802-5 SPECIFIC LANS Token Ring. Edn.3 2005 LANS. Wireless MAC/PHY specifications Edn 2 Retain. Will be superseded as soon the next revision of IEEE is ratified by ISO/IEC LAN GUIDELINES LLC Addresses Retain. IEEE 802 will provide a replacement at a future date LAN GUIDELINES Standard group MAC addresses 1997 Media Access Control (MAC) Bridging of Ethernet v2.0 in Local Area Networks 1995 COMMON LANS MAC service Retain. IEEE 802 will provide a replacement based upon 802.1AC at a future date COMMON LANS MAC bridges Retain. IEEE 802 will bridges provide a replacement at a future date based upon either 802.1D-2005 or 802.1Q-2011 Andrew Myles, Cisco

The JTC1 ad hoc will discuss SC6 “best practices”
The SC6 Chair has suggested some best practices, partially as a result of the WAPI situation: Accusations, written or verbal, of any other NBs or LOs, should be strictly forbidden. Accusations, written or verbal, of any standards owned by SC 6 or LOs, should be strictly forbidden. New work items of direct or obvious duplicate nature to existing standards within SC 6 or LOs should be strongly discouraged. Revisions of any SC 6 standards should not be attempted through other than the editors. Participants to SC 6 should keep to the common-sense spirit of cooperative peer collaboration and should, by no means, inadvertently exploit the venue of SC 6 as a hostile battle field. Andrew Myles, Cisco

The JTC1 ad hoc will discuss SC6 “best practices”
A group of 802 members have put together an alternative (11-12/29) Participants shall participate in a spirit of cooperation and collaboration Participants are reminded of the requirement to adhere to the ISO Code of Conduct during meetings and to maintain respect towards other participants and decorum at all time. Concentrate on the technical issues and not on personalities. Participants are reminded of ISO’s and IEC’s “one standard” principle and also Resolution #49 (ISO/IEC JTC 1 N9414). Any departure from “one standard” shall be justified in the NWIP Project Acceptance Criteria under Market Requirements” Participants are expected to provide constructive review of materials presented in SC 6. Participants are reminded of ISO’s copyright policy (ISO/IEC Directives, Part 1:2011,clause 2.13) and the need to seek approval from the content owner for inclusion of material in a proposal to SC6 Andrew Myles, Cisco

Are there any other matters?
July 2010 doc.: IEEE /0xxxr0 Are there any other matters? Andrew Myles, Cisco Andrew Myles, Cisco

The IEEE 802 JTC ad hoc will adjourn for the week
July 2010 doc.: IEEE /0xxxr0 The IEEE 802 JTC ad hoc will adjourn for the week Motion: The IEEE 802 JTC1 ad hoc, having completed its business in Jacksonville in January 2012, adjourns Moved: Seconded: Result Andrew Myles, Cisco Andrew Myles, Cisco

JTC1 Ad Hoc January 2012 agenda

Similar presentations

Presentation on theme: "JTC1 Ad Hoc January 2012 agenda"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

JTC1 Ad Hoc January 2012 agenda

Similar presentations

Presentation on theme: "JTC1 Ad Hoc January 2012 agenda"— Presentation transcript:

Similar presentations

About project

Feedback