Doc.: IEEE 802.11-14/0795r2 Submission July 2014 The China NB contributed a variation on the “usual comment” on IEEE 802.22 China NB comment on 802.22.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0908r1 Submission July 2013 Andrew Myles, CiscoSlide 1 IEEE 802 JTC1 SC closing report (July 13) Date: Authors:
Advertisements

Doc.: IEEE /0075r1 Submission January 2009 Jesse Walker, Intel CorporationSlide 1 JTC1 Ad Hoc January 2009 Agenda Date: Authors:
Doc.: IEEE /0510r1 Submission Apr 2015 Andrew Myles, CiscoSlide 1 IEEE 802 JTC1 statement for IEEE 802 EC review of subgroups 10 April 2015 Authors:
Doc.: IEEE /0194r0 Submission Jan 2015 Andrew Myles, CiscoSlide 1 IEEE 802 JTC1 SC closing report (Jan 2015) Date: Authors:
Doc.: IEEE /1454r7 Submission March 2013 IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process 20 March 2013 Haasz et al, IEEESlide.
Doc.: IEEE /1341r0 Submission September 2011 Andrew Myles, CiscoSlide 1 JTC1 SC September Closing Report 22 Sept 2011 Authors: Meeting.
Submission February 2014 Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AR 20 March 2014 Authors: NameCompanyPhone .
Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AS 20 March 2014 Authors: NameCompanyPhone .
Doc.: IEEE 802 ec EC Submission July 2014 Andrew Myles, CiscoSlide 1 IEEE 802 JTC1 Standing Committee opening report for IEEE 802 EC 14 July.
March 2015 Submission Proposed IEEE 802 Response to comments on IEEE 802.1AE/FDAmd 1 and FDAmd 2 ballots Berlin, March 2015 Slide 1.
Doc.: IEEE /0456r0 Submission April 2008 Jesse Walker, Intel CorporationSlide 1 Geneva JTC1/SC6 Liaison Report Date: Authors:
Doc.: IEEE /0173r0 Submission Jan 2010 Andrew Myles, CiscoSlide 1 Closing Report Date: Authors:
Doc.: IEEE /1454r0 Submission Jan 2013 IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process 15 January 2013 Haasz et al, IEEESlide.
July 2010 doc.: IEEE /0xxxr0 Proposed liaison presentation to SC6 in relation to the identifier conflict issue 9 May 2011 Authors: Andrew Myles,
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
EC Motions Package Authors: Date: October 2016
EC Motions Package Authors: Date: October 2016
July Plenary EC Closing Motions Package
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee Motions for WG mid-session plenary 9 May 2017 Authors: Name Company Phone.
IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6
IEEE 802 JTC1 Standing Committee July 2017 (Berlin) closing report
JTC1 ad hoc closing report (July 11)
IEEE 802 JTC1 Standing Committee formalization proposal
IEEE 802 JTC1 Standing Committee Nov 2017 motions for EC
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
IEEE 802 status report for ISO/IEC JTC1/SC6 meeting on 30 Oct 2017
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
IEEE 802 JTC1 Standing Committee Nov 2017 opening report for EC
IEEE 802 JTC1 Standing Committee Nov 2017 opening report for EC
Working Group November Plenary EC Closing Motion
Working Group November Plenary EC Closing Motion
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
IEEE 802 JTC1 Standing Committee July 2017 opening report for EC
July Plenary EC Closing Motions Package
IEEE 802 JTC1 Standing Committee May 2018 (Warsaw) closing report
IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6
July 2010 doc.: IEEE /0xxxr0 Responses to JTC1 NBs to comments made on FDIS ballots on IEEE ac & IEEE af 17 July 2015 Authors: Name.
IEEE 802 JTC1 Standing Committee Mar 2018 (Chicago) closing report
July 2010 doc.: IEEE /0xxxr0 Responses to JTC1 NBs to comments made on FDIS ballots on IEEE ac & IEEE af 17 July 2015 Authors: Name.
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
IEEE 802 JTC1 Standing Committee July 2018 (San Diego) closing report
JTC1 Ad Hoc Sept 2009 Closing Report
IEEE 802 JTC1 Standing Committee Nov 2016 closing report
November 2013 doc.: IEEE /1381r0 Telecommunications and Information Exchange Between Systems ISO/IEC JTC 1/SC 6 Document Number: 6N15925 Date:
July Supporting Material and Motions for the Closing EC Meeting July 13, 2018 Manchester Grand Hyatt San Diego, CA, USA Bob Heile, Wi-SUN.
July 2010 doc.: IEEE /0xxxr0 Proposed liaison presentation to SC6 in relation to liaisons between IEEE WG and ISO/IEC JTC1/SC 9 May 2011.
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
July Supporting Material and Motions for the Closing EC Meeting July 13, 2018 Manchester Grand Hyatt San Diego, CA, USA Bob Heile, Wi-SUN.
IEEE 802 JTC1 Standing Committee Mar 2017 closing report
JTC1 Ad Hoc July 2009 Closing Report
IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6 & 7
July 2010 doc.: IEEE /0735r2 Proposed liaison presentation to SC6 in relation to liaisons between IEEE WG and ISO/IEC JTC1/SC 9 May 2011.
July 2010 doc.: IEEE /0xxxr0 Proposed liaison presentation to SC6 in relation to liaisons between IEEE WG and ISO/IEC JTC1/SC 9 May 2011.
January 2014 IEEE 802 Response to comments on ISO/IEC JTC1/SC6 FDIS ballot of IEEE 802.1Xbx January 2016 Authors: Name Company Phone Karen.
IEEE 802 JTC1 Standing Committee Nov 2016 closing report
IEEE 802 JTC1 Standing Committee LS Recommendation
IEEE 802 JTC1 Standing Committee Mar 2019 opening report for EC
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee Summary of SC6/IEEE 802 agreement issue 13 March 2012 Authors: Andrew Myles, Cisco.
IEEE 802 JTC1 Standing Committee March 2019 (Vancouver) closing report
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee November 2017 (Orlando) closing report 10 November 2017 Authors: Name Company Phone.
July 2010 doc.: IEEE /0xxxr0 IEEE 802 status report to ISO/IEC JTC1/SC6 for SC6 meeting in April 2019 in Beijing, China 22 March 2019 Author:
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
JTC1 ad hoc closing report (May11)
Introduction Andrew Myles chairs the IEEE 802 JTC1 standing committee
IEEE 802 JTC1 Standing Committee Nov 2016 opening report for EC
IEEE 802 JTC1 Standing Committee Mar 2017 closing report
November 2013 doc.: IEEE /1381r0 Telecommunications and Information Exchange Between Systems ISO/IEC JTC 1/SC 6 Document Number: 6N15954 Date:
IEEE 802 JTC1 Standing Committee July 2019 (Vienna) closing report
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
Presentation transcript:

doc.: IEEE /0795r2 Submission July 2014 The China NB contributed a variation on the “usual comment” on IEEE China NB comment on In addition, China NB also has concerns that the ongoing FDIS processes are reducing the quality and reputation of ISO/IEC standards. We will bring our concerns to the attention of ISO/IEC central offices. Andrew Myles, CiscoSlide 1

doc.: IEEE /0795r2 Submission July 2014 The SC agreed in May 2014 on a response to the China NB comment on IEEE Response (part 1/3) IEEE 802 thanks the China NB for its comment during the 60 day ballot on IEEE as part of its consideration according to the PSDO agreement In the comment, the China NB objected to IEEE using a security mechanism based on the use of ISO/IEC/IEEE X because the China NB believes its comments in the previous FDIS ballot on ISO/IEC/IEEE X have not been satisfactorily resolved It is up to the China NB to determine whether their comments on previous FDIS ballots have been satisfactorily resolved or not. However, we note IEEE 802 has responded fully to every comment received from all ISO/IEC SC6 and JTC1 NBs during all 60 day and FDIS ballots undertaken as part of the PSDO defined process Andrew Myles, CiscoSlide 2

doc.: IEEE /0795r2 Submission July 2014 The SC agreed in May 2014 on a response to the China NB comment on IEEE Response (part 2/3) IEEE 802 does not know of any outstanding issues related to ISO/IEC/IEEE X, and notes that this standard is being successfully implemented globally today in billions of devices. IEEE 802 encourages any users of the standard, including China NB security experts, to provide further details of any issues related to ISO/IEC/IEEE X at any time This can be done by or at a face to face meeting of the IEEE Working Group. The IEEE Working Group meeting schedule is available from the IEEE Working Group Chair (Glenn Parsons, Andrew Myles, CiscoSlide 3

doc.: IEEE /0795r2 Submission July 2014 The SC agreed in May 2014 on a response to the China NB comment on IEEE Response (part 3/3) In the comment, the China NB also asserted that the quality and reputation of ISO/IEC standards have been diminished by the use of PSDO defined approval processes No evidence has been provided to justify this assertion, so it is difficult for IEEE 802 to respond in any meaningful way. However, IEEE 802 notes the PSDO agreement between IEEE and ISO has given ISO/IEC JTC1 NBs, as important stakeholders of the widely implemented and used ISO/IEC/IEEE 8802 series of standards, an effective mechanism for both review and approval. IEEE 802 believes the PSDO process has been very effective and encourages all NBs to make greater use of the opportunity to participate in the development and approval of the ISO/IEC/IEEE 8802 series of standards Andrew Myles, CiscoSlide 4

doc.: IEEE /0795r2 Submission July 2014 IEEE WG needs to ask SC6 to allocate revision responsibility for IEEE IEEE 802.1/3/11 standards are being liaised to ISO/IEC JTC1/SC6 for ratification under the PSDO based on an agreement by SC6 that the relevant IEEE 802 WG has responsibility for the revision process The agreement by SC6 is based on the existence of an established mechanism for NBs to contribute to the revision process in the IEEE 802 WG –This process is documented in N15606 The agreement was ratified by resolutions in SC6 in relation to each of IEEE 802.1/3/11 IEEE WG needs to ask for a similar agreement in relation to IEEE Andrew Myles, CiscoSlide 5

doc.: IEEE /0795r2 Submission July 2014 A liaison is required to ask SC6 for revision responsibility for Proposed liaison to SC6 (part 1/2) The IEEE Working Group is currently making use of the PSDO agreement between ISO and IEEE to enable ISO/IEC JTC1 NBs to review and ratify IEEE standards as ISO/IEC/IEEE standards The IEEE Working Group is using the same processes as those being used to enable the review and ratification the ISO/IEC/IEEE /3/11 series of standards, including those processes specified in 6N15606 ISO/IEC JTC1/SC6 has made the use of those processes the basis of resolutions within SC6 to allocate responsibility for the revision process of the ISO/IEC /3/11 series of standards to the relevant IEEE 802 Working Group Andrew Myles, CiscoSlide 6

doc.: IEEE /0795r2 Submission July 2014 A liaison is required to ask SC6 for revision responsibility for Proposed liaison to SC6 (part 1/2) The IEEE Working Group requests that SC6 adopts the following similar resolution with respect to the ISO/IEC/IEEE series of standards –As empowered by clause A1.2.1 of the PSDO agreement between ISO and IEEE, SC 6 decides to allocate responsibility for the revision process of the ISO/IEC/IEEE series of standards to the IEEE Working Group while the IEEE Working Group has an ongoing revision process for the IEEE standard. A condition of this resolution is that SC 6 and its NBs have access to an established mechanism to contribute to the revision process in the IEEE Working Group. Note that this proposed resolution is in the same form as Resolutions 6.1.9/10/11 that were approved in September 2012 at the ISO/IEC JTC 1/SC 6 plenary meeting in Gratkorn/Graz, Austria Andrew Myles, CiscoSlide 7

doc.: IEEE /0795r2 Submission July 2014 The SC will consider a recommendation to the IEEE WG and IEEE 802 EC for a SC6 liaison Motion The IEEE 802 JTC1 SC recommends to the IEEE WG and the IEEE 802 EC that a liaison, based on slides 44-45, be sent to ISO/IEC JTC1/SC6 asking that they allocate responsibility for the revision process of the ISO/IEC/IEEE series of standards to the IEEE WG Moved Seconded Result Andrew Myles, CiscoSlide 8