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

Re: [STDS-802-11-TGBN] 答复: [STDS-802-11-TGBN] Deadline Reminder for PDTs: Action Required from POCs



Hi, Alfred

Please, add the following to the 11bn PDT queue.

 

11-24/2023r0 PDT-PHY Overview of the PPDU encoding process, Junghoon Suh (Huawei)

 

Thank you

Regards

 

Junghoon Suh

 

From: gongbo (E) [mailto:000017a2c2fb48c4-dmarc-request@xxxxxxxxxxxxxxxxx]
Sent: December 3, 2024 4:10 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN]
答复: [STDS-802-11-TGBN] 答复: [STDS-802-11-TGBN] Deadline Reminder for PDTs: Action Required from POCs

 

Hi Alfred,

 

Could you please add the following  PDT contribution to 11bn PHY agenda?

 

11-24/2037r0, PDT-PHY-Null Subcarriers     Bo Gong (Huawei)

 

I schedule to upload it on 16th Dec.  

 

Best regards,

Bo Gong (Huawei)

 

 

发件人: liuchenchen [mailto:0000185315b29db3-dmarc-request@xxxxxxxxxxxxxxxxx]
发送时间: 2024123 16:48
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBN] 答复: [STDS-802-11-TGBN] Deadline Reminder for PDTs: Action Required from POCs

 

Hi Alfred,

 

Could you please add the following 3 PDT contribution to 11bn PHY agenda?

 

11-24/2034r0, PDT-PHY-Pilot Subcarriers      Chenchen Liu (Huawei)

11-24/2035r0, PDT-PHY-UHR-LTF                    Chenchen Liu (Huawei)

11-24/2036r0, PDT-PHY-Data field                   Chenchen Liu (Huawei)

 

 

I schedule to upload those on 16th Dec.  

 

Best regards,

Chenchen Liu

 

发件人: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
发送时间: 2024123 1:18
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBN] Deadline Reminder for PDTs: Action Required from POCs

 

Hello all,

 

I hope you had an enjoyable holiday.

 

I would like to remind the POCs of the following deadline:

For PDT submissions: I would like to ask/remind the following to POCs (you can find your name in the PDT queue) that are preparing the main skeleton (and spec text for the topic) of the sub clauses pertaining to that topic and uploading the base document to the mentor website:

For ease of identification, all draft text documents need to begin with "PDT-" for "Proposed Draft Text, and the topic classification (MAC/PHY/JOINT)" (e.g. 11-24-9999-00bn-PDT-MAC-This-Feature).

 Start a thread in the TGbn reflector for that topic, which is the point of reference for having discussions and exchanging feedback with other members.

Again, for ease of identification, the thread should start with [PDT-MAC/PHY/JOINT]

   Send me an e-mail with the PDT title, document number, and an estimated time of upload, so that I can populate the PDT queues. E-mail to be sent no later than December 2nd, 2024.

 

Regards,


Alfred

 

 

On Fri, Nov 22, 2024 at 12:10PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Hello all, 

 

The proposed telco agendas for Nov'24 to Jan'25 is uploaded. This revision contains the most up to date queue contents and received requests until November 22, 2024. 

You will notice that the agenda time will be split into three parts (with timing allocation that will be determined dynamically subject to contributions availabilities).

- PDT Submissions

- Running SPs

- Technical Submissions

For PDT submissions: I would like to ask/remind the following to POCs (you can find your name in the PDT queue) that are preparing the main skeleton (and spec text for the topic) of the sub clauses pertaining to that topic and uploading the base document to the mentor website:

For ease of identification, all draft text documents need to begin with "PDT-" for "Proposed Draft Text, and the topic classification (MAC/PHY/JOINT)" (e.g. 11-24-9999-00bn-PDT-MAC-This-Feature).

 Start a thread in the TGbn reflector for that topic, which is the point of reference for having discussions and exchanging feedback with other members.

Again, for ease of identification, the thread should start with [PDT-MAC/PHY/JOINT]

   Send me an e-mail with the PDT title, document number, and an estimated time of upload, so that I can populate the PDT queues. E-mail to be sent no later than December 2nd, 2024. 

 

For SP queue: Please send me requests following the usual routine, namely SP text, topic, and supporting list, and session.

 

For Technical Submissions queues, please see below.

Please let me know if I missed anything from the queues (ported from the F2F november queues), such as missing contribution, wrong topic classification, missing links, etc. 

 Please note that queue ordering and agendas are organized following the usual routines:

- Submissions ordered per-DCN, and distribution is on a per-topic basis
- Sunday (start of each F2F) deadline used to determine the cut-offs.

Note that as a side effect of merging two previous cut-offs into one queue there is a shift in the DCN order appearances. Similarly the same has happened when a DCN was in one cut-off, was deferred and then asked to be added back to the queue (as part of the subsequent cut-off).

 

As we prepare for these telcos, please take notice/act on the following:

1) Check that the presentations are properly classified and that they are uploaded to the server as soon as possible and no later than 24 hours prior to the scheduled meeting. Presentations that are not uploaded in time will be removed from the queues, and will lose their current priority (i.e., will be added as part of the ongoing cut-off). 

2) Some topics have a lot of contributions (in particular in MAC) and from the title of these contributions they seem to discuss similar concepts/issues. If your contribution falls in this category then please check with the other members if there is room for harmonization/consolidation (co-authoring, harmonized SPs, etc). 

3) In order to discuss as many MAC contributions as possible during the telcos, the time allocated per presentation will be limited to 15-20 mins (5 extra minutes available if the member wants to run an SP). So please make sure that you present your contribution within this time limit and that you leave enough time for any Q&As during the teleconference call. If no time is left for Q&As after your presentation then the TGbn reflector is a great tool to seek feedback from members. 

 

Let me know if you have any questions and enjoy the holidays.


Regards,

 

Alfred

 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe/TGbn Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302


 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe/TGbn Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302


To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1


To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1


To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1


To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1