| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
That would be
change the name of the field to ‘Sounding Dialog Token Number’ and change the description in D3.0 P89L10 to: The value of the Sounding Dialog Token
Number field is the value of the Sounding Dialog Token
Number subfield in the Ranging
10 NDP Announcement frame corresponding to the measurement sounding phase in which the
reported RSTA timestamps were measured (see 11.21.6.4.3 (TB Ranging measurement exchange)
12 and 11.21.6.4.8 (Measurement exchange in Passive TB Ranging mode)). (#1103, #3143)) From: Erik Lindskog
Hi Jonathan, Regarding the proposed resolutions to CID 5253.
I was thinking it would be clearer if we changed of the name of the ‘Dialog Token’ field here to ‘Sounding Dialog Token’ as this is what it is specified to contain.
However, I see that for ‘Location Measurement Report frame format’ we also have a ‘Dialog Token’ field that I think for non-TB and TB Ranging is copied from the ‘Sounding Dialog Token
number’. Maybe there is sort of a backwards consistency requirement here with the REVmc ranging. Maybe what we could do is to at least change in the description of the Dialog Token field
in D3.0 P89L10 to: The value of the Dialog Token field is the value of the Sounding Dialog Token
Number field in the Ranging
10 NDP Announcement frame corresponding to the measurement sounding phase in which the
reported RSTA timestamps were measured (see 11.21.6.4.3 (TB Ranging measurement exchange)
12 and 11.21.6.4.8 (Measurement exchange in Passive TB Ranging mode)). (#1103, #3143)) Though maybe we should indeed change to use the term the ‘Sounding Dialog Token Number’ here as we are using this term in Figure 9-64lb—Trigger Dependent Common Info subfield of Ranging Trigger on page 47 in
D3.0. In this case we would change the name of the field to ‘Sounding Dialog Token Number’ and change the description in D3.0 P89L10 to: The value of the Sounding Dialog Token
Number field is the value of the Sounding Dialog Token
Number field in the Ranging
10 NDP Announcement frame corresponding to the measurement sounding phase in which the
reported RSTA timestamps were measured (see 11.21.6.4.3 (TB Ranging measurement exchange)
12 and 11.21.6.4.8 (Measurement exchange in Passive TB Ranging mode)). (#1103, #3143)) Erik From: *** 802.11 TGaz - NGP - Next Generation Positioning *** [mailto:STDS-802-11-TGAZ@xxxxxxxxxxxxxxxxx]
On Behalf Of Segev, Jonathan Hello all, TGaz editor identified a set of CIDs that he considered technical or borderline editorial. The CIDs are: 5203, 5252, 5253, 5254, 5261, 5294, 5348, 5353, 5378, 5381, 5444 (11 total).
I’ve reviewed those and suggested resolutions in document 11-21-835 which is uploaded to mentor. I plan to review, if time allows, during the closing slot for TGaz on Mon.
Link to the doc. on Mentor:
https://mentor.ieee.org/802.11/dcn/21/11-21-0835-00-00az-lb253-group-cr.docx Feedback is appreciated. Best Regards, Jonathan Segev, Cell (WhatsApp): +1-408-203-3337 To unsubscribe from the STDS-802-11-TGAZ list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAZ&A=1 To unsubscribe from the STDS-802-11-TGAZ list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAZ&A=1 |