Sending this over the reflector.
See below, in CID 3266 I had proposed an editorial re-write of the secure LTF section. I can try a first cut and have folks review it and then polish it with Roy’s help.
If you want to volunteer to help with this, let me know. My plan is detailed in CID
3266, so if you have other ideas or thoughts on how to do it before I even start, let me know too.
Christian
From: Christian Berger
Sent: Thursday, June 25, 2020 7:53 AM
To: Roy Want <roywant@xxxxxxxxxx>
Subject: RE: [EXT] Fwd: TGaz CID 3266 - need some help with your CID comment
That is fine, assign the CID to me, but I would appreciate your help
😊
I will try to ping some folks to get more buy in.
Christian
Caution: EXT Email
Hi Christian,
Looks like this is becoming more involved than a typical editorial CID.
Do you mind if I assign
CID 3266 to you, and you can add other folk to the proposed solution to build consensus (perhaps include it in yourTGaz CID presentation list).
I'm happy to be one of those people, and will do an editorial pass on the proposed draft before your present.
--Roy
__________________________
Google
Android
Location & Context Team
MTV-PLYM1625-6C3A, Cell: 650 691 3600
Hi Roy,
I can do a first draft. Not sure if we should get more folks involved, I just don’t want to invest a lot of time and then have people go against it somehow.
Christian
Caution: EXT Email
Christian - just surfacing this for you again in case you missed it yesterday. --Roy
__________________________
Google
Android
Location & Context Team
---------- Forwarded message ---------
From: Roy Want <roywant@xxxxxxxxxx>
Date: Tue, Jun 23, 2020 at 4:36 PM
Subject: TGaz CID 3266 - need some help with your CID comment
To: Christian Berger <christian.berger@xxxxxxx>
Hi Christian,
I'm looking at your CID 3266 which has quite an involved set of instructions (see below). I'm prepared to do this but would appreciate it if you could send me a strawman of the
text reorganization you had in mind. I can then validate the changes are just editorial and edit it into D2.3. I think this will be quicker than me attempting a rewrite and missing key points you were trying to make.
|
3266
|
Christian Berger
|
249
|
2
|
11.22.6.4.6.1
|
153
|
22
|
E
|
Y
|
153.00
|
11.22.6.4.6.1
|
|
|
This subclause is very long and hard to read; I would suggest re-organizing it.
|
The space here is not sufficient to give a detailed description of a comment resolution, but I would make the following points: i) start with a general
section describing the differences to the non-secure case. ii) Then have the description of Figure 11-36n to describe the regular case, iii) then explain the NPD-A and NDP transmission parameters, iv) last have the error recovery. Also consider moving both
non-TB and TB description of NDP transmission ot a separate (joined) subclause similar to non-secure case. Finally to align with non-secure case, consider re-organizing to put TB mode first.
|
__________________________
Google
Android
Location & Context Team
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
|