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

Re: [STDS-802-11-TGBE] SP text for 11-20/1322r1 (PHY Signaling Methodology for 11be Releases)



Hi Edward,

 

Thank you for the suggestion. It is indeed cleaner. I did see a bit of grammar problem in my original text. I will update the SP in my contribution based on your suggestion before the meeting, just in cases others may have other suggestions.

 

Also, I will keep “•      The name of this 1-bit field is TBD” at the end of the SP.  Hope it is okay for you.

 

Best regards,

Ray

 

From: Edward Au <edward.ks.au@xxxxxxxxx>
Sent: Thursday, October 22, 2020 5:20 PM
To: Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] SP text for 11-20/1322r1 (PHY Signaling Methodology for 11be Releases)

 

Hi Ray,

 

In Table 36-19, the fields "PPDU Type" and Compression Mode" are separate, rather than a single field named "PPDU Type & Compression Mode".

 

How do you think about the following revision?

Do you agree the following?

- The bit immediately following the PPDU Type field and the Compression Mode field in the U-SIG of a MU-PPDU is reserved for indication of Release 2 features

- In Table 36-19 of D0.1, replace the description of the "Reserved (TBD)" field immediately after the Compression Mode field from "Reserved and set to 1 (TBD)" to "Maybe used for an expanded set of PPDU types, compressed mode, or other modes in Release 2 (TBD)"?


Regards,

Edward

 

On Thu, Oct 22, 2020 at 4:59 PM Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx> wrote:

Dear All,

 

Based on some offline discussions, I propose to use the following SP text for my contribution. I will take it to today’s PHY ad hoc. Please review and comment. Thanks.  

 

Do you agree that

  • The bit immediately after the "PPDU Type & Compression Mode" field in the U-SIG of a MU-PPDU is reserved for indication of Release 2 features and put “Maybe used for an expanded set of PPDU types or compressed mode or other modes in R2” in the Description field of this bit in the “U-SIG field of an EHT MU PPDU” table in D0.1?
    • The name of this 1-bit field is TBD

 

 

Best regards,

Ray

 

From: Bin Tian <btian@xxxxxxxxxxxxxxxx>
Sent: Friday, October 16, 2020 12:47 PM
To: Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>; ross.yujian@xxxxxxxxxx
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx; Sameer Vermani <svverman@xxxxxxxxxxxxxxxx>
Subject: RE: SP text for 11-20/1322r1 (PHY Signaling Methodology for 11be Releases)

 

Hi Ross and Rui

To ensure the forward compatibility,  I think it is important to define the Rx behavior on all the reserved bits.  Sameer is investigating it now and will share his thoughts soon.  I am open to name changes of some of the reserved field.

 

Thanks,

Bin

 

From: Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>
Sent: Friday, October 16, 2020 7:44 AM
To: ross.yujian@xxxxxxxxxx
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx; Sameer Vermani <svverman@xxxxxxxxxxxxxxxx>; Bin Tian <btian@xxxxxxxxxxxxxxxx>
Subject: RE: SP text for 11-20/1322r1 (PHY Signaling Methodology for 11be Releases)

 

CAUTION: This email originated from outside of the organization.

Hi Ross,

 

Thanks for the response.

 

Just to be clear, I copy part of Table 36-19 (U-SIG field of an EHT MU PPDU) in D0.1 below. Are you saying, in the row circled in the green box, change “Reserved and set to 1 (TBD)”  (in the Description field of the Table) to “Reserved for R2 features”, and change “Reserved (TBD)” to “Reserved”?

 

I am also fine with not saying anything to other reserved bits for now. We can made decision later.

 

 

 

 

 

 

Best regards,

Ray

 

From: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>
Sent: Friday, October 16, 2020 3:33 AM
To: Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>; Sameer Vermani <svverman@xxxxxxxxxxxxxxxx>; Bin Tian <btian@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: 答复: SP text for 11-20/1322r1 (PHY Signaling Methodology for 11be Releases)

 

I remember, last time Bin suggested to focus on the Rx behavior when STAs read reserved bit that are not default values.

 

For the naming of the bit immediately after the "PPDU Type & Compression Mode" field is, I prefer to add a description saying reserved for R2 features. Reserved bit is ok for the naming.

 

For other bits, I think we don’t need to say anything.

 

regards

于健 Ross Jian Yu

Huawei Technologies

 

发件人: Rui Yang [mailto:Rui.Yang@xxxxxxxxxxxxxxxx]
发送时间: 20201015 23:33
收件人: Sameer Vermani <svverman@xxxxxxxxxxxxxxxx>; Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>; Bin Tian <btian@xxxxxxxxxxxxxxxx>
抄送: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: SP text for 11-20/1322r1 (PHY Signaling Methodology for 11be Releases)

 

Dear Sameer, Ross, Bin and All,

 

Per our discussion at the end of presentation of 11-20/1322r1 on Oct 12 (PHY ad hoc), I made the SP text below that hopefully captures all your comments and suggestions. Please let me know if you have any further comment and suggestion.  

 

Do you agree that

·       The bit immediately after the "PPDU Type & Compression Mode" field in the U-SIG of a MU-PPDU is reserved for indication of Release 2 features and is labeled as “Reserved for R2 features”?

o   The name of the 1-bit field is TBD

 

·       All other reserved bits in the U-SIG and EHT-SIG of a MU-PPDU are labeled or footnoted as "Reserved for additional R1 or R2 features"?

 

Best regards,

Ray

 


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