[STDS-802-11-TGBN] 回复: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F T

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

Thanks Laurent.

发件人: Cariou, Laurent <laurent.cariou@xxxxxxxxx>
发送时间: 2026年9月17日 3:18
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F TGbn Agenda

Hi,

See attached green tagged for the following documents in AM2 today.

Thanks

Laurent

From: Kerstin Johnsson (Nokia) <000039130cefe96b-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, September 16, 2026 5:04 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F TGbn Agenda

Hey Duncan,

Just a few remaining editorial errors.

In 1810r2:

1. CID 16408: resolution says to move the subclause “37.16.1.3.3 Outline of ST procedures” to a new top-level subclause “37.16.1.5 Outline of ST procedures” and update all cross-references accordingly. But the inserted heading on p. 22, line 33, reads: (#16408)37.16.5 Outline of ST procedures

CID 13200: the Dialog Token rewrite on p. 19, line 4, says “is set to value of the Dialog Token field”, but it should be “is set to the value…"

3. CID 13604: on p. 22, line 7, “That” is replaced by “which,” but the following space is also deleted, producing “whichsupports” after accepting changes.

4. CID 18553: on p. 22, line 27, the rewrite produces “between the non-AP MLD with any AP MLD…” but the accepted resolution was “between the non-AP MLD and any AP…"

CID 18559: on p. 24, line 40, the “s” is inserted after the space following “provide,” so it now says “provide sthe physical location…”.

In 1811r2:

1. CID 17963: the accepted change is from “UHR Link Reconfiguration Multi-link element” to “Reconfiguration Multi-Link element”, but the actual redline deletes only “UHR”, leaving “Link Reconfiguration Multi-Link element” on page 19 line 5.

2. CID 18256: the inserted replacement on p.25, line 45, was meant to say "Enhanced Critical Updates Information Present”, but it says, "Enhanced (#18256) ~~BSS Parameter Change Count~~ Critical Update Information"

BR,

Kerstin

From: Kerstin Johnsson (Nokia) <kerstin.johnsson@xxxxxxxxx>
Sent: Monday, September 14, 2026 4:08 PM
To: Duncan Ho <dho@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F TGbn Agenda

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

One more:

1811, page 26:

via the target AP MLD (see 37.16.8 (ST execution procedure via the target

(#18791) MLD)).

You need that last parenthesis.

From: Kerstin Johnsson (Nokia) <kerstin.johnsson@xxxxxxxxx>
Date: Monday, September 14, 2026 at 13:03
To: Duncan Ho <dho@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F TGbn Agenda

Hi Duncan,

Thanks for handling all of these CIDS. I found a few typos in the corrections:

In 1811, CID 18791 did not get addressed as indicated in the “Resolution” column.

"or 37.16.10 (Downlink draining period)).”

In 1811, not sure why/how “en” got struck from the text on p. 26:

"The non-AP MLD may initiate the ST execution procedure by sending an ST”

In 1810, for CIDs 17497 and 20133, this reference did not get corrected accurately:

The Status Code field indicates the status of the neighboring AP probing via the current AP MLD as indicated in

(#17497)(#20133)Table 9-806 (Status codes)

For CID 16024, the accepted proposal identifies the intended mappings as GTK 12-56, IGTK 12-57, BIGTK 12-58, and CIGTK 12-59. The redline instead makes GTK, IGTK, and BIGTK all reference 12-56.

An MLO GTK KDE as defined in Figure

(#16024)

12-57

(MLO GTK KDE format).

An MLO IGTK KDE as defined in Figure

(#16024)

12-58

(MLO IGTK KDE format).

An MLO BIGTK KDE as defined in Figure

(#16024)

12-59

(MLO BIGTK KDE).

In 1812, the latter reference on p. 24 should be 37.16.8

request (see ~~37.16.10 (Downlink draining period)~~ 37.16.7 (ST execution procedure via the current AP MLD) and 36.16.8 (ST execution procedure via the target AP MLD)).

BR,

Kerstin

From: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Date: Friday, September 11, 2026 at 17:18
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F TGbn Agenda

CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.

Hi Alfred, and Seamless roaming TTT members,

I've uploaded the following 4 CRs to address the editorial comments of seamless roaming. @Alfred, could you please help me queue them for MAC?

@TTT members, could you please review these and let me know if you have any feedback? Most of them should be trivial.

2026	1809	TGbn	LB296 CR on Seamles Roaming editorial Part1	Download	[103 CIDs]
2026	1810	TGbn	LB296 CR on Seamles Roaming editorial Part 2	Download	[103 CIDs]
2026	1811	TGbn	LB296 CR on Seamles Roaming editorial Part 3	Download	[106 CIDs]
2026	1812	TGbn	LB296 CR on Seamles Roaming editorial Part 4	Download	[65 CIDs]

Thanks,

Duncan

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Tuesday, September 8, 2026 10:53 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F TGbn Agenda

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hello all,

The initial version of the TGbn Agenda for September F2F can be found here.

In order to plan efficiently for next week I would like to ask members that have been preliminary assigned CIDs (refer to database) to:

1) Obtain DCNs for CR submissions planned for Sept F2F,

2) Send me a submission request (preferrably including the TGbn reflector). Please make sure that the request includes the topic for each CR and the number of CIDs being resolved for each CR and whether it is Joint/PHY/MAC, and the earliest day that the CR is expected to be ready for presentation next week.

3) In addition please make sure that the CRs, once ready, are shared with the TTT members (again, preferably to the TGbn reflector) for early feedback, and are then uploaded to mentor at least 24 hours prior to the allocated meeting slot (i will post the updated agenda by Sunday EOB Hawaii time).

Let me know if you have any questions.

Regards,

Alfred

Alfred Asterjadhi, PhD

IEEE802.11 Vice Chair/TGbn Chair,

Qualcomm Technologies Inc.

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

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: 90-92 route de la Reine, 92100 Boulogne, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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

[STDS-802-11-TGBN] 回复: [STDS-802-11-TGBN] Posted: Preliminary Sept F2F TGbn Agenda