Dear Rojan and all,
Please see an update CR document 11-19/1539r1.
In this revision, I have:
-
Added language to WURModesetup.confirm and WURModesetup.indication to clarify that an unsolicited WUR Mode Setup frame is handled by the WURModesetup.confirm primitive.
-
Added WURPNUpdate parameter for all WURModeSetup primitives (.request, .confirm, .indication and .response).
It is the question whether we want to remove the sentence “This primitive is generated by the MLME as a result of an MLME-WURMODESETUP.request primitive
and indicates the results of the request.” from 6.3.122.3.3. personally, I am ok either way deleting or keeping it. It can be argued that even unsolicited WUR Mode Setup frame is an distant result of .request primitive,
but it is not very relevant.
Please let me know of any comments or changes.
Best regards,
Xiaofei Clement Wang • Principal Engineer • InterDigital
2 Huntington Quadrangle, Melville, NY, 11801 • T: +1 631-622-4028
From: rojan.chitrakar@xxxxxxxxxxxxxxxx <rojan.chitrakar@xxxxxxxxxxxxxxxx>
Sent: Wednesday, September 11, 2019 21:11
To: yunsongyang1@xxxxxxxxx; Xiaofei Wang <Xiaofei.Wang@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBA@xxxxxxxxxxxxxxxxx; po-kai.huang@xxxxxxxxx; Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>; Joseph Levy <Joseph.Levy@xxxxxxxxxxxxxxxx>
Subject: RE: [STDS-802-11-TGBA] Call for contributions for TGba F2F at Hanoi, Vietnam
Hi Xiaofei,
Yunsong has a valid point regarding WUR Operation element missing in .indication if used for unsolicited responses. Either we should add it in .indication or we should clarify that .confirm
is used for unsolicited responses and not .indication.
On a related note, WUR Mode Setup frames can also carry the WUR PN Update element. We missed it last time. If it is not too much trouble, can I request you to also add a WUR PN Update
field in all four primitives (request, confirm, indication, response) with following suggested text:
Name: WUR PN UPdate
Type: WUR PN Update element
Valid range: One or more WUR PN Update elements as defined in 9.4.2.300 (WUR PN Update element)
Description: Provides information related to update of WUR PNs. The parameter is optionally present if dot11RSNAWURFrameProtectionActivated is true; otherwise not present.
Thank you.
Best Regards,
Rojan
From: Yunsong Yang <yunsongyang1@xxxxxxxxx>
Sent: Thursday, 12 September 2019 3:58 AM
To: Xiaofei Wang <Xiaofei.Wang@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBA@xxxxxxxxxxxxxxxxx; Rojan Chitrakar <rojan.chitrakar@xxxxxxxxxxxxxxxx>; Huang, Po-kai <po-kai.huang@xxxxxxxxx>;
Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>; Joseph Levy <Joseph.Levy@xxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBA] Call for contributions for TGba F2F at Hanoi, Vietnam
Hi Xiaofei,
Receiving an unsolicited WUR Mode Setup frame should be reported to the SME by using .confirm, but not .indication primitive, because the unsolicited WUR Mode Setup may contain the WUR Mode element and WUR Operation element.
The .indication primitive doesn't contain the WUR Operation parameter and therefore can not be used for conveying the WUR Operation element received, unless we add one.
I will not be in Hanoi. I recommend that you discuss with the group to first determine which primitive should be used from semantics PoV before deciding on whether to add a WUR Operation parameter to the .indication primitive
or not. I will be happy to follow this up via e-mail. Thanks.
Dear Yunsong,
Thank you for your review.
Originally I had “in response to a WUR Mode Setup frame transmitted by the STA, or that is an unsolicited WUR Mode Setup frame.” But I deleted the last
part before sending out because of the following reasoning:
From the reading of the .indication primitive, it seems that the unsolicited WUR Mode Setup frame is handled there. For example, for the .indication primitive,
it says
“6.3.122.4.3 When generated
This primitive is generated by the MLME when a WUR Mode Setup frame is received.
6.3.122.4.4 Effect of receipt
On receipt of this primitive, the SME should operate according to the procedure in 29.8.2 (WUR mode setup).”
In addition, for the .comfirm primitive it says it is a result of a .request primitive and therefore it is probably not for unsolicited WUR Mode Setup frame.
But I think it is very important that we use precise language for the MLME primitives to differentiate the various primitives.
I plan to discuss this issue during the F2F meeting since there seems to be some confusion about the unsolicited WUR Mode Setup frame case.
Best regards,
Xiaofei Clement Wang • Principal Engineer • InterDigital
2 Huntington Quadrangle, Melville, NY, 11801 • T: +1 631-622-4028
From: *** 802.11 TGba - WUR- Wake-up Radio Operation *** <STDS-802-11-TGBA@xxxxxxxx>
On Behalf Of Yunsong Yang
Sent: Wednesday, September 11, 2019 13:06
To: STDS-802-11-TGBA@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBA] Call for contributions for TGba F2F at Hanoi, Vietnam
Hi Xiaofei,
Thank you for preparing this CR. I think we should ensure tnat the amended text also covers the case of receiving unsolicited WUR Mode Setup frame. Therefore, attached please see
my comment and proposed modification on your text. Thanks.
Dear Minyoung,
I have one contribution:
11-19/1539 CR for CID 3356 Xiaofei Wang (InterDigital)
Best regards,
Xiaofei Clement Wang • Principal Engineer • InterDigital
2 Huntington Quadrangle, Melville, NY, 11801 • T: +1 631-622-4028
From: Minyoung Park <mpark.ieee@xxxxxxxxx>
Sent: Tuesday, September 10, 2019 18:00
To: STDS-802-11-TGBA@xxxxxxxxxxxxxxxxx
Cc: Yongho Seok <yongho.seok@xxxxxxxxx>; Alfred Aster <asterjadhi@xxxxxxxxx>; Steve Shellhammer <sshellha@xxxxxxxxxxxxxxxx>;
Suhwook Kim <suhwook.kim@xxxxxxx>; Xiaofei Wang <Xiaofei.Wang@xxxxxxxxxxxxxxxx>; Leif Wilhelmsson R <leif.r.wilhelmsson@xxxxxxxxxxxx>;
Woojin Ahn <woojin.ahn@xxxxxxxxxxxxxx>
Subject: Call for contributions for TGba F2F at Hanoi, Vietnam
Dear all,
If you have contributions on the comment resolution, please send me the following information:
DCN, Title, Author (affiliation)
The following table shows the unresolved CIDs and assignees. Currently we have total 28 unresolved CIDs. If you see your name in the table, please make sure you prepare resolutions
for the f2f meeting. If you cannot provide resolutions to the comments, please let me know so that we can reassign them to others you can resolve the comments.
|
Row Labels
|
Count of Assignee
|
|
Yongho
|
9
|
|
Woojin
|
4
|
|
Alfred
|
4
|
|
Steve
|
4
|
|
Po-Kai
|
2
|
|
Suhwook
|
2
|
|
Xiaofei
|
1
|
|
Leif
|
1
|
|
Minyoung
|
1
|
|
Grand Total
|
28
|
To unsubscribe from the STDS-802-11-TGBA list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBA&A=1
To unsubscribe from the STDS-802-11-TGBA list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBA&A=1
To unsubscribe from the STDS-802-11-TGBA list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBA&A=1
|