Sponsor Ballot Comment Resolution

Slides:



Advertisements
Similar presentations
LB84 General AdHoc Group Sept. Closing TGn Motions
Advertisements

Overview of IEEE Date: Authors: August 2014
[ Interim Meetings 2006] Date: Authors: July 2005
March 2013 Opening Report Date: Authors: March 2013
Motions Date: Authors: January 2006
LB73 Noise and Location Categories
LB73 Noise and Location Categories
SG CUB Tentative Timeline
Waveform Generator Source Code
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
November Opening Report
Motion to accept Draft p 2.0
November 2013 Opening Report
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
March Opening Report Date: Authors: March 2010
TGp Closing Report Date: Authors: March 2006 Month Year
TGp Closing Report Date: Authors: May 2007 Month Year
Contribution on Location Privacy
January Opening Report
IEEE P Project Status Date: Authors: July 2013
November Opening Report
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
July 2014 Opening Report Date: Authors: July 2014
July 2012 Opening Report Date: Authors: July 2012
IEEE WG Opening Report – July 2008
Selection Procedure Recommendation
TGu-changes-from-d0-01-to-d0-02
September Opening Report
LB73 Noise and Location Categories
P Draft to Sponsor Ballot
EC Summary of PAR Development
March 2012 Opening Report Date: Authors: March 2012
Addressing White Spaces Across all of IEEE 802
IEEE P PAR Extension Request
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
November Opening Report
TGr Proposed Draft Revision Notice
Overview of WG Letter Ballot Process
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
IEEE P Wireless RANs Date:
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
November 2012 Opening Report
September 2012 Opening Report
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
Motion to go to Letter Ballot
TGu-changes-from-d0-04-to-d0-05
Motion for Study Group on TV White Space Coexistence
July 2014 Opening Report Date: Authors: July 2014
July Opening Report Date: Authors: July 2010
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
November 2014 Opening Report
July 2013 Opening Report Date: Authors: July 2013
Selection Procedure Recommendation
TGp Motions Date: Authors: January 2006 Month Year
May 2012 Opening Report Date: Authors: May 2012
Presentation transcript:

Sponsor Ballot Comment Resolution December 2013 Sponsor Ballot Comment Resolution Date: 2013-12-13 Authors: Notice: This document has been prepared to assist IEEE 802.19. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.19. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the TAG of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <shellhammer@ieee.org> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.19 TAG. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Steve Shellhammer, Qualcomm Steve Shellhammer, Qualcomm

December 2013 Abstract This presentation provides guidelines and procedures for Sponsor Ballot comment resolution The background part of the presentation is based on the IEEE-SA Standards Board Operations Manual See Section 5.4.3 Conduct of the standards balloting process http://standards.ieee.org/develop/policies/opman/sb_om.pdf Proposed guidelines and procedure are designed to satisfy the requirements of the IEEE-SA Standards Board Operations Manual Steve Shellhammer, Qualcomm

Background: Valid Ballot December 2013 Background: Valid Ballot For the ballot to be valid it must have a return rate of at least 75% The duration of the ballot can be extended up to 60 days in order to meet the return rate Steve Shellhammer, Qualcomm

December 2013 Background: Comments Comment resolution will use the spreadsheet from IEEE MyProject system since balloting is through MyProject Sponsor shall consider all comments that are received by the close of the ballot Sponsor shall make a reasonable attempt to resolve all Do Not Approve votes that are accompanied by comments Sponsors shall provide evidence of the consideration of each comment Comments that advocate changes in the proposed standard, whether technical or editorial, may be accepted, revised, or rejected Steve Shellhammer, Qualcomm

Background: Scope of Comments December 2013 Background: Scope of Comments Until the proposed standard has achieved 75% approval, comments can be based on any portion of the proposed standard Once the proposed standard has achieved 75% approval, comments in subsequent ballots shall be based only on the changed portions of the balloted proposed standard, portions of the balloted proposed standard affected by the changes, or portions of the balloted proposed standard that are the subject of unresolved comments associated with Do Not Approve votes. Steve Shellhammer, Qualcomm

Background: Ballot and Recirculations December 2013 Background: Ballot and Recirculations All substantive changes made since the last balloted proposed standard shall be identified and recirculated to the Sponsor balloting group All unresolved Do Not Approve votes with comments shall be recirculated to the Sponsor balloting group The verbatim text of each comment, the name of the Do Not Approve voter, and a response by the Sponsor conducting the resolution of comments shall be included in the recirculation ballot package Responses to comments that are not accepted verbatim shall include sufficient detail for Sponsor balloting group members to understand the rationale for rejection of the comment or revision of the change proposed by the commenter Further resolution efforts, including additional recirculation ballots, shall be required if Do Not Approve votes with new comments within the scope of the recirculation are submitted Steve Shellhammer, Qualcomm

Background: Completion of the Ballot December 2013 Background: Completion of the Ballot In order to submit the draft to RevCom the ballot must meet the following criteria ≥ 75% return rate < 30% abstain rate ≥ 75% approval rate Efforts to resolve Do Not Approve votes may continue for a brief period; however, if such resolution is not possible in a timely manner, the Sponsor should forward the submittal to RevCom because the IEEE has an obligation to the majority to review and publish the proposed standard quickly Copies of all unresolved Do Not Approve votes, together with the reasons given by the Do Not Approve voters and the responses by the Sponsor, shall be included with the ballot results submitted to RevCom Steve Shellhammer, Qualcomm

Comment Resolution Procedure December 2013 Comment Resolution Procedure All valid comments shall be considered Responses to comments that are not accepted verbatim shall include sufficient detail to understand the rationale for rejection of the comment or revision of the change proposed by the commenter If a commenter is not satisfied by the revision of the change proposed by the commenter, response may be changed from Revised to Rejected To do so the commenter shall be contacted Steve Shellhammer, Qualcomm

Comment Resolution Procedure Steps December 2013 Comment Resolution Procedure Steps For each comment the group will first decide if the comment will be accepted (exactly as written) or rejected If the comment is not accepted or rejected then we will seek a volunteer to propose a revised draft modification The volunteer will bring back to the group a proposed revised modification to the draft If the group and the original commenter agree on the revised modification then the group can mark the comment as revised along with the revised draft modification If an agreement cannot be made on the revised modification then the group may choose to mark the comment as either accepted or rejected Steve Shellhammer, Qualcomm

Comment Resolution Procedure December 2013 Comment Resolution Procedure All valid comments shall be considered Responses to comments that are not accepted verbatim shall include sufficient detail to understand the rationale for rejection of the comment or revision of the change proposed by the commenter All responses to the Revised and Rejected comments shall include sufficient detail to understand the rationale for such response Steve Shellhammer, Qualcomm