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

Re: [STDS-802-11-TGBE] AP removal and AP addition as critical update events - CR doc 22/1838r1

Hi Alfred,

 

Could you please list following document in MAC Ad-hoc queue for CID 11433, which is currently scheduled for Thu AM1 session.

 

  • 11-23/0036 - LB266 CR for ML Reconfig critical update events (3 CIDs, including CID 11433)

 

All,

This CR doc provides resolution for CIDs asking for AP Removal and AP Addition events to be considered as critical update events. I separate CIDs resolution into this CR doc for a separate discussion on this topic. Please review and provide any feedback/suggestions you have.

 

CR doc proposes two options for listing AP Removal and AP Addition as critical updates.

Option 1: AP Removal and AP Addition events added under clause 11.2.3.15 (TIM broadcast) as critical update events

Option 2: AP Removal and AP Addition events are indicated as ML critical update events under 35.3.10 (BSS parameter critical update procedure), without impacting TIM broadcast clause.

 

I am good with either approach. Please share feedback if you prefer one over the other.

Thanks,

Binita

 

 

From: Binita Gupta
Sent: Monday, January 9, 2023 12:28 PM
To: Yongho Seok <yongho.seok@xxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] AP removal and AP addition as critical update events - CR doc 22/1838r1

 

Correction – I meant AP Removal and AP Addition below.

 

Thanks,

Binita

 

From: Binita Gupta
Sent: Monday, January 9, 2023 12:25 PM
To: Yongho Seok <yongho.seok@xxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] AP removal and AP addition as critical update events - CR doc 22/1838r1

 

Hi Yongho,

 

Thanks for your feedback.

 

Sorry for my delayed reply. Please find attached my responses to your comments and suggestions. I have made revisions based on some of your feedback in attached.

 

For listing AP Removal and AP Addition as critical events (CID 11433), I am also good with your suggestion of listing these events under 11.2.3.15, instead of making a new subclause. This is what I had captured in 22/1838r0. I will include proposed text for that approach as well in the revised version, to present both options to the group.

 

Thanks,

Binita

 

From: Yongho Seok <yongho.seok@xxxxxxxxx>
Sent: Thursday, December 15, 2022 7:03 AM
To: Binita Gupta <binitagupta@xxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] AP removal and AP addition as critical update events - CR doc 22/1838r1

 

Hi Binita, Please find my comments in the attached file. Thanks, Yongho 2022년 12월 13일 (화) 오후 12: 12, Binita Gupta <00001d96db2c011d-dmarc-request@ listserv. ieee. org>님이 작성: Hi all, Just a reminder to review and provide any feedback on this

ZjQcmQRYFpfptBannerStart

This Message Is From an Untrusted Sender

You have not previously corresponded with this sender.

ZjQcmQRYFpfptBannerEnd

Hi Binita, 

Please find my comments in the attached file. 

 

Thanks,

Yongho 

 

2022년 12월 13일 (화) 오후 12:12, Binita Gupta <00001d96db2c011d-dmarc-request@xxxxxxxxxxxxxxxxx>님이 작성:

Hi all,

 

Just a reminder to review and provide any feedback on this topic in 22/1838r1.

This is schedule for presentation in this week’s Thursday call.

 

Thanks,

Binita

 

 

From: Binita Gupta <00001d96db2c011d-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, December 6, 2022 12:28 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] AP removal and AP addition as critical update events - CR doc 22/1838r1

 

Hi all, I am trying to resolve the issue raised in CIDs 11433 and 12806 – these CIDs identify that AP removal and AP addition should be considered as critical update events which increment BPCC along with setting the CUF field. Current

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

ZjQcmQRYFpfptBannerEnd

Hi all,

 

I am trying to resolve the issue raised in CIDs 11433 and 12806 – these CIDs identify that AP removal and AP addition should be considered as critical update events which increment BPCC along with setting the CUF field. Current draft spec only sets the CUF for these events, treating these differently than other critical update events – this is not desirable since this can lead to STA missing these critical updates if it misses the Beacons where the CUF was set. CR doc 22/1838r1 captures relevant issues under Discussion for these CIDs.

 

I have been discussing this offline with some of the members and we have aligned on text proposal in attached 22/1838r1. In summary, the proposed text adds a subclause 35.3.10.2 (Multi-link critical update events) which captures AP removal and AP addition as ML critical update events in addition to events captured in 11.2.3.15 (TIM Broadcast). Text in relevant places have been revised to refer to this new subclause instead of 11.2.3.15 (TIM Broadcast) for BSS parameter critical update.

 

Please review and provide any feedback on this proposal. This is scheduled to be presented in tomorrow’s TGbe call.

 

Thanks,

Binita

 

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