Editorial changes to approved resolutions

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0077r1 Submission January 2008 Stephen McCann, Nokia Siemens NetworksSlide 1 TGu Motions Date: Authors:
Advertisements

Doc.: IEEE /0077r0 Submission January 2008 Stephen McCann, Nokia Siemens NetworksSlide 1 TGu Motions Date: Authors:
Multi-STA BA Design Date: Authors: March 2016 Month Year
PHY-CCA Indication doc.: IEEE yy/xxxxr0 Date:
Comment Resolution Actions
Resource Negotiation for Unassociated STAs in MU Operation
TGax Editor’s Report – November 2016
FCC TVWS Terminology Date: Authors: Month Year Month Year
TGax Editor’s Report – September 2016
BRP Transmit Sector Sweep
Month Year Month Year doc.: IEEE yy/xxxxr0 doc.: IEEE /0135r0
PHY-CCA Indication doc.: IEEE yy/xxxxr0 Date:
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Corrections for D2.8 Date: Authors: May 2014 Name
General ad hoc- LB115- Comment Resolutions – Jan 08
LMSC P&P Issues for Closing Plenary
NDP Transmission Date: Authors: Month Year Month Year
TGn Sync MAC Response to Reasons and Cures
UL OFDMA-based Random Access Parameter Set (RAPS) element
The Effect of Preamble Error Model on MAC Simulator
MAC Clarifications Date: Authors: September 2016
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
Comments on CID 1599 Date: Authors: June 2007 June 2007
TGz Beijing May 2010 Closing Report
AP Location Capability
Resolution for CID 118 and 664 Date: Authors: Month Year
TGn Gen Ad Hoc March Status
Coex Ad Hoc January London Agenda and Report
doc.: IEEE <doc#>
VHT Frame Padding - Summary
Use Case Document Definitions
TGad July 2010 Editor Report
Feedback received on Revision PAR
Number of Encoder as a function of MCS
Comments on CID 1599 Date: Authors: June 2007 June 2007
Draft D4.01 status report Date: Authors: February 2010
IEEE P Wireless RANs Date:
TGn-LB97-General-adhoc-report
Identification Signal for Fixed devices
Explicit Block Ack Request in DL MU PPDU
PHY-CCA Indication doc.: IEEE yy/xxxxr0 Date:
‘On’ Symbol Generation
doc.: IEEE <doc#>
TGaj Editor Report for CC22
TGaj Editor Report for CC22
TGad Editor Report Date: Authors: May 2011 April 2007
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
Proposed Changes for D0.25 Comments
Multi-TID Aggregation for 11ay
Motivation for Vendor Specific Request Element
doc.: IEEE <doc#>
More Simulations on Secondary CCA
TGn Editor Report Oct 2006 Date: Authors: October 2006
VHT NAV Assertion Date: Authors: Month Year
TGp Closing Report Date: Author: September 2007 Month Year
TGaj Editor Report for LB220
TGaj Editor Report for LB226
TGn PHY Ad Hoc Submission on Selected Comments
Comment Resolution Actions
802.11s motion Date: Authors: November 2007 Month Year
TGn Gen Ad Hoc March Status
Non-AP STA Location Capability
TGaj editor report for Sponsor Ballot
doc.: IEEE <doc#>
Discussion on Functional Requirements
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
TGba Possible Architecture and Specification Issues
TGaq Closing Report Date: Authors: July 2015 July 2015
TGaj editor report for Sponsor Ballot
Presentation transcript:

Editorial changes to approved resolutions Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Editorial changes to approved resolutions Date: 2019-05-14 Authors: Robert Stacey, Intel John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Abstract Overview of some the actions this editor takes when incorporating approved resolutions and in the general maintenance of the draft Robert Stacey, Intel John Doe, Some Company

May 2019 Discussion The editor often makes editorial changes to the approved resolutions: To correct grammar To make style more cohesive with rest of the document and other resolutions When this occurs, the editor adds editing notes to the comment tracking database (Editing Notes column) Editor does not make technical changes However, sometimes what the editor perceives to be an editorial fix results in an inadvertant technical change. Editor is not trying to override the editorial will of the group; if a resolution is intended to express an editorial preference, the editor will abide by it The editor has a draft review committee primarily composed of the authors of the resolutions to catch errors Some examples are provided for discussion Robert Stacey, Intel

Example 1 Approved Draft Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Example 1 Following notations are used when describing the indices for a set of subcarriers: [x1:y1] represents the set of subcarriers whose index k satisfies x1 ≤ k ≤ y1. [x1:y1, x2:y2] represents the set of subcarriers whose index k satisfies either x1 ≤ k ≤ y1 or x2 ≤ k ≤ y2. Approved Draft Grammar: Add missing article, adjust number Style: Add bullets, remove periods Robert Stacey, Intel John Doe, Some Company

Example 2 Approved Draft May 2019 Example 2 Valid range of m for Equation (27-131) is as follows. PPDU is a 20, 40, 80 or 160 MHz PPDU: Valid range of m is -iRU26,start + 1 ≤ m ≤ -1. PPDU is an 80+80 MHz PPDU and iRU26,start is less than or equal to 37: Valid range of m is -iRU26,start + 1 ≤ m ≤ -1. PPDU is an 80+80 MHz PPDU and iRU26,start is greater than 37: Valid range of m is -iRU26,start + 38 ≤ m ≤ -1. Approved Draft Grammar: Missing article Style: Align with other variable descriptions Robert Stacey, Intel

Example 3 Approved Draft for review Draft May 2019 Example 3 A STA transmitting an HE PPDU that carries a broadcast addressed MPDU shall set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to 16 µs.  A STA transmitting an HE PPDU that carries a group addressed, but not broadcast addressed, MPDU shall not set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to a value which is less than that required for any of the intended recipients in the group address. Approved A STA transmitting an HE PPDU that carries a broadcast MPDU shall set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to 16 µs. A STA transmitting an HE PPDU that carries a multicast MPDU shall not set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to a value which is less than that required for any of the recipients in the multicast group. Draft for review Draft As identified during review, editor’s changes were not appropriate Robert Stacey, Intel