General ad hoc- LB115- Comment Resolutions – Jan 08

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0495r3 Submission May 2009 Bruce Kraemer, MarvellSlide 1 +1 (321) Marvell Lane, Santa Clara, CA, Name Company.
Advertisements

Doc.: IEEE /0883r1 Submission July 2010 Slide 1 Comment Resolution for “Spatial Reuse” Subgroup Date: Authors: Thomas Derham, Orange.
Doc.: IEEE /0509r3 Submission Proposed Resolution to CID 72, 119 and 128 Qian ChenSlide 1 May 2014 Date:
Doc.: IEEE /0408r0 Submission May 2005 John Klein, SymbolSlide 1 TPC Comments Notice: This document has been prepared to assist IEEE It.
Doc.: IEEE /889r0 Submission November 2003 Black/Sinivaara (Nokia)Slide 1 An introduction to the proposed IEEE802.11k PICS proforma Simon Black,
Doc.: IEEE /1845r0 Submission November 2006 Bruce Kraemer, MarvellSlide 1 10 MHz Channels Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /0537r0 Submission May 2010 Kazuyuki Sakoda, Sony CorporationSlide 1 General frame format comment resolution overview Date:
TGn Editor Report Jan 2009 Date: Authors:
LB225 CR (Link Adaptation)
Discussion on CID2199 Date: Authors: Jan 2014 Name Company
November 2008 doc.: IEEE November 2008
IMT-Advanced Opening Report
Preamble design aspects for MU-MIMO support
IMT-Advanced Report Tech Requirements Outline
General ad hoc- LB115- Comment Resolutions – Jan 08
General ad hoc- LB97- Comment Resolutions, Sep 07
Proposed Specification Framework for TGac – Introductory Comments
TGn Gen Ad Hoc July Motions
TGN LB84 PHY Ad Hoc Agenda and Minutes January 2007
Comments on CID 1599 Date: Authors: June 2007 June 2007
Proposed Specification Framework for TGac – Introductory Comments
Comparison of Draft Spec Framework Documents
AP Location Capability
Resolution for CID 118 and 664 Date: Authors: Month Year
TGn Gen Ad Hoc March Status
June 2006 doc.: IEEE /0851r0 June 2006 LB84 Frame Format Ad-hoc Comment Resolution CID# 701, 7239, 9979, 3773, 7127 Date: Authors:
Beamforming and Adaptation Ad Hoc Agenda
Explanations on CID #10076 Date: Authors: May 2006 May 2006
Proposed Specification Framework for TGac – Introductory Comments
Protection Assurance Method
TGw Closing Report March 2008
TGn Beamforming and Adaptation Ad hoc - Calibration-
Comments on CID 1599 Date: Authors: June 2007 June 2007
Suggested Resolution on CID #10074
Suggested Resolution on CID #10074
TPC Comments Date: Authors: January 2005
TGn-LB97-General-adhoc-report
March 2013 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Comment Resolution Suggestions Date Submitted:
MDA assorted comments-2
Protection Assurance Method
Measurement reporting in TGh
GEN ad hoc Summary - Sep 14 ‘07
Proposed Resolutions for PICS & other General Comments
Beam & LA January Agenda & Status
Beamforming and Link Adaptation Motions
LB97 Coex: Duplicate DSSS
Comments Clarification on VHT Format HT Control Field
TGn Proposed Draft Revision Notice
TGn Draft Redline Notice
TGN LB84 PHY Ad Hoc Agenda and Minutes January 2007
Fix the Issue on Number Of HE-SIG-B Symbols
Agenda and minutes TGn PHY ad hoc
Month Year doc.: IEEE /xxxxr0
Strawmodel ac Specification Framework
TGn Closing Report – July ‘06
TGn Meeting Report - June 02 ‘09
TGn LB84 – Frame Format Ad Hoc Status and Motions
Suggested Resolution on CID #10074
Discussion on PHY CIDs 2773 and 2775
General ad hoc- LB97- Coment Resolutions – Sep 07
TGn PHY Ad Hoc Submission on Selected Comments
TGn Gen Ad Hoc March Status
TGn LB84 – Frame Format Ad Hoc Status and Motions
Proposed Resolution to CID 1420
Proposed Resolution to CID 1420
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
TGn-LB97-General-adhoc-report
Resolution to CIDs on Date: Authors: August 2006
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
September, 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: Sept.
Presentation transcript:

General ad hoc- LB115- Comment Resolutions – Jan 08 January 2008 doc.: IEEE 802.11-08/0039r1 January 2008 General ad hoc- LB115- Comment Resolutions – Jan 08 Date: 2008-Jan-10 Authors: Name Company Address Phone email Bruce Kraemer Marvell +1 - 321 4 27 4098 bkraemer@ marvell .com 5488 Marvell Lane Santa Clara, CA 95054 Summary: Proposed comment resolutions for CIDs 5480, 5115, 5113, 5408, 5364, 5480, 5528, 5687 Bruce Kraemer, Marvell Bruce Kraemer, Marvell

CID 5840 January 2008 Discussion The TGn draft is only an amendment to the baseline standard 802.11-2007. The requested explanation is already included in the baseline as indicated below: Annex A … A.3 Instructions for completing the PICS proforma A.3.4 Conditional status The PICS proforma contains a number of conditional items. These are items for which both the applicability of the item itself, and its status if it does apply, mandatory or optional, are dependent upon whether or not certain other items are supported. Where a group of items is subject to the same condition for applicability, a separate preliminary question about the condition appears at the head of the group, with an instruction to skip to a later point in the questionnaire if the N/A answer is selected. Otherwise, individual conditional items are indicated by a conditional symbol in the Status column. A conditional symbol is of the form “<pred>:<S>”, where “<pred>” is a predicate as described below, and “<S>” is one of the status symbols M or O. If the value of the predicate is true, the conditional item is applicable, and its status is given by S: the support column is to be completed in the usual way. Otherwise, the conditional item is not relevant and the N/A answer is to be marked. A predicate is one of the following: An item-reference for an item in the PICS proforma: the value of the predicate is true if the item is marked as supported, and is false otherwise. b) A boolean expression constructed by combining item-references using the boolean operator OR: the value of the predicate is true if one or more of the items is marked as supported, and is false otherwise. Each item referenced in a predicate, or in a preliminary question for grouped conditional items, is indicated by an asterisk in the Item column. Bruce Kraemer, Marvell

CID 5840 Proposed resolution: Reject. January 2008 doc.: IEEE 802.11-08/0039r1 January 2008 CID 5840 Proposed resolution: Reject. The explanation requested is, in fact, already in the baseline standard in “A.3.4 Conditional status”. Adding additional explanatory text to the draft would only require its removal later in the process. Bruce Kraemer, Marvell Bruce Kraemer, Marvell

CID 5115 January 2008 Discussion Text in D3.02 “S.1 Waveform Generator Tool” currently reads: The waveform generator can be downloaded from the public IEEE 802.11 document web site. The waveform generator code may be found in document 11-06/1715 and the waveform generator description may be found in document 11-06/1714. (#2801) The reason for the wording chosen was that referring to the documents would be appropriate because the document numbering system is considered to be historically stable but to avoid tying the document location to a specific document server which may change over time. Proposed resolution: Reject. The reason for the wording chosen was that referring to the document IDs is adequate because the document numbering system is historically stable and the documents are publically available but details of the server containing the documents may change over time and should not be included in an amendment specification. Bruce Kraemer, Marvell

CID 5113 January 2008 Discussion Text in D 3.02 Clause 3 “Definitions” introduces the term OBSS: 3.n40 overlapping basic service set (OBSS): A BSS operating on the same channel as the STA’s (#5545) BSS and within (either partly or wholly) its BSA (#807). There is no corresponding entry in clause 4. Proposed resolution: Counter. Accept in principle. TGn Editor: add the following text in the appropriate location to clause 4 : OBSS overlapping basic service set Bruce Kraemer, Marvell

CID 5408 January 2008 Discussion Text in question in D 3.00 Clause 3 “Definitions” currently reads: 3.n16 high throughput (HT): the set of features as introduced in 5.2.9 (High Throughput (HT) STA). A STA supporting these features is an HT STA. A STA not supporting them is a non-HT STA. Text in question in D 3.02 Clause 3 “Definitions” currently reads: 3.n17 high throughput (HT): the set of features as introduced (#1983) in 5.2.9 (High Throughput (HT) STA (#964)). A STA supporting these features is an HT STA. A STA not supporting these features (#5542) is a non-HT STA. Proposed resolution: Counter TGn Editor: Remove the definition 3.n17 from D3.02 Bruce Kraemer, Marvell

CID 5364 January 2008 Discussion: Text in question in D 3.00 was: 3.n57 space-time block code / spatial multiplexing (STBC/SM): A combination of space-time block coding and spatial multiplexing where one spatial stream is transmitted using space time block coding, and one or two additional spatial streams are transmitted using spatial multiplexing. Text in question in D 3.02 now appears as (clause number only change; no text changes): 3.n58 space-time block code / spatial multiplexing (STBC/SM): A combination of space-time block coding and spatial multiplexing where one spatial stream is transmitted using space time block coding, and one or two additional spatial streams are transmitted using spatial multiplexing. (#792) There is also an acronym listed in clause 4 SM spatial multiplexing Bruce Kraemer, Marvell

CID 5364 January 2008 Proposed Resolution: Counter. Accept in principle TGn Editor: insert the blue text as shown below in the appropriate location in clause 3 : 3.nxx spatial multiplexing (SM): Spatial multiplexing is a transmission technique employing multiple antennas where each antenna independently transmits a portion of the data signal in a spatial stream from each of the multiple transmit antennas. Bruce Kraemer, Marvell

CID 5480 January 2008 Discussion In D3.0 the text reads: 3.n16 high throughput (HT): the set of features as introduced in 5.2.9 (High Throughput (HT) STA). A STA supporting these features is an HT STA. A STA not supporting them is a non-HT STA. In D3.02 the text reads: 3.n17 high throughput (HT): the set of features as introduced (#1983) in 5.2.9 (High Throughput (HT) STA (#964)). A STA supporting these features is an HT STA. A STA not supporting these features (#5542) is a non-HT STA. Bruce Kraemer, Marvell

CID 5480 Proposed Resolution January 2008 Proposed resolution: Counter TGn Editor: Remove the definition 3.n17 from D3.02 3.n17 high throughput (HT): the set of features as introduced (#1983) in 5.2.9 (High Throughput (HT) STA (#964)). A STA supporting these features is an HT STA. A STA not supporting these features (#5542) is a non-HT STA. Bruce Kraemer, Marvell

CID 5528 January 2008 Discussion Link adaptation is introduced in Clause 9.16 and indicates that channel sounding may be requested. 9.16 Link adaptation 9.16.1 Introduction To fully exploit MIMO channel variations and transmit beamforming on a MIMO link, a STA can request that another STA provide (#164) MIMO channel sounding and MCS feedback. Link Adaptation may be supported by immediate response or delayed (#164) response as described below. Unsolicited MCS feedback is also possible. (#164) — Immediate: An immediate response (#2353) occurs when the MFB responder transmits the response (#164) in the TXOP obtained by the TXOP holder. This approach allows the MFB requester to obtain the benefit of link adaptation within the same TXOP. — Delayed (#164): A delayed response (#2354) occurs when the MFB responder transmits the response in the role of a TXOP holder in response to an MCS request (#164) in a previous TXOP obtained by the MFB requester. — Unsolicited (#164): An unsolicited response occurs when a STA sends MCS feedback independent of any preceding MCS request. Bruce Kraemer, Marvell

CID 5528 7.1.3.5a defines the HT Control field January 2008 Bruce Kraemer, Marvell

January 2008 CID 5528 Bruce Kraemer, Marvell

CID 5528 January 2008 Resolution discussion: A sounding PPDU can be used for the general purpose of link adaptation and is not exclusively used for the purpose of beamforming. There needs to be a recognition of this in the PICS. Currently the section of the PICS that contains Sounding relationships is shown as below. Bruce Kraemer, Marvell

CID 5528 January 2008 Proposed Resolution Transfer to Beam & Link Adaptation ad hoc. Bruce Kraemer, Marvell

January 2008 CID 5687 Discussion There are 31 occurrences of “advertise” in D3.02 and 45 in 802.11-2007. Since this is a widely used term in the baseline it should be acceptable to continue its use in amenedments. Bruce Kraemer, Marvell

CID 5687 Proposed Resolution Reject January 2008 CID 5687 Proposed Resolution Reject There are 31 occurrences of “advertise” in D3.02 and 45 in 802.11-2007. Since this is a widely used term in the baseline it is acceptable to continue its use in this amendment. Bruce Kraemer, Marvell