Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Thank you Ali for your response. However, I respectfully do not agree with your view point.
I fail to understand why it is ok to have “inconsistent” (w.r.t. the signaling shown in 11-41i) signaling between the two MACs. IMHO it is much clearer to show the exact signaling between the MACs and mention
that one of the NDPs is not for sensing in the first two boxes. Even one does not need to refer to such text, rather one can infer it from the figure, since there is no report being generated for such cases. Multiple MS setup Req and Resp are, in some sense, error or uncommon scenarios (probabilistic/depend on certain factor(s)). We should show the signaling for the most common scenario. I do not see any no harm in showing the consistent signaling. I do not understand why we do not want to show it. Is it to make less clutter in the figure? Or is there a technical reason for it? thanks and regards -Anirud Anirudha (Anirud) Sahoo (He/Him) https://sites.google.com/view/a-sahoo National Institute of Standards and Technology Wireless Networks Division Communications Technology Lab 100 Bureau Drive, Stop 6730 Gaithersburg, MD 20899 Ph: 301-975-4439 From: Ali Raissinia <alirezar@xxxxxxxxxxxxxxxx>
Hi Anirud, as I have tried to explain it Rajat during last week’s meeting, the SME/MLME interface/diagram shouldn’t care about how many frame exchanges (or direction of it) occur between two MACs to obtain
the needed feedback (in this case report). In fact the transmission of request(s)/Response(s) *i.e. MS setup Request/Response) may occur many times due to retransmissions but we don’t show it in the associated diagram. Bottom line, I think the current diagram
seems to be sufficient as it conveys the required exchange. And BTW, we’d discussed this issue once before and that was the direction that Naren to capture the diagram as shown. Of course, we can always bring it back up but my thinking is that such details
are already in the normative section (i.e. 11.x.x.x) anyway so there should not be any ambiguity regardless.
Regards, Ali From: Sahoo, Anirudha (Fed) <00001823ca88828f-dmarc-request@xxxxxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Naren, I have the following concerns about the Non-TB case (Fig. 6-28b) in the document.
I suggest to address the above two concerns as follows.
thanks and regards -Anirud Anirudha (Anirud) Sahoo (He/Him) https://sites.google.com/view/a-sahoo National Institute of Standards and Technology Wireless Networks Division Communications Technology Lab 100 Bureau Drive, Stop 6730 Gaithersburg, MD 20899 Ph: 301-975-4439 From:
stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx>
On Behalf Of narengerile Hello TGbf friends I’ve uploaded a revised version r3 of the CR document for MLME part 1 on the server:
https://mentor.ieee.org/802.11/dcn/22/11-22-1365-03-00bf-cc40-cr-for-mlme-part-1.docx All the modifications compared to r2 are indicated by edits. Both figures and texts are revised.
Please let me know if you have any comment or question. Any feedback is welcome.
Thanks, Naren To unsubscribe from the STDS-802-11-TGBF list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 |