Doc.: IEEE 802.11-12/1454r0 Submission Jan 2013 IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process 15 January 2013 Haasz et al, IEEESlide.

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 /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.
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.
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:
September Session Supplementary Material
January Session Supplementary Material
September Session Chair’s Supplementary Material
July Session Supplementary Material
March Session Supplementary Material
Month Year IEEE Motions in July, 2016 Plenary
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
May Session Supplementary Material
JTC1 ad hoc closing report (July 11)
IEEE 802 JTC1 Standing Committee formalization proposal
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
Working Group November Plenary EC Closing Motion
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6
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.
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 2010 doc.: IEEE /0xxxr0 Proposed liaison presentation to SC6 in relation to liaisons between IEEE WG and ISO/IEC JTC1/SC 9 May 2011.
November Session Chair’s Supplementary Material
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
IEEE 802 JTC1 Standing Committee Mar 2017 closing report
September Session Chair’s Supplementary Material
January Session Supplementary Material
IEEE 802 JTC1 Standing Committee Nov 2015 opening report for EC
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.
<month year> doc.: IEEE < e> <November 2018>
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 Mar 2019 opening report for EC
IEEE 802 JTC1 Standing Committee March 2019 (Vancouver) closing report
March Session WG Chair’s Supplementary Material
March Session Supplementary Material
March Session WG Chair’s Supplementary Material
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:
November Session WG Chair’s Supplementary Material
November Session Supplementary Material
July Session Chair’s Supplementary Material
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
January Session Supplementary Material
JTC1 ad hoc closing report (May11)
July Session Chair’s Supplementary Material
November Session WG Chair’s Supplementary Material
<month year> doc.: IEEE < e> <November 2018>
March Session Supplementary Material
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
May Session WG Chair’s Supplementary Material
November Session Supplementary Material
November Session Supplementary Material
January Session Supplementary Material
IEEE 802 JTC1 Standing Committee July 2018 opening report for EC
Presentation transcript:

doc.: IEEE /1454r0 Submission Jan 2013 IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process 15 January 2013 Haasz et al, IEEESlide 1 Authors: NameCompanyPhone Jodi Andrew MylesCisco Bruce

Proposal for SC 6 Contributions to the IEEE 802.1, & Revision Process Bruce Kraemer IEEE 802 Category C Liaison

IEEE 802 is proposing mechanisms of exchange with & contribution by SC6 NBs 3 SC6 has invited 802 to participate in an ongoing exchange on items of mutual interest SC6 has allocated responsibility for 8802 revision processes to 802 WG’s conditional on a mechanism allowing SC6 NBs to contribute 802 proposes enabling the exchange of information using regular status reports 802 notes that much information about 802 activities is already publicly available 802 proposes to satisfy the condition by enabling SC6 NBs to comment on 802 drafts 802 proposes to provide three options for SC6 NB & delegates to comment on drafts 802 will resolve SC6 NB comments as soon as possible, even if they are provided late SC6 NB delegates may obtain voting rights by following normal IEEE 802 procedures RequestProposed solution

SC6 has invited 802 to participate in an ongoing exchange on items of mutual interest  In Sept 2012, SC6 invited IEEE 802 to participate in an ongoing exchange on items of mutual interest  The resolution (Res Information exchange between IEEE 802 & SC6) is as follows –SC 6 invites the IEEE 802 WG’s to exchange information about new work items that are within the scope of SC 6 & the respective IEEE 802 WG for information & potential coordination. 4

802 proposes enabling the exchange of information using regular status reports  IEEE 802 will provide a report after every 802 Plenary meeting –Held in March, July, November  The report will include at least the following information related to all IEEE 802 activities: –A list of published standards –A list of projects under development, including: Project approval date Project expiration date Expected date of IEEE Sponsor Ballot Expected date of submission of the draft to the IEEE Standards Board for final approval –A list of approved Study Groups Represents potential future projects under consideration  An example of a possible report format is embedded  The report will be submitted by IEEE 802 Liaison Officer for SC6 on behalf of the IEEE 802 Chair 5

802 notes that much information about 802 activities is already publicly available  Most information about IEEE 802 WG activities is available on publicly accessible websites  In particular information about all 802.1, & WG activities can be found on the following websites: – – –  SC6 NB delegates may access information about all IEEE 802 WG activities by: –Navigating through these websites at any time –Joining the associated reflectors (read-only access) –Attending WG meetings (registration fee required)  Only drafts are unavailable through these means; however, IEEE 802 is planning to liaise all drafts of standards to SC6 that we are planning to later submit to ISO/IEC for ratification under the PSDO agreement 6

SC6 has allocated conditional responsibility for 8802 revision processes to 802 WG’s  In Sept 2012, ISO/IEC JTC1/SC6 agreed to allocate responsibility for revision process to WG  The resolution (Res Responsibility for revisions) is as follows –As empowered by clause A1.2.1 of the PSDO agreement between ISO & IEEE, SC 6 decides to allocate responsibility for the revision process of the ISO/IEC standard to the IEEE WG while the IEEE WG has an ongoing revision process for the IEEE standard. A condition of this resolution is that SC 6 & its NBs have access to an established mechanism to contribute to the revision process in the IEEE WG.  The second part of the resolution makes it conditional on a mechanism being agreed that allows SC6 NBs to contribute to the revision process in the IEEE  Similar resolutions were agreed by SC6 with respect to any future ratified or standards 7

802 proposes to satisfy the condition by enabling SC6 NBs to comment on 802 drafts  A condition of resolutions through from the JTC 1/SC 6 Graz meetings is that SC 6 & its NBs have access to an established mechanism to contribute to the applicable revision processes  This condition is partially satisfied by making information about 802 activities easily accessible to SC6 NBs –SC6 will receive a report on 802 activities three times per year –SC6 NBs will have access to the public 802 websites & reflectors (read only)  In addition IEEE 802 proposes that: –All drafts of standards or amendments that are planned to be submitted to ISO/IEC for ratification under the PSDO be liaised to SC6 in parallel to Working Group Letter Ballots & Sponsor Ballots –All drafts liaised to SC6 will be accompanied by completed comment resolutions on any previous draft –SC6 NBs & SC6 NB delegates are invited to comment on these drafts, with the comments resolved in the same way as all other comments received on a draft 8

802 proposes to provide three options for SC6 NB & delegates to comment on drafts 9 WG or Sponsor ballot approved WG or Sponsor ballot started Draft, previous comment resolutions & comment invitation liaised to SC6 WG or Sponsor ballot completed SC6 NB or NB delegates submit comments on draft WG or Sponsor comment resolution completed Normal IEEE 802 processNew SC6 NB related process Option A Option B Option C

802 will resolve SC6 NB comments as soon as possible, even if they are provided late  IEEE 802 recognises that SC6 NBs & their delegates will often not be able to satisfy normal IEEE 802 deadlines for comments to ballots  IEEE 802 will solve his problem by processing comments from SC6 NBs & delegates in good faith as soon as possible, although this may mean they are only processed during maintenance procedures after ratification 10 Option AOption BOption C SC6 NB or delegate sends comments to 802 Liaison Officer before a ballot round closes SC6 NB or delegate sends comments to 802 Liaison Officer after ballot round closes but before comment resolution ficompletes SC6 NB or delegate sends comments to 802 Liaison Officer after ballot closes & after comment resolution completes Comments will be processed along with all other comments received during ballot round Comments will be processed along with all other comments received during ballot Comments will be processed as soon as possible; either during comment resolution on the next draft or during normal maintenance

SC6 NB delegates may obtain voting rights by following normal IEEE 802 procedures  It is not proposed that SC6 NBs or their delegates have voting rights in any IEEE 802 ballots  However, it should be noted that voting rights are mostly irrelevant in practice because IEEE 802 WGs all operate on a consensus basis  In addition, all substantive comments from any source are always processed & responded to with a substantive response  A SC6 NB delegate is always free to obtain voting rights by joining a ballot pool –For WG ballots, a member of the WG at the time a first draft is balloted automatically becomes a member of the WG ballot pool –For Sponsor ballots, anyone may join a Sponsor ballot pool by responding to a call to join the pool, and by either being a member of IEEE Standards Association or by paying the appropriate fee 11