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

[STDS-802-11-TGBE] DCN 20-0390r3 and DCN 20-0389r1



Hello Laurent,

 

Thank you for presenting the two contributions regarding MLD discovery. I agree with you that RNR is a good direction for basic discovery and MLD element is needed if some specific Probe Request .  I have a few questions

 

Regarding Part 1:

 

1.       In SP 1, what do you mean all APs? Do they contain the Aps which are in the same Multiple BSSID set as the reporting AP. In slide 6, it seems it excludes them. I am fine with the scheme in slide 6.

 

2.       In SP 2, I understand “same AP” is used to indicate the relationship between the reported AP and the reporting AP. Do you consider the relationship between other reported APs, such as AP2-2.4 and AP3-5 in slide 6, and the reporting AP?

 

 

Regarding Part 2:

 

In slide 4, beacon and regular Probe are good. But if AP 1 is in Multiple BSSID set, Multiple BSSID element will be sent in Beacon frame. My question is about the non-transmitted BSSID. If non-transmitted BSSID is in another MLD, do we need a ML element or just simple indication, like BSSID-index, in non-transmitted BSSID profile for basic discovery?

 

Best wishes

Ming Gan

 

 

发件人: Alfred Asterjadhi [mailto:asterjadhi@xxxxxxxxx]
发送时间: 202069 7:50
收件人: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBE] Candidate SFD text contributions for inclusion to TGbe SFD: Call for Review [REMINDER]

 

Hello all,

 

This is a gentle reminder on this call for review. Please see below.

 

Best Regards,

 

Alfred

 

 

Hello all,

 

Our TGbe Editor has prepared the Rev 26 of the compendium of SPs and potential changes to the SFD, which can be found below: 

 

This is a call for members to review the new SFD text contributions (which are highlighted in yellow  and identified by tags listed as [DCN (Presentation, Author, Affiliation), ...] SP#X, ...) in the compenidum of SPs document.

 

Please do send an e-mail in response to this Call For Review if you would like to identify any of these "new SFD text contributions" as contributions that need further discussion. The deadline for sending these e-mails is June 10th 2020 @10:00am ET.

 

A list of these requested contributions will be queued for discussion and run as a separate motion (Motions >=113) during the Joint conference call scheduled on June 11th 2020.

 

New SFD text contributions that have not received a request for further discussions will be part of the cumulative motion (Motion 112) that will be run at the same Joint conference call. 


Please refer to the document linked below for a list of the motions:

 

For more information please refer to the subclause "Guideline-Building Consensus and Populating the TGbe SFD" in the TGbe teleconference agendas: https://mentor.ieee.org/802.11/dcn/20/11-20-0735-15-00be-2020-mar-may-tgbe-teleconference-agendas.docx.

 

If you have any comments and/or questions please let me know.

 

Best Regards,

 

Alfred

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302


 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302


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