Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Gaurang, Ming and all, Gaurang, thanks. I repeat my suggestion below: If the concern is for non-TxBSSID, how about “host” link id info or
“anchor” link id info instead of “transmitting link id info”? This can work for both TxBSSID and nonTxBSSID. The intention is to differentiate the link whose info is not included in the STA Profile but is carried in the frame body outside the MLE and/or
the common info field of the MLE. “Link ID Info” is too generic and can lead to confusions. Regards, Rojan From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx> Hi Rojan, all, The following are the comments that are asking for changing the name of the Link ID Info subfield carried in the Common Info field of the Basic Multi-Link element. As discussed during today’s call, I have deferred these CIDs.
This topic has been discussed a number of times and I have received some feedback from members that a name change is needed. I would like to initiate this discussion to solicit input on a suitable term to differentiate b/w the Link ID for
a reported link and a reporting link. Requesting members to provide their suggestions so that I can resolve these CIDs. Thanks, Gaurang From: Rojan Chitrakar <rojan.chitrakar@xxxxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Gaurang, Ming, How about “host” link info or “anchor” link info instead of “transmitting link info”? This can work for both TxBSSID and nonTxBSSID. The intention is to differentiate the link that is not included in the STA Profile.
Best regards, Rojan Chitrakar 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 |