Re: [STDS-802-11-TGAH] Information of Annex B document amendment

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Dear TGah members

I'm checking the submission for annex B and have following comments.

Please give me your thoughts.

1) B.4.4.1 MAC protocol capabilities
According to the discussion on February 19th, 2014 Teleconference (11-14/0266r0), PSMP is not supported by the S1G STA.
Thus,
*PC37 Power save multi-poll (PSMP) 8.6.12.4 (PSMPframe format) CF27:O
should be changed to (CF27 AND not CF32):O

2) B.4.4.2 MAC frames
FT7 is defined as follows:
FT7 Beacon Clause 8 (Frame formats) (not CF2.3 and not CF32):M CF27:M

While CF27 is "Non-DMG STA" and an S1G STA is non-DMG STA, CF27 is true for the S1G STA.
Thus, addition of "and not CF32" to CF2.3 is not enough.

It should be "((not CF2.3 and not CF32):M (CF27 and not CF32):M".

3) B. 4. 17.1 HT MAC features
The status of "HTM3.2 A-MPDU format" and "HTM3.3 A-MPDU contents" is now "(CF16 & not CF32):M CF32: M".
It can be simplified to "(CF16 or CF32):M".

A S1G STA may support following HT MAC features:
- HTM8 Duration/ID rules for A-MPDU and TXOP
- HTM9 Truncation of TXOP as TXOP holder
- HTM10 Reception of +HTC frames

Thanks Regards

Mitsuru Iwaoka

(Yokogawa Electric Corp.)

2014-05-13 10:33 GMT+09:00 Kenichi Mori <mori.ken1@xxxxxxxxxxxxxxxx>:

Dear TGah members,

After a presentation of Annex B document, I received the following comment.

Based on this comment, I will revise S1GP6.4.

CF32 & S1GP1.1: O

CF32 & S1GP1.2: O

CF32 & S1GP1.3: M

CF32 & S1GP1.4: M

CF32 & S1GP1.5: M

Received comment is from here

I discussed the following issue in the document with Ken during the Monday PM1 session:

For the S1G PHY features on page 32, I suggested breaking up the Optional/Mandatory labeling for the "Greater than or equal to 2MHz long preamble format PPDU"

The intention is to say that for both APs and STAs, the >=2MHz long preamble format is mandatory if 4, 8, or 16MHz bandwidths are supported, and optional if only 1 and 2MHz bandwidths are supported (This is stated in text in section 24.1.1).

I think in the Status column, this should be expanded to indicate that support is mandatory conditional on whether 4, 8, 16MHz bandwidth operation is supported (Items S1GP1.3, S1GP1.4, S1GP1.5). For example, to indicate that the >=2MHz long preamble format is mandatory if 4MHz BW is supported, we could write "CF32 & S1GP1.3: M". Likewise, to indicate that the >=2MHz long preamble format is optional if ONLY 1MHz and 2MHz is supported, we could write "CF32 & S1GP1.1 & S1GP1.2: O".

However, we could make it even more precise if we're allowed to use "!" to indicate the "not supported" condition, like "CF32 & S1GP1.1 & S1GP1.2 & !S1GP1.3 & !S1GP1.4 & !S1GP1.5: M".

Regards,

Ken

*****************************************************************

Kenichi Mori mori.ken1@xxxxxxxxxxxxxxxx

Panasonic Corporation

R&D Division　Device Solutions Center　Radio Frequency Devices Group

TEL +81-50-3686-6589 (direct)

If you are not the intended recipient, please delete the message

and notify the sender.

*****************************************************************
_______________________________________________________________________________
IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.
SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-S1G and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.
Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________

IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.