description of the Dual Beacon subfield in subclause 9.4.2.219. 5165 Dorothy 141.36 11.1.3.10 We had as in comment Revised. Stanley in 11n with Agree in STBC. Noone principal. implemented it. See proposed Why are we change in doc. introducing yet 11-17/0576r2. another Delete this to reduce complexity in the spec. 5905 James Yee 141.50 11.1.3.10 Rather than stating As suggested. Revised. different elements The Dual may be carried, it Beacon should be specified mechanism is what are identical deleted. elements and See proposed contents that must change in doc. be carried in both 11-17/0576r2. types of Beacon frames. 6554 John Coffey 141.32 11.1.3.10 Inconsistent usage Change "beacon Revised. of defined terms: frames" to The related here we have "Beacon frames". subclause is "beacon frames", deleted. whereas See proposed everywhere else in change in doc. the drfat, including 11-17/0576r2. several places in the same section, we have "Beacon frames". 6560 John Coffey 141.51 11.1.3.10 Inconsistent use of Change "HE Revised. defined term: here EXT_SU" to The related we have "HE "HE_EXT_SU". subclause is EXT_SU", whereas deleted. everywhere else in See proposed the draft we have change in doc. "HE_EXT_SU". 11-17/0576r2. 7977 Mark 141.39 11.1.3.10 "The Beacon frame Change to "Time 0 Revised. RISON transmitted in is defined to be a The Dual PPDU format TBTT for the Beacon has TBTT at the Beacon frame mechanism is TSF value 0." is transmitted in deleted. unclear PPDU format See proposed (see 11.1.3.2)." change in doc. 11-17/0576r2. 9561 Yonggang 141.44 11.1.3.10 Using a half value as in the comment Revised. Fang of Beacon Interval The Dual of legacy beacon Beacon frames as offset of mechanism is HE beacon may not deleted.
description of the Dual Beacon subfield in subclause 9.4.2.219. 5165 Dorothy Stanley 141.36 11.1.3.10 We had in 11n with STBC. Noone implemented it. Why are we introducing yet another Delete this to reduce complexity in the spec. as in comment Revised. Agree in principal. See proposed change in doc. 11-17/0576r2. 5905 James Yee 141.50 11.1.3.10 Rather than stating different elements may be carried, it should be specified what are identical elements and contents that must be carried in both types of Beacon frames. As suggested. Revised. The Dual Beacon mechanism is deleted. See proposed change in doc. 11-17/0576r2. 6554 John Coffey 141.32 11.1.3.10 Inconsistent usage of defined terms: here we have "beacon frames", whereas everywhere else in the drfat, including several places in the same section, we have "Beacon frames". Change "beacon frames" to "Beacon frames". Revised. The related subclause is deleted. See proposed change in doc. 11-17/0576r2. 6560 John Coffey 141.51 11.1.3.10 Inconsistent use of defined term: here we have "HE EXT_SU", whereas everywhere else in the draft we have "HE_EXT_SU". Change "HE EXT_SU" to "HE_EXT_SU". Revised. The related subclause is deleted. See proposed change in doc. 11-17/0576r2. 7977 Mark RISON 141.39 11.1.3.10 "The Beacon frame transmitted in PPDU format has TBTT at the TSF value 0." is unclear Change to "Time 0 is defined to be a TBTT for the Beacon frame transmitted in PPDU format (see 11.1.3.2)." Revised. The Dual Beacon mechanism is deleted. See proposed change in doc. 11-17/0576r2. 9561 Yonggang Fang 141.44 11.1.3.10 Using a half value of Beacon Interval of legacy beacon frames as offset of HE beacon may not as in the comment Revised. The Dual Beacon mechanism is deleted.
11-17-0576-02-00ax-resolutions-for-comments-related-to-extended-range-beacon.docx