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

Re: [STDS-802-11-TGBK] [TGbk] Follow-up on the D2.0 MDR resolution discussion 7/9

Hi Roy,

 

See below in-line to yours, marked JS

 

From: Roy Want <roywant@xxxxxxxxxx>
Sent: Tuesday, July 9, 2024 6:22 PM
To: STDS-802-11-TGBK@xxxxxxxxxxxxxxxxx
Cc: Segev, Jonathan <jonathan.segev@xxxxxxxxx>
Subject: [TGbk] Follow-up on the D2.0 MDR resolution discussion 7/9

 

Dear TGbk:

 

Thank you for the discussion on the D2.0 MDR issues that still need resolution. We resolved 5 of the 7 questions with just 2 remaining, see link below:

 

https://mentor.ieee.org/802.11/dcn/24/11-24-0879-03-0000-ieee-p802-11bk-d2-0-mandatory-draft-review-mdr-report.docx

 

The remaining questions are listed below for your convenience, referencing D2.0.

 

1) P32.21, is this “may” correct?  Is there more that should be specified?  (Such as, if the bandwidth may be 320 MHz, may it also be something else worth stating?)

 

èNo change. BTW, it is out of scope of MDR.  TGbk Editor to bring this item to the TG for discussion (if è when?).

TG RESOLUTION: TBD

[JS] the Format and Bandwidth field referred to in P.32L.21 is the one in the Ranging Parameters.

The intent paragraph which includes the “If” statement is to describe the normal behavior for 320MHz.

“If the IFTMR frame included a 320MHz Ranging subelement…” the inclusion of 320MHz ranging subelement is not a certainty, but a possibility.

Hence should remain an IF and not changed to a WHEN (when is used to express a certainty or high likelihood and 320MHz FTM session is not of higher probability than any other BW).

RECOMMENDED RESOLUTION: Reject.

 

2) P100.12, is an adjective missing in the first phrase of, “Transmission … may start if ..”?  Compare to the “and” phrase, which is “shall start _immediately_ if…”

èTGbk to bring this item to the TG for discussion (may reverse the order?)  

TG RESOLUTION: TBD

[JS] The same exact statement exists and used for the transmission of the following protocols:

  1. 802.11-2012 Timing Measurement (11v using management and control frames) HT
  2. 802.11-2016 Fine Timing measurement (management and control frames) HT and VHT (and other PHYs)
  3. 802.11az – 2022 Fine Timing Measurement (using HE Ranging NDP and HE TB Ranging NDP frames). HT VHT HE DMG (additional PHYs not specified).

Sentence seems technically correct and any grammatical suggestion should be done in uniform to all other PHYs.

RECOMMENDED RESOLUTION: Reject.

 

Please propose solutions to these points over email to achieve a consensus before the Montreal meeting. I'll then incorporate them into 879r4 and we can motion approval of the document next week.

 

Thank you,

 

--Roy Want (Tech Editor)

 

__________________________

Google Android
Location & Context Team

MTV-PLYM1625-6C3A,  Cell: 650 691 3600

 

 

To unsubscribe from the STDS-802-11-TGBK list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBK&A=1