| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Thanks, Ron. I thought about it, but it is not ‘trivial’. For this particular section (34.X1.Y1. Scope), it is trivial – just write that PSDUs are mapped to PPDUs in case of A-PPDU. But
then, we have to define A-PPDU somewhere else (Clause 3 definition? Clause 34 introduction? Some subsection under Clause34 to describe A-PPDU in more detail?). I didn’t see any section assigned to do that yet, and I don’t think that will be a easy/quick
thing to write. And given that A-PPDU is an R2 feature, I would suggest that we defer writing that to a later point in time. Regards, Youhan From: Ron Porat <000009a0da80e877-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Youahn, Please see a comment on 1293:
Thanks, Ron From: Youhan Kim [mailto:youhank@xxxxxxxxxxxxxxxx]
Hi, Alfred, Sigurd and Tianyu, Please add the following draft text documents to the PHY agenda. 11-20/1293: PDT PHY – Scope and EHT PHY Functions 11-20/1295: PDT PHY – Overview of the PPDU encoding process 11-20/1294: PDT PHY – EHT PLME Thank you. Regards, Youhan From: Bin Tian <btian@xxxxxxxxxxxxxxxx>
CAUTION: This email originated from outside of
the organization. Hi Alfred, Sigurd and Tianyu Please add the following draft text to the PHY agenda 1153r1 PDT-PHY-Timing-Related parameters I have uploaded the r1 which corrects a few errors/typos (Thank Shimi for pointing them out!) and removes the content related to CBW240 Thanks, Bin From: Wook Bong Lee <wookbong.lee@xxxxxxxxxxx>
CAUTION: This email originated from outside of
the organization. Hi Alfred, Sigurd and Tianyu, Can you please add following three documents in PHY agenda? 11-20/1252r0, PDT-PHY-Frequency Tolerance, Wook Bong Lee (Samsung) 11-20/1253r1, PDT-PHY-Modulation Accuracy, Wook Bong Lee (Samsung) 11-20/1254r1, PDT-PHY-Receive specification: General and receiver minimum input sensitivity and channel rejection, Wook Bong Lee (Samsung) Best regards, Wook Bong Lee From: Alfred Asterjadhi [mailto:asterjadhi@xxxxxxxxx]
Hello all, This is a gentle reminder that when you have spec text ready for a particular subclause/topic then the POC should request the respective chairs (MAC/PHY/JOINT) to [add the contribution to the agenda] and run a SP for including
the prepared spec text to TGbe D0.1. Quoting the particular bullet from the guidelines that deals with this aspect: ·
When the spec text for a particular subclause/topic is ready then the POC should request the respective chairs (MAC/PHY/JOINT) to run a SP for including the prepared spec text to the D0.1 of 11be. o
The document that is planned to be ran should be posted in the server for at least 7 days prior to running the SP. o
If the SP is approved then the TGbe editor will include the spec text to the draft, otherwise the spec text will not be included in its current form. o
The deadline for completing this task is set for September 1st 2020 (EOD ET). o
Note: Figures should be provided to the editor in visio format (monochromatic). Please let me know if you have any questions and/or suggestions. Best Regards,
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 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 |