1. Proposed Resolution to CID 1420
September 2006
doc.: IEEE /1397r0
September 2006
Proposed Resolution to CID 1420
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 Working Group 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
John Ketchum, Qualcomm Incorporated
John Ketchum, Qualcomm Incorporated

2. September 2006
doc.: IEEE /1397r0
September 2006
Abstract
This document contains proposed changes to the IEEE P802.11n Draft to address the following LB84 comments:
1420, 7652
The changes marked in this document are based on TGn Draft version D1.03.
John Ketchum, Qualcomm Incorporated
John Ketchum, Qualcomm Incorporated

3. CID 1420 Comment: Proposed change:
September 2006
doc.: IEEE /1397r0
September 2006
CID 1420
Comment:
do we need to mention the other possible ways that this feedback is returned? Is the intent here simply to describe the case of "fast" linke adaptation? If so, then the other mechanisms need not be stated, but this sentence should then be qualified with the fact that fast link adaptation is being described (I know that the subclause header sort of says that, but...)
Proposed change:
start the sentence on line 19 with "For fast link adaptation, this frame may be
John Ketchum, Qualcomm Incorporated
John Ketchum, Qualcomm Incorporated

4. CID 7652 Comment: Proposed change:
September 2006
doc.: IEEE /1397r0
September 2006
CID 7652
Comment:
this subclause reads oddly - it introduces link adpatation which has just been defined in previous sections
Proposed change:
Replace heading with "Fast link adaptation using CSI feedback" and delete the first two paragraphs.
John Ketchum, Qualcomm Incorporated
John Ketchum, Qualcomm Incorporated

5. Text in Question 9.21.4 Fast link adaptation using explicit feedback
September 2006
doc.: IEEE /1397r0
September 2006
Text in Question
Fast link adaptation using explicit feedback
Two types of explicit feedback support fast link adaptation: MCS feedback and channel state feedback. MCS feedback is carried in an HT Control field in any supported frame type (see (QoS Control field) and a (HT Control field)). Channel state feedback is carried in the CSI matrices feedback management action frame defined in (MIMO CSI Matrices). This frame may be embedded in a QoS Null + HTC (MAP=1) frame with its Ack Policy field set to “no ack”, allowing it to be contained along with data or control frames inside an A-MPDU within an HT frame exchange.
John Ketchum, Qualcomm Incorporated
John Ketchum, Qualcomm Incorporated

6. Counter Proposal Counter proposal:
September 2006
doc.: IEEE /1397r0
September 2006
Counter Proposal
Counter proposal:
Remove section ( in D1.03).
The section mixes up link adaptation and explicit feedback in a confusing manner that adds nothing to the section.
These two mechanisms should be addressed separately in the text, as they are already in , , , and
John Ketchum, Qualcomm Incorporated
John Ketchum, Qualcomm Incorporated