| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Editors' Reflector ---
Hello Dan, Thanks for this. Some observations from me: 1.
Changing “may” to anything else requires care. In this case we’re not making editorial changes. We have done our job
in the MDR if we report the issues, although it’s obviously better to have a proposed resolution.
a.
Each needs to be considered in its merits. And either
i. Reword into declarative language (may contain -> optionally contains;
contains)
ii. Move a description of behaviour (may do) into clause 9/10
b.
Note that merely rewording “may” to “is allowed to” is generally not allowed. If you need to grant permission to do something,
then that needs to be in clause 9/10. 2.
Your point on the Bibliography:
a.
I think the heading is OK per IEEE-SA style. All Annexes are marked either informative or normative.
b.
Normative references should go in Clause 2, not here. Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) Tel: +1 (408) 2397485 (mobile, USA) ---------------------------------------------- From: Gal, Dan (Dan) [mailto:dan.gal@xxxxxxxxxxxxxxxxxx]
Hi Adrian, Attached please find my initial report of the MDR of REVmc D3.0 review. Your kind comments and improvement suggestions would be greatly appreciated. WRT to section 8 of the draft D3.0; I was wondering about the frequent use of “may” in the description of MAC messages. It is somewhat confusing
whether the “may” in many cases means “allowed to”, or rather “can do” or even just are an indications of the “likelihood” of a protocol event or message content to occur. I bet many 802.11 MAC designers are a bit confused as well…
J So, I have made a few suggestions to modify the language in some of the cases (in section 8 of D3.0) where the language seemed (to me) describing
a normative behavior (of STA and AP), but I am not a hundred percent sure that they are correct. Please review and advise. Thanks and best regards, Dan
From: *** IEEE stds-802-11-editors List *** [mailto:STDS-802-11-EDITORS@xxxxxxxx]
On Behalf Of Stephens, Adrian P --- This message came from the IEEE 802.11 Editors' Reflector ---
All –
(To answer Emily’s question) Your output is a Word document, based on the 802.11 template, that I will cut and paste into a submission. You can use lists, tables, etc… as you wish to
record your findings. The exception is those working with the MIB. They can record their findings either as a tracked changes version of the mib.txt, or as an updated text file.
However, if the changes are small in number, I would prefer to see this cut down to show only the changed parts. The REVmc D3.0 .txt file is there for your convenience to use with AntConc for regular _expression_ searches. You don’t have to use it. Please don’t send me
a marked up copy of the .txt file :0). Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) Tel: +1 (408) 2397485 (mobile, USA) ---------------------------------------------- From: *** IEEE stds-802-11-editors List *** [mailto:STDS-802-11-EDITORS@xxxxxxxx]
On Behalf Of Stephens, Adrian P --- This message came from the IEEE 802.11 Editors' Reflector ---
Thank you all for your participation in the REVmc MDR. Notes from our meeting are shown below. All please note that you are signed up for a task of review work. This is due end 2nd July AOE (anywhere on earth). I have an action to prepare .txt and MIB documents, which should be available tomorrow. I’ll send an email to this reflector. Notes:
1.
Agenda
a.
Discuss the purpose of MDR
b.
Briefly review the MDR process documentation -
MDR 11/615r5 Process
c.
Style Guide 09/1034r7
d.
Peter will present his work groupings
e.
Sign up individuals to a work grouping
f.
Agree a plan in terms of due date for initial findings, plus a review meeting.
2.
Present
a.
Yongho
b.
Edward
c.
Emily
d.
Peter
e.
Alfred
f.
Donald
g.
Adrian
3.
Apologies
a.
Jiamin Chen
b.
Dan Gal
4.
Issue Tasks
a.
MIB/References to MIB - 2 units
i.
Compile MIB - process 2.4 item 3 (Yongho)
ii.
Check references to MIB (Alfred)
1.
Style 2.15
b.
ANA/Numbering (Donald)
i.
Can check ANA numbering
1.
Process 2.4 item 2
ii.
Heading/Figure/Table/Equation numbering is probably doesn't need checking
c.
Figures/Tables/Equations (Emily)
i.
Style of how figure is drawn doesn't match style
ii.
Font size consistency / readability
1.
Style 2.18
iii.
Equations require PHY expertise
d.
Hyphenation/math (Peter)
i.
Style Section 2.10
ii.
Section 2.11 terminology consistency applied
iii.
Section 2.10
e.
Terminology e.g. frame vs packet vs PPDU vs MSDU (Edward)
i.
Style: 2.1.2
ii.
Style: 2.8
iii.
Style: 2.2
iv.
Style: 2.3
f.
Terminology - 2 (Jiamin)
i.
Style 2.4
ii.
Style 2.9
1.
Exclude 2.9.2, 2.9.3, 2.9.4
iii.
Style 2.13
g.
Clause-specific (Dan)
i.
Style 3.2 - normative verbs in 4.
ii.
Style 3.3
iii.
Style 3.5
iv.
Style 3.6
5.
Planning
a.
2nd July deadline for findings
b.
Review meeting
i.
9 am pacific, Friday 11th
6.
Tools
a.
"antconc" will do regular _expression_ searching on a text file
b.
Adrian to provide .txt files for
i.
Entire draft
ii.
MIB Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) Tel: +1 (408) 2397485 (mobile, USA) ---------------------------------------------- From: Peter Ecclesine (pecclesi) [mailto:pecclesi@xxxxxxxxx]
Some information for the call MDR discussion June 18, 2014 Style Guide 09/1034r9 MDR 11/615r5 Process Recent MDRs 11/872 aa, 11/873 ae, 11/874 ad, 13/451r2 af MDR groupings (615r5) MIB/References to MIB ANA/Numbering Figures/Tables/Equations Hyphenation/math Terminology e.g. frame vs packet vs PPDU vs MSDU REVmc Draft 3 3581 pages Clauses 2, 3 59 pages 4, 5 80 6, 7 416 pages 8 675 pages 9 290 pages 10 330 pages 11, 12, 13 307 pages PHYs 468 pages Annexes a, B 196 pages MIB 486 pages PHY annexes F, L, S 98 pages From: Stephens, Adrian P [mailto:Adrian.P.Stephens@xxxxxxxxx]
Dear 802.11 editors, A reminder to all 802.11 editors that we have this kick-off meeting for the 802.11REVmc mandatory draft review (MDR) tomorrow. Based on the response at the May session, I think most folks are committed to help with this activity. Thank you all, that should keep individual tasks to manageable proportions. Peter is preparing an initial grouping of the work that should take 1-2 days for each group, with the expectation that individuals will sign up for one of these groups at the prep meeting. If you cannot attend the meeting, but are willing to contribute to the MDR, please let me know before the meeting. Here’s what I’m expecting we’ll do tomorrow:
1.
Discuss the purpose of MDR
2.
Briefly review the MDR process documentation
3.
Peter will present his work groupings
4.
Sign up individuals to a work grouping
5.
Agree a plan in terms of due date for initial findings, plus a review meeting. The output of the process will be a joint report to TGmc, which will result in changes to REVmc D4.0. Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) Tel: +1 (408) 2397485 (mobile, USA) ---------------------------------------------- -----Original Appointment----- Based on the doodle responses received so far, this is the most popular time. Purpose of meeting: To create plan, work assignments to perform 802.11 REVm mandatory draft review. ......................................................................................................................................... Join by phone +1(916)356-2663 (or your local bridge access #) Choose
bridge 5. (Global) English (United States)
Conference ID: 865523407 [!OC([1033])!] ......................................................................................................................................... _______________________________________________________________________________
IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.
SELF SERVICE OPTION: Point your Browser to -
http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.
Further information can be found at:
http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________
_______________________________________________________________________________
IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.
SELF SERVICE OPTION: Point your Browser to -
http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.
Further information can be found at:
http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________
IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand. SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button. Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________ |