IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6 & 7

Slides:



Advertisements
Similar presentations
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:
Advertisements

Doc.: IEEE /0795r2 Submission July 2014 The China NB contributed a variation on the “usual comment” on IEEE China NB comment on
Doc.: IEEE /0173r0 Submission Jan 2010 Andrew Myles, CiscoSlide 1 Closing Report Date: Authors:
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
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
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
IEEE 802 JTC1 Standing Committee Nov 2018 opening report for EC
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
IEEE 802 JTC1 Standing Committee July 2016 opening report for EC
IEEE 802 JTC1 Standing Committee Slides for IEEE 802 EC opening
IEEE 802 JTC1 Standing Committee July 2017 opening report for EC
IEEE 802 JTC1 Standing Committee May 2018 (Warsaw) closing report
July 2010 doc.: IEEE /0xxxr0 Motion for LS to 3GPP RAN4 from IEEE PDED ad hoc meeting in Daejeon in May May 2017 Authors: Name.
IEEE 802 JTC1 Standing Committee Mar 2018 opening report for EC
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 opening report for EC
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
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee September 2017 (Hawaii) closing report 14 September 2017 Authors: Name Company Phone.
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee November 2018 (Bangkok) closing report 15 November 2018 Authors: Name Company Phone.
IEEE 802 JTC1 Standing Committee Nov 2016 closing report
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 Mar 2018 opening report for EC
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee November 2018 (Bangkok) closing report 16 Jan 2019 Authors: Name Company Phone .
IEEE 802 JTC1 Standing Committee Mar 2017 closing report
Possible liaison motion for IEEE as an IMT-2020 technology
JTC1 Ad Hoc January 2009 Closing Report
IEEE 802 JTC1 Standing Committee July 2016 opening report for EC
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee November 2017 (Orlando) closing report 10 November 2017 Authors: Name Company Phone.
IEEE 802 JTC1 Standing Committee Nov 2015 opening report for EC
IEEE 802 JTC1 Standing Committee Mar 2017 opening report for EC
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 Coexistence SC closing report in St Louis in Jan 2019
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
IEEE 802 JTC1 Standing Committee March 2019 (Vancouver) closing report
IEEE 802 JTC1 Standing Committee Mar 2016 opening report for EC
IEEE Coexistence SC closing report in Vancouver in Mar 2019
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee September 2018 (Hawaii) closing report 13 September 2018 Authors: Name Company Phone.
PDED Ad Hoc closing report in San Antonio in November 2016
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:
PDED Ad Hoc closing report in San Antonio in November 2016
IEEE 802 JTC1 Standing Committee Jan 2018 (Irvine) closing report
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
November 2010, Motions for the EC
IEEE PDED ad hoc closing report in Atlanta in Jan 2017
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee November 2018 (Bangkok) closing report 16 Jan 2019 Authors: Name Company Phone .
IEEE 802 JTC1 Standing Committee Nov 2016 opening report for EC
IEEE 802 JTC1 Standing Committee Mar 2017 closing report
IEEE 802 JTC1 Standing Committee Mar 2018 opening report for EC
IEEE 802 JTC1 Standing Committee July 2019 opening report for EC
Some contributions to ETSI BRAN
IEEE 802 JTC1 Standing Committee May 2019 (Atlanta) closing report
IEEE 802 JTC1 Standing Committee July 2019 (Vienna) closing report
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
Presentation transcript:

IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6 & 7 doc.: IEEE 802.11-10/0xxxr0 July 2010 IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6 & 7 9 Nov 2015 Authors: Name Company Phone email Andrew Myles (Chair) Cisco +61 2 84461010 +61 418 656587 amyles@cisco.com Peter Yee (Vice Chair) Andrew Myles, Cisco Andrew Myles, Cisco

IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6 & 7

Processes that should be followed in interactions with SC6 The following pages contain draft processes for interactions with SC6 Once refined and agreed by the SC6, they will be documented as an operations manual and approved by IEEE 802 EC The draft process include: How does a WG send a liaison to SC6? How does a WG send a draft (or ratified standard) to SC6 for information or review? How does a WG submit a standard for ratification under the PSDO process? How does a WG submit response to any comments received during the PSDO process? Andrew Myles, Cisco

Process: how does a WG send a liaison to SC6? Development The WG may develop a proposed liaison at any time It is suggested that the WG coordinate with the IEEE 802 JTC1 SC Approval The WG and then the IEEE 802 EC must approve liaisons to SC6 Transmission The WG Chair is responsible for transmitting the liaison to the SC6 Secretary Andrew Myles, Cisco

Process: how does a WG send a draft (or ratified standard) to SC6 for information or review? Development The WG may decide to send a draft (or a ratified standard) to SC6 for information or review at any time It is suggested that the WG coordinate with the IEEE 802 JTC1 SC The WG Chair must work with IEEE-SA staff to ensure the inclusion of appropriate front matter Approval The WG and the IEEE 802 EC must approve sending a draft (or a ratified standard) to SC6 and the request for any SC6 action The approval will normally be on the IEEE 802 EC consent agenda Transmission The WG Chair is responsible for notifying the SC6 Secretary that a draft (or a ratified standard) is available and any action expected of SC6 Normally the draft will be held in an IEEE 802 WG private area with only the user name/password sent to SC6 Andrew Myles, Cisco

Process: how does a WG submit a standard for ratification under the PSDO process? Development A WG may decide to submit a standard for ratification at any time It is suggested that the WG coordinate with the IEEE 802 JTC1 SC Approval The WG and the IEEE 802 EC shall approve submitting a standard for ratification under the PSDO process Transmission The WG Chair shall request the IEEE-SA staff liaison to arrange the execution of the PSDO process Andrew Myles, Cisco

Process: how does a WG submit response to any comments received during the PSDO process? Development A WG is responsible for developing responses to any comments received during the PSDO process It is suggested that the WG coordinate with the IEEE 802 JTC1 SC Approval The WG and the IEEE 802 EC shall approve submitting any responses to comments received during the PSDO process Transmission The WG Chair is responsible for sending any responses to the SC6 Secretary The WG Chair shall notify the IEEE-SA staff liaison so that they can ensure the next step of the PSDO process is executed Andrew Myles, Cisco