Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Jay, Thanks for your email. I made some changes to address both APs’ behavior in MAPC Discovery, and incorporated those in r6. Please see the upcoming email to TTT. In practice I introduced MAPC Discovery Request AND Response frames (both can be BC or UC). Please check out r6 and let me know if you have more comments. Thanks again! Giovanni From: yang.zhijie@xxxxxxxxxx <yang.zhijie@xxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Giovanni, The following description in MPAC discovery procedure in 599r5 only caputure the responding AP behavior after receiving individually addressed MAPC Discovery frame, what's the expected behavior for the responding AP in your mind if receving a group addressed
MAPC Discovery frame? 37.8.1.2 MAPC discovery This subclause defines MAPC discovery procedures for APs to advertise and discover their MAPC capabilities and common MAPC parameters. [CID147, CID148, CID1324 CID1398, CID3254]An AP may advertise its MAPC capabilities and common MAPC parameters bytransmitting a MAPC Discovery frame (see 9.6.7.x (MAPC Discovery frame format)) to the broadcast address, or as an individually addressed frame
to another AP. If an AP receives a soliciting individually addressed MAPC Discovery frame from a transmitting AP, the AP shall send anindividually addressed MAPC Discovery frameas a response to the transmitting AP. The value of the Dialog Token field of the MAPCDiscovery
frame (see Figure 9-J1)sent as a response by the AP shall be set to match the value of the Dialog Token field of the soliciting MAPC Discovery frame. Thanks Best Regards Jay Yang (杨志杰)
Original From: GiovanniChisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx> Date: 2025年04月17日
09:08 Subject: Re: [STDS-802-11-TGBN] MAC PDTs (2 PDTs): MAPC Signaling and Protocol Aspects, Co-RTWT Signaling and Protocol Aspects [MAC PDT: MAPC Signaling and Protocol Aspects] [MAC PDT: Co-RTWT Signaling and Protocol Aspects] Dear MAPC and Co-RTWT TTT members, Thanks for the additional feedback. A new revision is on Mentor for the two PDTs (25/0599r4, 25/0600r4). Please find the revisions here: (@Alfred Asterjadhi, please feel free to update the link on the TGbn agenda at your convenience) @li.yan16@xxxxxxxxxx, your comments are now addressed in r4 to better align with MLO signaling. @Shawn Kim, thanks
for the comments, which unfortunately could not be incorporated in r4 for the time being (some may need more discussions), will take an action on this after the presentation. @all, thanks again for the comments and suggestions. Presentation of these two documents is scheduled for Thursday 4/17 TGbn call. After the call we can work together
to resolve pending and new comments as needed. Best, Giovanni From: Shawn Kim <shawn.kim@xxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Dear Giovanni, Thank you for preparing the PDT documents. I have a couple of comments on the MAPC PDT — please find them in the attached file. Best regard, Shawn 2025년 4월 15일 (화)
오전 5:40, Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>님이
작성:
-- Sanghyun Kim, Ph.D 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 |