| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Thanks, Brian. Hi all, any further comments/views on this topic? Best regards, Yan. From: Brian Hart (brianh) [mailto:00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx]
Hi Yan, Jianhan and all I am aligned with Yan’s “proposed change” and “option 1” in 21/489r1. I have a presentation I am finalizing on the basis for why Jianhan and I do not form the same opinion
on this topic. Best regards Brian From: Yan Xin <Yan.Xin@xxxxxxxxxx>
Dear Jianhan, all: Thanks Jianhan for sending your view on CID 1279. It is an issue to mixed-use “80 MHz frequency segment” and “80 MHz frequency subblock” to represent the same meaning of spectrum in the Clause 36 and other clauses
through the current P802.11be D0.3. I have submitted a contribution 489r1 to get the group’s view on this issue
https://mentor.ieee.org/802.11/dcn/21/11-21-0489-01-00be-cr-on-cid-1279.docx
@all, please share your view/suggestions on the resolution for CID 1279. If needed, we may set up an offline call to discuss this.
Regards, Yan. From: Jianhan Liu [mailto:jianhanliu@xxxxxxxxx]
Dear Yan and All, The CID 1279 suggests replacing the "frequency segments" with "frequency subblocks". I think "frequency segment" is in fact the most appropriate word in 11be and, to be frank, changing 11ax to frequency sunblock is in fact causing more
confusion. I had at least five arguments listed in the following why we should not use "subblock": 1. "Subblock" is part of a main block, using "Subblock" without a clear reference to a main block
is really misleading. Also, a "block" in a spec in general refers to a functional block, such block diagram, etc. 2. "Segment Parser" is used for a long time and still in 11n/ac/ax/be.
Changing segment parser to Subblock parser caused unnecessary confusions to implementation guys. 3. in 11be, there is no 80+80 or 80+160 non-contiguous, so using frequency segments will not cause any confusion. Most technical contributions and discussions using frequency segments
and there seems no confusion at all. 4. "Definition of subblock: a block that is a subdivision of a larger block: such as. a : a functional subdivision of a building
or part of a building. b : a subdivision of a quantity, number, or section of things dealt with as a unit a sub-block of data." We can see that subblock is either a functional subdivision or for data, so using it for frequency and parser is not appropriate. 5. Descriptions like "20, 40 and 80 MHz EHT PPDUs have one 20, 40 and 80 MHz frequency subblock, respectively"
looks absurd. A is A, A is not a sub of A. Hopefully we can use the right word "segment" instead of using the inappropriate word "subblock" just because some guy proposed using "subblock" in 11me without fully considering technical details. Thanks and Regards, Jianhan To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |