-----------
CommentID:  489
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
The use of term "contention access period": There is already a term "contention period" for the same concept that is well known in 802-wireless community term.
CommentEnd:  

SuggestedRemedy:  
Replace all occurrences of "contention access period" with "contention period"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1843
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
6.	(E) Page 185, line 2: replace 'part of hereof' by 'part hereof'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1842
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
5.	(E) Page 185, line 52: replace 'life cycle' by 'life time'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1841
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
4.	(E) Page 185, line 44: replace 'provided' by 'indeed provided'
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1840
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
3.	(E) Page 184, line 27: replace 're-initialization' by 're-initialization of the device'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1836
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Statically identifying the device Id with the IEEE MAC address gives rise to anonymity concerns, since then the device Id identifies the device in a static and traceable way. One distinguishes a number of issues, including (1) Tracking of devices and thereby their users; (2) trace-ability of the manufacturer of the WPAN-chip, which might lead to passively monitoring which devices are owned by whom (e.g., for device theft). (Note: lack of anonymity was a major criticism of the original Bluetooth specification. It led to a change requirement by Ericcson, after this privacy issue had been advertised on the front cover of the NY Times).
CommentEnd:  

SuggestedRemedy:  
Do not statically identify the device Id with the IEEE MAC address. Instead, add a separate section on how the device Id should be interpreted.  Add a separate section on how the device Id should be interpreted, thus leaving room for dynamic linkage of the device Id to a (pseudonym) of the IEEE MAC address of the device. As for now, this section would just describe that the device Id equals the IEEE MAC address (so, we have compliance with the current draft and formats). If anonymity concerns give rise to a change requirement, one only needs to change this added section to cater for the anonymity requirement, not all occurrences of the device Id throughout the whole standard (i.e., it is acts as an abstract module). Of course, we should give the proper format and, in particular, the required length of the device Id proper consideration. The current 48-bit device Id might not be enough to provide anonymity guarantees (if these are required).
RemedyEnd:  

Response:  
PROPOSED REJECT. The changes required at this time will be similar to any changes required when it is necessary to implement this capability.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1822
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
The list of editorial attributions must be changed to include the following contributors as follows:Gregg Rasor, Security and Privacy Committee ChairAri Singer, Security and Privacy Assistant EditorRene Struik, Security and Privacy Assistant Editor
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1772
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The backward compatibilty or relationship with 802.15.1 devices is not addressed
CommentEnd:  

SuggestedRemedy:  
Please address the compatibility/relationship issue clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Backwards compatibility is explained in the draft text to be added to the draft found in 00000r0P802-15-3-Annex_Coexistence.pdf. Interoperability is not mandated, and not prohibited.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1755
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The backward compatibilty or relationship with 802.15.1 devices is not addressed
CommentEnd:  

SuggestedRemedy:  
Please address the compatibility/relationship issue clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT.  Backwards compatibility is explained in the draft text to be added to the draft found in 00000r0P802-15-3-Annex_Coexistence.pdf. Interoperability is not mandated, and not prohibited.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1746
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext {201, 865, 668, 661}
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The backward compatibilty or relationship with 802.15.1 devices is not addressed
CommentEnd:  

SuggestedRemedy:  
Please address the compatibility/relationship issue clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Backwards compatibility is explained in the draft text to be added to the draft found in 00000r0P802-15-3-Annex_Coexistence.pdf. Interoperability is not mandated, and not prohibited.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1739
CommenterName:  Golmie, Nada
CommenterEmail:  nada@nist.gov
CommenterPhone:  (301) 975-4190
CommenterFax:  
CommenterCo:  NIST
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
The current TG3 draft does not address the issue of coexistence between 802.15.3 devices and other devices in the band such as 802.11b and Bluetooth.
CommentEnd:  

SuggestedRemedy:  
1) Add a clause or subclause that describes the interference problem resulting from having 802.15.3 devices co-located with 802.11b, Bluetooth devices. Performance results quantifying the impact of interference can be added as well. 2) Include solutions to remedy the problem.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The proposed informative Annex (00000r0P802-15-3-Annex_Coexistence.pdf) has a description of the coexistence methods that are available in the draft. Also see 02/041r2 for a presentation and additional text on this issue. For 802.15.4 compatibility see subclause 6.9 in 00000D13P802-15-4__Draft_Standard.pdf. In addition the informative Annex will have information regarding performance.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1730
CommenterName:  Lansford, Jim
CommenterEmail:  jimlansford@mobilian.com
CommenterPhone:  +1 405 377 6170
CommenterFax:  +1 405 747 5229
CommenterCo:  Mobilian
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
Despite the fact that 802.15.3 is described as a WPAN under the umbrella of the WPAN working group (802.15), there is no mention of interference, interoperability, or coexistence with the only other WPAN standard to go through letter ballot, 802.15.1.  This specification has no mention of how it will maintain QoS in the presence of significant other interference in the same band: Bluetooth, microwave ovens, etc.  Even in the "802.11b coexistence" mode, there is no method described that says how the 802.15.3 system will be placed in this channel plan. While older specifications such as 802.11b could have been developed without recognition of other users of the band, IEEE would do the industry a disservice by publishing specifications whose ability to coexist with other IEEE wireless standards was unknown (at best) or poor (at worst).
CommentEnd:  

SuggestedRemedy:  
The specification needs a coexistence section that describes: a) mechanisms for QoS maintenance in the presence of interference (with informative sections that quantify the problem), b) coexistence mechanisms for 802.15.1/Bluetooth, and c) channel selection algorithms that not only address 802.11b coexistence in an automatic way, but also describe avoidance mechanisms for microwave ovens and other types of interference (both periodic and non-periodic).
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The proposed informative Annex (00000r0P802-15-3-Annex_Coexistence.pdf) has a description of the coexistence methods that are available in the draft. Also see 02/041r2 for a presentation and additional text on this issue. For 802.15.4 compatibility see subclause 6.9 in 00000D13P802-15-4__Draft_Standard.pdf. Accept informative text provided by the commenter on QoS issue.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  1/24/2002
VoterStatus: 

-----------
CommentID:  1728
CommenterName:  Liang, Jie
CommenterEmail:  jliang@ieee.org
CommenterPhone:  214 480 4105
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
There are no coexistence study so far regarding the coexistence property of a device implementing this specification. It is well known problem that 2.4GHz ISM band is already crowded with WLAN and BT devices. It is important to show that devices implementing this draft can coexist with the incumbent.
CommentEnd:  

SuggestedRemedy:  
1. Get TG2 involved in evaluating the coexistence property of the draft. 2. Add sections in the draft to explain what are the tools that can be used to have better coexistence properties. For instance, channel assessment and selection, power control, etc.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The proposed informative Annex (00000r0P802-15-3-Annex_Coexistence.pdf) has a description of the coexistence methods that are available in the draft. Also see 02/041r2 for a presentation and additional text on this issue. For 802.15.4 compatibility see subclause 6.9 in 00000D13P802-15-4__Draft_Standard.pdf. TG2 has been consulted and they will help with analysis.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1844
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
7.	(TR) Page 185, line 6: in front of the sentence 'To facilitate…' insert the following sentence: 'It will accept any commands from an authenticated device.' Comment: the current text does not cover the consequences of a successful authentication.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Page 185, line 6: in front of the sentence 'To facilitate…' insert the following sentence: 'It will accept any commands from an authenticated device.'
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  485
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
R_ALFVIN-NOTE: THIS COMMENT WAS SUBMITTED INCOMPLETE/BLANK AS SHOWN. 
R_ALFVIN-NOTE: THE COMMENT TYPE WAS NOT SELECTED BY THE SUBMITTER.
CommentEnd:  

SuggestedRemedy:  
R_ALFVIN-NOTE: NO REMEDY WAS SUBMITTED WITH THIS COMMENT.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  94
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Clause heading do not follow IEEE Standards Sytle Manual.  Only the first word is to be capitalized.
CommentEnd:  

SuggestedRemedy:  
Follow the IEEE Standards Style Manual for Clause headings. Partial list of where corrections need to be made (5.3.7, 5.3.8, 6.3.8, 6.3.9, 6.3.16, 6.5.3, 10.3.2, 11.2-11.2.6, 11.2.8, 11.3.2-11.3.4, 11.4, 11.5.2, 11.5.3, A.1.1, B.3.1, B.3.2)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  520
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
use of "what" and "how many" in colloquial sense
CommentEnd:  

SuggestedRemedy:  
this draft has about 6 use of "what" and a couple of "how many" used in colloquial sense. Please change those sentences appropriately. an example is line 16, page 151.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  768
CommenterName:  Huckabee, Laura
CommenterEmail:  laura.huckabee@timedomain.com
CommenterPhone:  256.428.6422
CommenterFax:  256.759.0678
CommenterCo:  Time Domain Corporation
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
It is not clear that <= 1 second connect time is achievable (especially with existing security clauses).
CommentEnd:  

SuggestedRemedy:  
Clarify in Clause 5 all connection time issues.  Review impact of security to see if connect time is attainable.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  798
CommenterName:  Kinney, Patrick
CommenterEmail:  pat.kinney@ieee.org
CommenterPhone:  724-425-7952
CommenterFax:  
CommenterCo:  Invensys
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Many points in the MAC sections refer to 2.4 GHz.  These would need to be changed if another PHY is implemented
CommentEnd:  

SuggestedRemedy:  
remove all references to 2.4 GHz
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1327
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
"Only the DEV that is receiving a unicast stream addressed to it shall send a delayed-ACK command." This should specify that the stream must be on with ACK Policy of Delayed ACK.
CommentEnd:  

SuggestedRemedy:  
Change sentence to: "Only the DEV that is receiving a unicast stream addressed to it swith ACK Policy set to delayed ACK shall send a delayed-ACK command."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1356
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The standard does not address the issue of wireless coexistence sufficiently.
CommentEnd:  

SuggestedRemedy:  
A clause on coexistence needs to be added to the 802.15.3 standard.  The clause should include, at a minimum, the following sub-clauses: 1. A sub-clause listing which wireless 802 networks are approved for operation in the same location as an 802.15.3 WPAN, and which are not approved for operation in the same location as an 802.15.3 WPAN. 2. A sub-clause quantifying the performance of an 802.15.3 WPAN that a user can expect, in the presence of the various approved wireless 802 networks. 3. A sub-clause quantifying the performance of the various approved wireless 802 networks that a user can expect, in the presence of an 802.15.3 network.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1358
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The terms piconet and WPAN both seem to mean the same thing.  The term piconet is not defined in clause 3 and wireless personal area network is also not defined, so it is difficult to be sure if this is the case.
CommentEnd:  

SuggestedRemedy:  
If the two terms mean the same thing then use only one throughout the standard.  I would recommend WPAN since it is the one most often used within the IEEE.  Drop the term piconet with the standard and use only WPAN.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The committee has decided to use piconet in the 802.15.3 draft since it was also commonly used in the 802.15.1 draft as well. WPAN use will be limited or eliminated as much as possible.

Definition of piconet: A collection of one or more logically associated devices that share a single identifier with a common coordinator.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/19/2002
VoterStatus: 

-----------
CommentID:  1366
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
48 bit and 8 bit address names are confusing and inconsistent.  AD-AD sounds like something that kids take Ritalin for.  Address is usually reserved in 802 standards for 48 bit MAC address.
CommentEnd:  

SuggestedRemedy:  
Change AD-AD to AID - Association ID. Use "MAC Address" or "Address" for 48 bit 802 address.   Get rid of DEVAddress, AssociDEVAddress, DevID Use AID for all 8 bit addresses - Source AID, Destination AID, etc. Also, SA8, and DA8 would be the AIDs, and SA48 or DA48 would be the 48 bit MAC addresses.   Make this change throughout the doc
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Use resolution as found in comments 565 and 571.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1367
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Source Addreess and Destination Address order is inconsistent.  6.8.1 MAC_DATA.request( DA, SA ) 7.2 Header: [... DA, SA ] 7.4.10 CTA [ SA, DA ]
CommentEnd:  

SuggestedRemedy:  
Always use Destination Address followed by Source Address Change CTA to Destination Address followed by Source Address
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1441
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Half the time we use "an MLME..."  and half the time we use "a MLME..."  Should be "an MLME."  This comment applies to ALL acronyms in the draft.
CommentEnd:  

SuggestedRemedy:  
Change to "an MLME."  Also, change all other uses of "an" and "a" before acronyms to follow the rules based on the first sound, not whether the first letter is a vowel or a consonant.  From  http://webster.commnet.edu/grammar/abbreviations.htm   Using articles with abbreviations and acronyms:         One of the most often asked questions about grammar         has to do with the choice of articles — a, an, the —         to precede an abbreviation or acronym. Do we say an         FBI agent or a FBI agent? Although "F" is obviously         a consonant and we would precede any word that         begins with "F" with "a," we precede FBI with "an"         because the first sound we make when we say FBI is         not an "f-sound," it is an "eff-sound." Thus we say         we're going to a PTO meeting where an NCO will         address us. We say we saw a UFO because, although         the abbreviation begins with a 'U," we pronounce the         "U" as if it were spelled "yoo." Whether we say a         URL or an URL depends on whether we pronounce it         as "earl" or as "u*r*l."
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1482
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
We agreed to change Kus to ms throughout the document.  Looks like only half of the instances got update.  Half still have Kus.
CommentEnd:  

SuggestedRemedy:  
Change all values of Kus to ms.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1577
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
"group addressed frame" should be changed globally to "broadcast or multicast frame" since we never define group addressed frame.
CommentEnd:  

SuggestedRemedy:  
Do a global change from "group addressed frame" to "broadcast or multicast frame"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1695
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
I have concentrated on tech issues in clauses 6, 7, 8, and 11, plus general "typo patrol" throughout the document.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1720
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
No mechanism to deal with the possible overlap of two or more piconets on the same physical channel. This would cause self interference among WPAN devices.  Following scenario should be considered: 1. Two piconet initially established on the same channel when they are far away from each other. 2. How will devices detect presence of other piconet if piconets come within proximity of each other. 3. If it's possible to detect another piconet, there are several options: a. One piconet switches to another channel if available. b. Two piconets merge and become one c. Both piconet want to keep operating independently, however device in one piconet is able to communncate with device in another piconet
CommentEnd:  

SuggestedRemedy:  
MAC clauses add functions for piconets becoming overlap, considering piconets will be moving
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.
Reference Document 02/041r2 for proposed approach.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  95
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Multiple clause headings with the same name.  For example Overview, Scope, Child piconet, and Neighbor piconet.
CommentEnd:  

SuggestedRemedy:  
Modify the clause heading with adjectives that are more appropiate or merge the clauses together, if they are the same.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1850
CommenterName:  Dydyk, Michael
CommenterEmail:  Michael.Dydyk@Motorola.com
CommenterPhone:  480-775-7020
CommenterFax:  480-570-2841
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
The document does not fully address coexistence in the 2.4 GHz band.
CommentEnd:  

SuggestedRemedy:  
Fully address coexistence in the 2.4 GHz band.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/24/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1846
CommenterName:  Dydyk, Michael
CommenterEmail:  Michael.Dydyk@Motorola.com
CommenterPhone:  480-775-7020
CommenterFax:  480-570-2841
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
There are TBDs
CommentEnd:  

SuggestedRemedy:  
Remove the 3 TBDs
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/24/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  97
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Where are the requirements for coexistence with 802.15.1, 802.15.4, and 802.11 a/b?  I have not seen any discussion on solutions for this issue.bb
CommentEnd:  

SuggestedRemedy:  
Requirements needed to meet the intent of the PAR.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The requirements are as stated in the 802.15.3 PAR. The proposed informative Annex (00000r0P802-15-3-Annex_Coexistence.pdf) has a description of the coexistence methods that are available in the draft. Also see 02/041r2 for a presentation and additional text on this issue. For 802.15.4 compatibility see subclause 6.9 in 00000D13P802-15-4__Draft_Standard.pdf.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1790
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The backward compatibilty or relationship with 802.15.1 devices is not addressed
CommentEnd:  

SuggestedRemedy:  
Please address the compatibility/relationship issue clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Backwards compatibility is explained in the draft text to be added to the draft found in 00000r0P802-15-3-Annex_Coexistence.pdf. Interoperability is not mandated, and not prohibited.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1851
CommenterName:  Kerry, Stuart
CommenterEmail:  stuart.kerry@philips.com
CommenterPhone:  408-474-7356
CommenterFax:  408-348-3171
CommenterCo:  Philips
Clause:  00
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
Whereby, I support the fact the specification is required by applications and Industry, and needs to be published within the normal process timeframes, I believe that the current 802.15.3 base specification does not fully address my concerns with regards to coexistence with other published IEEE 802 Wireless Standards.
CommentEnd:  

SuggestedRemedy:  
More consideration needs to be applied to this complex interaction before my NO vote is changed to a YES vote.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. The committee has developed analysis and text that describe the capabilities for coexistence and interoperability for 802.15.3 and 802.15.1 and 802.11b.  The relevant documents are 00000P802-15-3-Annex_Coexistence.pdf and 01/041r2.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/24/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  1/24/2002
VoterStatus: 

-----------
CommentID:  4
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  00
Subclause:  
Page:  0
Line:  
CommentType:  E

Comment:  
Abstract lacks mention that the standard is extensible to include alternate physical layers
CommentEnd:  

SuggestedRemedy:  
add after data types. "and is designed to support addtional physical layers as might be specified at a later time."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1742
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 668
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  107
Line:  36
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Resolved in comments 296.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1786
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  107
Line:  36
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolved as in 1744
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  b
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1768
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  107
Line:  36
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolved as in 1744
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1751
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  107
Line:  36
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolved as in 1744
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1769
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  133
Line:  39
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Resolved by 294.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1752
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  133
Line:  39
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Resolved by 294.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1743
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 668
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  133
Line:  39
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Resolved by comment 294.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1787
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  133
Line:  39
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Resolved by comment 294.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1788
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  175
Line:  31
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolved as in 1744
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1753
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  175
Line:  31
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Clause 9 has been deleted. TBD has been removed.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1770
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  175
Line:  31
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Clause has been deleted.Also closes 1744, 1779, 1753, 1788.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1744
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 668
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  175
Line:  31
CommentType:  TR

Comment:  
There are TBDs.
CommentEnd:  

SuggestedRemedy:  
Please fill in the appropriate values.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Clause 9 has been deleted. TBD has been removed.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1773
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  24
Line:  40
CommentType:  E

Comment:  
Type of ReasonCode is octet (should be Enumeration for consistency's sake).
CommentEnd:  

SuggestedRemedy:  
Change type of ReasonCode to Enumeration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1774
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  29
Line:  37
CommentType:  E

Comment:  
Type of ReasonCode is octet (should be Enumeration for consistency's sake).
CommentEnd:  

SuggestedRemedy:  
Change type of ReasonCode to Enumeration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1775
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  32
Line:  18
CommentType:  E

Comment:  
Type of ReasonCode is octet (should be Enumeration for consistency's sake).
CommentEnd:  

SuggestedRemedy:  
Change type of ReasonCode to Enumeration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1780
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  39
Line:  32
CommentType:  E

Comment:  
ReasonCode undefined (for corresponding MLME primitives)
CommentEnd:  

SuggestedRemedy:  
Define ReasonCode in Table 14;15;15;16
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1781
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  4
Line:  35
CommentType:  E

Comment:  
ReasonCode undefined (for corresponding MLME primitives)
CommentEnd:  

SuggestedRemedy:  
Define ReasonCode in Table 14;15;15;16
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1782
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  42
Line:  10
CommentType:  E

Comment:  
ReasonCode undefined (for corresponding MLME primitives)
CommentEnd:  

SuggestedRemedy:  
Define ReasonCode in Table 14;15;15;16
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1783
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  44
Line:  8
CommentType:  E

Comment:  
ReasonCode undefined (for corresponding MLME primitives)
CommentEnd:  

SuggestedRemedy:  
Define ReasonCode in Table 14;15;15;16
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1776
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  49
Line:  22
CommentType:  E

Comment:  
Type of ReasonCode is octet (should be Enumeration for consistency's sake).
CommentEnd:  

SuggestedRemedy:  
Change type of ReasonCode to Enumeration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1847
CommenterName:  Dydyk, Michael
CommenterEmail:  Michael.Dydyk@Motorola.com
CommenterPhone:  480-775-7020
CommenterFax:  480-570-2841
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  54
Line:  3
CommentType:  E

Comment:  
Editorial
CommentEnd:  

SuggestedRemedy:  
Change from Figure 4 to 3.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/24/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1848
CommenterName:  Dydyk, Michael
CommenterEmail:  Michael.Dydyk@Motorola.com
CommenterPhone:  480-775-7020
CommenterFax:  480-570-2841
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  54
Line:  30
CommentType:  E

Comment:  
Editorial
CommentEnd:  

SuggestedRemedy:  
Change from Figure 5 to 4.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/24/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1777
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  55
Line:  20
CommentType:  E

Comment:  
Type of ReasonCode is octet (should be Enumeration for consistency's sake).
CommentEnd:  

SuggestedRemedy:  
Change type of ReasonCode to Enumeration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1778
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  59
Line:  7
CommentType:  E

Comment:  
Type of ReasonCode is octet (should be Enumeration for consistency's sake).
CommentEnd:  

SuggestedRemedy:  
Change type of ReasonCode to Enumeration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1779
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  00
Subclause:  
Page:  68
Line:  50
CommentType:  E

Comment:  
Type of ReasonCode is octet (should be Enumeration for consistency's sake).
CommentEnd:  

SuggestedRemedy:  
Change type of ReasonCode to Enumeration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1849
CommenterName:  Dydyk, Michael
CommenterEmail:  Michael.Dydyk@Motorola.com
CommenterPhone:  480-775-7020
CommenterFax:  480-570-2841
CommenterCo:  Motorola
Clause:  00
Subclause:  
Page:  93
Line:  47
CommentType:  E

Comment:  
What does older revision of the standard mean?
CommentEnd:  

SuggestedRemedy:  
Change or remove older version
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/24/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1697
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  00
Subclause:  -
Page:  1
Line:  26
CommentType:  E

Comment:  
"TM" is not needed in "WPAN(TM)s" as the first use in the title.
CommentEnd:  

SuggestedRemedy:  
use just "WPAN"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  191
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  
Line:  2
CommentType:  E

Comment:  
The editor comment "ED Note: The standard description of the 802 family of networking protocols will go here." brings up the question how will the 802.15 WG depict the 802 Family as they introduce a 2nd (and 3rd) MAC sublayer to the traditional figure (see 802.15.1/D1.0.1 Figure 1)?  It is important that the WG communicate their Projects and their distinct identities, one solution per problem, etc.  This frontmatter subclause should be short but concise such that the 802.15.xx designations are clear to the public.  The titles are clear now the figure 1 and resultant description of Fig 1 should be modified to communicate our mutiplicity of projects.
CommentEnd:  

SuggestedRemedy:  
I suggest that the Editor add the 'standard description' and submit a modified Figure 1 so that the WG can review and comment.  If the Project 802.15.3 Editors need help e.g., Fig1.eps, etc. please advise.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  192
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  
Line:  48
CommentType:  E

Comment:  
The Table of Contents and Bookmark Annex Titles are incorrectly used.  E.g., "(normative)Service Specific Convergence Sub layer." should read "Annex A (normative) Service Specific Convergence Sub layer."
CommentEnd:  

SuggestedRemedy:  
The Editor needs to review the PDF creation function while in FrameMaker.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  291
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  0
Line:  0
CommentType:  T

Comment:  
Are the use of shall/should/may/can/will/must throughout the document in accordance with IEEE's style?
CommentEnd:  

SuggestedRemedy:  
Review the use of shall/should/may/can/will/must throughout the document to be sure they are used in accordance with IEEE's style.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  286
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  0
Line:  0
CommentType:  E

Comment:  
The the term "IEEE" is reserved for approved standards only.
CommentEnd:  

SuggestedRemedy:  
Remove "IEEE" from the designation "IEEE Draft P802.15.3/D09" in the runningheads.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  285
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  0
Line:  0
CommentType:  E

Comment:  
It was very hard to determine exactly what text changed from D08 to D09 based on the Editor-in-Chief's usage of the FrameMaker change bar feature inside the draft i.e., Format/Document/Change Bars.
CommentEnd:  

SuggestedRemedy:  
When the D10 is produced I require that when all edits are applied and the *.book file is open the FM File/Utilities/Compare Books feature be used to compare the D09 Book to the D10 Book (all the *.fm files should be open too).  The D10 should be released in a clean and compared version; a change bar version can also be released too but again it is hard for this Balloter, and maybe others, to determine exactly what text changes were made. The default for the FM compare utility is that editing marks are shown in color and with a change bar on the left side of the page. The color editing marks are used to indicate delete and insert actions to the draft. The editing marks specifies the location of the change and describes what is being changed either by using red strikethrough (to remove old material) or green underscore (to add new material)." More info: http://ieee802.org/15/pub/SB2/SB2-info.html
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  284
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  0
Line:  0
CommentType:  E

Comment:  
Add the current date to the runningheads by the draft number for additional clarity.
CommentEnd:  

SuggestedRemedy:  
Please produce D10 with the current date.  Note that this commenter can provide a frontmatter and body template to TG3 that uses the PC System Clock automatically date stampiong the draft when the PDF is produced.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  281
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  0
Line:  0
CommentType:  E

Comment:  
The 802.15.3 D09 does not uses uniformity of structure or of style when it comes to lists.  For example subclause 5.1.1. has a dashed list, 6.1 uses a alpabetical listing, and 7.2.8 uses a numeric listing, etc.
CommentEnd:  

SuggestedRemedy:  
I suggest the Editor-in-Chief review the IEEE Standards Style Manual and then entire document should be edited for uniformity.  Also, note that a colon is used to introduce a list only when the words "following" or "follows" are used in the introductory sentence, or if the sentence is complete grammatically.  If the introduction is an incomplete sentence, then a colon is not used.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  235
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  00
Subclause:  00
Page:  0
Line:  0
CommentType:  E

Comment:  
The terms "sub-layer" and/or "sub-clause", used throughout 802.15.3//D09, are spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer" and/or "subclause" throughout 802.15.3/D09, dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1793
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  2
Page:  
Line:  
CommentType:  E

Comment:  
One distinguishes communication behavior and security associations within a piconet (ordinary devices, security managers, and piconet controller), between different piconets (piconet, child piconet, neighbor piconet), and between devices and the external trusted party. The term 'DEV' could therefore be occasionally used to denote things that are not a device, but, e.g., a neighbor piconet, thus causing confusion. Moreover, devices can have different roles. Adopting a more general term avoids this confusion.
CommentEnd:  

SuggestedRemedy:  
Replace the concept 'DEV' by 'entity' or a similarly appropriate term throughout the clause.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1828
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  00
Subclause:  3.4.2.2
Page:  186
Line:  
CommentType:  TR

Comment:  
If disassociation request by a particular device would be automatically honored without evidence regarding the authenticity of this request, one can launch a simple denial of service attack on each device in the piconet.
CommentEnd:  

SuggestedRemedy:  
The details of the disassociation request initiated by the device itself should be specified.Specify the disassociation request protocol in such a way that honoring this request is subject to positive evidence as to the identity of the originator of that request (data origin authentication).
RemedyEnd:  

Response:  
PROPOSED REJECT. Until there is a valid and implementable documented proposal, this cannot be considered.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  Z
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1318
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  7.5.7.1
Page:  124
Line:  31
CommentType:  TR

Comment:  
What language is this in?  "The current beacon number when that primitive is received by the SME is used to calculate the beacon number for the next EPSTime event and inserts that beacon number as EPSNext when building the EPS action request command."
CommentEnd:  

SuggestedRemedy:  
First of all, the referred to primitive, MLME-POWERMANGEMENT.request, is sent by the SME, it is not received by the SME. Next, Please translate  this to English.  It is unreadable.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Separate all of the MLME's for power management using the new compromise proposal with the reduced number of commands.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  721
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  00
Subclause:  8.2.7
Page:  143
Line:  36
CommentType:  TR

Comment:  
The text between lines 36 and 41 is an incorrect description  of the PNC information broadcasting function.
CommentEnd:  

SuggestedRemedy:  
See detailed resolution in doc 02/037r0
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Association Info
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1541
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  8.4
Page:  146
Line:  5
CommentType:  E

Comment:  
Slots have both fixed start time and duration
CommentEnd:  

SuggestedRemedy:  
Change to "During the CFP, the PNC controls the channel access by assigning time slots to individual DEVs with each time slot having a fixed start time and duration."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1548
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  00
Subclause:  8.4.2.1
Page:  147
Line:  16
CommentType:  TR

Comment:  
"The method for choosing the random integer should be unique for each DEV and use the random number generator resident on the DEV."  What does this mean?  We need to choose a unique random number generator for each DEEV?  Or do we just need to choose an unique seed.
CommentEnd:  

SuggestedRemedy:  
Specify that a uniqueue seed is required, not a unique random number algorithm.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Replace "The method for choosing the random integer should be unique for each DEV and use the random number generator resident on the DEV." with
"The random number generated for a DEV should be statistically uncorrelated with random numbers generated by other DEVs."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  61
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  00
Subclause:  Abstract
Page:  
Line:  0
CommentType:  E

Comment:  
The type of equipment 802.15.3 supports is more than "voice and data".
CommentEnd:  

SuggestedRemedy:  
Replace "voice and data" in Absract with "multi-media and data" or just "multimedia".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  78
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  00
Subclause:  multiple
Page:  
Line:  
CommentType:  TR

Comment:  
The repeater service implements an overly complex scheme to increase the number of devices that are allowed to communicate in a piconet. This service does not seem to be necessary nor desired for personal operating space devices that can be repositioned to provide communication capability. In addition, the inclusion of the 11Mbps data rate ensures that any DEV that can communicate with the PNC using the default 22Mbps data rate should also be able to communicate with any other devices that can also communicate with the PNC. The ability to communicate between all devices in a piconet with the POS of the PNC can be provided without the complex repeater service.
CommentEnd:  

SuggestedRemedy:  
Remove all references to repeater service: 7.2.1.10 Repeater field section on page 96 lines 12-16. Remove repeater field in Figure 12 on page 94. In section 7.2.1, change "...SECurity and repeater." to "...and SECurity." on page 94 line 26. Remove Repeater lines from Tables 61 and 62 on page 99. Remove three repeater service commands from Table 65 on page 110. Change "... SEC and Repeater ..." to "... and SEC ..." in line 50 on page 111. Remove Repeater memory from Figure 37 on page 112. Remove lines 22-23 on page 112 describing repeater memory. Change "...SEC and Repeater ..." to "...SEC ..." in line 42 on page 113. Change "...SEC and Repeater ..." to "...SEC ..." in line 38 on page 114. Change "...SEC and Repeater ..." to "...SEC ..." in lines 1-2 on page 116. Remove all of section 7.5.6, 7.5.6.1, 7.5.6.2, 7.5.6.3, Figure 55 and Figure 56 on pages 122 and 123. Remove first two sentences of the fourth paragraph of section 8.1 on page 137, lines 27-28 describing when repeater service can be used. Remove Repeater Memory line from Table 68 on page 139. Remove "including those additional streams needed to support the repeater service" from lines 2-3 on page 153 in section 8.6. Remove last two sentences in section 8.8.6 on page 159, lines 10-12. Remove all of section 8.11 and Figure 92. Remove section 8.13.3.12 on page 171 lines 20-28.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  193
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  01
Subclause:  00
Page:  1
Line:  1
CommentType:  E

Comment:  
The Editor used the wrong FrameMaker Template i.e., framemaker6_frontmatter.fm vs. framemaker6_body.fm therefore causing the running title to be omitted.
CommentEnd:  

SuggestedRemedy:  
Please use the framemaker6_body.fm template and force the running title to be used.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1
CommenterName:  Alfvin, Rick
CommenterEmail:  alfvin@appairent.com
CommenterPhone:  585-214-2464
CommenterFax:  585-781-0952
CommenterCo:  Appairent Technologies, Inc.
Clause:  01
Subclause:  1
Page:  1
Line:  35
CommentType:  T

Comment:  
The Scope section of the Draft should reflect essentially the same wording as the Scope section of the PAR.
CommentEnd:  

SuggestedRemedy:  
Change the Scope section of the Draft to reflect the wording of the Scope section of the PAR.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  283
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  01
Subclause:  1.0
Page:  1
Line:  41
CommentType:  E

Comment:  
The 802.15.1 D09 uses words inconsistently e.g., here "10 meters" and subclause 3.39, page 7, line 4 "10 m", etc.  Also, TX, transmit or transmitter, (RX receive or receiver too) are used inconsistently too.
CommentEnd:  

SuggestedRemedy:  
The later is found in Clause 4 but I suggest the Editor-in-Chief use words consistently.  Also, the find and replace feature in FrameMaker makes it easy to do and more importantly it will be easier for the reader in the end.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  92
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  01
Subclause:  1.1
Page:  1
Line:  37
CommentType:  TR

Comment:  
The scope does not match the one listed in the PAR
CommentEnd:  

SuggestedRemedy:  
Match the scope text with the text of the original PAR
RemedyEnd:  

Response:  
PROPOSED ACCEPT.  
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  484
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  01
Subclause:  1.1
Page:  1
Line:  38
CommentType:  T

Comment:  
The Scope sub-clause is required to be essentially the wording that is found in the PAR.  The wording in this clause was carried over from 802.15.1 and never updated.
CommentEnd:  

SuggestedRemedy:  
Change the wording to be essentially the same as what is found in the PAR.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1368
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  01
Subclause:  1.1
Page:  1
Line:  40
CommentType:  E

Comment:  
POS has bad connotations and should be avoided.
CommentEnd:  

SuggestedRemedy:  
Find an new acronym.  Maybe Personal Access Space (PAS) Do a global change.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  90
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  01
Subclause:  1.1
Page:  1
Line:  44
CommentType:  TR

Comment:  
The term interoperability is defined, yet it is not the one defined in IEEE 100, nor is this definition include in clause 3 (definitions). Clause 1.1 is not an appropriate place to define terms.
CommentEnd:  

SuggestedRemedy:  
Remove this statement from the document.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  765
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  01
Subclause:  1.1
Page:  1
Line:  4648
CommentType:  TR

Comment:  
In this text, co-existance is a stated goal of 802.15.3.  However, further text can not be found to guide designers in anyway.
CommentEnd:  

SuggestedRemedy:  
Co-existance has, in recent years, moved from a nice to have item to a must have item.  Co-existance is even more important in unlicensed bands, as consumer electronics manufacturers have learned through the years, any defect in performance (for what ever reason) will result in a returned product.  A returned product is worse than 'no sale' becuase there are cost involved plus a negative product image established in the consumer's mind.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  91
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  01
Subclause:  1.1
Page:  1
Line:  47
CommentType:  TR

Comment:  
The term coexistence is defined, yet is is not listed in clause 3. Clause 1.1 is not an appropriate place to define terms, nor is this an appropiate document to define the term coexistence.
CommentEnd:  

SuggestedRemedy:  
Remove this statement from the document.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  856
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  01
Subclause:  1.2
Page:  2
Line:  10
CommentType:  E

Comment:  
Missing the word "as" at the end of line 10
CommentEnd:  

SuggestedRemedy:  
networked, such as comput-
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1658
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  01
Subclause:  1.2
Page:  2
Line:  10
CommentType:  E

Comment:  
"such" should be "such as"
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  59
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  01
Subclause:  1.2
Page:  2
Line:  11
CommentType:  E

Comment:  
The list of example devices do not include some of the key devices targeted for 802.15.3 applications: TVs, imaging kiosks, and set top boxes.
CommentEnd:  

SuggestedRemedy:  
Add the following in place of "and printers" "printers, kiosks, set top boxes, TVs and other stationary items that mobile devices may wish to use."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  282
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  01
Subclause:  1.2
Page:  2
Line:  13
CommentType:  E

Comment:  
I recommend not using "&" in the standard.
CommentEnd:  

SuggestedRemedy:  
Change "&" to "and".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  58
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  01
Subclause:  1.2
Page:  2
Line:  3
CommentType:  E

Comment:  
Bad Grammar
CommentEnd:  

SuggestedRemedy:  
Change "for a low complexity" to for low complexity"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  93
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  01
Subclause:  1.2
Page:  2
Line:  3
CommentType:  TR

Comment:  
The Purpose does not match the purpose in the PAR
CommentEnd:  

SuggestedRemedy:  
Replace the current purpose with the text from the original PAR
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  96
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  01
Subclause:  2
Page:  2
Line:  9
CommentType:  T

Comment:  
"Devices included in the definition are those that are carried, worn or located near the body."  This description is not consistent with the definition on page 7, which states that objects within 10 m of device or person.
CommentEnd:  

SuggestedRemedy:  
This current description would exclude stationary objects that are not located on a person, such as a projector.  Make this definition the same as the previous definition.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Replace text with the wording from the definition 3.39.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  854
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  02
Subclause:  
Page:  34
Line:  
CommentType:  T

Comment:  
Subclause 7.4.7 refers to IEEE P1363
CommentEnd:  

SuggestedRemedy:  
Include reference to IEEE P1363
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  483
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  02
Subclause:  2
Page:  3
Line:  16
CommentType:  T

Comment:  
The ASN.1 references are not relevant to this standard.
CommentEnd:  

SuggestedRemedy:  
Delete the references beginning with ISO/IEC 8824-1:1995(E) on line 16 through ISO/IEC 8825-2:1996(E) on line 37.  Also delete ITU-T Recommendation Z.105 on page 4, line 1.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  486
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  03
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Add the definition of Super frame
CommentEnd:  

SuggestedRemedy:  
Add the definition of Super frame
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  858
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  
Page:  5
Line:  50
CommentType:  T

Comment:  
missing a definition
CommentEnd:  

SuggestedRemedy:  
add definition for device-ID: Specifies the MAC address of the DEV under consideration.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Device ID: The MAC address of a device in an 802.15.3 piconet.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  287
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  00
Page:  10
Line:  14
CommentType:  E

Comment:  
The acronym "MLME MAC layer management entity" uses incorrect definition.  The Medium Access Control refers to a sublayer of the Data Link Layer and is not a layer.
CommentEnd:  

SuggestedRemedy:  
I suggest the term "sublayer" be used or "MLME MAC sublayer management entity".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  292
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  00
Page:  5
Line:  34
CommentType:  E

Comment:  
The sentence "For the purposes of this standard, the following terms and definitions apply. IEEE 100, The Authoritative Dictionary of Standards Terms should be referenced for terms not defined in this clause." needs to be italicized.
CommentEnd:  

SuggestedRemedy:  
I suggest you apply italics as indicated: "For the purposes of this standard, the following terms and definitions apply. <italicize>IEEE 100, The Authoritative Dictionary of Standards Terms should be referenced for terms</italicize> not defined in this clause."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  7
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.11
Page:  5
Line:  33
CommentType:  E

Comment:  
It might be a bit confusing using the term "alternate coordinator." Although it is perhaps technically an AC, we should avoid confusion on naming
CommentEnd:  

SuggestedRemedy:  
change from "alternate" to "child piconet"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  8
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.13
Page:  5
Line:  40
CommentType:  E

Comment:  
use of the term units is not consistent with terminology for the standard
CommentEnd:  

SuggestedRemedy:  
change "units" to "devices"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1369
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.15
Page:  5
Line:  45
CommentType:  E

Comment:  
"device" should not be used in the definition of "device"
CommentEnd:  

SuggestedRemedy:  
change definition to "Any entity that..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  9
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.16
Page:  5
Line:  48
CommentType:  E

Comment:  
the word "and" is a typo
CommentEnd:  

SuggestedRemedy:  
change "and" to "an"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  195
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.17
Page:  5
Line:  52
CommentType:  E

Comment:  
The definition sentence does not end in a period: in order to provide data integrity and source authentication
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  859
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.19
Page:  6
Line:  1
CommentType:  T

Comment:  
definition for enhanced power save seems incomplete.  Does differentiate EPS from RPS.
CommentEnd:  

SuggestedRemedy:  
have power management sub-group clarify the definition.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1791
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  03
Subclause:  3.19
Page:  6
Line:  1
CommentType:  E

Comment:  
A the power management ...
CommentEnd:  

SuggestedRemedy:  
The power management ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1758
CommenterName:  Carmeli, Boaz
CommenterEmail:  boazc@il.ibm.com
CommenterPhone:  972-4-8296504
CommenterFax:  
CommenterCo:  IBM
Clause:  03
Subclause:  3.19
Page:  6
Line:  1
CommentType:  E

Comment:  
A the ....
CommentEnd:  

SuggestedRemedy:  
The ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  5
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.2
Page:  5
Line:  8
CommentType:  E

Comment:  
since active is used in power managment, there should be additional text to mention this connection.
CommentEnd:  

SuggestedRemedy:  
after "an enhanced power save" device joints the piconet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  860
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.20
Page:  6
Line:  4
CommentType:  T

Comment:  
Too wordy ...
CommentEnd:  

SuggestedRemedy:  
remove all text in the definition except the following:  the nominal time value for the inter-wake periods for enhanced power save devices.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1759
CommenterName:  Carmeli, Boaz
CommenterEmail:  boazc@il.ibm.com
CommenterPhone:  972-4-8296504
CommenterFax:  
CommenterCo:  IBM
Clause:  03
Subclause:  3.20
Page:  6
Line:  4-5
CommentType:  E

Comment:  
.... save mode-mode.
CommentEnd:  

SuggestedRemedy:  
.... save mode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  861
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.21
Page:  6
Line:  8
CommentType:  E

Comment:  
too wordy
CommentEnd:  

SuggestedRemedy:  
remove the word "very"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  862
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.22
Page:  6
Line:  12
CommentType:  T

Comment:  
Remove second sentence
CommentEnd:  

SuggestedRemedy:  
Remove sentence that starts with "A single enhanced ..."
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1760
CommenterName:  Carmeli, Boaz
CommenterEmail:  boazc@il.ibm.com
CommenterPhone:  972-4-8296504
CommenterFax:  
CommenterCo:  IBM
Clause:  03
Subclause:  3.25
Page:  6
Line:  20
CommentType:  E

Comment:  
.... an entity is who they calim to be.
CommentEnd:  

SuggestedRemedy:  
an entity is who it calim to be.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  196
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.28
Page:  6
Line:  27
CommentType:  E

Comment:  
The definition sentence does not end in a period: is known only by the participating entities
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  197
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.29
Page:  6
Line:  29
CommentType:  E

Comment:  
The definition sentence does not end in a period: 3.29 key transport: a process by which an entity sends a key to another entity
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  198
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.36
Page:  6
Line:  47
CommentType:  E

Comment:  
The definition sentence does not end in a period: 3.36 mutual entity authentication: a process by which two entities authenticate each other
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  10
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.37
Page:  6
Line:  50
CommentType:  E

Comment:  
the term "alternate coordinator" might be confusing
CommentEnd:  

SuggestedRemedy:  
change "alternate" to "neighbor piconet"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  199
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.41
Page:  7
Line:  11
CommentType:  E

Comment:  
The definition sentence does not end in a period: decryption or key establishment procedures depending on the type of key pair
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  200
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.42
Page:  7
Line:  14
CommentType:  E

Comment:  
The definition sentence does not end in a period: given seed that has the statistical properties of a random sequence of bits when the seed is not known
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  201
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.44
Page:  7
Line:  20
CommentType:  E

Comment:  
The definition sentence does not end in a period: encryption or key establishment procedures depending on the type of key pair
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  202
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.45
Page:  7
Line:  22
CommentType:  E

Comment:  
The definition sentence does not end in a period: 3.45 public-key pair: a related pair of data elements including a public key and a private key
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  203
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.46
Page:  7
Line:  26
CommentType:  E

Comment:  
The definition sentence does not end in a period: the integrity of the data being associated
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1370
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.47
Page:  
Line:  
CommentType:  E

Comment:  
Q in Quality of sevvice is capitalized, but not S
CommentEnd:  

SuggestedRemedy:  
Change to Quality of Service
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  204
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.49
Page:  7
Line:  37
CommentType:  E

Comment:  
The definition sentence does not end in a period: 3.49 random number generator: a device that provides a sequence of bits that is unpredictable
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1371
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.49
Page:  7
Line:  37
CommentType:  E

Comment:  
Didn't we change random number generator to pseudorandom number generator?
CommentEnd:  

SuggestedRemedy:  
change random number generator to pseudorandom number generator
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  11
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.50
Page:  7
Line:  39
CommentType:  T

Comment:  
the wording that mentions "excluding the beacon" should be changed as noted below since in reduced power save, most elements (beacon, CAP, MTS) shall be listened to.
CommentEnd:  

SuggestedRemedy:  
change "excluding the beacon" to "when contention free period slots are not allocated to the device"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  730
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  03
Subclause:  3.50
Page:  7
Line:  39
CommentType:  E

Comment:  
Not clear when referening mto a radio transmitter.
CommentEnd:  

SuggestedRemedy:  
Change the word 'level' to consumption'.  Change from 'reduces its power level for part' to 'reduces its power consumption for part'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1372
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.50
Page:  7
Line:  39
CommentType:  E

Comment:  
reduced power save - sounds like it saves less power
CommentEnd:  

SuggestedRemedy:  
eliminate all references to rps because it is normal operation and not a special mode
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  205
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.51
Page:  7
Line:  43
CommentType:  E

Comment:  
The definition sentence does not end in a period: and key distribution
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  206
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.53
Page:  7
Line:  49
CommentType:  E

Comment:  
The definition sentence does not end in a period: been modified and that the owner of the private key signed the data
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  207
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.54
Page:  7
Line:  52
CommentType:  E

Comment:  
The definition sentence does not end in a period: and the source of the signer
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  208
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.55
Page:  7
Line:  54
CommentType:  E

Comment:  
The definition sentence does not end in a period: 3.55 source authentication: authentication of the sender of the data
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1373
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.56
Page:  
Line:  
CommentType:  E

Comment:  
The first version of SDL was issued in 1976.  Anything 25 years old should not be called modern.
CommentEnd:  

SuggestedRemedy:  
Remove "modern" from the definition of SDL
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  209
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.58
Page:  8
Line:  9
CommentType:  E

Comment:  
The definition sentence does not end in a period: tion/decryption and/or integrity protection/integrity verification depending on its intended use
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  12
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.61
Page:  8
Line:  18
CommentType:  T

Comment:  
an eps dev will only look past the beacon on a wake superframe if there is indication in the beacon that it transmit or receive operations are to be performed.
CommentEnd:  

SuggestedRemedy:  
also be available for sending or receiving operations "based on beacon information."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change "and also" to be "and based on beacon information also"
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  857
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  03
Subclause:  3.8
Page:  5
Line:  24
CommentType:  T

Comment:  
unclear sentence structure ... not sure what is the correct definition
CommentEnd:  

SuggestedRemedy:  
have power management sub-group rewrite this sentence
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  729
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  03
Subclause:  3.8
Page:  5
Line:  25
CommentType:  E

Comment:  
The word 'enhances' should be singular.
CommentEnd:  

SuggestedRemedy:  
Make singular.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  6
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  03
Subclause:  3.8
Page:  5
Line:  25
CommentType:  E

Comment:  
enhanced is correct
CommentEnd:  

SuggestedRemedy:  
change from "enhances" to "enhanced"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  194
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  03
Subclause:  3.9
Page:  5
Line:  28
CommentType:  E

Comment:  
The definition sentence does not end in a period: additional information through the creation of a public-key certificate
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  98
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  03
Subclause:  40
Page:  7
Line:  7
CommentType:  T

Comment:  
"other services" - this description does not provide any information about how the piconet coordinator is different from other devices in the piconet.
CommentEnd:  

SuggestedRemedy:  
Need to provide categories of services that are provided by the coordinator.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change the word services to "services, e.g. quality of service, synchronization, association, "
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  99
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  03
Subclause:  48
Page:  7
Line:  30
CommentType:  E

Comment:  
"in a wireless personal area network" - does this definition of quality of service strictness apply to all WPAN systems or just 802.15.3.
CommentEnd:  

SuggestedRemedy:  
Clarify that this is true for only .15.3 systems
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  105
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  04
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Add SFNext to the acronym list.
CommentEnd:  

SuggestedRemedy:  
Define
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1549
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  04
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Why do we have RNG specified?  Should be PRNG.
CommentEnd:  

SuggestedRemedy:  
Delete RNG and replace with PRNG
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  804
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  04
Subclause:  
Page:  10
Line:  
CommentType:  E

Comment:  
missing: OID, PSRC, SFNext
CommentEnd:  

SuggestedRemedy:  
add OID, PSRC, SFNext
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  103
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  04
Subclause:  
Page:  10
Line:  23
CommentType:  E

Comment:  
PCS - common term used in the wireless telecom arena.
CommentEnd:  

SuggestedRemedy:  
Find another TLA.  Maybe PCSL.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  863
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  04
Subclause:  
Page:  10
Line:  41
CommentType:  E

Comment:  
Add term "OID"
CommentEnd:  

SuggestedRemedy:  
OID = object identifier
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  104
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  04
Subclause:  
Page:  10
Line:  49
CommentType:  E

Comment:  
RPS - too similar to revolutions per sec.
CommentEnd:  

SuggestedRemedy:  
Find another TLA.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  101
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  04
Subclause:  
Page:  9
Line:  31
CommentType:  E

Comment:  
Del-ACK - 802.11e had used DlyAck for this term.  To allow new readers to easily determine functionality similarities between different standards, like terms should be the same.
CommentEnd:  

SuggestedRemedy:  
Use DlyAck.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  100
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  04
Subclause:  
Page:  9
Line:  4
CommentType:  E

Comment:  
AD-AD is a strange acronym
CommentEnd:  

SuggestedRemedy:  
I suggest making it AD-ADDR to indicate more clearly that this is a type of address.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1761
CommenterName:  Carmeli, Boaz
CommenterEmail:  boazc@il.ibm.com
CommenterPhone:  972-4-8296504
CommenterFax:  
CommenterCo:  IBM
Clause:  04
Subclause:  
Page:  9
Line:  42
CommentType:  E

Comment:  
EPS set
CommentEnd:  

SuggestedRemedy:  
EPSSet (Consistency with previous acros)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  803
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  04
Subclause:  
Page:  9
Line:  43
CommentType:  E

Comment:  
Remove 'EPS CTA', because 'EPS' and 'CTA' are already there. Otherwise you need to include also other combinations like 'EPS CTR' that can be found in the document.
CommentEnd:  

SuggestedRemedy:  
Remove 'EPS CTA'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  102
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  04
Subclause:  
Page:  9
Line:  54
CommentType:  E

Comment:  
Imm-ACK - to provide a short term try using ImAck.  This would make it consistent with my suggestion in comment 7 (DlyAck).
CommentEnd:  

SuggestedRemedy:  
Use ImAck
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1357
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  04
Subclause:  
Page:  910
Line:  
CommentType:  TR

Comment:  
There are acroynyms for both FER and PER.  I do not see a distiction between a frame and a packet, so FER and PER seem to be the same.
CommentEnd:  

SuggestedRemedy:  
Use either the term Frame or the term Packet.  Then drop the other term throughout the standard. Also, drop either FER or PER from this clause.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Delete PER from acronyms, and change occurrence of PER in 11.6.1 to FER and at all other locaitons in the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  212
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  04
Subclause:  00
Page:  10
Line:  23
CommentType:  E

Comment:  
The term "sub-layer", used in PCS packet convergence sub-layer, is spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer", dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  213
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  04
Subclause:  00
Page:  11
Line:  9
CommentType:  E

Comment:  
The term "sub-layer", used in SSCS service specific convergence sub-layer, is spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer", dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  211
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  04
Subclause:  00
Page:  9
Line:  21
CommentType:  E

Comment:  
The term "sub-layer", used in CPS common part sub-layer, is spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer", dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  210
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  04
Subclause:  00
Page:  9
Line:  8
CommentType:  E

Comment:  
The "ACTIVE CTA" entry is to long (10char) for the standard tab setting for the acronym list clause entry.
CommentEnd:  

SuggestedRemedy:  
Change tab setting so that "ACTIVE CTA" become the new tab (plus some spaces for readability of "active mode channel time allocation") setting for the clause.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  756
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  04
Subclause:  4
Page:  10
Line:  21
CommentType:  E

Comment:  
Need definition of OID
CommentEnd:  

SuggestedRemedy:  
OID    object identifier
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  136
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
The flow of this section needs to be revisited.  It does not read easily.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1765
CommenterName:  Callaway, Ed
CommenterEmail:  ed.callaway@motorola.com
CommenterPhone:  +1-954-723-8341
CommenterFax:  +1-954-557-7187
CommenterCo:  Motorola
Clause:  05
Subclause:  
Page:  13
Line:  
CommentType:  E

Comment:  
Coexistence features of 15.3 are not clearly stated, in a single location.
CommentEnd:  

SuggestedRemedy:  
I suggest that a subclause be added to Clause 5, explicitly describing how paragraph 6 of the PAR ("A goal of the WPAN-HR Task Group will be to achieve a level of interoperability or coexistence with other 802.15 Task Groups . . . it is also the intent of this project to work toward a level of coexistence with other wireless devices . . .") is satisfied.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  871
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  
Page:  17
Line:  54
CommentType:  TR

Comment:  
Need to add a clause 5.6
CommentEnd:  

SuggestedRemedy:  
5.6 Coexistence with other IEEE802 devices - Overview  PHY subcommittee members need to add "overview" text that indicates how 802.15.3 2.4 GHz PHY is going to coexist with 802.11, 802.11b and 802.15.1 devices.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Document 02/041r2 covers proposed coexistence methods.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  107
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  .1.1
Page:  13
Line:  33
CommentType:  E

Comment:  
This paragraph describes a potential implementation.  Unless this point drives a specific requirement to come, it should be excluded.
CommentEnd:  

SuggestedRemedy:  
Remove the paragraph or drive a point.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  108
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  .1.2
Page:  13
Line:  42
CommentType:  E

Comment:  
"For technical reasons, ..." - what technical reasons?
CommentEnd:  

SuggestedRemedy:  
Please explain what the point being driven in this paragraph.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  106
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  1
Page:  13
Line:  16
CommentType:  E

Comment:  
This paragraph does not add anything to the text.
CommentEnd:  

SuggestedRemedy:  
Delete the paragraph or add some content.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  109
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  1.2
Page:  13
Line:  42
CommentType:  E

Comment:  
"Propogation effects ..." - The message of this sentence is unclear.
CommentEnd:  

SuggestedRemedy:  
Clarify point.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1719
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  05
Subclause:  2
Page:  14
Line:  1
CommentType:  TR

Comment:  
Operation of draft HR WPAN requires presence of a PNC. If a person owns two WPAN devices but neither of them are AC capable, then his/her products will be useful only when someone else's PNC shows up and is generous enough to provide the functions/services.
CommentEnd:  

SuggestedRemedy:  
Make basic PNC function (beacon) mandatory so two devices can at least discover each other and exchange capability.
RemedyEnd:  

Response:  
PROPOSED REJECT. The group feels that certains devices for cost consideration will always required a separate PNC for operation. E.g., remote speaker. Resolve as in comment 37
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  b
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  110
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3
Page:  14
Line:  13
CommentType:  E

Comment:  
Bullets should be in same order as they are listed in the subsections.
CommentEnd:  

SuggestedRemedy:  
Order appropriately
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  487
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  05
Subclause:  3
Page:  14
Line:  23
CommentType:  E

Comment:  
use of "multiple levels" is confusing and for some converning
CommentEnd:  

SuggestedRemedy:  
Remove "mulitple" and  "levels"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  111
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3
Page:  14
Line:  23
CommentType:  E

Comment:  
Why is this sentence not a bullet?  It does not have enough information to stand alone as a paragraph.
CommentEnd:  

SuggestedRemedy:  
Make a bullet item
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  112
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.1
Page:  14
Line:  27
CommentType:  TR

Comment:  
A WPAN only requires 1 device?  or is the WPAN formed when a complete response if received from another device interested in joining a piconet?
CommentEnd:  

SuggestedRemedy:  
Clarify
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. . After "superframe." Add "Thus even if there are no associated DEVs, the PNC beaconing is considered to be a piconet."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  114
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.2
Page:  14
Line:  48
CommentType:  E

Comment:  
"authenticate with the PNC and then with any other DEV ..." - the listed models only authenticate with the PNC, not with other DEVs.
CommentEnd:  

SuggestedRemedy:  
Wording issue.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  116
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.2
Page:  15
Line:  7
CommentType:  E

Comment:  
"... e.g. ssh ..."  - what is ssh?
CommentEnd:  

SuggestedRemedy:  
If this term is going to be used, define it in the acronyms.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  115
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.2
Page:  15
Line:  7
CommentType:  TR

Comment:  
Does this paragraph indicate that the defined method could be over written by a higher level protocol?
CommentEnd:  

SuggestedRemedy:  
Need clarification.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete that sentence. "Higher level . . . this standard."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  117
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.3
Page:  15
Line:  12
CommentType:  E

Comment:  
"streamless asynchronous exchange"  and "asynchronous connection" - how do these terms differ?  It is not obvious at this point in the document.  Also, define what is meant by "small amount of data".  Different people would have a different tolerance for data size.
CommentEnd:  

SuggestedRemedy:  
Needs more explanation.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  118
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.4
Page:  15
Line:  20
CommentType:  E

Comment:  
"connection process" - this is not a descriptive discussion.  Is it special?  Are there any key features?
CommentEnd:  

SuggestedRemedy:  
More description desired.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  119
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.5
Page:  15
Line:  24
CommentType:  E

Comment:  
How does a device know when to expect to transmit or receive?  Need more intro information to understand this feature.
CommentEnd:  

SuggestedRemedy:  
More explanation needed.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  120
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.6
Page:  15
Line:  32
CommentType:  T

Comment:  
What if none of the remaining devices have the capability to be a PNC?  Does the piconet disappear?
CommentEnd:  

SuggestedRemedy:  
Finish explaining all cases.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Add the sentence: "If the PNC stops sending a beacon for any reason, after a certain period of time,  the piconet ceases to exist."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  121
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.7
Page:  15
Line:  38
CommentType:  E

Comment:  
A figure showing how a child piconet relates to the original piconet is needed here.
CommentEnd:  

SuggestedRemedy:  
Provide figure
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  490
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  05
Subclause:  3.7
Page:  15
Line:  41
CommentType:  E

Comment:  
PIND?
CommentEnd:  

SuggestedRemedy:  
change "PIND" to "PNID"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  122
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.8
Page:  15
Line:  49
CommentType:  E

Comment:  
A figure showing how a neighbor piconet relates to the original piconet is needed here.
CommentEnd:  

SuggestedRemedy:  
Provide figure
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  123
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.8
Page:  15
Line:  49
CommentType:  T

Comment:  
Description here is the same as a child piconet.  It makes it hard to understand why a neighbor piconet is needed and why it is technically beneficial.  If the complexity is to be added to provide this functionality, there should be a strong explanation of it's benefit.
CommentEnd:  

SuggestedRemedy:  
More explanation needed here to determine benefit of this functionality.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  x
ResponseStatus:  o
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  125
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  3.8
Page:  16
Line:  6
CommentType:  E

Comment:  
What is the last statement saying?  The point is not clear.
CommentEnd:  

SuggestedRemedy:  
Clarify statement
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  124
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  4
Page:  16
Line:  10
CommentType:  E

Comment:  
Figure needed to communicate quickly the available operation modes.
CommentEnd:  

SuggestedRemedy:  
Provide figure
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  127
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  4
Page:  16
Line:  11
CommentType:  E

Comment:  
How does 5.4.1 and 5.4.2 relate to this paragraph.
CommentEnd:  

SuggestedRemedy:  
Check section flow.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  126
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  4
Page:  16
Line:  12
CommentType:  E

Comment:  
"... stopping a piconet." - based on 5.6.1, this should be ending a piconet.
CommentEnd:  

SuggestedRemedy:  
Provide consistency in document terms.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  129
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  4.2
Page:  16
Line:  24
CommentType:  E

Comment:  
The last sentence is awkward.  Is it trying to say that sync streams have different acknowledgement modes?
CommentEnd:  

SuggestedRemedy:  
Provide clarification
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  128
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  5
Page:  16
Line:  27
CommentType:  E

Comment:  
Is this section really the same as 5.4?
CommentEnd:  

SuggestedRemedy:  
Look at combining sections.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  130
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  5
Page:  16
Line:  27
CommentType:  TR

Comment:  
How do the states relate?  Is there a state flow diagram?
CommentEnd:  

SuggestedRemedy:  
Provide state flow diagram.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. State diagrams will be added to the appropriate clauses with a cross reference in clause 5.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  20
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.0
Page:  
Line:  
CommentType:  E

Comment:  
a covering comment should be located at the first instance of CAP to cover MTS operation
CommentEnd:  

SuggestedRemedy:  
Don't know exactly where but add "Throughout this clause, when CAP is referenced, the capabilities that CAP would provide may be alternatively provided by Management Time slots (MTS)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  18
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.0
Page:  13
Line:  
CommentType:  E

Comment:  
It is noted that WPAN and piconet may be used with the same meaning in clause 5. Should we consistent with one or the other? Suggested is piconet although no strong preference except that piconet seems to be general term thoughout the document.
CommentEnd:  

SuggestedRemedy:  
change multiple instances of "WPAN" to "piconet"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  290
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.1
Page:  13
Line:  12
CommentType:  E

Comment:  
The term metropolitan area network (MAN) is used but it is not defined in Clause 4, however, the WAN, LAN, and PAN are.
CommentEnd:  

SuggestedRemedy:  
Add "MAN metropolitan area network" to Clause 4.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  288
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.1
Page:  13
Line:  16
CommentType:  E

Comment:  
The word "wireless" in the sentence "Additionally, WPANs have the expected wireless differences as found in the following paragraphs." should be clarified by adding "medium".
CommentEnd:  

SuggestedRemedy:  
I suggest the sentence be changed to "Additionally, WPANs have the expected wireless medium differences as found in the following paragraphs."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  214
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.1.1
Page:  13
Line:  24
CommentType:  E

Comment:  
The following sentence does not end in a period: conformant PHY transceivers are known to be unable to receive network frames
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  864
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.1.1
Page:  13
Line:  25
CommentType:  T

Comment:  
Don't understand what the text is trying to say  "The PHY is unprotected from outside signals."
CommentEnd:  

SuggestedRemedy:  
add additional text to clarify meaning
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete the itemization point. "the PHY . . . signals."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  215
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.1.1
Page:  13
Line:  26
CommentType:  E

Comment:  
The following sentence does not end in a period: The WPAN has a dynamic topology
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1374
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.1.1
Page:  13
Line:  26
CommentType:  E

Comment:  
First use of DEV shouls say "device (DEV)"
CommentEnd:  

SuggestedRemedy:  
change DEV to device (DEV) Is there some to to automatically check the first use of acronyms?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  289
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.2
Page:  13
Line:  5054
CommentType:  T

Comment:  
The text that describes the components of the IEEE 802.15.3 WPAN is clear but I was expecting a figure that depicted the components of the WPAN being described.
CommentEnd:  

SuggestedRemedy:  
I suggest a figure be created and added that depicts the components of the IEEE 802.15.3 WPAN.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  62
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  05
Subclause:  5.2
Page:  14
Line:  2
CommentType:  E

Comment:  
PNC management does not include security nor extended power save.
CommentEnd:  

SuggestedRemedy:  
Change "quality of service (Q0S)" to "quality of service (QoS), security, and power save"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1659
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.2
Page:  14
Line:  2
CommentType:  E

Comment:  
Should say "Additionally the PNC manages the quality of service (QoS) requirements and authentication requirements of the WPAN."
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  799
CommenterName:  Kinney, Patrick
CommenterEmail:  pat.kinney@ieee.org
CommenterPhone:  724-425-7952
CommenterFax:  
CommenterCo:  Invensys
Clause:  05
Subclause:  5.2
Page:  16
Line:  
CommentType:  T

Comment:  
A node needs to be authenticated, then authorized before it can join a network.  The following statement: "If the beacon indicates a piconet of interest to the DEV, it will attempt to authenticate with the PNC. Upon success, it is considered to be in the WPAN." does not refer to authorization.
CommentEnd:  

SuggestedRemedy:  
add verbage or mechanism to include authorization from a higher layer?
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Change "to athenticate with the PNC." to "to associate with the PNC. If authentication is required, the DEV is also required to authenticate with the PNC."

Authentication process implicitly includes authorization in our draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  131
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  5.2
Page:  16
Line:  42
CommentType:  E

Comment:  
"... (whether it needs to power management or not) ..."  - the "to" is not needed in sentence.
CommentEnd:  

SuggestedRemedy:  
Remove "to".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  132
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  5.2
Page:  16
Line:  43
CommentType:  E

Comment:  
"... a PNC handover could occur." - change the to state "... a PNC handover is possible."
CommentEnd:  

SuggestedRemedy:  
Change suggested above.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1375
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3
Page:  14
Line:  12
CommentType:  E

Comment:  
PAN should be WPAN
CommentEnd:  

SuggestedRemedy:  
Change PAN to WPAN
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  216
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.3
Page:  14
Line:  1315
CommentType:  E

Comment:  
The following sentences do not end in a period: — Allow DEVs to form and terminate PANs — Transport data between DEVs — Authenticate DEVs with each other
CommentEnd:  

SuggestedRemedy:  
Add the periods.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  63
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  05
Subclause:  5.3
Page:  14
Line:  23
CommentType:  E

Comment:  
The data transport does not explicitly support multiple quality of service levels with optional priority. There is an SSCS that could be used to map prioritized QoS service traffic to specific GTS allocations, but this is not done in the MAC.
CommentEnd:  

SuggestedRemedy:  
Remove sentence on line 23. If desired to include a statement about QoS, include as an additional bullet the following: A proceedure to allocate bandwidth and fixed time slots to support establishment of data streams that can guarantee repetitive allocation of bandwidth required for isochronous connections.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1359
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  05
Subclause:  5.3
Page:  15
Line:  
CommentType:  T

Comment:  
The complexity of supporting the child and neighboring piconet capability seems high.  There does not seem to be any significant value in either since it does not increase the overall capacity.
CommentEnd:  

SuggestedRemedy:  
Eliminate the child and neighboring piconet concept or alternativly include a short statement of the utility of these capabilities.
RemedyEnd:  

Response:  
PROPOSED ACCEPT.  Add text that identifies possible uses of child and neighbor piconets. Bob Huang to provide by Monday evening.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  217
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.3.1
Page:  14
Line:  3336
CommentType:  E

Comment:  
The following sentences do not end in a period: — Beacon — Contention Free Period (CFP). This is composed of data streams, either synchronous or isochronous, with quality of service provisions
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  13
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.3.1
Page:  14
Line:  34
CommentType:  E

Comment:  
Figure 1 starting on line 38 includes MTS1 and MTS2 elements but the text does not reflect this
CommentEnd:  

SuggestedRemedy:  
add after CAP - "or an alternate management time slot (MTS) method"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  64
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  05
Subclause:  5.3.1
Page:  14
Line:  3436
CommentType:  E

Comment:  
The use of the CAP and the CFP are optional based on how the PNC allocated time in the superframe. In section 8.4.3.3, page 151, line 4-5 it is noted that "the PNC is responsible for choosing the CAP size if a CAP is used." In section 7.4.2, page 102, line 47-48 states: "The CFP duration is the time allocated to the CFP ... has a range of [0-524280] uS." This makes use of the CAP and the CFP optional as defined by the PNC.
CommentEnd:  

SuggestedRemedy:  
Change the two lines to: - Connection Access Period (CAP) when allocated. - Connection Free Period (CFP) when allocated.  followed by: The superframe will always have a Beacon and at least one CAP or CFP, and may have a Beacon, CAP, and CFP in that order.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  865
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3.1
Page:  14
Line:  35
CommentType:  E

Comment:  
grammatical error
CommentEnd:  

SuggestedRemedy:  
Contention Free Period (CFP), which is composed of ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1383
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3.1
Page:  14
Line:  35
CommentType:  E

Comment:  
synchronous stream should be asynchronous stream
CommentEnd:  

SuggestedRemedy:  
change synchronous to asynchronous.  Actually, do a global search on "synchronous" and either change to asynchronous or isochronous as appropriate.  In 5.3.4 synchronous is used instead of isochronous.  in 5.3.3 synchronous is used instead of isochronous.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1378
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3.2
Page:  14
Line:  48
CommentType:  E

Comment:  
authenticate "and then with any other DEV with which communication is required" is inconsistent with security clause.
CommentEnd:  

SuggestedRemedy:  
Remove reference to authenticating with other DEVs.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  65
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  05
Subclause:  5.3.2
Page:  14
Line:  4849
CommentType:  E

Comment:  
DEVs are not required to authenticate with any other DEV with which communication is required. Instead, once a DEV is authenticated with the PNC, it belongs to the authenticated devices in the piconet and may utilized the resources of the piconet to allocated time slots and communicate with other DEVs in the piconet.
CommentEnd:  

SuggestedRemedy:  
Change "... with the PNC and then with any other DEV with which communication is required." to "... with the PNC."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  219
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.3.2
Page:  14
Line:  5052
CommentType:  E

Comment:  
The following sentences do not end in a period: a) Open - no authentication is required and data is not encrypted by the MAC b) Authentication - DEVs authenticate with the PNC before they have access to the piconet’s resources. Data is not encrypted by the MAC  and why are the Clause 5 lists different i.e., subclause 5.3.1 unordered and 5.3.2 ordered.  Refer to IEEE Standards Style Manual, 12. Homogeneity, pg. 14.
CommentEnd:  

SuggestedRemedy:  
Add the period and change the lists to be consistent i.e., all ordered or all unordered.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1660
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3.2
Page:  15
Line:  2
CommentType:  T

Comment:  
Saying that the data is "encrypted" is not really what one might want.  Entities may want to know that the transmission came from the appropriate person and wasn't tampered with (data integrity) and/or have the data encrypted.  We should allow for these different combinations of integrity and privacy.
CommentEnd:  

SuggestedRemedy:  
Change second sentence in paragraph to: "All data sent in the piconet uses payload protection (data integrity and/or data encryption) with the piconet payload protection key(s)."  Comment via Ari Singer.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  731
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  05
Subclause:  5.3.2
Page:  15
Line:  7
CommentType:  E

Comment:  
'ssh' is not defined either here or in clause 4.
CommentEnd:  

SuggestedRemedy:  
Define.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  866
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3.2
Page:  15
Line:  7
CommentType:  T

Comment:  
add to clause 4
CommentEnd:  

SuggestedRemedy:  
add "ssh" to clause 4 ... off-hand I do not know what ssh means.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Sentence was deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  66
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  05
Subclause:  5.3.3
Page:  15
Line:  12
CommentType:  E

Comment:  
Bad grammar.
CommentEnd:  

SuggestedRemedy:  
Change "is sent using either by" to "is sent either by".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  14
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.3.3
Page:  15
Line:  12
CommentType:  E

Comment:  
the second "using" seems to be extra
CommentEnd:  

SuggestedRemedy:  
omit the second instance of "using" on this line. Perhaps drop "either" as well.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  867
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3.3
Page:  15
Line:  1213
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
change to ...  Data is sent using either by a streamless asynchronous exchange, or by ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1379
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.3.3
Page:  15
Line:  13
CommentType:  E

Comment:  
"asynchronous connection" and "isochronous connection"  should be stream
CommentEnd:  

SuggestedRemedy:  
change connection to stream
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  67
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  05
Subclause:  5.3.4
Page:  15
Line:  1820
CommentType:  E

Comment:  
The PNC does not allocate 'bandwidth'. It does allocate time slots in which a pair of DEVs can use any of the supported bit rates in order to obtain an effective throughput rate from the available raw bandwidth and the amount of error recovery required by the effective BER of the channel.
CommentEnd:  

SuggestedRemedy:  
Replace this section with: "Asyncrhonous or synchronous data streams are established for use in the CFP by the allocation of GTSs. The PNC manages allocation of GTSs based on the DEVs requirements and the DEVs then use the GTSs as needed. These streams are established by a connection process."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1792
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  05
Subclause:  5.3.7
Page:  15
Line:  41
CommentType:  E

Comment:  
PIND
CommentEnd:  

SuggestedRemedy:  
PNID
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  15
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.3.7
Page:  15
Line:  42
CommentType:  E

Comment:  
multiple comments 1. suggest changing "private" GTS to better convey the idea. 2. need to add "for the child" in line 43 3. missing word in sentence.
CommentEnd:  

SuggestedRemedy:  
1. change "private" to "reserved" 2. after acknowledgments, insert "for the child"  3. at beginning of line 47, add "to"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1762
CommenterName:  Carmeli, Boaz
CommenterEmail:  boazc@il.ibm.com
CommenterPhone:  972-4-8296504
CommenterFax:  
CommenterCo:  IBM
Clause:  05
Subclause:  5.3.7
Page:  15
Line:  43
CommentType:  E

Comment:  
.... handled within in the child...
CommentEnd:  

SuggestedRemedy:  
.... handled within the child...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  16
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.3.8
Page:  15
Line:  54
CommentType:  T

Comment:  
1. use reserved or another term rather than private 2. add clarification as to what assoc, auth, sec and acks are related to
CommentEnd:  

SuggestedRemedy:  
1. change "private" to "reserved" 2. after acknowledgments, insert "for the neighbor"
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change "private GTS" to "time slot". Accept second part as written.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1712
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  05
Subclause:  5.3.8
Page:  16
Line:  4
CommentType:  TR

Comment:  
Does this suggest any 802-compliant wireless devices can operate as a 15.3 neighbor piconet and solve co-existing issue?
CommentEnd:  

SuggestedRemedy:  
This statement should be removed or clarified.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Other wireless devices could utilize the neighbor piconet capability to allocate time within an existing 802.15.3 piconet so that that wireless device could utilize the allocated time to coexist in the same spectrum as the existing 802.15.3 piconet. The other wireless device would need to use the 802.15.3 commands to associate as a neighbor piconet.

Delete "802-compliant" and also change "for supporting . . . Neighbor" to be "of using this coexistence method".
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  732
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  05
Subclause:  5.4
Page:  16
Line:  11
CommentType:  E

Comment:  
Some of the list of states (association, authentication, stream connection, etc.) are more device actions than WPAN states. Thus 'disassociation' should be included.
CommentEnd:  

SuggestedRemedy:  
Add 'disassociation'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  17
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.4
Page:  16
Line:  11
CommentType:  E

Comment:  
There is no mention of MTS at this level and at least a brief mention should be present in the overview of operation.
CommentEnd:  

SuggestedRemedy:  
add 5.4.3 MTS operation The stanard provides an alternative to CAP through the use of management time slots (MTS). Management time slots are located within the CFP.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1380
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.4
Page:  16
Line:  12
CommentType:  E

Comment:  
WPAN operation states and DEV operations have been mixed.
CommentEnd:  

SuggestedRemedy:  
...WPAN has sevaral states of operation: An 802.15.3 WPAN has several states of operation: establishment, optional coordination function transfer, and stopping a piconet. DEVs have several states of operration: association, authentication, stream connection establishment, data exchange.  These WPAN and DEV states operate around the structure of the superframe.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  733
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  05
Subclause:  5.4.1
Page:  16
Line:  17
CommentType:  E

Comment:  
CSMA/CA is not defined in the document.
CommentEnd:  

SuggestedRemedy:  
Define.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1381
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.4.2
Page:  16
Line:  25
CommentType:  E

Comment:  
Data in asynchronous streams does not have to be acknowledged.  Broadcast streams are not acknowledged.
CommentEnd:  

SuggestedRemedy:  
Change to: Data in asynchronous streams can be acknowledged, and synchronous streams are able to request acknowledgement as well.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1388
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.4.3
Page:  16
Line:  27
CommentType:  E

Comment:  
Need to add a section on MTS
CommentEnd:  

SuggestedRemedy:  
Add MTS description:  Management Time Slots are a type of GTS that can be used to allow communications between the DEVs and the PNC.  MTS slots can either be assigned or they can be shared slots that are accessed using SLotted Aloha.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  133
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  5.5
Page:  17
Line:  14
CommentType:  E

Comment:  
"... a new DEVs joins." - add the following:  "... a new DEVs joins with more capability."
CommentEnd:  

SuggestedRemedy:  
See above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1661
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.2
Page:  16
Line:  3940
CommentType:  T

Comment:  
Again, privacy should be payload protection.
CommentEnd:  

SuggestedRemedy:  
Change sentence to "If payload protection is enabled for the piconet, then the DEV receives the symmetric piconet payload protection key(s) during authentication."   Comment via Ari Singer.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Replacing sentence "If privacy . . . encrypt data." Change "during" to "after" the the suggested remedy.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  19
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.5.2
Page:  16
Line:  42
CommentType:  TR

Comment:  
power management status is not part of join. power management is negotiated between peers so is not part of join between DEV and PNC. The text is in error. We could replace this with the ability of a DEV to support power management.
CommentEnd:  

SuggestedRemedy:  
change the text to "its ability to support power management " and remove "it power management status (whether it needs to power management or not"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1382
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.2
Page:  16
Line:  42
CommentType:  E

Comment:  
"whether it needs to power mangement or not" is not proper grammar
CommentEnd:  

SuggestedRemedy:  
probably need to drop the "to" or change to "to use"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  868
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.3
Page:  16
Line:  48
CommentType:  TR

Comment:  
add some text
CommentEnd:  

SuggestedRemedy:  
... from the PNC during the CAP or MTS.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Change "CAP" to "CAP or MTS".
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1384
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.3
Page:  16
Line:  48
CommentType:  E

Comment:  
"during the CAP" should be "during the CAP or MTS"
CommentEnd:  

SuggestedRemedy:  
add "or MTS"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  22
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  05
Subclause:  5.5.4
Page:  17
Line:  4
CommentType:  T

Comment:  
I thought that we dropped the "data window." If we did, we should change the text in this subclause.
CommentEnd:  

SuggestedRemedy:  
remove "data window of the"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1386
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.4
Page:  17
Line:  4
CommentType:  E

Comment:  
asynch data is only allowed in the CAP if the PNC allows it.
CommentEnd:  

SuggestedRemedy:  
add "if allowed by the PNC." to the end of the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1385
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.4
Page:  17
Line:  4
CommentType:  E

Comment:  
there is no "data window" in the CAP
CommentEnd:  

SuggestedRemedy:  
Remove reference to "data window"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  869
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.5
Page:  17
Line:  11
CommentType:  E

Comment:  
change as shown
CommentEnd:  

SuggestedRemedy:  
It is possible, for many reasons, that the PNC function will be transferred.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  870
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.6
Page:  17
Line:  22
CommentType:  E

Comment:  
Rewrite as ...
CommentEnd:  

SuggestedRemedy:  
Power is removed from all the DEVs
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  220
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  5.5.6
Page:  17
Line:  22
CommentType:  E

Comment:  
The following sentence does not end in a period: — Power is removed removing power from all the DEVs
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  73
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  05
Subclause:  5.5.6
Page:  17
Line:  22
CommentType:  E

Comment:  
Bad Grammar
CommentEnd:  

SuggestedRemedy:  
Change "... removed removing power ..." to "... removed by removing power ..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1387
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  5.5.6
Page:  17
Line:  22
CommentType:  E

Comment:  
"Power is removed removing power from all DEVs" does not make sense
CommentEnd:  

SuggestedRemedy:  
Change to "Power is removed from the DEV before the DEV can perform a PNC handover."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  735
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  05
Subclause:  5.5.6
Page:  17
Line:  26
CommentType:  E

Comment:  
This refers to a parent piconet ending a subsidary piconet, however it is the parent PNC that can end the subsidary piconet.
CommentEnd:  

SuggestedRemedy:  
Change 'parent piconet' to 'parent PNC'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  134
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  5.6
Page:  17
Line:  27
CommentType:  E

Comment:  
"via the disassociation command ..." - this mode of operation should be included in section 5.4.
CommentEnd:  

SuggestedRemedy:  
Add disassociation command to 5.4.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  135
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  5.6.1
Page:  17
Line:  38
CommentType:  T

Comment:  
Why would the PNC of the former child piconet immediately form a new piconet if it did not choose to continue operation after the parent piconet disappears?  Isn't this the same as removing the parent device ID element and continuing the piconet?
CommentEnd:  

SuggestedRemedy:  
Explain why this possible operation?  Explain why it is necessary.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete sentence on line 38 "However . . . The new piconet.".
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  488
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  05
Subclause:  Figure 1
Page:  14
Line:  
CommentType:  E

Comment:  
command and Data in CAP is confusing: makes the reader think all the commands are tx first and then the data
CommentEnd:  

SuggestedRemedy:  
merge the two blocks in CAP to one with the content "Command/Data"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  218
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  05
Subclause:  Figure 1
Page:  14
Line:  41
CommentType:  E

Comment:  
The term "GTS2" in Figure 1 is inconsistently used.
CommentEnd:  

SuggestedRemedy:  
Change the term to "GTS 2" (adding a space) to match GTS 1, GTS N, etc.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  113
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  05
Subclause:  Figure 1
Page:  14
Line:  41
CommentType:  T

Comment:  
Are GTS and MTS packets randomly intertwined?  Figure is unclear?  If this level of detail exists in the figure, it should be explained in the section.
CommentEnd:  

SuggestedRemedy:  
Clarify figure and explain in the section.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete MTS and GTS representations from Figure 1. Add text following "service provision" "This period  includes both MTS and GTS allocaitons."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1377
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  Figure 1
Page:  14
Line:  41
CommentType:  E

Comment:  
GTS N and MTS N make it look like there are an equal number of MTS and GTSs
CommentEnd:  

SuggestedRemedy:  
Change MTS N to MTS M.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1376
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  05
Subclause:  FIgure 1
Page:  14
Line:  41
CommentType:  T

Comment:  
CAP is devided into Command and Data - inconsistent with text
CommentEnd:  

SuggestedRemedy:  
Remove reference to command and data from the cap in Figure 1
RemedyEnd:  

Response:  
PROPOSED ACCEPT.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1423
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Putting clause 6 before clause 7 and 8 will confuse new readers.
CommentEnd:  

SuggestedRemedy:  
Move Clause 6 after Clause 8
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  138
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  1.1
Page:  20
Line:  5
CommentType:  T

Comment:  
How does MAC CPS fit into figure 2?
CommentEnd:  

SuggestedRemedy:  
Include this term and how it relates in figure 2
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy Figure A.1 to Figure 2 with any appropriate changes. Make sure suppporting text is adequate.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  137
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  1.1
Page:  20
Line:  7
CommentType:  E

Comment:  
SSCS needs to be defined
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1711
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  06
Subclause:  3.1.1
Page:  23
Line:  32
CommentType:  E

Comment:  
No MLME-STREAM-CONNECT primitive in Table 1
CommentEnd:  

SuggestedRemedy:  
change to MLME-CREATE-STREAM
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1715
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  06
Subclause:  3.13, 3.14
Page:  5055
Line:  
CommentType:  TR

Comment:  
No time out for these two primitives
CommentEnd:  

SuggestedRemedy:  
Add time out parameters to the MLME-CREATE-STREME & MLME-MODIFY-STREME primitives
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Add value called timeout as type duration, valid range >1, Description of "Time in ms that the MAC allows for completion of this command."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  142
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  4.1
Page:  71
Line:  47
CommentType:  E

Comment:  
"... by the LME ..." - should this be "PLME"?
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  143
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  4.5
Page:  74
Line:  3
CommentType:  E

Comment:  
"... by the LME ..." - should this be "PLME"?
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  144
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  6
Page:  75
Line:  51
CommentType:  E

Comment:  
Need to list the PHY PIB groups in this section to make it easier to for the reader to know what to expect in this section.
CommentEnd:  

SuggestedRemedy:  
List PHY PIB groups.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  872
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.1
Page:  19
Line:  15
CommentType:  E

Comment:  
missing definite article, add as shown below
CommentEnd:  

SuggestedRemedy:  
... functions on behalf of the general system ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  873
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.1
Page:  19
Line:  16
CommentType:  E

Comment:  
missing definitive article, modify as shown below
CommentEnd:  

SuggestedRemedy:  
relationship among the man-
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  446
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.1
Page:  19
Line:  20
CommentType:  T

Comment:  
The figure does not include the SSCS layer.
CommentEnd:  

SuggestedRemedy:  
Replace the figure with the one from A.1 or modify it to include the SSCS layer.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy Figure A.1 to Figure 2 with any appropriate changes. Make sure suppporting text is adequate.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  447
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.1
Page:  19
Line:  44
CommentType:  T

Comment:  
Should list all of the SAPs in this enumeration.
CommentEnd:  

SuggestedRemedy:  
Add SSCS SAP, MAC SAP and PHY SAP as items a and b (and fix numbering).
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  223
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.1
Page:  19
Line:  4648
CommentType:  E

Comment:  
The ordered list starts at "d)" which is incorrect it should be a).
CommentEnd:  

SuggestedRemedy:  
Modify the ordered list to span "a)-c)".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1389
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.1
Page:  19
Line:  6
CommentType:  E

Comment:  
"may" does not belong in "Both MAC and PHY may conceptually"
CommentEnd:  

SuggestedRemedy:  
remove "may"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  221
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.1
Page:  19
Line:  6
CommentType:  E

Comment:  
The term "sub-layer", used in the sentence "Both MAC and PHY layers may conceptually include management entities, called the MAC sub-layer...", is spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer", dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  550
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  06
Subclause:  6.1
Page:  76
Line:  41
CommentType:  TR

Comment:  
5 GHz and UWB are assumed to be future spectral bands to be used without any justification or mention given apriori. How can a current standard have mention of specifics of future standard
CommentEnd:  

SuggestedRemedy:  
The 5 GHz and UWB should not be mentioned in this table to avoid confusion.
RemedyEnd:  

Response:  
ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  224
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.1.1
Page:  20
Line:  5
CommentType:  E

Comment:  
The term "sub-layer", used in the subclause title "6.1.1 MAC common part sub-layer (MAC CPS)", is spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer", dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1391
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.1.1
Page:  20
Line:  7
CommentType:  E

Comment:  
"The MAC CPS provides stream-oriented service to the SSCS."  What about non-stream?
CommentEnd:  

SuggestedRemedy:  
add "and non-stream-oriented" and modify the paragraph to address non-stream flows.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  874
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.2
Page:  20
Line:  20
CommentType:  T

Comment:  
replace the word PAN with personality
CommentEnd:  

SuggestedRemedy:  
... as a personality information ...
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change PAN Information Base to Personal Information Base in this section and in clause 1. Change 'personality' to 'characteristics' in this paragraph. Delete ", hence the acronym PIB".
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  225
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.2
Page:  20
Line:  24
CommentType:  E

Comment:  
The term "sub-layer", used in the subclause title "...personality of the sub-layer, hence the acronym PIB.", is spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer", dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  875
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.2
Page:  20
Line:  26
CommentType:  E

Comment:  
In lines 26 and 27, remove the hyphens
CommentEnd:  

SuggestedRemedy:  
PIB-related --> PIB related user-entity --> user entity
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  448
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.2
Page:  20
Line:  34
CommentType:  T

Comment:  
Add a table with definitions of the parameters for these commands.
CommentEnd:  

SuggestedRemedy:  
Add the following defintions:  Name           Type        Valid range                 Description PIBattribute  octet string  Any PIB attribute as       The name of the PIB                             defined in 6.5 and 6.6     attribute  PIBvalue      variable      as defined in 6.5 and 6.6  The PIB value  status        enumeration   SUCCESS, INVALID_PIB_      The result of the                             ATTRIBUTE, READ_ONLY_PIB_  command.                             ATTRIBUTE, WRITE_ONLY_PIB_                             ATTRIBUTE
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 

Name
Type
Valid range
Description 

PIBattribute
octet string
 Any PIB attribute as  defined in 6.5 and 6.6 
The name of the PIB  attribute 
 
PIBvalue
 variable
as defined in 6.5 and 6.6
The PIB value

status
enumeration
SUCCESS, INVALID_PIB_ ATTRIBUTE, READ_ONLY_PIB_ATTRIBUTE, WRITE_ONLY_PIB_ATTRIBUTE
The result of the command.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  552
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  22
Line:  37
CommentType:  E

Comment:  
The MLME-POWERMGT  primitive in Table 1 is in the wrong location.
CommentEnd:  

SuggestedRemedy:  
Move MLME-PowerMgt primitive at the beginning of Table 1 to the position just before the MLME-CREATE-STREAM primitive.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  556
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  14
CommentType:  E

Comment:  
The MLME-CREATE-REPEATER primitive is missing from Table 1.
CommentEnd:  

SuggestedRemedy:  
Please add MLME-CREATE-REPEATER primitive to Table 1 just after the MLME-CHANNEL-STATUS primitive in Table 1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  555
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  14
CommentType:  E

Comment:  
MLME-Tx-POWER-CHANGE primitive is missing from Table 1.
CommentEnd:  

SuggestedRemedy:  
Please add MLME-Tx-POWER-CHANGE primitive to Table 1 just before the MLME-CHANNEL-STATUS primitive in Table 1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  557
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  15
CommentType:  E

Comment:  
The MLME-REMOTE-SCAN primitive is missing from Table 1.
CommentEnd:  

SuggestedRemedy:  
Please add the MLME-REMOTE-SCAN primitive to Table 1 just after the MLME-CREATE-REPEATER primitive and just before the MLME-CHANGE-CHANNEL primitive in Table 1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  559
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  17
CommentType:  E

Comment:  
The MLME-PNC-HANDOVER primitive is missing from Table 1.
CommentEnd:  

SuggestedRemedy:  
Please add the MLME-PNC-HANDOVER primitive to Table 1 just before the MLME-PROBE-PNC primitive in Table 1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  560
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  19
CommentType:  E

Comment:  
The MLME-NEW-PNC primitive is missing from Table 1.
CommentEnd:  

SuggestedRemedy:  
Please add the MLME-NEW-PNC primitive to Table 1 just after the MLME-PROBE-PNC primitive.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  558
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  19
CommentType:  E

Comment:  
The MLME-DEV-INFO primitive is in the wrong location in Table 1.
CommentEnd:  

SuggestedRemedy:  
Please move the MLME-DEV-INFO primitive from its current location to just after the MLME-CHANGE-CHANNEL table location.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  449
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3
Page:  23
Line:  19
CommentType:  E

Comment:  
Change MLME-DEV-INFO to be MLME-PROBE-DEV since that more closely reflects the command name.
CommentEnd:  

SuggestedRemedy:  
Change as indicated here and in 6.3.19.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  553
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  5
CommentType:  E

Comment:  
The MLME-RESET primitive in Table 1 is in the wrong table location.
CommentEnd:  

SuggestedRemedy:  
Please move the MLME-RESET primitive from its current position in Table 1 to the first position in Table 1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  554
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3
Page:  23
Line:  6
CommentType:  E

Comment:  
The MLME-START primitive is in the wrong table position in Table 1.
CommentEnd:  

SuggestedRemedy:  
Please move the MLME-START primitive from its current position in Table 1 to the second position in Table 1 just after MLME-RESET.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1662
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3 Table 1
Page:  22
Line:  51
CommentType:  T

Comment:  
MLME-DISTRIBUTE-KEY does not have a response.  Without a response, the PNC (or security manager) will not know if the associated DEV actually received the key or not.
CommentEnd:  

SuggestedRemedy:  
Add a response message.  Comment via Ari Singer.
RemedyEnd:  

Response:  
PROPOSED REJECT. If DEV does not properly decode message, it will make another request.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  1422
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1
Page:  23
Line:  
CommentType:  TR

Comment:  
Break MLME-POWERMGT command up into separate MLMEs, like security/authentication did.
CommentEnd:  

SuggestedRemedy:  
Break up into Peer Wakup, wakeup, DEV to PNC PS Information, query, join...
RemedyEnd:  

Response:  
PROPOSED ACCEPT.  Jay and WMS will draft the new MLMEs.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  603
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.1
Page:  23
Line:  22
CommentType:  E

Comment:  
The Power Management clauses 6.3.1, 6.3.1.1, 6.3.1.1.1, 6.3.1.1.2, 6.3.1.2, 6.3.1.2.1, 6.3.1.2.2 should be moved to the space just after clause 6.3.15.4 Terminate Stream Message  Sequence Chart.
CommentEnd:  

SuggestedRemedy:  
Please move the indicated Power Management clauses to the location just after the Terminate Stream Message Sequence Chart.  This new location makes more sense from a functional perspective.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  226
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.3.1
Page:  23
Line:  24
CommentType:  E

Comment:  
The following sentence does not end in a period: The parameters used for these commands are defined in Table 2
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1407
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1
Page:  25
Line:  
CommentType:  TR

Comment:  
Why is there no MLME-POWERMGT.response.  The PNC should send a response in response to an indication.
CommentEnd:  

SuggestedRemedy:  
Add MLME-POWERMGT.response
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Split MLME into separate commands. Jay and WMS to provide. Ensure there are responses when appropriate.e.g., EPSAction command.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1405
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1
Page:  25
Line:  10
CommentType:  TR

Comment:  
MLME-POWERMGT.indication only has one parameter, but it really needs to have almost all of the parameters as the request.  The PNC will receive an indication as the result of recieving a power managemnt command.
CommentEnd:  

SuggestedRemedy:  
Add appropriate parameters to the indication.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Splite MLME into separate commands. Jay and WMS to provide. Ensure that parameters in a .request match the parameters in a .indication.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  25
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  06
Subclause:  6.3.1.1
Page:  23
Line:  30
CommentType:  TR

Comment:  
Text mentions that information is available prior to association. In fact, the power management information is a post-assocation process.
CommentEnd:  

SuggestedRemedy:  
change "prior to association" to "after association"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  450
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.1.1
Page:  23
Line:  31
CommentType:  T

Comment:  
Power managment commands are relevant only in the context of an associated device.
CommentEnd:  

SuggestedRemedy:  
Change "to the DEV prior to association" to be "to the DEV after association"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  876
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1.1
Page:  23
Line:  35
CommentType:  E

Comment:  
missing commas after parameters
CommentEnd:  

SuggestedRemedy:  
add commas after the following parameters: RequestType EPSSet EPSStatus
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  227
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.3.1.1
Page:  23
Line:  46
CommentType:  E

Comment:  
The following sentence does not end in a period: The parameters for this command are defined in Table 2
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1395
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1.1.1
Page:  24
Line:  7
CommentType:  E

Comment:  
Poor sentence - to implement the power-saving strategy of an implementation.
CommentEnd:  

SuggestedRemedy:  
Choose better wording
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1591
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1.1.1 Table 2
Page:  24
Line:  
CommentType:  E

Comment:  
Having EPS be both a mode and an EPSSatus is very confusing.
CommentEnd:  

SuggestedRemedy:  
Rename either the EPSStatus values to EPS_Active and EPS_Inactive
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1393
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1.1.2
Page:  24
Line:  
CommentType:  T

Comment:  
Need to specify which commands are associated with the generation of the MLME-POWERMANAGEMENT .request.
CommentEnd:  

SuggestedRemedy:  
Add description of which commands are generated in response to MLME-POWERMANAGEMENT .request.  If there is a one to one mapping of request type and Action type that needs to be spelled out.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Jay and WMS will do this while adding new MLME text.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1404
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.1.1.2
Page:  24
Line:  48
CommentType:  TR

Comment:  
This request better do more than "sets the DEV power management parameters."  Doesn't it also determine which power management commands are sent to the PNC or the other DEV?
CommentEnd:  

SuggestedRemedy:  
Put together a table that shows explicitly which PM commands are sent as a result of which PM primatives in the MLME
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Split MLME into separate primitives. Jay and WMS to provide.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  228
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.3.1.2
Page:  25
Line:  14
CommentType:  E

Comment:  
The following sentence does not end in a period: The parameters for this command are defined in Table 2
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  451
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.1.3
Page:  25
Line:  27
CommentType:  T

Comment:  
The power managment changes come about as a result of changes in the beacon, not from direct communications with other DEVs.
CommentEnd:  

SuggestedRemedy:  
Change "from a specific peer MAC entity" to be "from the PNC"  Also change "result of acommand ... in the piconet." to be "result of a change in the beacon."
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  229
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.3.1.3
Page:  25
Line:  28
CommentType:  E

Comment:  
The following sentence does not end in a semicolon: primitive are as follows
CommentEnd:  

SuggestedRemedy:  
Add the semicolon.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  230
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.3.1.3
Page:  25
Line:  34
CommentType:  E

Comment:  
The following sentence does not end in a period: The parameters for this command are defined in Table 2
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1669
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.10
Page:  
Line:  
CommentType:  T

Comment:  
When does DE-AUTHENTICATE actually get used?  What purpose does it serve?  I don't think it really makes sense to have a command that says that your key has been compromised if that is what this is for.
CommentEnd:  

SuggestedRemedy:  
Recommend removing these commands.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  462
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.10.1
Page:  44
Line:  34
CommentType:  T

Comment:  
The DeviceID parameter description is inaccurate.
CommentEnd:  

SuggestedRemedy:  
Change "de-authentication process" to be "de-authentication process or the MAC entity which is requesting de-authentication"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  463
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.10.1
Page:  44
Line:  36
CommentType:  T

Comment:  
The valid rane of the ReasonCode for de-authenticate is incorrect.
CommentEnd:  

SuggestedRemedy:  
Add the "TIMEOUT" to the valid range
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  464
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.10.1
Page:  44
Line:  49
CommentType:  T

Comment:  
The de-authenticate command does not use a reason code.
CommentEnd:  

SuggestedRemedy:  
Delete ReasonCode from the semantics of the primitive in two places, page 44, line 49 and page 45, line 39 (in the .indication primitive).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  599
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.11
Page:  46
Line:  1
CommentType:  E

Comment:  
Clauses 6.3.11, 6.3.11.1, 6.3.11.1.1, 6.3.11.1.2 and Table 18 should be where clause 6.3.1 is located on page 23.
CommentEnd:  

SuggestedRemedy:  
Please move the requested clauses to the indicated location.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  592
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.11.1
Page:  46
Line:  10
CommentType:  T

Comment:  
DeviceID is an unnecessary parameter left over from 802.11.
CommentEnd:  

SuggestedRemedy:  
Please remove.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  465
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.11.1
Page:  46
Line:  10
CommentType:  T

Comment:  
The DeviceID of a DEV is set through the PIB commands and should not be set here.
CommentEnd:  

SuggestedRemedy:  
Delete the DeviceID primitive parameter from the semantics and table 18.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  594
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.11.1.1
Page:  46
Line:  33
CommentType:  E

Comment:  
Text describing when the MLME-RESET.request is generated is partially incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the text to: The primitive is sent by the DME to its MLME to reset the MAC to its initial conditions.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  595
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.11.1.2
Page:  46
Line:  38
CommentType:  T

Comment:  
Text describing the effect reception of the MLME-RESET.request primitive has on the local MAC entity is incomplete.
CommentEnd:  

SuggestedRemedy:  
Please change the first sentence in this clause to:  "The DEV MLME, upon receiving this primitive, sends a DISASSOCIATION-REQUEST command frame to the PNC, sets the MAC to its initial conditions and clears all of its internal variables to their default values."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  596
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.11.1.2
Page:  46
Line:  40
CommentType:  T

Comment:  
The last sentence of this clause is unnecessary.
CommentEnd:  

SuggestedRemedy:  
Please remove the last sentence from this clause since the MLME-RESET.confirm is unneeded.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  597
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.11.1.2
Page:  46
Line:  40
CommentType:  T

Comment:  
Text describing the effect this primitive has upon the PNC MLME is missing.
CommentEnd:  

SuggestedRemedy:  
Please add this paragraph to this clause:  "The PNC MLME, upon receiving this primitive, behaves the same as the DEV MLME with the exception that it transmits a beacon containing a PICONET-SHUTDOWN information element. "
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  598
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.11.2
Page:  46
Line:  42
CommentType:  T

Comment:  
Clauses  6.3.11.2, 6.3.11.2.1, 6.3.11.2.2, and Table 19 are unnecessary.
CommentEnd:  

SuggestedRemedy:  
Please remove.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  600
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.12
Page:  47
Line:  13
CommentType:  E

Comment:  
Clauses 6.3.12, 6.3.12.1, 6.3.12.1.1, 6.3.12.1.2, 6.3.12.2, 6.3.12.2.1, 6.3.12.2.2 should be moved to where clause 6.3.2 is located so that the MLME-START primitives follow the MLME-RESET primitive at the beginning of MLME-SAP interface section.
CommentEnd:  

SuggestedRemedy:  
Please move the indicated clauses.  It makes more sense to have these clauses located near the MLME-SCAN clauses.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  915
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.12.1
Page:  47
Line:  22
CommentType:  E

Comment:  
add commas
CommentEnd:  

SuggestedRemedy:  
add commas to the following parameters  PiconetType ChannelList ChannelScanDuration MACParameterSet
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  293
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.12.1
Page:  47
Line:  45
CommentType:  T

Comment:  
The parameter CapabilityInformation field is listed in the primitive but is not defined.
CommentEnd:  

SuggestedRemedy:  
Delete the parameter CapabilityInformation
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  916
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.12.1
Page:  47
Line:  53
CommentType:  TR

Comment:  
Add a figure
CommentEnd:  

SuggestedRemedy:  
Add a figure to show the MACParameterSet vector
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Turn the text at the bottom of the page into a table. Add types as appropriate.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  917
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.12.1
Page:  47
Line:  54
CommentType:  TR

Comment:  
Reference to CAP Mode
CommentEnd:  

SuggestedRemedy:  
CAP Mode is not defined in clause 7.4.2.  MAC subcommittee needs to clarify the reference here.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change CAP Mode to be Piconet mode which is acutally defined in section 7.4.2.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1411
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.12.2
Page:  48
Line:  14
CommentType:  E

Comment:  
Move Start MLME to be adjacent to Scan, Synchronization and Associate.
CommentEnd:  

SuggestedRemedy:  
Move Start MLME to be adjacent to Scan, Synchronization and Associate.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  601
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.12.2
Page:  48
Line:  20
CommentType:  TR

Comment:  
The PiconetDescriptionSet parameter is missing from the MLME-START.confirm primitive.
CommentEnd:  

SuggestedRemedy:  
Please add the PiconetDescriptionSet parameter to the MLME-START.confirm primitive.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy the entry for PiconetDescriptionSet from MLME-SCAN.xxx, table 4 to MLME-START.xxx, table 20.  Use a cross reference to table 5 for the definition.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1424
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.12.2
Page:  48
Line:  21
CommentType:  TR

Comment:  
MLME-START.confirm should have the channel number that the piconet was started in.
CommentEnd:  

SuggestedRemedy:  
Add Channel Number to the MLME-START.confirm  parameters.
RemedyEnd:  

Response:  
PROPOSED REJECT. The channel number is returned in the piconet description set list.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  602
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.13
Page:  48
Line:  45
CommentType:  TR

Comment:  
The MLME-CHANNEL-TIME.request, indication,response and confirm are missing.
CommentEnd:  

SuggestedRemedy:  
Please insert clauses 6.xxxx from 01/410r1 into the space just before clause 6.3.13 Stream creation.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  D
ResponseStatus:  W
Topic:  CTR
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1430
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.13.1
Page:  50
Line:  15
CommentType:  E

Comment:  
Source and destination addresses should be initiator and target for consistency with stream management command.
CommentEnd:  

SuggestedRemedy:  
Change source and destination addresses to initiator and target
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1428
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.13.1
Page:  50
Line:  22
CommentType:  TR

Comment:  
Add direction parameter to MLME-CREATE-STREAM.request
CommentEnd:  

SuggestedRemedy:  
Add direction parameter
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add direction parameter, value integer, valid range 0-1, definition "The direction of the stream, as defined in 7.5.10.3."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  919
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.13.1.2
Page:  50
Line:  33
CommentType:  E

Comment:  
Modify the sentence of line 33 as shown below.
CommentEnd:  

SuggestedRemedy:  
... command (ActionType=request) (7.5.10.3), which is ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  466
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.13.5
Page:  53
Line:  10
CommentType:  T

Comment:  
The primitive parameters for MLME-STREAM-CTA.indication are not defined.
CommentEnd:  

SuggestedRemedy:  
Copy the definitions from table 25 for StreamIndex and SlotStartTimeSet into a table in 6.3.13.5
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1431
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.13.5
Page:  53
Line:  8
CommentType:  E

Comment:  
Slot Start Time set is defined in Table 25 - reference needed
CommentEnd:  

SuggestedRemedy:  
Add reference to Table 25
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1433
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.13.6
Page:  
Line:  
CommentType:  E

Comment:  
If we are going to have a figure showing bipartate MSC from DEV to PNC, we should show bipartate negotiaon from PNC to DEV.
CommentEnd:  

SuggestedRemedy:  
Add figure showing bipartate negotiaon from PNC to DEV.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1434
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.13.6
Page:  54
Line:  
CommentType:  TR

Comment:  
Eliminate tripartate negotiation.
CommentEnd:  

SuggestedRemedy:  
bipartate negotiaon between the PNC and DEV is all that is needed.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  CTR
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1435
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.14
Page:  55
Line:  
CommentType:  TR

Comment:  
Stream 0 is used regardless of destination address.  Need to specify a destination DEV to start a channel time request for non stream data.
CommentEnd:  

SuggestedRemedy:  
Add destination address to the MLME-MODIFY-STREAM.request
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Add DestinationAddress, value MACAddress, valid range Any valid MACAddress, description "The destination address of the stream connection being modified."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  922
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.14.1.2
Page:  56
Line:  20
CommentType:  E

Comment:  
modify line 20 as shown below
CommentEnd:  

SuggestedRemedy:  
... command (7.5.10.1), which it will send ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  923
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.14.3.2
Page:  57
Line:  22
CommentType:  E

Comment:  
Modify line 22 as shown below
CommentEnd:  

SuggestedRemedy:  
... CHANNEL-TIME-GRANT command (7.5.10.2) with a ....
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  924
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.14.4.2
Page:  57
Line:  46
CommentType:  TR

Comment:  
ACK_TIMEOUT is referenced several times in clause 6.3.XX, but I can't find the definition of ACK_TIMEOUT.
CommentEnd:  

SuggestedRemedy:  
MAC subcommittee to provide a clause reference to ACK_TIMEOUT.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Add similar text to 01/410r1 that replaces ACK_TIMEOUT with RESPONSE_TIMEOUT and defines it as the response not being received within the specified time in the Effect of/upon receipt.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  925
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.14.4.2
Page:  57
Line:  52
CommentType:  E

Comment:  
Word misspelt
CommentEnd:  

SuggestedRemedy:  
Line 52, replace "with out" with "without"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  467
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.15
Page:  59
Line:  7
CommentType:  T

Comment:  
The definition of the ReasonCode for terminate stream is incorrect.
CommentEnd:  

SuggestedRemedy:  
Change the 3 entries as follows:  Type          Valid range         Description Enumeration   SUCCESS, TIMEOUT    Indicates the result of the stream                                         termination command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  926
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.15.3
Page:  60
Line:  24
CommentType:  E

Comment:  
Missing comma
CommentEnd:  

SuggestedRemedy:  
add a comma at the end of the parameter Streamindex
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  604
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16
Page:  61
Line:  23
CommentType:  TR

Comment:  
The MLME-Tx-POWER-CHANGE.request, indication, and confirm  primitives are missing from Clause 6.3 MLME-SAP interface.
CommentEnd:  

SuggestedRemedy:  
Please insert clauses 6.3.1 through 6.3.1.3.2 of 01/410r1 into the D09 just before the Channel Status subclause and just after the Power Management subclauses.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  231
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.3.16
Page:  61
Line:  26
CommentType:  E

Comment:  
The following sentence does not end in a period: primitive parameters are defined in Table 28
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  468
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.16
Page:  61
Line:  31
CommentType:  T

Comment:  
The RequestorDEVAddress is not defined and the ReasonCode is missing an enumeration.
CommentEnd:  

SuggestedRemedy:  
Add the following as the first row:  RequestorDEVAddress  MAC address  Any valid MAC address   The MAC address of the DEV which is requesting the channel status.  Add "TIMEOUT" to the valid range for ReasonCode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1438
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.16.1
Page:  62
Line:  7
CommentType:  T

Comment:  
The requesting DEV choose the window size, not the responding DEV.
CommentEnd:  

SuggestedRemedy:  
Add window size to the request, and also to the Channel Status Request command in clause 7.5.4.3 and the indication in 6.3.16.2
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  606
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.1
Page:  62
Line:  7
CommentType:  T

Comment:  
DestinationDEVAddress is an incorrect parameter name.
CommentEnd:  

SuggestedRemedy:  
Please change to RemoteDevAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RemoteDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  469
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.16.1
Page:  62
Line:  8
CommentType:  T

Comment:  
DestinationDEVAddress does not match other usage.
CommentEnd:  

SuggestedRemedy:  
Change "DestinationDEVAddress" to be "RemoteDEVAddress"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  470
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.16.1
Page:  62
Line:  8
CommentType:  T

Comment:  
ChannelIndex is an invalid parameter for a status report since all DEVs in the piconet use the same channel.
CommentEnd:  

SuggestedRemedy:  
Delete ChannelIndex from the semantics of the primitive and delete "on the indicated ChannelIndex" from line 21.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  607
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.1
Page:  62
Line:  8
CommentType:  T

Comment:  
ChannelIndex is an unnecessary parameter. Since the current Channel-Status command frame is only valid in the current piconet channel.
CommentEnd:  

SuggestedRemedy:  
Please remove the ChannelIndex parameter from this primitive.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  608
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.1.1
Page:  62
Line:  16
CommentType:  T

Comment:  
DestinationDEVAddress is the wrong parameter name.
CommentEnd:  

SuggestedRemedy:  
Please change from DestinationDEVAddress to RemoteDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change from DestinationDEVAddress to RemoteDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  613
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.1.1.2
Page:  62
Line:  22
CommentType:  T

Comment:  
The DestinationDEVAddress parameter at the end of the indicated sentence is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to RemoteDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RemoteDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  609
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.1.2
Page:  62
Line:  20
CommentType:  E

Comment:  
Missing xref to the CHANNEL-STATUS-REQUEST command frame described in Clause 7.
CommentEnd:  

SuggestedRemedy:  
Please add the appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  610
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.1.2
Page:  62
Line:  21
CommentType:  T

Comment:  
the sentence fragment ...on the indicated ChannelIndex... is not needed.
CommentEnd:  

SuggestedRemedy:  
Please remove the indicated sentence fragment.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  611
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.2
Page:  62
Line:  30
CommentType:  T

Comment:  
The RequestorDEVAddress in an incorrect parameter name.
CommentEnd:  

SuggestedRemedy:  
Please change from RequestorDEVAddress to RequestorDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change from RequestorDEVAddress to RequestorDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  612
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.3
Page:  63
Line:  7
CommentType:  T

Comment:  
The RequestorDEVAddress is an incorrect parameter name
CommentEnd:  

SuggestedRemedy:  
Please change to RequestorDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RequestorDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  614
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.3.2
Page:  63
Line:  25
CommentType:  E

Comment:  
Missing xref to the CHANNEL-STATUS-RESPONSE command clause in Clause 7
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  615
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.4
Page:  63
Line:  35
CommentType:  T

Comment:  
The RemoteDEVAddress is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to RemoteDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RemoteDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  616
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.4.1
Page:  63
Line:  49
CommentType:  T

Comment:  
the ReasonCode message "ACK_TIMEOUT" at the end of the indicated sentence is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change from ACK_TIMEOUT to RESPONSE_TIMEOUT.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  617
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.5
Page:  64
Line:  15
CommentType:  T

Comment:  
The MLME-CHANNEL-STATUS message sequence chart is missing the ChnlStatusRspTO timer.
CommentEnd:  

SuggestedRemedy:  
Please provide the appropriate timer symbol for the message sequence chart.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  618
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.16.5
Page:  64
Line:  31
CommentType:  TR

Comment:  
The MLME-CREATE-REPEATER.request, indication, response, and confirm primitives are missing from the MLME-SAP interface clause.
CommentEnd:  

SuggestedRemedy:  
Please insert clauses 6.3.1.8 through 6.3.1.11.2  just after the 6.3.16.5 MLME-CHANNEL-STATUS message sequence chart.
RemedyEnd:  

Response:  
REJECT. Despite the hard work by the commenter in creating the MLME's, the repeater functionality was deleted.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  1/24/2002
VoterStatus: 

-----------
CommentID:  620
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.17
Page:  64
Line:  31
CommentType:  TR

Comment:  
The MLME-REMOTE-SCAN.request, indication, response and confirm primitives are missing from the MLME-SAP interface clause.
CommentEnd:  

SuggestedRemedy:  
Please insert clauses 6.3.1.13 through 6.3.1.16.2 from 01/410r1 into the space just after the MLME-CHANNEL-STATUS and MLME-CREATE-REPEATER message sequence chart clause.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE.  Include the text with the modifications noted in the Dallas minutes to break apart the MSC.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  619
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.17
Page:  64
Line:  31
CommentType:  T

Comment:  
The MLME-CHANNEL-STATUS and MLME-CREATE-REPEATER message sequence chart is missing.
CommentEnd:  

SuggestedRemedy:  
Please insert the MLME-CHANNEL-STATUS and MLME-CREATE-REPEATER message sequence chart clause and diagram just after the last clause of the MLME-CREATE-REPEATER.confirm primitive.  Text and diagram are in clause 6.3.1.12 of doc 01/410r1
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  621
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.17
Page:  64
Line:  42
CommentType:  T

Comment:  
The NewChannelIndex data type is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change from octet to integer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1442
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.18
Page:  65
Line:  
CommentType:  E

Comment:  
Subclause is called Peer attribute discover, but the MLMEs are MLME-PROBE-PNC, and they cause device information request commands to be sent, not probe commands.
CommentEnd:  

SuggestedRemedy:  
Get ride of the word "probe" in the MLMEs.  change to MLME-PNC-Information.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  623
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18
Page:  65
Line:  49
CommentType:  T

Comment:  
The  MLME-CHANNEL-STATUS-, MLME-REMOTE-SCAN, and MLME-CHANGE-CHANNEL message sequence chart is missing from the MLME-SAP interface clause.
CommentEnd:  

SuggestedRemedy:  
Please insert Clause 6.3.1.19 from doc 01/410r1
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  624
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18
Page:  65
Line:  49
CommentType:  T

Comment:  
The MLME-PNC-HANDOVER.request is missing from the MLME-SAP interface clause.
CommentEnd:  

SuggestedRemedy:  
Please insert clauses 6.3.1.24  through 6.3.26.2 of the MLME-PNC-HANDOVER.request, indication, response and confirm clauses into the space just before current D09 clause 6.3.18.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  625
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18
Page:  65
Line:  50
CommentType:  E

Comment:  
The clause title "Peer attribute discovery" is incorrect
CommentEnd:  

SuggestedRemedy:  
Change the clause title to: "Retrieving PNC Info"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  626
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18
Page:  65
Line:  52
CommentType:  E

Comment:  
Missing xref to Peer Discovery sub clause in Clause 8.
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  471
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.18
Page:  66
Line:  15
CommentType:  T

Comment:  
The ReasonCode needs "TIMEOUT" added as part of its valid range.
CommentEnd:  

SuggestedRemedy:  
Change as indicated.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  472
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.18.1
Page:  66
Line:  19
CommentType:  T

Comment:  
The use of the probe request does not require that a DEV be authenticated.
CommentEnd:  

SuggestedRemedy:  
Delete the word "authenticated" from line 19, 20, 36 and 37 all on page 66 (i.e. every occurance in 6.3.18.1).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1670
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.18.1
Page:  66
Line:  1939
CommentType:  T

Comment:  
Why does the PROBE-PNC command only get information about authenticated DEVs?  Can this only be done in a secure piconet?  What is the purpose of this command?
CommentEnd:  

SuggestedRemedy:  
Recommend explaining the purpose of this command (if it isn't in there already).  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  630
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.1
Page:  66
Line:  24
CommentType:  T

Comment:  
The QueriedDEVIDSet parameter name is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change the QueriedDEVIDSet parameter name to QueriedDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change the QueriedDEVIDSet parameter name to QueriedDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  631
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.1.2
Page:  66
Line:  35
CommentType:  E

Comment:  
Missing xref to the PROBE-PNC-REQUEST command previously known as the DEVICE-INFO-REQUEST command.
CommentEnd:  

SuggestedRemedy:  
Please provide the appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1440
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.18.1.2
Page:  66
Line:  35
CommentType:  T

Comment:  
What is the PROBE-PNC-REQUEST command?
CommentEnd:  

SuggestedRemedy:  
Remove this and keep only DEVICE-INFORMATION-REQUEST command.  Do this globally for 6.3.18.1-4
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  633
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.2
Page:  66
Line:  48
CommentType:  T

Comment:  
RequestorDEVAddress parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to: RequestorDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to: RequestorDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  634
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.3
Page:  67
Line:  17
CommentType:  T

Comment:  
RequestorDEVAddress parameter name is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change to RequestorDEVAID
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RequestorDevID
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  635
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.3
Page:  67
Line:  18
CommentType:  T

Comment:  
DevInfoSet parameter name is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change to: PNCInfoSet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  636
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.3.2
Page:  67
Line:  29
CommentType:  E

Comment:  
Missing xref to PROBE-PNC-RESPONSE command frame clause previously known as DEVICE-INFORMATION-RESPONSE clause in clause 7.0
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  637
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.4
Page:  67
Line:  38
CommentType:  T

Comment:  
DEVInfoSet parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to: PNCInfoSet
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  638
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.4.1
Page:  67
Line:  47
CommentType:  E

Comment:  
Missing xref to PROBE-PNC-RESPONSE command.
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  639
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.4.1
Page:  67
Line:  48
CommentType:  T

Comment:  
ACK_TIMEOUT ReasonCode is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to: RESPONSE_TIMEOUT
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  640
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.4.2
Page:  68
Line:  1
CommentType:  TR

Comment:  
This sentence fragment " ...and may initiate another MLME-PROBE-PNC.request...
CommentEnd:  

SuggestedRemedy:  
Change the sentence fragment above to this:  In the case where this MLME-PROBE-PNC primitives have been used by a device as part of the PNC-HANDOVER process, the initiating DME shall initiate an MLME-NEW-PNC.request.  In the case where the MLME-PROBE-PNC primitives have been used by a device to simply request DEV information held by the PNC, the initiating DME may initiate another MLME-PROBE-PNC.request for a differenct remote device, or it may initiate an MLME-DEV-INFO.request.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change the sentence fragment above to this: In the case where this MLME-PNC-INFO primitives have been used by a device as part of the PNC-HANDOVER process, the initiating DME shall initiate an MLME-NEW-PNC.request.  In the case where the MLME-PNC-INFO primitives have been used by a device to simply request DEV information held by the PNC, the initiating DME may initiate another MLME-PNC-INFO.request for a differenet remote device, or it may initiate an MLME-PROBE.request.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  1/24/2002
VoterStatus: 

-----------
CommentID:  641
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18.5
Page:  68
Line:  8
CommentType:  E

Comment:  
DEV-2 label in MSC is incorrect
CommentEnd:  

SuggestedRemedy:  
Change to PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  632
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.18/2
Page:  66
Line:  47
CommentType:  T

Comment:  
QueriedDEVIDSet parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to: QueriedDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to: QueriedDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1443
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.19
Page:  
Line:  
CommentType:  E

Comment:  
MLME-DEV-INFO MLMEs don't send Device Information commands, they send probe rewquest commands.
CommentEnd:  

SuggestedRemedy:  
Change the names to MLME-DEV-Probe for consistency and readability.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  645
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19
Page:  68
Line:  30
CommentType:  E

Comment:  
Current Location of clauses 6.3.19-6.3.19.5 is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please move the MLME-DEV-INFO clauses and MSC to just after the MLME-CHANNEL-STATUS, MLME-REMOTE-SCAN, and MLME-CHANGE-CHANNEL message sequence chart and just before the MLME-PNC-HANDOVER.request clause.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  473
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.19
Page:  68
Line:  50
CommentType:  T

Comment:  
The definition of the ReasonCode is incorrect.
CommentEnd:  

SuggestedRemedy:  
Change the two entries to be:  Type          Valid range Enumeration  SUCCESS, TIMEOUT
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  474
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.19
Page:  69
Line:  1
CommentType:  T

Comment:  
The sentence "The ReasonCode ... for failure." does not belong here since it has been put into the table.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  648
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19.1
Page:  69
Line:  11
CommentType:  T

Comment:  
DestinationDEVAddress parameter name is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change to RemoteDEVAID
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RemoteDevID
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1444
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.19.1.1
Page:  69
Line:  22
CommentType:  E

Comment:  
This MLME should send the probe command, not the device informmation request (which goes to the PNC).
CommentEnd:  

SuggestedRemedy:  
Remove "DEVICE-INFORMATION_REQUEST" and just keep PROBE-REQUEST.  Do a global change for 6.3.19.1-4
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  646
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19.1.2
Page:  69
Line:  22
CommentType:  E

Comment:  
Missing xref to the DEVICE-INFORMATION-REQUEST command frame previously known as PROBE-REQUEST.
CommentEnd:  

SuggestedRemedy:  
Please add the appropriate xref
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  649
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19.2
Page:  69
Line:  34
CommentType:  T

Comment:  
REquestorDEVAddress parameter is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change to RequestorDEVAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RequestorDevID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  647
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19.2.1
Page:  69
Line:  42
CommentType:  E

Comment:  
Missing xref to DEVICE-INFORMATION-REQUEST command frame previously known as PROBE-REQUEST.
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  650
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19.3
Page:  70
Line:  8
CommentType:  T

Comment:  
RequestorDEVAddress parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to RequestorDEVAID
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to RequestorDevID
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1445
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.19.4
Page:  
Line:  
CommentType:  TR

Comment:  
MLME-DEV-INFO.confirm needs a DestinationDeviceID so the DME knows who is responding.
CommentEnd:  

SuggestedRemedy:  
Add DestinationDeviceID (or new name) to the MLME confirm.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  651
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19.4.1
Page:  70
Line:  36
CommentType:  E

Comment:  
Missing xref to DEVICE-INFORMATION-RESPONSE previously known as PROBE-RESPONSE.
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  652
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.19.4.1
Page:  70
Line:  37
CommentType:  T

Comment:  
ACK_TIMEOUT ReasonCode is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to RESPONSE-TIMEOUT.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  927
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.19.5
Page:  71
Line:  1
CommentType:  TR

Comment:  
Opening sentence is missing the opening clause.  Modify as shown below.
CommentEnd:  

SuggestedRemedy:  
Figure 10 illustrates the sequence of ...
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  452
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.2.1
Page:  26
Line:  21
CommentType:  T

Comment:  
No such thing as a generic PNID.  This is handled by the OpenScan parameter.
CommentEnd:  

SuggestedRemedy:  
Delete the words "generic or a"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  880
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.2.1
Page:  26
Line:  7
CommentType:  E

Comment:  
Missing comma
CommentEnd:  

SuggestedRemedy:  
Put a comma after the parameter "OpenScan"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  561
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.2.1
Page:  26
Line:  7
CommentType:  TR

Comment:  
OpenScan is an unneeded parameter.
CommentEnd:  

SuggestedRemedy:  
Please remove the OpenScan parameter from the paramter list for the MLME-SCAN-REQUEST primitive.
RemedyEnd:  

Response:  
PROPOSED REJECT. Openscan needed since there is no reserved PNID.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  453
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.2.1.2
Page:  26
Line:  42
CommentType:  T

Comment:  
The paragraph defines the functional description of the scan process that is already adequately defined in clause 8.  The redundant description is an abomination to the technical editor and will cause woe, wailing and gnashing of the teeth.
CommentEnd:  

SuggestedRemedy:  
Delete the sentences "The time spent by ... and aggregated into a PiconetDescriptionSet.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Note that multiple paragraphs are being deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1409
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.2.1.2
Page:  26
Line:  45
CommentType:  T

Comment:  
The scan is done once PNID is found, but there is a small but non-zero probablity that the same PNID may be heard on separate chanels
CommentEnd:  

SuggestedRemedy:  
Continue scan until all channels are scanned regardless if desired PNID is found.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. In 8.2.1, page 138, line 4, change "available in the PHY" to "indicated in the MLME command that initiated the scan." Replace the text "If the beacon . . Openscan, then" with "If the DEV finds only a frame and no beacon it shall report it as a part of the MLMEScan/Start.confirm commands. The".

Note: The original comment references text that was deleted due to another accepted comment.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  1413
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.3
Page:  29
Line:  
CommentType:  TR

Comment:  
Need a MLME-SyncLost.indicate to tell the DME that the DEV can no longer hear the Beacon.
CommentEnd:  

SuggestedRemedy:  
Add a MLME-SyncLost.indicate
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. WMS to provide text. Has no parameters. Sent when the ATP expires with no beacon heard.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  882
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.3.1
Page:  28
Line:  13
CommentType:  E

Comment:  
Remove comma
CommentEnd:  

SuggestedRemedy:  
remove comma after parameter "SyncFailureTimeout"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  569
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.3.1
Page:  28
Line:  8
CommentType:  TR

Comment:  
The functional description of the MLME-SYNCH.request primitive is incomplete.
CommentEnd:  

SuggestedRemedy:  
Please change the first sentence to this:  This primitive is used to initiate a local synchronization with a specific piconet beacon only when the PNID is set to 0xFFFF.
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  656
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.1
Page:  29
Line:  46
CommentType:  T

Comment:  
The DeviceAddress parameter is missing from the parameter list.
CommentEnd:  

SuggestedRemedy:  
Please insert the DeviceAddress parameter into the MLME-ASSOCIATE.request parameter list just before the CapabilityInformation parameter.
RemedyEnd:  

Response:  
PROPOSED REJECT. The MAC will insert the DEVAddress of itself.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  573
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.1.2
Page:  30
Line:  8
CommentType:  E

Comment:  
No xref to ASSOCIATION-REQUEST command frame type.
CommentEnd:  

SuggestedRemedy:  
Please add the required xref to the appropriate subclause in clause 7.0
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  655
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.1.2
Page:  30
Line:  8
CommentType:  T

Comment:  
the sentence fragment "...specified by the the DeviceID parameter." is unnecessary.
CommentEnd:  

SuggestedRemedy:  
Please remove the indicated sentence fragment.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  657
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.2
Page:  30
Line:  18
CommentType:  T

Comment:  
The DeviceID parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to DeviceAddress.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  DEVAddress instead of DeviceAddress.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  658
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.3
Page:  30
Line:  41
CommentType:  T

Comment:  
The DeviceID parameter name is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change to DeviceAddress.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. DEVAddress instead of DeviceAddress.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  659
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.3
Page:  30
Line:  42
CommentType:  T

Comment:  
The AssocDEVAddress parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to DeviceAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. DevID instead of DeviceAID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  574
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.3.2
Page:  31
Line:  3
CommentType:  E

Comment:  
xref to ASSOCIATE-RESPONSE command frame type is missing.
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref to ASSOCIATE-RESPONSE command frame type in Clause 7.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  575
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.4
Page:  31
Line:  12
CommentType:  TR

Comment:  
AssocDEVAddress parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change AssocDEVAddress to DeviceAID
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. DevID instead of DeviceAID
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  577
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.4.1
Page:  31
Line:  19
CommentType:  E

Comment:  
xref to ASSOCIATION-RESPONSE command frame subclause of clause 7 is missing.
CommentEnd:  

SuggestedRemedy:  
Please provide the appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  576
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.4.1
Page:  31
Line:  20
CommentType:  TR

Comment:  
The sentence fragment "...and a directed frame with null payload..."
CommentEnd:  

SuggestedRemedy:  
Please change the indicated phrase to: "...and a beacon containing the NewAssociatedDEV Information element..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Association Info
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  578
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.4.2
Page:  31
Line:  26
CommentType:  TR

Comment:  
AssocDEVAddress is an incorrect parameter name.
CommentEnd:  

SuggestedRemedy:  
Please change both instances of AssocDEVAddress to DeviceAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Use DevID instead of DeviceAID.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  579
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.5
Page:  32
Line:  1
CommentType:  TR

Comment:  
The title of clause 6.3.4.5 MLME-ASOCIATION-RESPONSE.indication is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the indicated clause title to: MLME-NEW-ASSOCIATED-DEV.indication.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The clause is being deleted so it doesn't matter any longer.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  454
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.4.5
Page:  32
Line:  1
CommentType:  T

Comment:  
This command is unecessary.  When an new DEV associates, the PNC sends out the new DEV info table anyway.  A DEV may not even be listening for association response frames since it has already been associated.
CommentEnd:  

SuggestedRemedy:  
Delete the entire command.  If not, delete the ReasonCode, since by definition it is set to SUCCESS for this command to be generated.  Also, change the description of AssocDEVAddress to be "The allocated device address of the DEV that has been associated." since the association was successful for this command to have been issued.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Delete the command. 6.3.4.5 up to but not including 6.3.4.6 and including table 9.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  660
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.5
Page:  32
Line:  3
CommentType:  TR

Comment:  
The sentence fragment : "...reception of a broadcast ASSOCIATION-RESPONSE command." is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the indicated sentence fragment to: " ...reception of a beacon containing a NEW-ASSOCIATED-DEV information element.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. This section has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  662
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.5
Page:  32
Line:  6
CommentType:  TR

Comment:  
The MLME-ASSOCIATION-RESPONSE.indication primitive no longer needed.
CommentEnd:  

SuggestedRemedy:  
Please change the indicated primitive to: MLME-NEW-ASSOCIATED-DEV.indication.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Association Info
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  661
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.5
Page:  32
Line:  8
CommentType:  T

Comment:  
The ReasonCode parameter name is unneeded.
CommentEnd:  

SuggestedRemedy:  
Please remove the ReasonCode parameter from the MLME-NEW-ASSOCIATED-DEV.indication parameter list.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  885
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.4.5
Page:  32
Line:  9
CommentType:  E

Comment:  
add a comma and remove a comma
CommentEnd:  

SuggestedRemedy:  
Add a comma after DeviceID Remove the comma after AssocDEVAddress
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  666
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.5.1
Page:  32
Line:  30
CommentType:  T

Comment:  
The sentence fragment "... a broadcast ASSOCIATION-RESPONSE command with a ReasonCode of SUCCESS."
CommentEnd:  

SuggestedRemedy:  
Please change the indicated fragment to: "... a beacon containing a NEW-ASSOCIATED-DEV information element."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. This section has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  667
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.5.2
Page:  32
Line:  35
CommentType:  T

Comment:  
The text describing  the Effect of receipt is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change the indicated text to: " The non-initiating DME, when it receives the MLME-NEW-ASSOCIATED-DEV.indication primitive, is provided with the DeviceAddress and DeviceAID of a successfully associated DEV."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. This section has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  580
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.4.6
Page:  32
Line:  38
CommentType:  T

Comment:  
Missing Association message sequence chart.
CommentEnd:  

SuggestedRemedy:  
Please provide missing message sequence chart.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Al Heberling wil proivde MSC.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  886
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.4.6
Page:  32
Line:  39
CommentType:  TR

Comment:  
Missing MSC
CommentEnd:  

SuggestedRemedy:  
Add in the MSC ... MAC subcommittee
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. See 580.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  581
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5
Page:  32
Line:  43
CommentType:  E

Comment:  
Missing xref to Dissaociation subclause in Clause 8.
CommentEnd:  

SuggestedRemedy:  
Please provide missing xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  582
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5.1
Page:  33
Line:  6
CommentType:  TR

Comment:  
DeviceID is incorrect parameter name and its data type is incorrect as well.
CommentEnd:  

SuggestedRemedy:  
Please change DeviceID to DeviceAID and change the data type from MAC address to Integer with range 1-255.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change DeviceID to DevID and change the data type from MAC address to Integer with range 1-255. Also see comment 571.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  583
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5.1
Page:  33
Line:  7
CommentType:  T

Comment:  
ReasonCode is unneccesary.
CommentEnd:  

SuggestedRemedy:  
Please remove ReasonCode as a parameter.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  585
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5.1.2
Page:  33
Line:  29
CommentType:  E

Comment:  
Missing xref to DISASSOCIATION-REQUEST command frame subclause in clause 7.
CommentEnd:  

SuggestedRemedy:  
Please provide appropriate xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  586
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5.2
Page:  33
Line:  37
CommentType:  E

Comment:  
Missing xref to DISASSOCIATION-REQUEST command sub clause in clause 7.
CommentEnd:  

SuggestedRemedy:  
Please provide missing xref.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  587
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5.2
Page:  33
Line:  41
CommentType:  T

Comment:  
DeviceID parm name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change DeviceID to DeviceAID.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Resolution as in comment 565.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  588
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5.2
Page:  33
Line:  42
CommentType:  T

Comment:  
ReasonCode is unneccesary.
CommentEnd:  

SuggestedRemedy:  
Please remove ReasonCode as a parameter for this primitive.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  591
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.3.5.3
Page:  34
Line:  13
CommentType:  TR

Comment:  
Clauses 6.3.5.3, 6.3.5.3.1 and 2 along with Table 12 are not needed to satisfy the requirments of the disassociation protocol.
CommentEnd:  

SuggestedRemedy:  
Please remove MLME-Disassociate.confirm and its subclauses.
RemedyEnd:  

Response:  
PROPOSED REJECT. There is a chance that this command may be used in some situations.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  850
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  06
Subclause:  6.3.6
Page:  3536
Line:  
CommentType:  TR

Comment:  
Include the possibility for authentication of the PNC.
CommentEnd:  

SuggestedRemedy:  
Include the 'PublicKeyChallenge' as an optional parameter in the MLME-AUTHENTICATE.request and MLME-AUTHENTICATE.indication.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.  The possibility of PNC authentication will be addressed by the proposals.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  851
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  06
Subclause:  6.3.6
Page:  3637
Line:  
CommentType:  TR

Comment:  
Include the possibility for authentication of the PNC.
CommentEnd:  

SuggestedRemedy:  
Include the 'PublicKeyProofe' as a conditional parameter in the MLME-AUTHENTICATE.response and MLME-AUTHENTICATE.confirm.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.  The possibility of PNC authentication will be addressed by the proposals.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1663
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.6 Table 13
Page:  35
Line:  140
CommentType:  T

Comment:  
DEVPublicKeyObjectLength, AuthenticationInfoLength, SecurityManagerPublicKeyLength, PublicKeyChallengeLength and PublicKeyProofLength should all have values greater than or equal to 0, not 1.  It may be that these fields are intentionally left blank.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  894
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.6.2.2
Page:  36
Line:  30
CommentType:  TR

Comment:  
The text says ...  "The DME may use the MLME-CHALLENGE.request command to obtain additional security information from the associated DEV.
CommentEnd:  

SuggestedRemedy:  
Security subgroup needs to provide reference in text where this procedure is described.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  895
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.6.2.2
Page:  36
Line:  32
CommentType:  TR

Comment:  
The text at the end of line 32 describes an authentication sequence.
CommentEnd:  

SuggestedRemedy:  
Security subcommittee needs to provide text reference to this authentication sequence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  455
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.7
Page:  37
Line:  54
CommentType:  T

Comment:  
The reason code is missing.
CommentEnd:  

SuggestedRemedy:  
Add the following row to the table:  Reason code     enumeration     SUCCESS, FAIL,    Indicates the result of                                 TIMEOUT           the challenge command
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1664
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.7 Table 14
Page:  37
Line:  3554
CommentType:  T

Comment:  
PublicKeyChallengeLength and PublicKeyProofLength should have values greater than or equal to 0, not 1.  It may be that these fields are intentionally left blank.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  897
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.7.1
Page:  38
Line:  3
CommentType:  TR

Comment:  
Description of public key authentication challenge
CommentEnd:  

SuggestedRemedy:  
What and where are the public key authentication challenge described?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  898
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.7.4
Page:  39
Line:  31
CommentType:  TR

Comment:  
Missing ReasonCode
CommentEnd:  

SuggestedRemedy:  
Table 14 does not define the ReasonCode.  The security subcommittee needs to provide the reason codes.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy ReasonCode from Table 13 to Table 14. Also close 455.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1416
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.7.4
Page:  39
Line:  32
CommentType:  TR

Comment:  
Reason Code needs to be defined in Table 14
CommentEnd:  

SuggestedRemedy:  
Define the reason code in Table 14.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Reason code to be added.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  899
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.7.4.2
Page:  39
Line:  44
CommentType:  E

Comment:  
missing phrase ...
CommentEnd:  

SuggestedRemedy:  
... of the results, via the reason code, of a previously ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  456
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.8
Page:  40
Line:  11
CommentType:  T

Comment:  
The device ID purpose is incorrect.
CommentEnd:  

SuggestedRemedy:  
Change "with which ... process" to "that is requesting the key"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  457
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.8
Page:  40
Line:  13
CommentType:  E

Comment:  
Acronyms for KeyPurpose not defined.
CommentEnd:  

SuggestedRemedy:  
Add acronyms for KEK, DEK, DIK and SEED to the acronym clause.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  458
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.8
Page:  40
Line:  25
CommentType:  T

Comment:  
The reason code for request key is missing.
CommentEnd:  

SuggestedRemedy:  
Add a row to the end of the table which is:  ReasonCode   Enumeration  SUCCESS, NOT_AUTHORIZED,  Indicates the result of                           TIME_OUT                  the key request command
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1666
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8 Table 15
Page:  40
Line:  
CommentType:  E

Comment:  
DistributeKeyFailureTimeout should be removed.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1665
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8 Table 15
Page:  40
Line:  725
CommentType:  T

Comment:  
EncryptedKeyObjectLength should have values greater than or equal to 0, not 1.  It may be that this field is intentionally left blank.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  904
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8.1.1
Page:  40
Line:  41
CommentType:  TR

Comment:  
PNC requirement to be the security manager
CommentEnd:  

SuggestedRemedy:  
In line 41 it is required that the PNC be the security manager, yet no place in the text is this function detailed.  The security subcommittee needs to provide the details.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  905
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8.2.2
Page:  41
Line:  19
CommentType:  TR

Comment:  
Line 19 indicates that "the PNC shall encrypt and return the designated key"
CommentEnd:  

SuggestedRemedy:  
Security committee needs to provide the encryption algorithm.  What is the algorithm?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  906
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8.2.2
Page:  41
Line:  22
CommentType:  TR

Comment:  
In line 22, reference is made to a null key and the appropriate result code.
CommentEnd:  

SuggestedRemedy:  
Security committee to provide definition of a null key and what are the associated (and appropriate) result codes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  907
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8.3
Page:  41
Line:  35
CommentType:  TR

Comment:  
Problem with ReasonCode parameter
CommentEnd:  

SuggestedRemedy:  
Referenced table 15 does not provide the reason code definitions.  Security committee needs to provide these reason codes.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add ReasonCode to Table 15 with values of SUCCESS or FAILURE.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1419
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8.3
Page:  41
Line:  35
CommentType:  TR

Comment:  
Reason code needs to be defined in Tsable 15.
CommentEnd:  

SuggestedRemedy:  
Define reason code in Table 15
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Add ReasonCode, type enumeration, valid range "SUCCESS, FAIL, TIMEOUT"
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  908
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8.3.1
Page:  41
Line:  43
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
change the last word in line 43 from "message" to "response".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  909
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.8.4
Page:  42
Line:  4
CommentType:  TR

Comment:  
in line 4, reference is made to an "encrypted format".
CommentEnd:  

SuggestedRemedy:  
Security subcommittee to provide the details as to what is this encrypted format.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1668
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.9
Page:  
Line:  
CommentType:  T

Comment:  
An MLME-DISTRIBUTE-KEY.response should be created so that the DEV that decided to distribute the key can know whether the key was successfully decrypted or not.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  
PROPOSED REJECT. If DEV does not properly decode message, it will make another request.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  459
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.9
Page:  42
Line:  35
CommentType:  T

Comment:  
The DeviceID description is incorrect.
CommentEnd:  

SuggestedRemedy:  
Change "which which ... process" to "to which the key will be sent"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  460
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.9
Page:  42
Line:  47
CommentType:  T

Comment:  
The ReasonCode for distribute key is not defined.
CommentEnd:  

SuggestedRemedy:  
Add the following to the end of table 16:  ReasonCode   Enumeration  SUCCESS, TIME_OUT   Indicates the result of the                                               distribute key command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1667
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.9 Table 16
Page:  42
Line:  3147
CommentType:  T

Comment:  
EncryptedKeyObjectLength should have values greater than or equal to 0, not 1.  It may be that this field is intentionally left blank.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  911
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.9.1/.2/.3
Page:  43
Line:  1
CommentType:  TR

Comment:  
Spelling error in 6.3.9.1, 6.3.9.2, and 6.3.9.3
CommentEnd:  

SuggestedRemedy:  
The commands are misspelt ... replace "distibute" with "distribute"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  912
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.9.2.2
Page:  43
Line:  45
CommentType:  T

Comment:  
question on command type
CommentEnd:  

SuggestedRemedy:  
Question for security committee ... in line 45 the command is given as "MLME.DISTRIBUTE-KEY.response".  Should this be "MLME.DISTRIBUTE-KEY.indication"?
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete second sentence in this paragraph "Then DME shall . . . Command." Also closes 461
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  461
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.3.9.2.2
Page:  43
Line:  45
CommentType:  T

Comment:  
The MLME-DISTRIBUTE-KEY.response command does not exist.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "The DME shall ... command."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1421
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.9.3
Page:  44
Line:  8
CommentType:  TR

Comment:  
Reason Code needs to be added to table 16
CommentEnd:  

SuggestedRemedy:  
Add reason code to table 16
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add to Table 16 ReasonCode, type enumeration, valid range "SUCCESS, TIMEOUT", Description "The result of the key distribution attempt."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  913
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.9.3
Page:  44
Line:  8
CommentType:  TR

Comment:  
ReasonCode missing
CommentEnd:  

SuggestedRemedy:  
Table 16 does not provide the reason code ... security committee needs to define the reason code.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolve as in 460.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  914
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.3.9.3.1
Page:  44
Line:  15
CommentType:  TR

Comment:  
Reference to "directed distribute key request command" and a "broadcast distributed key request command".  These seem like two different commands.
CommentEnd:  

SuggestedRemedy:  
Security commmittee needs to clarify what primitives handle these two commands.  Are they differentiated by parameters?  If so, which parameters?
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. They are differentiated by the DevID used to send the .request command.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  654
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.4
Page:  71
Line:  21
CommentType:  T

Comment:  
The MLME-PNC-HANDOVER message sequence chart is missing.
CommentEnd:  

SuggestedRemedy:  
Please insert Clause 6.3.1.34 MLME-DEV-INFO, MLME-PNC-HANDOVER, MLME-PROBE-PNC, and MLME-NEW-PNC message sequence chart from doc 01/410r1
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  653
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  6.4
Page:  71
Line:  26
CommentType:  T

Comment:  
The MLME-NEW-PNC.request, indication and confirm primitives are missing from the MLME-SAP interface clause.
CommentEnd:  

SuggestedRemedy:  
Please insert clauses 6.3.1.31 through 6.3.1.33.2 from doc 01/410r1 into the space just after Clause 6.3.18.5 MLME-PROBE-PNC message sequence chart.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  928
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.4
Page:  71
Line:  30
CommentType:  E

Comment:  
Modify first line of clause 6.4 as shown below.
CommentEnd:  

SuggestedRemedy:  
... PLME-SET primitives operating on the PHY PIB ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  929
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.4.1
Page:  71
Line:  47
CommentType:  T

Comment:  
Modify as shown below ...
CommentEnd:  

SuggestedRemedy:  
... shall be a request by the PLME to reset ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  482
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.4.19.1
Page:  92
Line:  22
CommentType:  T

Comment:  
The descriptions of When generated and Effect of receipt are copied from another sub-clause and are incorrect for this one.
CommentEnd:  

SuggestedRemedy:  
Change "sub-layer needs to ... of an MPDU." to be "sub-layer wants to change the PHY power management state." in 6.9.4.19.1, line 22  Change "will be to start the ... state machine." to be "will be to enter the indicated power management level." in 6.9.4.19.2, line 26
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  930
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.4.2.2
Page:  72
Line:  33
CommentType:  T

Comment:  
Modify as shown below ...
CommentEnd:  

SuggestedRemedy:  
The PLME is notified ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  931
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.4.3
Page:  72
Line:  44
CommentType:  E

Comment:  
remove comma
CommentEnd:  

SuggestedRemedy:  
Remove the comma after the parameter "DataRate".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  932
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.4.4.2
Page:  73
Line:  42
CommentType:  T

Comment:  
Modify as shown below ...
CommentEnd:  

SuggestedRemedy:  
The PLME is notified ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  933
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.4.5
Page:  74
Line:  3
CommentType:  E

Comment:  
Modify as shown below
CommentEnd:  

SuggestedRemedy:  
This optional primitive shall be a request by the PLME to ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  934
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.5.1
Page:  74
Line:  41
CommentType:  T

Comment:  
Add reference to table
CommentEnd:  

SuggestedRemedy:  
The PIB PNC group, Table 37, ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  935
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.5.2
Page:  74
Line:  46
CommentType:  T

Comment:  
Add reference to table
CommentEnd:  

SuggestedRemedy:  
The PIB characteristics group, Table 38, ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  936
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.5.3
Page:  74
Line:  51
CommentType:  T

Comment:  
Add reference to the table
CommentEnd:  

SuggestedRemedy:  
... authentication group, Table 39, ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1671
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.5.3 Table 39
Page:  76
Line:  319
CommentType:  T

Comment:  
Why does the device care about the last device to authenticate and deauthenticate?  Where does it get this information?
CommentEnd:  

SuggestedRemedy:  
Remove AuthenticateFailDevice (why is it called "Fail" anyway?) and DeauthenticateDevice.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  937
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.5.4
Page:  75
Line:  45
CommentType:  T

Comment:  
Add reference to table
CommentEnd:  

SuggestedRemedy:  
... association group, Table 40, contains ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  938
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.6
Page:  75
Line:  52
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... PHY PIB values that are unique to ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  939
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.6.1
Page:  76
Line:  34
CommentType:  T

Comment:  
modify as shown below
CommentEnd:  

SuggestedRemedy:  
... on the regulatory domains for the 2.4 GHz PHY is given in 11.1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1731
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  06
Subclause:  6.6.1
Page:  76
Line:  41
CommentType:  T

Comment:  
5 GHz and UWB are assumed to be future spectral bands to be used without any justification or mention given a prior. This is confusing.
CommentEnd:  

SuggestedRemedy:  
The 5 GHz and UWB should not be mentioned in this table to avoid confusion.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  444
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.6.1
Page:  76
Line:  42
CommentType:  T

Comment:  
The assignment of 5 GHz and UWB PHY layers presumes too much.  It is not clear if there will be another PHY layer, if so what format it will be or what it will be called.  If a new PHY layer is added, the new draft can add its definition to the PIB.  It is not required at this time.
CommentEnd:  

SuggestedRemedy:  
Delete the assignments for 5 GHz and UWB.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  940
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.6.2
Page:  77
Line:  4
CommentType:  TR

Comment:  
The text in line 4 claims there is a mapping between the data rate vector and the actual data rate that is PHY dependent.  Where is this mapping in clause 11.  How does this map to the PHYPIB_DataRateVector and the PHYPIB_CurrentDataRate?
CommentEnd:  

SuggestedRemedy:  
Refer to the PHY subgroup.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1732
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  06
Subclause:  6.6.8
Page:  79
Line:  5
CommentType:  T

Comment:  
PHYPIB_CCA_Threshold is programmable but not enough guidance as to what values it should assume has been given in the standard.
CommentEnd:  

SuggestedRemedy:  
I suggest that CCA threshold values should be defined depending on TX power levels similar to 802.11b standard.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  445
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.6.8
Page:  79
Line:  5
CommentType:  T

Comment:  
The CCA threshold should depend on the transmitter power, which can be changed.
CommentEnd:  

SuggestedRemedy:  
Change "Static" to "Dynamic"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1696
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  06
Subclause:  6.6.9
Page:  79
Line:  1023
CommentType:  TR

Comment:  
6.6.9 PHY PIB ranging support: The PHYPIB_Range object calls for two octets, range in meters in the first octet, and fractional part of a meter in cm for the second octet.  At the moment nothing supports this in clause 11. It is too early to understand if this is the correct format to carry us into the future.  Since we don't know how "location awareness," which might include ranging and other attributes, will be addressed in 3a. It is better to remove the object now rather than be faced with a work-around in the future.
CommentEnd:  

SuggestedRemedy:  
Remove the PHYPIB_Range object.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1733
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  06
Subclause:  6.6.9
Page:  79
Line:  19
CommentType:  T

Comment:  
Both "m" and "cm" portion of the range have been given an octet. Since the range is less than 10 m, I think the "cm" portion should be given more bits.
CommentEnd:  

SuggestedRemedy:  
Allocate more bits for the fraction part of the range.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  945
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.6.9
Page:  79
Line:  9
CommentType:  TR

Comment:  
Need to add a statement to clause 6.6.9 that the PHY of clause 11 does not support ranging.
CommentEnd:  

SuggestedRemedy:  
Add the following statement at the end of line 12   (Note: the IEEE802.15.3 PHY of clause 11 does not currently support ranging).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  475
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.7.1.1
Page:  80
Line:  4
CommentType:  T

Comment:  
Multicast is not supported in this standard.
CommentEnd:  

SuggestedRemedy:  
Delete the words "and multicast" from three places, line 4 in 6.7.1.1, line 15 in 6.7.1.2 and line 33 in 6.7.3.  Also, change "reorderable multicast service" to be "reorderable broadcast service"
RemedyEnd:  

Response:  
PROPOSED REJECT. Add a paragraph in clause 8 that defines the scope and intention of multicast in this draft. 8.6.1 is the target clause. WMS to write text.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  1452
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.7.1.1
Page:  80
Line:  6
CommentType:  E

Comment:  
The sentence "Broadcast and Multicast transport are part of the asynchronous data service provided by the MAC." provides no information.  Unicast is part of the data service, too.
CommentEnd:  

SuggestedRemedy:  
Remove this sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1454
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.7.1.1
Page:  80
Line:  6
CommentType:  TR

Comment:  
"All DEVs shall support the asynchronous data service."  This is a LAN mentality, not WPAN.  Devs can may be simplified by eliminating asynchronous data service.
CommentEnd:  

SuggestedRemedy:  
Make asynchronous data service optional.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1453
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.7.1.2
Page:  80
Line:  15
CommentType:  E

Comment:  
The sentence "Broadcast and Multicast transport are part of the asynchronous data service provided by the MAC." provides no information.  Unicast is part of the data service, too.
CommentEnd:  

SuggestedRemedy:  
Remove this sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  77
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  06
Subclause:  6.7.2
Page:  80
Line:  1824
CommentType:  TR

Comment:  
The 802.15.3 MAC does not support any prioritization of MSDUs delivered to it nor does it directly handle parameterized QoS requests. This section seems to be left over from earlier drafts that had an as yet undefined model for QoS that was not accepted.
CommentEnd:  

SuggestedRemedy:  
Remove Section 8.7.2.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Move the paragraph to Annex A.3.1
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1455
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.7.3
Page:  80
Line:  3439
CommentType:  E

Comment:  
Remove reference to strictly ordered service class.  This is an 802.11 holdover.
CommentEnd:  

SuggestedRemedy:  
Remove references about strictly ordered service class.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  233
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.7.3
Page:  80
Line:  3942
CommentType:  E

Comment:  
The following sentences do not end in a period: "device and the intended recipient devices" and "However, it does not maintain ordering among MSDUs belonging to different streams"
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  947
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.7.3
Page:  80
Line:  41
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
change the sentence at the end of line 41 and the beginning of line 42 as:  ... identified logical connection; however, it does not ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  551
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  06
Subclause:  6.8
Page:  76
Line:  41
CommentType:  TR

Comment:  
PHYPIB_CCA_Threshold is programmable but not enough guidance as to what values it should assume has been given in the standard.
CommentEnd:  

SuggestedRemedy:  
CCA threshold values should be defined depending on TX power levels similar to 802.11b standard.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  948
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.8
Page:  80
Line:  49
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... to understand the parameters which need ...  (remove the comma after the word parameters)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1456
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.8.1
Page:  81
Line:  
CommentType:  T

Comment:  
Need a MAC_DATA.confirm to indicate status in the event of a failure.
CommentEnd:  

SuggestedRemedy:  
Add a MAC_DATA.confirm
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  949
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.8.1
Page:  81
Line:  36
CommentType:  E

Comment:  
remove comma
CommentEnd:  

SuggestedRemedy:  
remove comma after the parameter  Data
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  950
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.8.2
Page:  82
Line:  13
CommentType:  E

Comment:  
remove comma
CommentEnd:  

SuggestedRemedy:  
remove comma after the parameter  ReceptionStatus
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  951
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.9.1
Page:  82
Line:  32
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
add a comma as shown below  ... characteristics of, and methods of, transmitting and ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  476
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.9.3
Page:  82
Line:  46
CommentType:  T

Comment:  
There is only one type of primitive defined in the PHY service specification now.
CommentEnd:  

SuggestedRemedy:  
Delete "The primitives associated ...  sub-layer to sub-layer interactions." and connect the following paragraph to the previous one.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  234
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.9.3
Page:  82
Line:  46
CommentType:  E

Comment:  
The term "sub-layer", used in the subclause title "...This sub-clause provides an overview of the PHY services."
CommentEnd:  

SuggestedRemedy:  
Change to "sublayer", dropping the hyphen.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  477
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.9.3.1
Page:  83
Line:  1
CommentType:  T

Comment:  
This sub-clause is redundant and therefore really irritates the technical editor while simultaneously promoting bad habits.
CommentEnd:  

SuggestedRemedy:  
Delete sub-clause 6.9.3.1 in its entirety and wipe it from our minds.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  478
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.9.4.1
Page:  84
Line:  51
CommentType:  T

Comment:  
The definition of the DATA parameter is redundant and annoying.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "The DATA parameters is an octet value." in 6.9.4.1 and 6.9.4.2.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  237
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.9.4.11.2
Page:  88
Line:  44
CommentType:  E

Comment:  
The following sentence does not end in a period: The effect of receipt of this primitive by the MAC is unspecified
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  955
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.9.4.12
Page:  89
Line:  6
CommentType:  TR

Comment:  
In line 6 and also in line 10, the parameter STATE is incorrect.  The parameter name is actually STATUS.  This is needed to be consistent with table 54.
CommentEnd:  

SuggestedRemedy:  
Replace STATE with STATUS in two places as discussed above.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  480
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.9.4.12.1
Page:  89
Line:  18
CommentType:  T

Comment:  
The criteria given are not applicable to this standard.
CommentEnd:  

SuggestedRemedy:  
Change "the period indicated ... has expired." to be "the chnannel has been quiet for an aCCADetectTime period."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  481
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.9.4.13
Page:  89
Line:  34
CommentType:  T

Comment:  
The AntSelect parameter is already defined and we don't need any more ants at our picnic.
CommentEnd:  

SuggestedRemedy:  
Replace the sentence "AntSelect is an ... shall be used." with "The primitive parameter is defined in Table 55"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  238
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.9.4.18
Page:  91
Line:  33
CommentType:  E

Comment:  
The following sentence does not end in a period: — NoError. This value is used to indicate that no error occurred during the receive process in the PHY
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  26
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  06
Subclause:  6.9.4.19
Page:  92
Line:  1
CommentType:  TR

Comment:  
It is not clear, how a PHY may be returned to the powered state. This primitive is specified for placing the PHY in one of several available power states. It is recommended that the primitive also serve to restore full power. As an alternative, an additional primitive may meet the requirement.
CommentEnd:  

SuggestedRemedy:  
in 6.9.4.19 table 57 note that this includes the state for a fully powered PHY in 6.6.10 table 50, make the same note  some text touch up may be desired so it is clear that powering up is also via the same mechanism.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Jay Bain to provide exact text updates.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  956
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.9.4.19
Page:  92
Line:  3
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... to the local PHY to enter the ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  27
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  06
Subclause:  6.9.4.19.1
Page:  92
Line:  19
CommentType:  TR

Comment:  
the text of both when generated and effect of receipt seems to have been pasted from elsewhere and does not match the power managment of this sub-clause.
CommentEnd:  

SuggestedRemedy:  
change the when generated to : This primitive will be issued by the MAC sub-layer to the PHY entity whenever the MAC sub-layer needs to change the power state of the PHY  change the effect of receipt to : The effect of receipt is to transistion the PHY to the desired state if possible, and then generate the PHY-PWRMGT.confirm primitive
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Also closes 482.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  479
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  06
Subclause:  6.9.4.4
Page:  86
Line:  11
CommentType:  T

Comment:  
There is no PLCP
CommentEnd:  

SuggestedRemedy:  
Change "contains both the PLCP and PHY" to be "contains the PHY"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1459
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  6.9.4.4.2
Page:  86
Line:  21
CommentType:  TR

Comment:  
Need to specify that the preamble starts when this command is received.
CommentEnd:  

SuggestedRemedy:  
Specify that the Preamble starts when PHY-TX-START.request is received.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  236
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  6.9.4.9.2
Page:  88
Line:  8
CommentType:  E

Comment:  
The following sentence does not end in a period: The effect of receipt of this primitive by the MAC is unspecified
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  146
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  7.1.1
Page:  80
Line:  8
CommentType:  E

Comment:  
It is indicate that two services classes exist.  This is an introduction paragraph, the classes should be listed.
CommentEnd:  

SuggestedRemedy:  
List the service classes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  147
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  8
Page:  80
Line:  44
CommentType:  T

Comment:  
MAC CPS SAP is not shown in Figure 2.  It is hard to understand how it fits in without seeing the relationships pictorially.
CommentEnd:  

SuggestedRemedy:  
Add MAC CPS SAP to Figure 2.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  150
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  9.4.11
Page:  88
Line:  30
CommentType:  E

Comment:  
"PHY has begun the CCA process." - shouldn't this be "ended the CCA process"?  Possible cut and paste oversight.
CommentEnd:  

SuggestedRemedy:  
Fix
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  23
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  06
Subclause:  figure 2
Page:  19
Line:  18
CommentType:  T

Comment:  
It would seem that the reference model should include something like a convergence layer for QoS.
CommentEnd:  

SuggestedRemedy:  
Update the figure to include QoS sublayer if appropriate
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy Figure A.1 to Figure 2 with any appropriate changes. Make sure suppporting text is adequate.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1390
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Figure 2
Page:  19
Line:  18
CommentType:  T

Comment:  
How does MAC-CPS fit in to Figure 2?  Is the MAC-SAP in figure 2 the MAC-CPS SAP or the SSCS SAP?
CommentEnd:  

SuggestedRemedy:  
Make clear whether what is called the MAC in Figure 2 is the MAC-CPS, or both the MAC-CPS and the SSCS.  It is not clear how Figure 2 and Figure A.1 are related.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy Figure A.1 to Figure 2 with any appropriate changes. Make sure suppporting text is adequate.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  222
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  Figure 2
Page:  19
Line:  2829
CommentType:  E

Comment:  
In Figure 6-2 the term "MAC sub-layer" and "PHY sub-layer" are incorrectly used; it should be MAC sublayer and PHY layer, respectively.
CommentEnd:  

SuggestedRemedy:  
Change Figure 6-2 to read "MAC sublayer" and "PHY layer".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  140
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  Figure 3
Page:  54
Line:  1
CommentType:  E

Comment:  
Which way is the communication flowing?  DEV1 to DEV2 or vice versa?
CommentEnd:  

SuggestedRemedy:  
Make a clear statement to the reader of communication flow.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1439
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Figure 8
Page:  64
Line:  10
CommentType:  E

Comment:  
Why is the PNC on of the MLMEs in a channel status request?
CommentEnd:  

SuggestedRemedy:  
Change to DEV-1 and DEV-2
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1432
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Figure3
Page:  54
Line:  6
CommentType:  E

Comment:  
Move the PNC to in between Dev A and Dev B since A and B only talk to the PNC.  This will simplify the drawing.
CommentEnd:  

SuggestedRemedy:  
Move the PNC to in between Dev A and Dev B since A and B only talk to the PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  668
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 10
Page:  33
Line:  15
CommentType:  T

Comment:  
DeviceID parm name, data type, valid range, and description are incorrect
CommentEnd:  

SuggestedRemedy:  
Change parm name to: DeviceAID; data type to: Integer; valid range to:0-255; and description to: "Specifies the DEVAID of the peer device with which to perform the disassociation process."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. DevID, type Integer, range any valid DevID (xref 7.2.3) Specifies the DevID of the peer MAC entity . . .
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  584
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 10
Page:  33
Line:  19
CommentType:  T

Comment:  
ReasonCode is unneccesary.
CommentEnd:  

SuggestedRemedy:  
Please remove ReasonCode from Table 10.
RemedyEnd:  

Response:  
PROPOSED REJECT.  Recognize that most of the reason codes may be removed, but there are still at least two different reasons required.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  887
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 11
Page:  34
Line:  1
CommentType:  E

Comment:  
Incorrect Title
CommentEnd:  

SuggestedRemedy:  
Should be  MLME-DISASSOCIATE.indication primitive parameters
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  590
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 11
Page:  34
Line:  10
CommentType:  T

Comment:  
ReasonCode is unnecessary.
CommentEnd:  

SuggestedRemedy:  
Please remove ReasonCode from Table 11.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  589
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 11
Page:  34
Line:  5
CommentType:  T

Comment:  
DeviceID parameter name, data type, Valid range and description fields are incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change DeviceID to DeviceAID; data type to: Integer; valid range to: 1-255; description to: " Specifies the DEVAID of the peer device with which the association relationship is terminated.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change DeviceID to DevID; data type to: Integer; valid range to: 1-255; description to: " Specifies the DevID of the peer device with which the association relationship is terminated.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  888
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 12
Page:  34
Line:  22
CommentType:  E

Comment:  
Incorrect Title
CommentEnd:  

SuggestedRemedy:  
Should be  MLME-DISASSOCIATE.confirm primitive parameters
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  889
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 13
Page:  35
Line:  1
CommentType:  T

Comment:  
Under the Type column ... should the integer type be defined as to the number of octets?    Also, what is the nature of the byte string ... shouldn't the number of bytes be specified?
CommentEnd:  

SuggestedRemedy:  
Refer to MAC/security subcommittee to supply number of octets.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Will use integer and octet strings in tables.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  893
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 13
Page:  35
Line:  17
CommentType:  T

Comment:  
Wrong word
CommentEnd:  

SuggestedRemedy:  
second line of description for AuthenticationInfoLength parameter ...  change the word "device" to "defined"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  60
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  06
Subclause:  Table 13
Page:  35
Line:  17
CommentType:  E

Comment:  
'device' used instead of 'defined'
CommentEnd:  

SuggestedRemedy:  
Replace "format as device" with "format as defined"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  890
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 13
Page:  35
Line:  22
CommentType:  TR

Comment:  
Unused parameters
CommentEnd:  

SuggestedRemedy:  
The following are listed as parameters for a primitive ... but no primitives use these.  Where are they used?  SecurityManagerPublicKeyObjectLength SecurityManagerPublicKeyObject
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  891
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 13
Page:  35
Line:  28
CommentType:  T

Comment:  
Unused parameters
CommentEnd:  

SuggestedRemedy:  
Delete the following parameters from table 13.  They are used in table 14 and are redundant.  PublicKeyChallengeLength PublicKeyChallenge PublicKeyProofLength PublicKeyProof
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  892
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 13
Page:  35
Line:  8
CommentType:  TR

Comment:  
Reference to cipher suite
CommentEnd:  

SuggestedRemedy:  
The description for the parameter DEVPublicKeyObject refers to a cipher suite.  The cipher suite details are not present in draft 9 text.  Needs to be added.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  74
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  06
Subclause:  Table 14
Page:  37
Line:  0
CommentType:  TR

Comment:  
The MLME-CHALLENGE primitive parameters does not include the ReasonCode parameter
CommentEnd:  

SuggestedRemedy:  
Add ReasonCode to Table 14 as an Enumeration, Valid Range of SUCCESS or TIMEOUT, and Description as "The result of the challenge command." Note that success here is defined to be reception of a valid Challenge.confirm frame from the peer DEV and not whether the PublicKeyProof is correct.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add ReasonCode to Table 14 as an Enumeration, Valid Range of SUCCESS, FAILURE, or TIMEOUT, and Description as "The result of the challenge command." Note that success here is defined to be reception of a valid Challenge.confirm frame from the peer DEV and not whether the PublicKeyProof is correct. Also closes 455.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  896
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 14
Page:  37
Line:  35
CommentType:  T

Comment:  
Under the Type column ... should the integer type be defined as to the number of octets?    Also, what is the nature of the byte string ... shouldn't the number of bytes be specified?
CommentEnd:  

SuggestedRemedy:  
Refer to MAC/security subcommittee to supply number of octets.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Will use integer and octet strings in tables.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  901
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 15
Page:  40
Line:  
CommentType:  T

Comment:  
Need octets associated with Types integer and  byte string in table 15
CommentEnd:  

SuggestedRemedy:  
MAC/security provide octets
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Will use integer and octet strings in tables.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  903
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 15
Page:  40
Line:  
CommentType:  TR

Comment:  
Unused parameter
CommentEnd:  

SuggestedRemedy:  
In table 15, the parameter DistributeKeyFailureTimeout is defined but not used by any primitives.  Security committee needs to clarify.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Remove DistributeKeyFailureTimeout from Table 15.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  902
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 15
Page:  40
Line:  
CommentType:  TR

Comment:  
Add following to clause 4 acronyms
CommentEnd:  

SuggestedRemedy:  
DEK DIK SEED
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  900
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 15
Page:  40
Line:  13
CommentType:  TR

Comment:  
Lacking definition and explaination
CommentEnd:  

SuggestedRemedy:  
security subcommittee needs to define and explain usage of the following items from table 15  KEK DEK DIK SEED
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  910
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 16
Page:  42
Line:  
CommentType:  TR

Comment:  
In type column of table 16, how many octets are required?
CommentEnd:  

SuggestedRemedy:  
security committee to provide octets
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Will use integer and octet strings in Tables.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  593
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 18
Page:  46
Line:  19
CommentType:  T

Comment:  
DeviceID is an unnecessary entry in the parameter table.
CommentEnd:  

SuggestedRemedy:  
Please remove.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1398
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 2
Page:  23
Line:  
CommentType:  E

Comment:  
What does this mean "The operating superframe length adjusts this value."
CommentEnd:  

SuggestedRemedy:  
Please clarify
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1397
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 2
Page:  24
Line:  12
CommentType:  T

Comment:  
Why is EPSTime in ms and not superframes?
CommentEnd:  

SuggestedRemedy:  
Change EPS time to superframes.  Only 8 bits needed.
RemedyEnd:  

Response:  
PROPOSED REJECT. This is just to wake up the dev host. Not required who did it and could be multiple.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  877
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 2
Page:  24
Line:  17
CommentType:  E

Comment:  
Run on sentence ... add white space.
CommentEnd:  

SuggestedRemedy:  
... management mode.  Defined in ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1399
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 2
Page:  24
Line:  17
CommentType:  E

Comment:  
"This element has no meaning if the EPS DEV is not in power management mode."  In WHAT power mangement mode.
CommentEnd:  

SuggestedRemedy:  
Please clarify should probably be EPS mode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1396
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 2
Page:  24
Line:  19
CommentType:  T

Comment:  
Is EPS Sync only allowed in the PNC?
CommentEnd:  

SuggestedRemedy:  
Clarify
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Clarification will be made in 7.5.7.1.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  878
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 2
Page:  24
Line:  25
CommentType:  E

Comment:  
missing definite article
CommentEnd:  

SuggestedRemedy:  
from errors rather than waiting for the next
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  879
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 2
Page:  24
Line:  43
CommentType:  TR

Comment:  
Reason code definitions ... there are no reason codes in clause 7.5.7.2
CommentEnd:  

SuggestedRemedy:  
have management subgroup provide proper reference to reason codes
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change xref from 7.5.7.2. To Table 67. Change ResonCode to ActionType.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  918
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 22
Page:  49
Line:  
CommentType:  TR

Comment:  
Provide a figure that shows the vector representation of "ServiceFlowList" and "ARQList" as reflected in tables 23 and 24 respectively.
CommentEnd:  

SuggestedRemedy:  
Add these two figures to clause 6.3.13
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1427
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 22
Page:  49
Line:  
CommentType:  TR

Comment:  
Direction bit needed for the MLME-CREATE-STREAM parameters.
CommentEnd:  

SuggestedRemedy:  
Add direction bit.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add a field, name direction, type integer, valid range 0-1, description, "The direction of the stream, as defined in 7.5.10.3."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1426
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 22
Page:  49
Line:  17
CommentType:  TR

Comment:  
2 octet SequenceNumber is inconsistent with the 1 octet stream requeest identifier in the stream request command.  Also, we have a Sequence Number field in the MAC header - 2 words, but still too close.
CommentEnd:  

SuggestedRemedy:  
Change 2 octet Sequence Number field to 1 octet StreamRequestIdentifier.  Change all instances of SequenceNumber to StreamRequestIdentifier in all of clause 6.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Use type integer, valid range 0-255.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1425
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 22
Page:  49
Line:  5
CommentType:  TR

Comment:  
Source Address and destination address should be the 48 bit MAC address, not the 8 bid AD-AD.  This is for 2 reasons:  1) to be consistent with the other MLMEs.  Wo does the address translation, the DME or the MLME?  We need to be consistent.  Second, the stream request command should contain MAC addresses, not AD-ADs to safeguard against discrepancies.
CommentEnd:  

SuggestedRemedy:  
Replace these 8 bit AD-ADs with 48 bit MAC Address
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1429
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 23
Page:  49
Line:  3540
CommentType:  TR

Comment:  
Remove Peak Rate, Min rate and Max Burst Size from from service flow and stream mangement.  The PNC cannot guarantee any of these.  It can only guarantee channel time.  If RSVP or other reservation protocol is used, the will negotiate at a higher layer, not at the MAC.
CommentEnd:  

SuggestedRemedy:  
Remove Peak Rate, Min rate and Max Burst Size from from service flow  and stream management.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  CTR
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  139
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  Table 23
Page:  49
Line:  49
CommentType:  TR

Comment:  
Is MaxTXDelayVariation the same thing as Jitter?  802.11e has both a jitter and a delay bound.  Which is being specified here?
CommentEnd:  

SuggestedRemedy:  
I would like to see both jitter and delay defined.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. MaxTXDelayVariation is jitter within the MAC layer. 802.11e is CSMA and 802.15.3 is TDMA in the GTS. This command only deals with TDMA allocation in GTS.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  920
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 25
Page:  55
Line:  
CommentType:  TR

Comment:  
Add a figure to show the ChannelTimeList vector as referenced in table 26
CommentEnd:  

SuggestedRemedy:  
Add this figure
RemedyEnd:  

Response:  
PROPOSED REJECT. Table 25 references table 26 where it is defined.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  921
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 25
Page:  55
Line:  
CommentType:  TR

Comment:  
How is EPS impacted by a stream modification.  Does the "SlotStartTimeSet" parameter shown in table 25 also apply to SFNext?
CommentEnd:  

SuggestedRemedy:  
Refer this question to the power management subcommittee.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. The power management section and MLME's will be rewritten based on the Dallas minutes, documents 01/138r2 and 02/067r1. The overloading of CTRB's will be stopped and new elements defined.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  141
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  Table 26
Page:  55
Line:  42
CommentType:  TR

Comment:  
Is Maximum allocation delay the same thing as Jitter?  802.11e has both a jitter and a delay bound.  Which is being specified here?
CommentEnd:  

SuggestedRemedy:  
I would like to see both jitter and delay defined.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. Maximum Allocation Delay should be Maximum Allocation Delay Variation. It represents the amount of variation in the delay which is jitter. Change as indicated in the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  605
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 28
Page:  61
Line:  33
CommentType:  T

Comment:  
The RemoteDEVAddress is an inconsistent parameter name.  Also its data type is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change RemoteDevAddress to RemoteDevAID and its data type to an integer with a range of 0-255
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change RemoteDevAddress to RemoteDevID and its data type to an integer with a range of 0-255
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  622
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 29
Page:  64
Line:  45
CommentType:  T

Comment:  
The ChannelChangeTimeout data type is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the data type from octet to Duration with valid range of 0 to 255 ms?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  562
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 3
Page:  26
Line:  16
CommentType:  TR

Comment:  
The OpenScan paramter is unneeded.
CommentEnd:  

SuggestedRemedy:  
Please remove the OpenScan parameter from Table 3.
RemedyEnd:  

Response:  
PROPOSED REJECT.     
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  563
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 3
Page:  26
Line:  22
CommentType:  TR

Comment:  
The definition for PNID is partially correct.
CommentEnd:  

SuggestedRemedy:  
Please change the definition from its current text to: PNID "indicates to the MLME to either search for a specific PNID when the PNID is set to 0x0000 through 0xFFFE, or search for all PNIDs when the PNID is set to 0xFFFF."
RemedyEnd:  

Response:  
PROPOSED REJECT. Openscan is used rather than a reserved PNID.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  881
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 3
Page:  26
Line:  27
CommentType:  T

Comment:  
Valid range for the ChannelScanDuration
CommentEnd:  

SuggestedRemedy:  
range is listed as 100-65535 ... should this be 0-65535?
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  564
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 3
Page:  26
Line:  29
CommentType:  T

Comment:  
The last sentence of the ChannelScanDuration description is not needed.
CommentEnd:  

SuggestedRemedy:  
Please remove the last sentence of the ChannelScanDuration description.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  629
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 30
Page:  66
Line:  11
CommentType:  T

Comment:  
DEVInfoSet is an incorrect parameter name.
CommentEnd:  

SuggestedRemedy:  
Please change the DEVInfoSet parameter name to: PNCInfoSet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  627
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 30
Page:  66
Line:  5
CommentType:  T

Comment:  
QueriedDEVIDSet is an incorrect parameter name, data type and valid range.
CommentEnd:  

SuggestedRemedy:  
Please change the QueriedDEVIDSet parameter name to QueriedDEVAID; its data type to Integer, and its valid range to 0-255.  Also change the description to: " The QueriedDEVAID when set to an integer value less than 255 will return information from the PNC regarding a CTA for a specific DEV.  It the QueriedDEVAID is set to a broadcast AID value of 255 then the PNC will return CTA information for all the associated DEVs.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change the QueriedDEVIDSet parameter name to QueriedDevID; its data type to Integer, and its valid range to 0-255.  Also change the description to: " The QueriedDevID when set to an integer value less than 255 will return information from the PNC regarding a CTA for a specific DEV.  It the QueriedDevID is set to a broadcast ID value of 255 then the PNC will return CTA information for all the associated DEVs.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  628
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 30
Page:  66
Line:  8
CommentType:  T

Comment:  
The RequestorDEVAddress parameter name, its data type, valid range and description are incorrrect.
CommentEnd:  

SuggestedRemedy:  
Please change the RequestorDEVAddress to RequestorDEVAID, its data type to Integer, its valid range to 0-255 and its description to:"The DEVAID of the DEV that is requesting the information from the PNC.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change the RequestorDEVAddress to RequestorDevID, its data type to Integer, its valid range to 0-255 and its description to:"The DevID of the DEV that is requesting the information from the PNC.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  642
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 31
Page:  68
Line:  39
CommentType:  T

Comment:  
DestinationDEVAddress parameter name is incorrect, data type is incorrect, valid range is incorrect, and description are incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change parameter name to RemoteDEVAID, data type to Integer, Valid range to 0-255, and description to: "The RemoteDEVAID of the DEV from ..."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change parameter name to RemoteDevID, data type to Integer, Valid range to 0-255, and description to: "The RemoteDevID of the DEV from ..."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  643
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 31
Page:  68
Line:  42
CommentType:  T

Comment:  
RequestorDEVAddress parameter name is incorrect, the data type is incorrect, valid range is incorrect, and the description is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change parameter name to: RequestorDEVAID, the data type to: Integer, the valid range to: 0-255, and the description to: " The DEVAID of the DEV requesting the information."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change parameter name to: RequestorDevID, the data type to: Integer, the valid range to: 0-255, and the description to: " The DevID of the DEV requesting the information."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  644
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 31
Page:  68
Line:  50
CommentType:  T

Comment:  
The ReasonCode data type field is incorrect and its valid range is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change ReasonCode data type field to: Enumeration, and the valid range to: "SUCCESS, RESPONSE_TIMEOUT
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1447
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 38
Page:  75
Line:  34
CommentType:  T

Comment:  
Dont really need 65535 CTAs
CommentEnd:  

SuggestedRemedy:  
Change MACPIBMaxProcessedCTAs to 8 bits
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1248
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 39
Page:  76
Line:  
CommentType:  TR

Comment:  
The second entry in this table is "privacy".  Are we going to call this privacy or security.
CommentEnd:  

SuggestedRemedy:  
Remove all reference to "privacy and private" and replace with "security or secure".  (The other way around is ok to, but we need to be consistent.)
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. Change the name, add 3 options, no authentication, authentication, authentication and payload protection.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  145
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  Table 41
Page:  76
Line:  40
CommentType:  E

Comment:  
PHYPIB_Type includes definitions for currently undefined PHYs (5 GHz and UWB).  It is good to put a place holder, but do not presume a solution before the SG3a group has a chance to determine future possibilities.
CommentEnd:  

SuggestedRemedy:  
Indicate the values are reserved for future PHYs
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  232
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  06
Subclause:  Table 41
Page:  76
Line:  43
CommentType:  E

Comment:  
In Table 41 the terms "UWB and ETSI, FCC, IC, ARIB" are introduced for the first time and are not defined in this clause and/or Clause 4.
CommentEnd:  

SuggestedRemedy:  
Please add "UWB ultra-wideband and ETSI European Telecommunications Standards Institute, FCC Federal Communications Commission, IC Industry Canada, ARIB Association of Radio Industries and Businesses" to Clause 4.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  941
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 44
Page:  77
Line:  
CommentType:  TR

Comment:  
The Managed objects are PHY dependent but are not defined in clause 11.
CommentEnd:  

SuggestedRemedy:  
The PHY subcommittee needs to add the following items to clause 11  PHYPIB_TxMaxPower PHYPIB_TxPowerStepSize PHYPIB_CurrentPowerLevel
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  942
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 47
Page:  78
Line:  
CommentType:  TR

Comment:  
Managed Object in Table 47 is misspelt
CommentEnd:  

SuggestedRemedy:  
Correct spelling ... it should be  PHYPIB_MPDULengthMax
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  943
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 47
Page:  78
Line:  
CommentType:  TR

Comment:  
Clause 11 does not list the managed object
CommentEnd:  

SuggestedRemedy:  
Define PHYPIB_MPDULengthMax in clause 11 ... refer to PHY subcommittee
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  944
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 48
Page:  79
Line:  
CommentType:  TR

Comment:  
Managed Object is misspelt
CommentEnd:  

SuggestedRemedy:  
Spelling should be  PHYPIB_CCAThreshold
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  565
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 5
Page:  27
Line:  35
CommentType:  TR

Comment:  
DeviceID is inconsistently used through out the document.
CommentEnd:  

SuggestedRemedy:  
Please change DeviceID to DeviceAddress when referring to a parameter of data type address(48bit).  It is a more accurate description of the data type.  The association between DeviceID and MAC address is not intuitively obvious.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Use DEV Address and DEVAddress instead of DeviceID and Device ID as appropriate when referring to a 48-bit MAC address.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  566
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 5
Page:  27
Line:  37
CommentType:  T

Comment:  
The Beacon  Period data type is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the  Beacon Period data type to duration.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change all time durations to be type duration, change most octets to be integer, byte string to octet string, only in type columns of tables in clause 6.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  567
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 5
Page:  27
Line:  39
CommentType:  T

Comment:  
The parameter Channel is incomplete.
CommentEnd:  

SuggestedRemedy:  
Please change the parameter Channel to ChannelIndex and its data type to integer.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  568
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 5
Page:  27
Line:  41
CommentType:  T

Comment:  
The parameter name " Parent Device ID" is inconsistent.
CommentEnd:  

SuggestedRemedy:  
Please change the parameter name from Parent Device ID to ParentDevAddress which is more consistent with its data type of MAC address(48bit)
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  946
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 50
Page:  79
Line:  
CommentType:  TR

Comment:  
Clause 11 does not address the managed objects of table 50
CommentEnd:  

SuggestedRemedy:  
The PHY committee needs to add reference to the values used for PHYPIB_NumPSLevels and PHYPIB_PSLevelReturn.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  952
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 54
Page:  84
Line:  
CommentType:  T

Comment:  
Add figures to illustrate the vectors TXVECTOR and RXVECTOR
CommentEnd:  

SuggestedRemedy:  
add two figures
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  149
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  Table 54
Page:  84
Line:  11
CommentType:  E

Comment:  
"A set of parameters" - not very descriptive
CommentEnd:  

SuggestedRemedy:  
add "(see Table 56)"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  148
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  06
Subclause:  Table 54
Page:  84
Line:  8
CommentType:  E

Comment:  
"A set of parameters" - not very descriptive
CommentEnd:  

SuggestedRemedy:  
add "(see Table 55)"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  953
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 55
Page:  84
Line:  
CommentType:  TR

Comment:  
Unused parameter ...
CommentEnd:  

SuggestedRemedy:  
In table 55, in the value column for parameter Length, it is stated the max number of octets is determined by PHYPIB_LengthMax.  Should this be PHYPIB_MPDU_LengthMax.  If not, then where is PHYPIB_LengthMax defined?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1458
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 56
Page:  84
Line:  33
CommentType:  TR

Comment:  
Remove PHYPIB_DataRates from the Rx vector.  It should be Rxtate, not PIB.
CommentEnd:  

SuggestedRemedy:  
Change PHYPIB_DataRates to RxRate
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  883
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 6
Page:  28
Line:  25
CommentType:  T

Comment:  
Type for SyncFailureTimeout
CommentEnd:  

SuggestedRemedy:  
Should this be one octet?  Is there an upper limit?
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolved as in 566. Upper limit not specified.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  570
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 8
Page:  29
Line:  25
CommentType:  T

Comment:  
DeviceID is inconsistent with its data type.
CommentEnd:  

SuggestedRemedy:  
Please change DeviceID to DeviceAddress since its data type is MAC address(48bit)
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. DEVAddress
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  884
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table 8
Page:  29
Line:  31
CommentType:  T

Comment:  
Type for AssociationTimeOutPeriod
CommentEnd:  

SuggestedRemedy:  
Should be integer with 2 octets
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Duration. See 566 for direction.Change valid range to be Xref to 7.5.2.1. Add in 7.5.2.1, this implies a range of 0-65535 ms.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  572
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 8
Page:  29
Line:  32
CommentType:  TR

Comment:  
AssociationTimeOutPeriod has an incorrect data type.
CommentEnd:  

SuggestedRemedy:  
The AssociationTimeOutPeriod data type should be changed from Integer to Duration.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  571
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 8
Page:  29
Line:  33
CommentType:  T

Comment:  
AssocDevAddress is inconsistent with its data type.
CommentEnd:  

SuggestedRemedy:  
Please change AssocDevAddress to DeviceAid which is short for Device Assoiciation ID.  Also change the data type from octet to integer.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change AssocDevAddress to DevID.

Note: Change AD-AD to DevID as well in draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  663
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 9
Page:  32
Line:  18
CommentType:  T

Comment:  
The ReasonCode parameter, data type, valid range, and Description are unnecessary given the new name of this primitive.
CommentEnd:  

SuggestedRemedy:  
Please remove the indicated fields from the table.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Table 9 has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  664
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 9
Page:  32
Line:  20
CommentType:  T

Comment:  
The DeviceID parameter name, and description are incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the DeviceID parm name to DeviceAddress.  Also change the Description to: The deviceAddress of the DEV that has been associated.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Table 9 has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  665
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  06
Subclause:  Table 9
Page:  32
Line:  23
CommentType:  T

Comment:  
The AssocDEVAddress parm name, data type, and description are incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the parm name to DeviceAID; the data type to Integer; and the description to: " The association ID of a new device that has become associated with the piconet."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Table 9 has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1392
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table1
Page:  2223
Line:  35
CommentType:  E

Comment:  
Table is missing some lines
CommentEnd:  

SuggestedRemedy:  
Fix the table
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1414
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table13
Page:  35
Line:  5
CommentType:  TR

Comment:  
All the parameters in this table need maximum values in the valid range column so that implementers can choose the proper number of bits to use in their implements.
CommentEnd:  

SuggestedRemedy:  
Add maximum values into the Valid Range column for all fields.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Change valid range to be "1-256" for the six key object lenghts.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1415
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table14
Page:  37
Line:  37
CommentType:  TR

Comment:  
Table 14 needs maximum valuse in the range so that implementers can size their design.
CommentEnd:  

SuggestedRemedy:  
Add maximum values into the range column in Table 14
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Put an upper limit of 256 in the valid range for the three key lengths in Table 14.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1418
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table15
Page:  40
Line:  13
CommentType:  E

Comment:  
Need to define KEK, DEK, DIK, and SEED for us non-cryptographers, besides just the acronyms.
CommentEnd:  

SuggestedRemedy:  
Define KEK, DEK, KIK, and SEED, besides just the acronym.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1417
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table15
Page:  40
Line:  725
CommentType:  TR

Comment:  
Table 15 needs maximum values in the range column
CommentEnd:  

SuggestedRemedy:  
Add max into the Valid Range column
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Put maximum value of 256 in the valid range for the EncryptedKeyObjectLength.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1420
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table16
Page:  42
Line:  32
CommentType:  TR

Comment:  
Need max values column
CommentEnd:  

SuggestedRemedy:  
Need Max Values Column.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change valid range for EncryptedKeyObjectLength to be "1-256".
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1406
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table2
Page:  24
Line:  
CommentType:  TR

Comment:  
If you have peer wakeup, you need to have a peer address
CommentEnd:  

SuggestedRemedy:  
add peer address to the MLME parameters
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  1401
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table2
Page:  24
Line:  23
CommentType:  TR

Comment:  
It is not clear why the PNC needs to know that the device is RPS vs. PM_OFF.
CommentEnd:  

SuggestedRemedy:  
Remove RPS as a state altogether.  Any device can do what is described here ase RPS.  There is no need to differetiate between active and EPS.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete RPS as a separate state, the PNC is informed via the capability field if the DEV is going to use power save methods.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1402
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table2
Page:  24
Line:  28
CommentType:  TR

Comment:  
Why is PowerManagementPriority here and not in the capability field where it belongs.
CommentEnd:  

SuggestedRemedy:  
Remove PowerManagement Priority from the MLME.  Add it to the PIB if it is really needed, or better yet eliminate it.  What is to keep manufactureres from setting this to the  High for all their devices so that they appear to get better battery life than the competitors.  Our hardware team says that slot positions will not save any significant amount of power.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Remove from the MLME. Add to the PIB capability information element. Put in bits 8-9 in Figure 22. Ensure that it can be set from the Dev host. Delete PowerMgmtPriority from Figure 58 page 125 section 7.5.7.3.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1403
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table2
Page:  24
Line:  33
CommentType:  E

Comment:  
I see no mention of ReasonCode in 7.5.7.2
CommentEnd:  

SuggestedRemedy:  
Should Reason Code really be Action Type in Table 67?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1400
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table2
Page:  24
Line:  37
CommentType:  TR

Comment:  
There is no request type for Peer Wakeup, wakeup, DEV to PNC PS Information Command
CommentEnd:  

SuggestedRemedy:  
Add Peer wakeup request type
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Split MLME PowerMgmt command into separate MLMEs for each command. Jay and WMS are providing.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1394
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table2
Page:  24
Line:  5
CommentType:  E

Comment:  
I don't see RequestType in 7.5.7.1.  Is this the same as EPS Action request command entries?
CommentEnd:  

SuggestedRemedy:  
Please Clarify
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1436
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table28
Page:  61
Line:  32
CommentType:  E

Comment:  
Table is missing a vertical line between Valid Range and Description
CommentEnd:  

SuggestedRemedy:  
Add the vertical line
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1437
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table28
Page:  61
Line:  33
CommentType:  E

Comment:  
RemoteDEVAddress does not match the parameters in the MLMEs
CommentEnd:  

SuggestedRemedy:  
remove RemoteDEVAddress and add DestinationevAddress (or replacement) and RequestorDEVAddress (or replacement)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1408
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table31
Page:  26
Line:  21
CommentType:  TR

Comment:  
Where does the DEV get the PNID from to scan for?   Are PNIDs random at startup, or does PNC always use same PNID?   What if different PNC?
CommentEnd:  

SuggestedRemedy:  
Need to address where PNID to scan for comes from.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. DME has option of remembering PNID to allow DEV to join a specific piconet.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1446
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table37
Page:  75
Line:  7
CommentType:  T

Comment:  
What is MACPIBCFPMaxDuration used for
CommentEnd:  

SuggestedRemedy:  
Get rid of MACPIBCFPMaxDuration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1448
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table39
Page:  76
Line:  
CommentType:  E

Comment:  
Why are table 39 and 40 in Clause 6.6?
CommentEnd:  

SuggestedRemedy:  
Move table 39 and 40 to clause 6.5
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1449
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table42
Page:  77
Line:  
CommentType:  TR

Comment:  
PHYPIB_CurrentDataRate shouldn't be a PHY PIB.  It is passed at the PHY SAP on a packet by packet basis.
CommentEnd:  

SuggestedRemedy:  
Remove PHYPIB_CurrentDataRate from the PIB
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1450
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table43
Page:  
Line:  
CommentType:  TR

Comment:  
Curfrent Rx and TX antenna are passed at the PHY SAP and should not be PIB  values becasue they are set on a packet by packet basis.
CommentEnd:  

SuggestedRemedy:  
Remove current Rx and Current Tx antenna from PIB
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1451
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table44
Page:  77
Line:  52
CommentType:  TR

Comment:  
Current Power Level doesn't belong in the PIB.  It is sent with each packet at the PHY SAP
CommentEnd:  

SuggestedRemedy:  
Remove PHYPIB_CurrentPowerLevel from the PIB
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1410
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table5
Page:  27
Line:  33
CommentType:  TR

Comment:  
There is no way to indicate that a frame with the PNID was found, but not a beacon
CommentEnd:  

SuggestedRemedy:  
Add a "PiconetStatus" where 0 indicates no frames were found, 1 indicates frames were found but not the beacon, and 2 indicates the beacon was found.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Type will be integer. Valid range 0-2. 

Note: This will improve ability to detect other piconets and reduce likelyhood of starting another piconet in an occuppied channel.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1412
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table5
Page:  27
Line:  43
CommentType:  TR

Comment:  
No indication of power level if no beacon found.
CommentEnd:  

SuggestedRemedy:  
Provide a signal strength field for avoidance of 802.11 or other users
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.

Add to MLME-SCAN a parameter, Channel Rating, type integer, valid range 0-255, that rates channels, 1 through N from "best" to "worst", 1 is the best channel (i.e. least interference) while N is the worst channel, (i.e. the most interference.)

Add to scan procedure:
"If a DEV is looking to start a new piconet, then it should also look for potential interference in the channels that it scans and rate the channels, from best (lowest interference) to worst (highest interference) and return this information in the MLME-SCAN.confirm command via the ChannelRating.  The DEV should choose to start the piconet in the channel with the least amount of interference in the channel."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1457
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Table55
Page:  84
Line:  
CommentType:  TR

Comment:  
Data Rate and Power Level should not be PIB parameters.  Rename the value.
CommentEnd:  

SuggestedRemedy:  
change data rate and power lavel from being PIB valuse
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  954
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  06
Subclause:  Tables 55 and 56
Page:  84
Line:  
CommentType:  T

Comment:  
Add text to explain why the TX and RX MAC headers are passed in the TX and RX vectors.
CommentEnd:  

SuggestedRemedy:  
Text that can be added to clause 6.9.4  "The MAC headers TxMacHead and RxMacHead are passed in the TX vector and RX vector respectively to facilitate calculation of the HCS as illustrated in Figure 107."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1499
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  
Page:  109
Line:  33
CommentType:  TR

Comment:  
If the device uses EPS power management at any time during a session, this field is set to 2.   Is this bit set anticipating EPS being used, or is it set after EPS is first used?  After an EPS set id joined?
CommentEnd:  

SuggestedRemedy:  
Please clarify.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change "uses" to "intends to use".
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  151
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  1
Page:  93
Line:  12
CommentType:  E

Comment:  
Figure desired to outline the MAC frame format
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1469
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  12
Page:  97
Line:  12
CommentType:  T

Comment:  
Do we really need a 16 bit sequence number?  If we eliinate delayed ACK, we can probably get away with a 4 bit sequence number.
CommentEnd:  

SuggestedRemedy:  
Reduce sequence number to 4 bits if we eliminate delayed ACK.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  152
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  2
Page:  94
Line:  4
CommentType:  E

Comment:  
"Each field is defined in 7.2.1."  - Shouldn't this be 7.2?
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  154
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  2.1.10
Page:  96
Line:  15
CommentType:  T

Comment:  
"repeater service" - why is this service needed?  Wouldn't the devices just talk in a peer to peer mode?  What benefit is there to having a go between (the PNC)?
CommentEnd:  

SuggestedRemedy:  
Need understanding of this feature.  Not explained well.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  491
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  2.1.4
Page:  95
Line:  32
CommentType:  E

Comment:  
use of word can mean different thing to different people
CommentEnd:  

SuggestedRemedy:  
replace "maintain word aligned frames" to "maintain two-octet alignment of the frames"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  492
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  2.1.7
Page:  
Line:  
CommentType:  TR

Comment:  
Retry bit: This bit is unnecessary since the MAC will have to check for seq-number in the rx-frame to detect duplicates anyway.
CommentEnd:  

SuggestedRemedy:  
Remove "retry bit" from frame control field and mark its current position as reserved for future use
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Delete 7.2.1.7 and xrefs to it. Update table 61, 62, and other occurrances in the text. Delete the sentence "The frames received . . . Desitination DEV." on page 121, line 49, section 7.5.4.4.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  495
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  2.3
Page:  
Line:  
CommentType:  TR

Comment:  
Reserve 0xF0 to 0xF9 for future use: We never know what else we'll need special addresses for.
CommentEnd:  

SuggestedRemedy:  
Reserve 0xF0 to 0xF9 for future use
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  496
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  2.3
Page:  97
Line:  8
CommentType:  TR

Comment:  
In clause 8, it is mandated that isoch data shall always be streams. But here it seems to say it is upto DEV.
CommentEnd:  

SuggestedRemedy:  
Remove "or isochronous" in line 8 and add "All isochronous data transfers shall be streams"
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Remove the sentence "The use of . . . Up to the DEV." in 7.2.4, page 97, line 7.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  155
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  2.4
Page:  97
Line:  6
CommentType:  E

Comment:  
This information is already stated on page 96, line 52.  This paragraph is not needed.
CommentEnd:  

SuggestedRemedy:  
Delete the paragraph.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  494
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  2.9.1
Page:  
Line:  
CommentType:  E

Comment:  
add a line describing the situation of SEC bit being set to '0'. otherwise it might be interpreted to be undefinde behavior.
CommentEnd:  

SuggestedRemedy:  
When SEC bit is set 0 the frame body shall not be encrypted.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  156
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  3
Page:  98
Line:  14
CommentType:  E

Comment:  
"... four defined frame types."  - What are they?  Please list them, otherwise the sentence is useless.
CommentEnd:  

SuggestedRemedy:  
State frame types up front.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1709
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  3.1
Page:  
Line:  
CommentType:  E

Comment:  
No frame format for Beacon like that of Fig. 14 & 16
CommentEnd:  

SuggestedRemedy:  
Add general data frame for Beacon
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  157
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  3.1
Page:  98
Line:  29
CommentType:  T

Comment:  
"The information elements in the beacon frame may appear in any order in the beacon ..."  - How do you know what you are looking at if they can appear in any order?
CommentEnd:  

SuggestedRemedy:  
Clarify meaning or method of information determination.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  158
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  3.1
Page:  98
Line:  30
CommentType:  T

Comment:  
"... DEVs may ignore any elements in the beacon that are not listed in Table 60."  - then what are the optional elements that can be ignored.  Please state them explicitly.
CommentEnd:  

SuggestedRemedy:  
Need a clear understanding of what is optional and what is mandatory.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1708
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  3.1,   Table  60
Page:  98
Line:  
CommentType:  E

Comment:  
DEV GTS status (7.4.12) information is not listed in Table 60
CommentEnd:  

SuggestedRemedy:  
Add DEV GTS status as an entry in Table 60
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1721
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  3.1, Table 60
Page:  98
Line:  
CommentType:  TR

Comment:  
PNC should be able to broadcast Application specific information (Table 63, p101) as needed
CommentEnd:  

SuggestedRemedy:  
Add entry for Application specific information in Table 60
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  498
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4
Page:  
Line:  
CommentType:  TR

Comment:  
Is Transmit power change an info-element or command? it is listed in Table-63 on page 101, but described as a command in 7.5.5.1. In addition 8.14.2 references this as a command. the descrription in 7.5.5.1 describes this as an info-element
CommentEnd:  

SuggestedRemedy:  
Chnage the description in 7.5.5.1 from info-element to command
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Also closes 313.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  497
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4
Page:  
Line:  
CommentType:  TR

Comment:  
Is Transmit power change an info-element or command? it is listed in Table-63 on page 101, but described as a command in 7.5.5.1. In addition 8.14.2 references this as a command
CommentEnd:  

SuggestedRemedy:  
Move Transmit power change from Table-63 to Table-65
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Resolves 313 as well.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  502
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.10
Page:  106
Line:  
CommentType:  TR

Comment:  
Given that there can be different guard-band between GTS and between CFP and CAP depending on PHY type and network conditions, it is a good idea to let the PNC account for it when allocating the channel time. To enable that degree of freedom at PNC we need "Slot-duration" in CTA-block in figure-30
CommentEnd:  

SuggestedRemedy:  
Add a two-octet long Slot-duration field in figure-30 (and text in clause 7.4.10) with the resolution of this field being 8-microsec.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. WMS will provide text that implements the slot duration and account for the possibility of fragmenting the beacon or why not to fragment. In accordance with any guard time impact. Due by February 12.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  504
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.10
Page:  107
Line:  
CommentType:  E

Comment:  
Definition of SFNext is better suited to be later in the sub-clause
CommentEnd:  

SuggestedRemedy:  
1. move lines 27:31 on page 107 to be starting right after the current line number 44 on the same page. 2. change "as the SFNext" on line 26, page 107 to "as the SFNext, which is defined later in this clause" 3. reference the place of definition for EPSNext at its first use (at current line #30, page 107) 4. change the second occurrence of "set to 0" on line 34, page 107 to "set to 1" 5. remove line 36 6. Use of "slot location field" in lines 37:43 on page 107, without its definition. Actually its name is different in figure-30.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  503
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.10
Page:  107
Line:  
CommentType:  TR

Comment:  
Key change field in figure-31 is unused
CommentEnd:  

SuggestedRemedy:  
remove "key change" field from figure-31 and mark b2 as reserved.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Change is indicated in 296.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  161
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  4.10
Page:  107
Line:  34
CommentType:  T

Comment:  
"The bit shall be set to 0 if they are in ACTIVE mode and shall be set to 0 if they are in EPS mode."  Which one should be set to 1?
CommentEnd:  

SuggestedRemedy:  
Pick a value of 1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  162
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  4.10
Page:  107
Line:  35
CommentType:  TR

Comment:  
This paragraph is very vague and does not say anything.  Given the TBD, I assume this is a place holder for data to come.
CommentEnd:  

SuggestedRemedy:  
Looks like agreement is needed here to determine the requirement for this place holder.  Finish discussion and complete requirement.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. This sentence has been deleted. See comment 296.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1351
CommenterName:  Seals, Michael
CommenterEmail:  mseals@intersil.com
CommenterPhone:  (321) 724-7172
CommenterFax:  
CommenterCo:  Intersil
Clause:  07
Subclause:  4.10
Page:  107
Line:  35
CommentType:  TR

Comment:  
The meaning of the key change bit is TBD.
CommentEnd:  

SuggestedRemedy:  
Define the meaning or remove the bit.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Bit has been removed.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  163
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  4.10
Page:  107
Line:  38
CommentType:  E

Comment:  
This paragraph is a repeat of one on page 107, line 23.
CommentEnd:  

SuggestedRemedy:  
Consolidate information.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  505
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.10
Page:  107
Line:  46
CommentType:  TR

Comment:  
Use of "guard time" without defining it. Beacon does not contain it.
CommentEnd:  

SuggestedRemedy:  
Remove line-46 and all references to "guard time" in the draft. However state in clause 8.4.3.2, add a paragraph describing the need for guard time and how PNC is expected to take that into account while allocating the channel time.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add slot duration to take care of guard time. Remove guard time at this point. Add section that defines guard time required for receivers to start listening in time to receive. WMS is providing text.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  506
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.11
Page:  108
Line:  
CommentType:  E

Comment:  
Lack of examples to MaxAssignedCTAs and MaxProcessedCTAs make the readers think they are same.
CommentEnd:  

SuggestedRemedy:  
Add examples to clearly state the differences and relation between MaxAssignedCTAs and MaxProcessedCTAs.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  507
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.12
Page:  108
Line:  
CommentType:  TR

Comment:  
line-37 claims that the "element" itself is 256 bit bitmap where as figure-33 has 8-octets (64 bits) of bitmap as a field of the element. If DEV is required to look at CTAs in the worst case what savings is envisioned by this element that reduces the complexity of an implementation. At best this adds complexity to the implementation in checking these bits and then checking the GTS AND it adds to the overhead in the beacon. Beside that, having read EPS several times now, I am not convinced about the justification to add this complex mechanism in to the MAC. Later comments will detail more on this opinion.
CommentEnd:  

SuggestedRemedy:  
Remove DEV GTS status element and all references to it from the draft.
RemedyEnd:  

Response:  
PROPOSED REJECT. The committee feels that there is potentially an advantage to preserving the DEV GTS functionality.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  508
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.13
Page:  109
Line:  
CommentType:  TR

Comment:  
1. Figure-34 is inconsistent in "length" field and the contents of the element 2. Nowhere in the draft I see the text describing how this is set at PNC and how it is used at DEVs. 3. on lines 35:36: If EPS device is asleep how does it make use of this info? if this is for other DEVs, how is it useful. 4. What is the guarantee that DEVs always get EPS status of another DEV through beacon? Why not use a simple mechanism wherein a DEV can tell the PNC that it is going to be asleep and hence not allocate GTS with the current DEV in question as the recipient? What is the justification for the complexity of this mechansism that is being thrusted upon implementors?
CommentEnd:  

SuggestedRemedy:  
Simplify "power management parameters" to have just the list of Device addresses of those DEVs that are currently asleep. no other field is needed as the receiving DEVs know that if an address is present in this list, that device is asleep.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The power management section is going to be rewritten based on proposals 01/384r2, 02/067r1 and the minutes.  We are going to implement some version of the TIM element.  There will be additional elements to allow for EPS mode.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  165
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  4.13
Page:  109
Line:  18
CommentType:  T

Comment:  
What is a "EPS set"?  Where is it defined?  For that matter, where is RPS defined?  Is it a parameter set by the design and communicated through the PIB?
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  509
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.14
Page:  109
Line:  
CommentType:  E

Comment:  
Figure 36: spec on length missing
CommentEnd:  

SuggestedRemedy:  
Figure 36: mark the length of variable field (app-specific data) as 'n' and note in the Length field that the length is equal to 'n+1'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  510
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.15
Page:  110
Line:  
CommentType:  TR

Comment:  
For ease of understanding and implementation (use of clean ifs and elses), there is a need to reorder the command-type value to a given command.
CommentEnd:  

SuggestedRemedy:  
Move the association related commands to the top to start from value 0x0000, followed by authentication commands.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  511
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.15
Page:  110
Line:  
CommentType:  E

Comment:  
Ordering the subclauses for commands to be in the same order as the order of commands in Table-65 is very helpful
CommentEnd:  

SuggestedRemedy:  
Reorder the subclauses describing the individual commands to be in the same order as their appearence in Table-65
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  512
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.15
Page:  110
Line:  
CommentType:  TR

Comment:  
Just the number of commands, fields/subfields in information elements makes one wonder why power management has to be this complex. Why not simple commands like (a) sleep-time-request from DEV to PNC (b) sleep-time-grant/reject from PNC to DEV? What is not being acheived in those simple commands that is being achieved by this complex mechanism? What is the justification to add this complex mechanism to a draft that is supposed to spec a low-cost, low-power PAN implementation?
CommentEnd:  

SuggestedRemedy:  
Remove all the power management commands and all the references to them from the draft. Simplify power management to the following - Request for sleep time by DEV - Accept/Reject by PNC - Broadcast the addresses of sleeping DEV in Beacon - Allocation/modification of GTS by PNC depending on who is awake
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The power management section is going to be rewritten based on proposals 01/384r2, 02/067r1 and the minutes.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  499
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.2
Page:  103
Line:  13
CommentType:  TR

Comment:  
Why should PNC increment and publish DEK? if the key is changed the key-distribution scheme should make sure all the relavant DEVs in the pcionet are informed before the change. Moreover, keys must be per-link and not global per piconet.
CommentEnd:  

SuggestedRemedy:  
Remove Key number from Figure-19 and all references to it from the draft
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1722
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  4.3, Fig.22
Page:  103
Line:  
CommentType:  TR

Comment:  
No information regarding possible applications/services will provided by a devices (host) is included in capability field. Products should be classified based on application (PDA, Digital camera, camcorder, etc) and mapped to one field of capability. Therefore, a DEV can pre-filter device information sent by PNC(device information response command) for further actions.  Currently no information is provided to DME for a device to select peer devices in the piconet for communication after association.
CommentEnd:  

SuggestedRemedy:  
Add 'product category' field to capability information
RemedyEnd:  

Response:  
PROPOSED REJECT. The Application Specific Information Element can be used for this purpose.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  U
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  160
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  4.5
Page:  104
Line:  54
CommentType:  T

Comment:  
"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?
CommentEnd:  

SuggestedRemedy:  
Unclear about actual meaning.  State clearly.
RemedyEnd:  

Response:  
Changing all Kus to ms in document.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  500
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.6
Page:  105
Line:  
CommentType:  TR

Comment:  
Supported rates in 11.7 presents less than one octet encoding to indicate the support for multiple rates.
CommentEnd:  

SuggestedRemedy:  
Change "supported rates" field in figure-25 from (1-8) octet(s) to 1-octet.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  501
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  4.7
Page:  105
Line:  
CommentType:  E

Comment:  
Use of OID is confusing as the same term is used for the first 3-octets of IEEE MAC addresses.
CommentEnd:  

SuggestedRemedy:  
Pick a new name for OID in this subclause and at all places referencing to it in the draft
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  513
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.1
Page:  
Line:  
CommentType:  E

Comment:  
some inconsistencies
CommentEnd:  

SuggestedRemedy:  
1. 7.5.1.1, 7.5.1.2 and 7.5.1.3 describe them as "action types". change the description to "commands" 2. these subclause must refer to figure-37 for command structure 3. Change the caption of figure-37 to "PNC selection commands format"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  166
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  5.1
Page:  112
Line:  33
CommentType:  E

Comment:  
"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?
CommentEnd:  

SuggestedRemedy:  
State meaning clearly
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  523
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.10
Page:  
Line:  
CommentType:  E

Comment:  
length nconsistency
CommentEnd:  

SuggestedRemedy:  
Inconsistency in the content of length field "n*10". change it is "n*12"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1716
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  5.10
Page:  130
Line:  25
CommentType:  TR

Comment:  
It is confusing that this command seems suggesting a DEV seeking to communicate with target DEV needs to use this command,even if after a stream connection has been established. While CTA for one stream is assigned at the end of stream conection (Fig.3).
CommentEnd:  

SuggestedRemedy:  
Clarify if this command is used in conjunction with streme management command for establishment of communication and required for allocating time slots for the stream
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  stream
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  524
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.10.1
Page:  
Line:  
CommentType:  TR

Comment:  
Again, the complexity of power management has crept into frame formats of CTRB also. And the PNC must strive to rx and set these values appropriately for all different combinations, while the DEVs strive to produce/consume those bits and act appropriately. Why? Why not a simple mechanism of one command exchange between DEV and PNC to tell whether a DEV is planning to go to sleep? I don;t see any justification for this complexity all around the spec for power management.
CommentEnd:  

SuggestedRemedy:  
Remove CTRB type, EPS set and allocation period from figure-72 and all references to those fields from the draft.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The power management section is going to be rewritten based on proposals 01/384r2, 02/067r1 and the minutes.  We are going to change the EPS CTA elements to be a separate, smaller element that is less confusing and therefore evil.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  525
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.10.1
Page:  
Line:  
CommentType:  TR

Comment:  
Minimum GTS time can be reduce to one octet. If the other octet has to be left reserved, so be it since that creates room for future expansion.
CommentEnd:  

SuggestedRemedy:  
1. Reduce Minimum GTS time to one octet in figure-72 2.  Make the name of the field and the description uniform with that in figure-66. Better yet, describe at one place and reference it at another to avoid duplication
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Minimum GTS Slot time is a value requiring more than 8-bits. The other occurrence in Figure 66 will be removed. All occurrances of Minimum GTS Slot time will be the same size.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  526
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.10.1
Page:  
Line:  
CommentType:  TR

Comment:  
The complexity of power management has crept into frame formats of channel time grant and stream management also. The PNC must strive to rx and set these values appropriately for all different combinations, while the DEVs strive to produce/consume those bits and act appropriately. Why? Why not a simple mechanism of one command exchange between DEV and PNC to tell whether a DEV is planning to go to sleep? I don't see any justification for this complexity all around the spec for power management.
CommentEnd:  

SuggestedRemedy:  
Remove Grant-status(s) from figure-73, remove figure 74 and all references to those fields from the draft. Remove GTS type from figure-76 and all references to that field from the draft.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  CTR
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  527
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.10.1
Page:  
Line:  
CommentType:  TR

Comment:  
Action type is incomplete
CommentEnd:  

SuggestedRemedy:  
specify a value of '3' to be applicable for "Dest-DEV to PNC" case also.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add sentence in section 7.5.10.3, page 133, line 29 following "In the response." add "This indicates that the target accepts the stream connection with the parameters indicated."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1706
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  5.10.1
Page:  130
Line:  23
CommentType:  E

Comment:  
Each CTRB in Fig. 72 is 12 octets Also Length field in Fig.71 shows n*10
CommentEnd:  

SuggestedRemedy:  
Modify the text & Fig. 71 & 72 to be consistent
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1707
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  5.10.2, Fig. 73, 74
Page:  132
Line:  
CommentType:  E

Comment:  
Grant status field (Fig. 73) in Fig. 74 is 3 octets Reason code of Fig. 74 should be b16-b19
CommentEnd:  

SuggestedRemedy:  
Modify Length field (=n*9) and Grant status field (3 octets) to be consistent Modify Reason code (b16-b19) in Fig. 74
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  528
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.10.3
Page:  
Line:  
CommentType:  TR

Comment:  
Minimum requested channel time can be reduce to one octet. If the other octet has to be left reserved, so be it since that creates room for future expansion.
CommentEnd:  

SuggestedRemedy:  
1. Reduce Minimum requested channel time to one octet in figure-77 and remove the reserved field since the two-octet alignement is acheived by the reduction of size for Minimum requested channel time 2. Make the name of the field and the description uniform with that in figure-66. Better yet, describe at one place and reference it at another to avoid duplication
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Minimum Requested Channel time (Minimum GTS Slot) time is a value requiring more than 8-bits. The other occurrence in Figure 66 will be removed. All occurrances of Minimum GTS Slot time will be the same size.

Note that Minimum Requested Channel time changed to Minimum GTS Slot time per comment 529.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  529
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.10.3
Page:  
Line:  
CommentType:  TR

Comment:  
MAx TX delay variation in figure-77 and MAximum allocation delay in figure-72 are same but have different name and description
CommentEnd:  

SuggestedRemedy:  
Make the name of the field and the description uniform between figure-77 and figure-72. Better yet, describe at one place and reference it at another to avoid duplication
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Use the naming and text in Figure 72 and xref Figure 77 to Figure 72. In Figure 77 change:

Inter-time slot duration becomes Allocation period
Minimum … slot becomes Minimum GTS time
Requested … slot becomes Desired GTS time
Max TX delay variation becomes Maximum allocation delay

Text on page 134 and 135 use xref (defined 7.5.10.1) instead of redefining.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1352
CommenterName:  Seals, Michael
CommenterEmail:  mseals@intersil.com
CommenterPhone:  (321) 724-7172
CommenterFax:  
CommenterCo:  Intersil
Clause:  07
Subclause:  5.10.3
Page:  133
Line:  39
CommentType:  TR

Comment:  
The security field is TBD.
CommentEnd:  

SuggestedRemedy:  
Define the field or remove it.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  171
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  5.10.3
Page:  135
Line:  618
CommentType:  E

Comment:  
"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?
CommentEnd:  

SuggestedRemedy:  
Clarify meaning.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  172
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  5.10.3
Page:  135
Line:  8
CommentType:  E

Comment:  
"in Koctets/s" (with u meaning micro here) - is this to mean that units are 1024 octets/sec increments?
CommentEnd:  

SuggestedRemedy:  
Clarify meaning
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  514
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.2
Page:  
Line:  
CommentType:  E

Comment:  
Use of "commands frame body chall be formatted ..."  is wrong. Command is not a frame by itself, but some command frames may have only one command in them (along with MAC header, FCS etc.)
CommentEnd:  

SuggestedRemedy:  
Change all occurrences of "command frame body shall be formatted .." to means the following 1. Command structure is shown in figure-xx (no change in reference) 2. A frame containing certain commands like association, disassocition, authenticatio, deauthentication shall not contain any other commands. It shall be the sole command present in a command frame.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  515
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.3
Page:  
Line:  
CommentType:  TR

Comment:  
Use of redundant fields that increase the overhead and lead to inconsistencies in the implementation
CommentEnd:  

SuggestedRemedy:  
1. remove PublicKeyObjectLength in figure-42 2. remove AuthenticationInfoLength in figure-43 3. remove PublicKeyChallengeLength in figure-44 4. Remove PublicKeyProofLength in figure-45 5. remove EncryptedKeyObjectLength in figure-47 6. remove EncryptedKeyObjectLength in figure-48  7. for all the above add one line each as to the formula to derive those  fields at rx (or use those at tx) from the "Length" field present in the info-element structure.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. As long as we do not change to all information elements in commands.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  516
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.4
Page:  
Line:  
CommentType:  TR

Comment:  
Probe request and response command types are redundant since their format is exactly same. Define one command with that format "Probe Information" and use it both as request and response
CommentEnd:  

SuggestedRemedy:  
Define one command with that format "Probe Information" with the format as in figure-50 and use it both as probe-request and probe-response in the behavior description
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Define one command with that format "Probe Information" with the format as in figure-50 and use it both as probe-request and probe-response in the behavior description. Clean up the description of MSB-set for binary coded information identifiers. Ensure that all zero Information Request is only valid for no information being requested. Clean up clause 8.9 that reference probe-request and probe-response.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  167
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  5.4.4
Page:  121
Line:  29
CommentType:  E

Comment:  
"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?
CommentEnd:  

SuggestedRemedy:  
State meaning clearly
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  517
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.6
Page:  
Line:  
CommentType:  E

Comment:  
Use of "CTRB"  without definition
CommentEnd:  

SuggestedRemedy:  
1. expand CTRB 2. replace "channel time" in lines 42 and 43 with CTRB
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  518
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.7
Page:  
Line:  
CommentType:  TR

Comment:  
There are 6 different commands for power management and two of them with a different set of multiple action types, totalling 13 different actions. In addition there are different states within EPS such as momentary EPS. Just the listings in Table-66 and Table-67 outpour the complexity involved in the specified power management mechanism. Why not simple commands like (a) sleep-time-request from DEV to PNC (b) sleep-time-grant/reject from PNC to DEV? What is not being acheived in those simple commands that is being achieved by this complex mechanism? What is the justification to add this complex mechanism to a draft that is supposed to spec a low-cost, low-power PAN implementation?
CommentEnd:  

SuggestedRemedy:  
Remove all the power management commands and all the references to them from the draft. Simplify power management to the following - Request for sleep time by DEV - Accept/Reject by PNC - Broadcast the addresses of sleeping DEV in Beacon - Allocation/modification of GTS by PNC depending on who is awake
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The power management section is going to be rewritten based on proposals 01/384r2, 02/067r1 and the minutes.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  519
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.7
Page:  
Line:  
CommentType:  E

Comment:  
This entire section is full of inconsistencies, use of terms never used anywhere in the draft, grammatical mistakes and language not suitable for an 802 standard. Some of them are: 1. what is "self sleep" as used in line 19 page 126 2. why is the sentence in line-19 needed? what is it conveying? 3. Language: one example is lines 16-20 on page-126.
CommentEnd:  

SuggestedRemedy:  
I request the editor to read this clause and correct them. I am givingup on listing them as there are just too many to list.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  521
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.8.2
Page:  
Line:  
CommentType:  E

Comment:  
use of "TX slots"
CommentEnd:  

SuggestedRemedy:  
Change "Number of TX slots" in the text of 7.5.8.2 and figure-64 to "number of GTS"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  522
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  07
Subclause:  5.8.3
Page:  
Line:  
CommentType:  E

Comment:  
Stream index is listed in figure-66 but there is no description of what it is?
CommentEnd:  

SuggestedRemedy:  
Relate the "Stream index" in figure-66 to the description in lines 36:37 on page 128
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1718
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  5.8.3
Page:  128
Line:  
CommentType:  T

Comment:  
What is the streme index of child/neighbor piconet? Are these fields(Duration between time slots, Min. requested channel time, Requested channel time per time slot) appled to the private GTS for child piconet?
CommentEnd:  

SuggestedRemedy:  
Please clarify
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. That command has been deleted because the capabilities are handled by the device information response command (will be changed to PNC information response command). Text has been added in clause 8 to clarify use of these parameters.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  169
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  5.8.3
Page:  128
Line:  31
CommentType:  E

Comment:  
"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?
CommentEnd:  

SuggestedRemedy:  
Clarify meaning
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  168
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  5.8.3
Page:  128
Line:  6
CommentType:  E

Comment:  
"... same response rules a the device ..."  - should be "as".
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1460
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7
Page:  93
Line:  3
CommentType:  E

Comment:  
This clause does more than just specify the frame formats.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence after the first:  An overview of the MAC frame is followed by a description of the general frame format, a description of the individual frame types, complete documentation of the information elements and then the command frames.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1461
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7
Page:  93
Line:  4
CommentType:  E

Comment:  
FCS and HCS are checked to validate the received frames.
CommentEnd:  

SuggestedRemedy:  
modify the sentence as follows:  either error free or in error, using the header check sequesnce (HCS) and frame check sequesnce (FCS).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  958
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.1
Page:  93
Line:  14
CommentType:  E

Comment:  
poor sentence structure ... suggest rewrite as shown in sentence fragment below
CommentEnd:  

SuggestedRemedy:  
... sequence number information, and optional traffic category ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  299
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.1
Page:  93
Line:  14
CommentType:  T

Comment:  
Enumeration items are inclomplete in their description.
CommentEnd:  

SuggestedRemedy:  
In a) change "frame control, address " to "frame control, network identification, source address, destination adress "  In d) change "(FCS) which" to "(FCS), if the frame body is non-zero length, which"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1112
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.1
Page:  93
Line:  15
CommentType:  T

Comment:  
The frame header structure is not described clearly, the CRC type of HCS should be specified, and a correction made to the specification of the FCS CRC designation.
CommentEnd:  

SuggestedRemedy:  
Rewrite as follows:  a) A frame header that includes the PHY header and the MAC header. The MAC header comprises frame control, ...,traffic category informantion. b) A fixed length header check sequence (HCS), which contains an IEEE 16-bit cyclic redundncy code CRC-16) for the frame header. c) ...  d) ... code(CRC-32).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  957
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.1
Page:  93
Line:  16
CommentType:  TR

Comment:  
reference is made to a "traffic category".  This term is used just once in the whole docuement (i.e. used only in this sentence).
CommentEnd:  

SuggestedRemedy:  
Question for MAC subcommittee ... resolve if this is the correct name.  Is there another more common name used in the document?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  300
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.1.1
Page:  93
Line:  26
CommentType:  T

Comment:  
Requirements are not strong enough for bit ordering.
CommentEnd:  

SuggestedRemedy:  
Change "left-most bit is transmitted" to "left-most bit shall be transmitted" in line 26, change "a single octet are sent to" to be "longer than a single octet shall be sent to" in line 31, change "convention and is transmitted" to "convention and shall be transmitted" in line 34 and change "in decimal are coded" to be "in decimal shall be coded" in lin 37.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1462
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.1.1
Page:  93
Line:  26
CommentType:  T

Comment:  
"order in which they are passed to the PHY,"  is not technically correct, since the interface between the MAC and the PHY is likely not serial.
CommentEnd:  

SuggestedRemedy:  
replace with "order in which they are transmitted on the air,"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  301
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.1.1
Page:  93
Line:  27
CommentType:  T

Comment:  
Need a figure to show how the bit ordering is used in the figures that follow.
CommentEnd:  

SuggestedRemedy:  
Add the figure once it has been generated and reviewed.  Figure should have multiple fields with LSb and MSb indicated for each of the fields, an indication of the order in which they are sent over the air and an example of a simple command or information element with specific values.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  959
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.1.1
Page:  93
Line:  28
CommentType:  E

Comment:  
remove the comma as shown below
CommentEnd:  

SuggestedRemedy:  
... fields are numbered from 0 to k, ....
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  960
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.1.1
Page:  93
Line:  36
CommentType:  TR

Comment:  
Item to add to clause 3
CommentEnd:  

SuggestedRemedy:  
Please add the definition of a "natural number" to clause 3
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1360
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  07
Subclause:  7.2
Page:  9596
Line:  
CommentType:  T

Comment:  
The MAC Frame includes a retry bit and a sequence number field.  It seems that the sequence number makes the retry bit unnecessary.
CommentEnd:  

SuggestedRemedy:  
Eliminate the retry bit if it is in fact redundant
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  302
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.1
Page:  94
Line:  25
CommentType:  T

Comment:  
The description of the frame control field repeats what is in the figure and therefore is redundant and evil.
CommentEnd:  

SuggestedRemedy:  
Change "consists of the ... and repeater" with "is used to identify the type of frame and how it is to be handled."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  805
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.2.1
Page:  94
Line:  30
CommentType:  TR

Comment:  
in Figure 12 bit 10 is missing
CommentEnd:  

SuggestedRemedy:  
Add bit 10 in figure 12 and indicate 'reserved', possibly reorder the bits.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Move 11-12 to 10-11 and move bit 14 to bit 12 and make 13-15 reserved.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  303
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.1
Page:  94
Line:  44
CommentType:  T

Comment:  
"will" is not formal language.
CommentEnd:  

SuggestedRemedy:  
Change "supports will discard" to "supports may discard"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1464
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.1.2
Page:  95
Line:  4
CommentType:  T

Comment:  
Get rid of Delayed ACK.  This will unnecessarily complicate the MAC to implement.  We should keep a WPAN as simple as possible.
CommentEnd:  

SuggestedRemedy:  
Eliminate Delayed ACK.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  852
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.2.1.3
Page:  95
Line:  21
CommentType:  T

Comment:  
Immediate acknowledgement can be indicated in the ACK-policy field. Therefore the frame type 'Immediate acknowledgement' is redundant.
CommentEnd:  

SuggestedRemedy:  
If ACK-policy field is used to indicate 'immediate acknowledgement' than the frame type 'Immediate acknowledgement' may be removed.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1465
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.1.5
Page:  95
Line:  37
CommentType:  E

Comment:  
"... command frames that is the start of the current..."  is incorrect grammar - frames is.
CommentEnd:  

SuggestedRemedy:  
Replace with "... command frames that are the first frame in the current..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  304
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.1.5
Page:  95
Line:  37
CommentType:  T

Comment:  
Informal language used, change to shall
CommentEnd:  

SuggestedRemedy:  
Change "is set to" to be "shall be set to" in 2 places in each 7.2.1.5, 7.2.1.6, 7.2.1.7, 7.2.1.10 and one place in 7.2.1.9
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  806
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.2.1.5
Page:  95
Line:  38
CommentType:  T

Comment:  
clarify value of frag-start field for frames, which are not fragmented
CommentEnd:  

SuggestedRemedy:  
add additional text at the end of the first sentence e.g.: ...start of the current MSDU/MCDU, which consists of multiple fregments.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  961
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.1.5 & 7.2.1.6
Page:  95
Line:  36
CommentType:  T

Comment:  
Why two Frag fields ... start and end?
CommentEnd:  

SuggestedRemedy:  
Couldn't the fragmentation process be signified by setting a single bit?  0=not fragmentating and 1=fragmentating
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1466
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.1.6
Page:  95
Line:  42
CommentType:  E

Comment:  
"... command frames that is the start of the current..."  is incorrect grammar - frames is.
CommentEnd:  

SuggestedRemedy:  
Replace with "... command frames that are the first frame in the current..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  807
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.2.1.6
Page:  95
Line:  43
CommentType:  T

Comment:  
clarify value of frag-end field for frames, which are not fragmented
CommentEnd:  

SuggestedRemedy:  
add additional text at the end of the first sentence e.g.: ...end of the current MSDU/MCDU, which consists of multiple fregments.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  962
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.1.9
Page:  96
Line:  9
CommentType:  TR

Comment:  
Lack reference to information on encryption key
CommentEnd:  

SuggestedRemedy:  
Please provide reference for the following sentence fragment  "currently assigned data encryption key"  where in clause 10 is this data contained?  If not present it needs to be added.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1672
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.1.9
Page:  96
Line:  910
CommentType:  E

Comment:  
Should change the sentence to "When the SEC bit is set to 1, the frame body is protected by payload protection using the currently assigned payload protection key(s) for the piconet."
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1467
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.2
Page:  96
Line:  20
CommentType:  TR

Comment:  
"The PNID remains constant during the current instantiation of the piconet and may be persistent for multiple sequential instantiations of the piconet by the same PNC."  "May be persistent"?  Hos is it determined if it is persistent?  Up to the implenter?  Do PNCs always use the same PNID?
CommentEnd:  

SuggestedRemedy:  
Need to describe the details of persistence of the PNID.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  239
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.2.3
Page:  96
Line:  3035
CommentType:  E

Comment:  
The following sentences do not end in a period: — The address value 0 is reserved for the PNC, for coordinator related transmissions and receptions — The address value of all-ones (0xFF) is reserved for broadcast frames ... — The address value of 0xFD is reserved for multicast frames — The address values of 0xFA, 0xFB or 0xFC are reserved for neighbor piconets
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  305
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.3
Page:  96
Line:  34
CommentType:  T

Comment:  
No multicast capabilities have been defined for this standard.  There is no way to create or join multicast groups.  Delete all references to multicast addresses (this is one of the first).
CommentEnd:  

SuggestedRemedy:  
Delete the itemization point "- the address value of 0xFD is reserved for multicast frames." and change the neighbor PNC addresses to be one more (i.e. 0xFB, 0xFC and 0xFD).
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  963
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.3
Page:  96
Line:  35
CommentType:  TR

Comment:  
There are only 3 addresses available for neighor piconets.
CommentEnd:  

SuggestedRemedy:  
Please increase the addresses available from 3 to 6 ... 4 on each side, 1 above and 1 below.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1468
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.3
Page:  96
Line:  35
CommentType:  T

Comment:  
Not sure why 3 addresses are reserved for neighbor piconets.  Why 3?  Is that enough?
CommentEnd:  

SuggestedRemedy:  
Describe the benefit of using a reserved address, or else just use the capability field for a DEV to indicate a neighbor piconet?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  808
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.2.3
Page:  96
Line:  35
CommentType:  T

Comment:  
There are address values for neighbor piconets, but not for child piconets.
CommentEnd:  

SuggestedRemedy:  
Add address values for child piconets, if required.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  306
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.4
Page:  96
Line:  40
CommentType:  T

Comment:  
Informal language
CommentEnd:  

SuggestedRemedy:  
Change "is set to zero, and ignored upon reception," to be "shall be set to zero on transmission and shall be ignored upon reception "
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  307
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.4
Page:  96
Line:  50
CommentType:  T

Comment:  
Add requirement for formatting.
CommentEnd:  

SuggestedRemedy:  
Change "... and priority." to be "... and priority and shall be formatted as illustrated in Fig. 13."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1470
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.5
Page:  97
Line:  14
CommentType:  T

Comment:  
Is the same sequence number counter used for asynchronlous datea to all destinations?  If so, this will mess up the Rx frame loss counter in channel status response.  If a separate counter is needed it will complicate implementations.
CommentEnd:  

SuggestedRemedy:  
Specify that a single counter is used for all frames and that the Rx frame loss counter may not be accurate for asynchronous frames.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1361
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  07
Subclause:  7.2.6
Page:  97
Line:  
CommentType:  T

Comment:  
The MAC header check sequence (HCS) should be calculated and implemented by the MAC and not the PHY.  The layers should not be mixed.
CommentEnd:  

SuggestedRemedy:  
Have the MAC, not the PHY, calculate and implement the MCS.
RemedyEnd:  

Response:  
PROPOSED REJECT. Because the PHY header is short and because of the desire to reduce overhead, we decided very early on to use only one CRC to protect both headers.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1471
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.6
Page:  97
Line:  28
CommentType:  T

Comment:  
Need to clarify that the MAC ignores the HCS.
CommentEnd:  

SuggestedRemedy:  
add the following sentence "The MAC always ignores the CS field upon reception."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  308
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.7
Page:  97
Line:  33
CommentType:  T

Comment:  
Security information is no longer included as separate data, delete this reference.
CommentEnd:  

SuggestedRemedy:  
Delete ", including the security information if any"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  964
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.2.7
Page:  97
Line:  34
CommentType:  TR

Comment:  
This clause states there is security information in the frame body.
CommentEnd:  

SuggestedRemedy:  
Provide reference to the specific clause 10 subclause that describes this security information.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  309
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.8
Page:  97
Line:  43
CommentType:  T

Comment:  
Informal language
CommentEnd:  

SuggestedRemedy:  
Change "The FCS is calculated" to be "The FCS shall be calculated" on line 43 and "The FCS field is transmitted" to be "The FCS field shall be transmitted"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  809
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.2.8
Page:  97
Line:  49
CommentType:  E

Comment:  
unclear formula
CommentEnd:  

SuggestedRemedy:  
replace 'xkx(x31+' by 'xk*(x31+'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  310
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.2.8
Page:  98
Line:  1
CommentType:  T

Comment:  
Informal language.  Also, shouldn't all implementations initiallize the the HCS remainder to the same number?
CommentEnd:  

SuggestedRemedy:  
Delete "As a typical implementation, " and change "division is preset" to be "division shall be preset" in line 1 and change "remainder is preset" to be "remainder shall be preset" in line 5
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  810
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.3
Page:  98
Line:  14
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'within command frame' by 'within a command frame'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  811
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.3
Page:  98
Line:  19
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'shall the number' by 'shall indicate the number'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  965
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.3
Page:  98
Line:  19
CommentType:  E

Comment:  
rewrite sentence as shown below.
CommentEnd:  

SuggestedRemedy:  
The length field of the frame shall count the number of octets, including the stuffed octet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1472
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.3
Page:  98
Line:  20
CommentType:  E

Comment:  
clarify that the pad octet field is in the header
CommentEnd:  

SuggestedRemedy:  
Modify the sentence as follows:  "...the pad octet field in the header..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1473
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.3.1
Page:  98
Line:  29
CommentType:  TR

Comment:  
Allowing inforamtion elements in any order in the beacon will complicate the design.  CTAs should be the last IEs in the beacon.
CommentEnd:  

SuggestedRemedy:  
Change the sentence as follows:  "The information elements in the beacon frame may appear in any order in the beacon, excetpt that chanel time alocations (CTAs) appear last.   DEVs may ignore any elements in the beacon which are not listed in Table 60."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  311
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.3.1
Page:  98
Line:  44
CommentType:  T

Comment:  
The channel time allocations are required in every beacon.  Also, the DEV GTS status is not indicated as an allowed element in the beacon.
CommentEnd:  

SuggestedRemedy:  
Change "As needed" to "In every beacon" for channel time allocation in table 60.  Also, add a row at the bottom of Table 60 that is "DEV GTS Status" "7.4.12" "Indicates if a DEV's GTSs have changed" "As needed"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1478
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.3.3
Page:  
Line:  
CommentType:  TR

Comment:  
"A command data unit (MCDU) may also be transmitted in fragments, as described in 8.7."  This is inconstent with the fact that the sequence numbers from all command frames use a single counter.  Since all command frames do not go to the same destination, fragementation does not work.
CommentEnd:  

SuggestedRemedy:  
Change to : "Command data units (MCDUs) cannot be fragmented."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  812
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.3.3
Page:  100
Line:  3
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'sent in either in' by 'sent either in'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  240
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.3.3
Page:  100
Line:  4
CommentType:  E

Comment:  
The following sentence has an error in punctuation: PNC and the DEV or during the CAP,.
CommentEnd:  

SuggestedRemedy:  
Delete the comma.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  966
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.3.3
Page:  100
Line:  4
CommentType:  E

Comment:  
add words as shown below ...
CommentEnd:  

SuggestedRemedy:  
PNC and the DEV (during a MTS) or during ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  312
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.3.3
Page:  100
Line:  6
CommentType:  T

Comment:  
Not all commands are allowed to be chained together.  Some shall be sent individually
CommentEnd:  

SuggestedRemedy:  
Insert the following sentence after "... as shown in Figure 15."  The following commands shall be sent in a command frame that contains only the command: alternate PNC announcement, new PNC announcement, association request, disassociation request.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  967
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.3.4
Page:  100
Line:  42
CommentType:  E

Comment:  
missing definitive article, add as shown below
CommentEnd:  

SuggestedRemedy:  
The frame format of the data frame ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  313
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4
Page:  101
Line:  26
CommentType:  T

Comment:  
The transmit power change is a command, not an information element and has already been moved to the appropriate location in the draft.
CommentEnd:  

SuggestedRemedy:  
Update tables 63 and 65 by moving the transmit power change command from 63 to 65.  Renumber the information element ID's and command ID's as necessary.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  968
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4
Page:  101
Line:  43
CommentType:  E

Comment:  
modify sentence as shown below
CommentEnd:  

SuggestedRemedy:  
frames that are allowed to include ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  969
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4
Page:  101
Line:  45
CommentType:  E

Comment:  
Modify sentence as shown below
CommentEnd:  

SuggestedRemedy:  
... 2-octet boundary within the frame body.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  736
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.4 Table 63
Page:  101
Line:  3637
CommentType:  TR

Comment:  
Element ID should be provided for the IEEE ID of a parent PNC. This will appear (as correctly shown) in Table 60 (refer page 98).  Note: originally, the parent IEEE ID was to be identified by its position as last in the beacon.  However, the ASIE also requests the last position. Therefore, we should declare an element ID for the parent IEEE ID and allow the parent ID to take any position in the beacon.
CommentEnd:  

SuggestedRemedy:  
Add element ID 0x0F for Parent PNC IEEE ID and decrement to reserved element IDs by one.  Use the format in Figure 18 (page 102).
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Name it Neighbor PNC DEV Address. Verify that this is the same as adopted for the MLME.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1480
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.1
Page:  102
Line:  
CommentType:  T

Comment:  
What is the purpose of max burst duration?  Is this for a single frame, or for multiple frames?
CommentEnd:  

SuggestedRemedy:  
Clarify the use of max burst duration or eliminate it.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  320
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.10
Page:  106
Line:  46
CommentType:  T

Comment:  
Change the label "Slot Start time or SFNext" to be "slot location" since that is how it is referenced in the definitions.
CommentEnd:  

SuggestedRemedy:  
Change as indicated.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  817
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4.10
Page:  106
Line:  47
CommentType:  E

Comment:  
Align text in Figure 30 with text on next page.
CommentEnd:  

SuggestedRemedy:  
Last field should be called 'slot location field'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1489
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  1
CommentType:  TR

Comment:  
I disagree that directed frames should not be allowed in a broadcast GTS.  Allowing directed frames in a broadcast GTS should would help the efficiency of transmitting asychronous traffic.
CommentEnd:  

SuggestedRemedy:  
Change this to say that directed frames are allowed in a broadcast GTS.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Delete the sentence "If this is a … time slot."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  989
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  28
CommentType:  T

Comment:  
This paragraph references a field that contains "the least significant two octets of a beacon number".
CommentEnd:  

SuggestedRemedy:  
This paragraph is confusing.  Power management subcomittee needs to clarify and provide addditional references to other clauses.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  990
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  33
CommentType:  TR

Comment:  
appears there is a typo as shown below
CommentEnd:  

SuggestedRemedy:  
... and shall be set to 1 if they are in EPS mode.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1113
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  33
CommentType:  T

Comment:  
CTA type specified the same for ACTIVE and EPS modes
CommentEnd:  

SuggestedRemedy:  
Change to:  ... and shall be set to 1 if they are in EPS mode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  818
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  34
CommentType:  TR

Comment:  
incorrect setting of CTA-type-bit
CommentEnd:  

SuggestedRemedy:  
correct text to: ... shall be set to 1 if they are in EPS mode.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1757
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  34
CommentType:  E

Comment:  
set to 0 if they are in EPS ... (typo)
CommentEnd:  

SuggestedRemedy:  
set to 1 if they are in EPS ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  991
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  35
CommentType:  TR

Comment:  
Need to resolve TDB
CommentEnd:  

SuggestedRemedy:  
Security subcommittee needs to resolve this TBD in this line.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1674
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  35
CommentType:  T

Comment:  
The key change bit is defined as TBD.  I actually don't see any reason for it at this point, but we can leave it in if we really want to.
CommentEnd:  

SuggestedRemedy:  
Change the line to "The key change bit is reserved for possible security implementations.  In the current version of the standard, this bit shall be set to 0."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  296
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  36
CommentType:  T

Comment:  
TBD in "The key change bit is reserved for possible security implementation with TBD meaning"
CommentEnd:  

SuggestedRemedy:  
This function has been taken over by the key field in the piconet synchronization parameters information element.  Delete the sentence and the key bit (b2) from Figure 31.  Add the bit to the reserved bits.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Also closes 162, 1351, 1742, 1768, 1751, 1786, 1674.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1493
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  42
CommentType:  E

Comment:  
It needs to be made clear that the timing starts from the begining of the beacon preamble
CommentEnd:  

SuggestedRemedy:  
Modify the sentence as follows:  "The value of this field is always an offset from the start of superframe and hence the start of transmission of the preamble of the beacon frame from the PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  992
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  42
CommentType:  E

Comment:  
grammatical as shown below
CommentEnd:  

SuggestedRemedy:  
... offset from the start of the superframe and hence the start of the transmission of the beacon frame ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1491
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  43
CommentType:  TR

Comment:  
Since superframe duraqtion is limited to 100 ms, having the slot start time be 16 bits of 8 us resolution is not an effective use of bits.  Also, having 8 us of resolution is going to allow efficient allocation of GTS slots for high rate PHYs.
CommentEnd:  

SuggestedRemedy:  
Change resolution for CTAs to 1 us, with the max then 65.535 ms.  Change the sentence to say: "The resolution of this field is 1 µs and so the range is [0-65535] µs."
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1492
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.10
Page:  107
Line:  46
CommentType:  TR

Comment:  
This line will change when we add the duration field back in as we agreed to.
CommentEnd:  

SuggestedRemedy:  
Modify this sentenc to say"  The eand of each GTS slot is the start of the GTS slot plus the duration.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Modify sentence to say "The end of each time slot is the start time of the time slot plus the time slot duration."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1114
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.4.10
Page:  108
Line:  10
CommentType:  T

Comment:  
Line in table says AWAKE rather than WAKE, and does not indicate that there is a GTS slot.
CommentEnd:  

SuggestedRemedy:  
Change entry to:  EPS CTA, WAKE superframe w/ GTS
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  321
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.11
Page:  108
Line:  30
CommentType:  T

Comment:  
Multicast capabilities are not defined for this protocol.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "The destination address may include group or multicast destinations."
RemedyEnd:  

Response:  
PROPOSED REJECT.  Add a paragraph in clause 8 that defines the scope and intention of multicast in this draft. 8.6.1 is the target clause. WMS to write text. In this clause change 'group' to 'broadcast'.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  1495
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.11
Page:  108
Line:  33
CommentType:  TR

Comment:  
Mea Culpa:  I no longer feel think that the Max CTAs field is a good idea.  It is open to abuse by manufacturers who want to save power in their devices.  It will also be difficult to interoperate if all devices choose a small number.
CommentEnd:  

SuggestedRemedy:  
Remove the Max CTAs field and all references to it.  We would be better off limiting the number of CTAs in a piconet.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Add parameter aMinProcessedCTAs value 64 to Table 73. Insert sentence after "… destination." "MaxProcessedCTAs shall be no less than aMinProcessedCTAs."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  994
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.12
Page:  108
Line:  40
CommentType:  E

Comment:  
add commas to sentence as shown below
CommentEnd:  

SuggestedRemedy:  
... DEV to know if any GTSs, where it is either the SA or DA, have changed ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  243
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.4.12
Page:  108
Line:  44
CommentType:  E

Comment:  
The following sentence does not end in a period: and not all bits in the bitmap
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  819
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4.12
Page:  108
Line:  49
CommentType:  TR

Comment:  
wrong octet number and length (256 bits = 32 octets)
CommentEnd:  

SuggestedRemedy:  
correct from 8 to 32 octets Lenth(=32)
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1496
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.12
Page:  109
Line:  1
CommentType:  E

Comment:  
Need to clarify this sentence: "If either it’s DEV GTS status bit or the broadcast GTS status bit is set to one, then the DEV needs to process the CTAs in that beacon."
CommentEnd:  

SuggestedRemedy:  
Modify as follows: "If either it’s DEV GTS status bit or the broadcast GTS status bit is set to one or it did not correctly receive and process the preceeding beacon, then the DEV needs to process the CTAs in that beacon."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  244
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.4.13
Page:  109
Line:  21
CommentType:  E

Comment:  
The following sentence does not end in a period: The EPS info field shall be formatted as illustrated in Figure 35
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1498
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.13
Page:  109
Line:  32
CommentType:  E

Comment:  
Having EPS be both a mode and a state is too confusing.
CommentEnd:  

SuggestedRemedy:  
Rename the EPS state to something other than EPS.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1500
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.13
Page:  109
Line:  33
CommentType:  TR

Comment:  
"If the DEV will not use any power management, the field will be set to 0."  Why would any device listen to GTSs that are not assigned to it.  Any device should be able to do RPS.  There is no need to have an active state.
CommentEnd:  

SuggestedRemedy:  
Power management ACTIVE vs RPS is an implementer decidision.  There shoudl be no distindction in the standard between RPS and active devices.  Only one bit is needed for the PowerManagementMode.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. ChangePowerManagementMode to be one bit. Change "… is set to 2 ... will be set to 0 …" to be "…shall be set to 1. The bit shall be set to 0 otherwise."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  322
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.13
Page:  109
Line:  33
CommentType:  T

Comment:  
Informal language used to define characteristics.
CommentEnd:  

SuggestedRemedy:  
Change "this field is set to 2." to be "this field shall be set to 2." and change "the field is set to 1" to be "the field shall be set to 1" and change "the field will be set to 0" to be "the field shall be set to 0"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1501
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.13
Page:  109
Line:  35
CommentType:  E

Comment:  
"EPS status indicates the current operation (EPS or ACTIVE) for an EPS DEV and has meaning for a DEV with PowerManagementMode set = 2."  should say "only has meaning"
CommentEnd:  

SuggestedRemedy:  
Change sentence to: "EPS status indicates the current operation (EPS or ACTIVE) for an EPS DEV and only has meaning for a DEV with PowerManagementMode set = 2."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  323
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.13
Page:  109
Line:  36
CommentType:  T

Comment:  
Informal language to describe the characterisitcs of EPS status
CommentEnd:  

SuggestedRemedy:  
Change "A value of 1 is set" to be "The value shall be set to 1" and change "A value of 0 is set" to be "The value shall be set to 0"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1497
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.13
Page:  5
Line:  8
CommentType:  TR

Comment:  
It is not clear to me where thie Power management parameters infotmation element resides?  In the Beacon?  In a pwoer management frame?  I did a search and I didn't find "power management parameters element anywhere in the rest of the draft.
CommentEnd:  

SuggestedRemedy:  
Please clarify where this element is used or remove it.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  997
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.14
Page:  109
Line:  
CommentType:  T

Comment:  
Deletion of clause 7.4.14
CommentEnd:  

SuggestedRemedy:  
I see no need for the application specific information information element.  Unless someone can justify it, please delete the entire clause.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1502
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.14
Page:  109
Line:  4
CommentType:  TR

Comment:  
How is gteh application specific data put into the ASIE  There is no MLME to do this.
CommentEnd:  

SuggestedRemedy:  
Need to create and MLME to put application specific data into the ASIE.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Bob Huang will write the appropriate MLME.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  324
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.14
Page:  110
Line:  9
CommentType:  T

Comment:  
The restrictions on negotiating theuse of the ASIE is too restrictive.
CommentEnd:  

SuggestedRemedy:  
Delete " using a standard a GTS or CFP message exchange" since the negotiation is outside of the scope of the standard.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  763
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.4.14
Page:  110
Line:  9
CommentType:  TR

Comment:  
Text says that GTS or CFP mesaage exchange sets up the application specific capability.  This means that higher protocol layers are involved.  However, I can not find how the DME tells the MAC what information to put in the ASIE element or when to remove the ASIE.
CommentEnd:  

SuggestedRemedy:  
Add MLME.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  1/24/2002
VoterStatus: 

-----------
CommentID:  241
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.4.2
Page:  102
Line:  30
CommentType:  E

Comment:  
The following sentence does not end in a period: The format of the piconet synchronization parameter element shall be formatted as illustrated in Figure 19
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  972
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.2
Page:  102
Line:  43
CommentType:  T

Comment:  
Field resolution is 8 uS ... this may be inefficient for 100+ Mbps data rates.  Changing this to something less (like 1 uS) impacts a number of issues in the standard.
CommentEnd:  

SuggestedRemedy:  
Bill Shvodian of XtremeSpectrum to provide text on a recommended solution.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  314
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.2
Page:  102
Line:  49
CommentType:  T

Comment:  
The CAP duration is not the time offset from the start of the beacon to the start of the CFP.
CommentEnd:  

SuggestedRemedy:  
Change "The same value is used as the time offset" to "The same value is used to calculate the time offset"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1479
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.2
Page:  102
Line:  50
CommentType:  TR

Comment:  
"The duration of the CAP is computed as the difference between the superframe duration and the CFP duration." The beacon duration needs to be accounted for.
CommentEnd:  

SuggestedRemedy:  
The duration of the CAP is computed as the difference between the superframe duration and the CFP duration minus the Beacon time.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  45
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.4.2
Page:  102
Line:  52
CommentType:  T

Comment:  
There is no mention here of what the setting should be when MTS is used rather than CAP. Also, the xref to 8.4.2 would indicate that more would be found there, and 8.4.2 is fairly short in description.
CommentEnd:  

SuggestedRemedy:  
specify setting for MTS.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  973
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.2
Page:  103
Line:  1
CommentType:  TR

Comment:  
Reference is made to the "current data encyrption key (DEK)"
CommentEnd:  

SuggestedRemedy:  
Provide reference to the DEK details.  If the subclause is missing in clause 10 then provide the details.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  242
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.4.2
Page:  103
Line:  27
CommentType:  E

Comment:  
The following sentence does not end in a period: — 0b11: both authentication and data encryption are required
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  315
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.2
Page:  103
Line:  29
CommentType:  T

Comment:  
The piconet synchronization parameters element does not include the guard time.  The TG had agreed to use a constant guard time broadcast by the PNC to account for differences in the clocks of the DEVs participating in the piconet.  This addition was held off on the chance that the CTAs would have both start and stop times.  Since they do not, we need to add guard time back in.
CommentEnd:  

SuggestedRemedy:  
Add a 2 octet element to the end of the piconet synchronization parameters element that indicates the piconet guard time in microseconds, 0-65536 us.  Also need to add to clause 8 the use of the guard time with the CFP.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1481
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.2
Page:  103
Line:  29
CommentType:  TR

Comment:  
Rather than wasting a value, change the ecoding so that in the future we can allow a key per SA/DA pair.
CommentEnd:  

SuggestedRemedy:  
— 0b00: neither authentication nor data encryption are required. — 0b01: authentication is required. — 0b10: both authentication and data encryption are required - single Key per piconet — 0b11: both authentication and data encryption are required - single key per SA/DA pair
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1756
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  07
Subclause:  7.4.3
Page:  103
Line:  49
CommentType:  E

Comment:  
b0-b5, b6-b9 (supported data rates should be 5 bits, not 6 bits)
CommentEnd:  

SuggestedRemedy:  
b0-b4, b5-b9
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  813
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4.3
Page:  103
Line:  50
CommentType:  T

Comment:  
there is a bit for 'Neighbor PNC', but not for 'Child PNC'
CommentEnd:  

SuggestedRemedy:  
Add a bit for 'Child PNC', if required.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  316
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.3
Page:  104
Line:  17
CommentType:  T

Comment:  
The PNC Des-mode description is incorrect.
CommentEnd:  

SuggestedRemedy:  
Change the definition to match what is now in clause 8, the new definitions chould read:  The PNC Des-Mode is the designated mode of the DEV.  This bit shall be set to 1 if it is desired that the DEV be the PNC of the piconet and the AC bit is set to 1.  Otherwise this bit shall be set to 0.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  814
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4.3
Page:  104
Line:  5
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'if DEV is intends to be' by  'if DEV intends to be'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  44
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.4.3
Page:  104
Line:  8
CommentType:  T

Comment:  
A left over in that EPS is called sleep state. Also, this bit should be to indicate possiblility of operating in EPS mode. Other information carried elsewhere
CommentEnd:  

SuggestedRemedy:  
Change text: The PSAVE bit shall be set to 1 if the DEV is capable of using EPS mode as part of power management.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1764
CommenterName:  Carmeli, Boaz
CommenterEmail:  boazc@il.ibm.com
CommenterPhone:  972-4-8296504
CommenterFax:  
CommenterCo:  IBM
Clause:  07
Subclause:  7.4.3
Page:  104
Line:  9
CommentType:  E

Comment:  
Otherwise the PS bit ...
CommentEnd:  

SuggestedRemedy:  
Otherwise the PSAVE bit ... (Consistency with previous row)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  317
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.5
Page:  104
Line:  45
CommentType:  E

Comment:  
All occurances of Kus were to be changed to milliseconds, but some were missed.
CommentEnd:  

SuggestedRemedy:  
Change all occurances (there are 2 on 104 and more follow in clause 7) of Kus to milliseconds
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  977
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.5
Page:  104
Line:  53
CommentType:  E

Comment:  
modify sentence as shown below
CommentEnd:  

SuggestedRemedy:  
... DEVs shall expect a beacon from the PNC in ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  980
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.6
Page:  105
Line:  3
CommentType:  E

Comment:  
Add a definite article as shown below
CommentEnd:  

SuggestedRemedy:  
... are conveyed to the MAC ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  982
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.7
Page:  105
Line:  30
CommentType:  T

Comment:  
Addition to clause 4
CommentEnd:  

SuggestedRemedy:  
Add OID to the acronyms list
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1483
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.7
Page:  105
Line:  31
CommentType:  E

Comment:  
OID needs to be defined here and in the acronyms, not just in the appendix.
CommentEnd:  

SuggestedRemedy:  
Define OID and add to the appendix.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  983
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.7
Page:  105
Line:  33
CommentType:  TR

Comment:  
Reference is made to IEEE P1363
CommentEnd:  

SuggestedRemedy:  
Clause 10 does not make reference to IEEE P1363 and it appears that it should.  How does P1363 enter into the security algorithms?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1673
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.7
Page:  105
Line:  3334
CommentType:  T

Comment:  
The cipher suites are not defined according to any standard.  In particular, the IEEE P1363 standard, which is Std IEEE 1363-2000, does not contain any cipher suites in it.
CommentEnd:  

SuggestedRemedy:  
Recommend changing the sentence to "The OID field specifies a unique cipher suite."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  815
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4.8
Page:  105
Line:  44
CommentType:  TR

Comment:  
wrong length value
CommentEnd:  

SuggestedRemedy:  
Length(=3)
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1763
CommenterName:  Carmeli, Boaz
CommenterEmail:  boazc@il.ibm.com
CommenterPhone:  972-4-8296504
CommenterFax:  
CommenterCo:  IBM
Clause:  07
Subclause:  7.4.8
Page:  105
Line:  44
CommentType:  E

Comment:  
Length (=2)
CommentEnd:  

SuggestedRemedy:  
Length (=3)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  985
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.8
Page:  106
Line:  3
CommentType:  E

Comment:  
modify sentence as shown below
CommentEnd:  

SuggestedRemedy:  
The current TX power is the DEVs estimate ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1485
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.8
Page:  106
Line:  3
CommentType:  E

Comment:  
"the" missing
CommentEnd:  

SuggestedRemedy:  
Change to "The current Tx Power is THE DEVs estimate..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1486
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.8
Page:  106
Line:  6
CommentType:  T

Comment:  
Why is power at the antenna used, and not eirp?
CommentEnd:  

SuggestedRemedy:  
change to eirp
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  318
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.9
Page:  106
Line:  10
CommentType:  T

Comment:  
The description of piconet maximum transmit power is incorrect.
CommentEnd:  

SuggestedRemedy:  
Change "... communicate the transmit power control (TPC) capabilities of a DEV." to be "... communicate the maximum power allowed by the PNC as described in 8.14.1"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  816
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4.9
Page:  106
Line:  10
CommentType:  TR

Comment:  
wrong sentence above figure 28 (correct description below figure 28)
CommentEnd:  

SuggestedRemedy:  
Delete wrong sentence about TPC capabilities of a DEV.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  319
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.4.9
Page:  106
Line:  15
CommentType:  T

Comment:  
Delete reserved field, elements can be defined as odd lengths, the protocol automatically pads them to even numbers of octets.
CommentEnd:  

SuggestedRemedy:  
Delete the field "Reserved" and change the length of the element to 1
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1487
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.4.9
Page:  106
Line:  23
CommentType:  T

Comment:  
Why would we limit transmit power and not eirp?
CommentEnd:  

SuggestedRemedy:  
Change piconet maximum transmit power to limit eirp.  Antennal gain PIB may be needed.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  853
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.4-7.5
Page:  
Line:  
CommentType:  TR

Comment:  
Each command has its own defined structure. This requires to store all the command structures.
CommentEnd:  

SuggestedRemedy:  
A command should only contain 'information elements', e.g. all the commands that now contain an 'Device ID'-field should instead contain the 'Device identifier' information element. This requires the definition of additional information elements, e.g. 'Key object', 'Authentication info', 'Key challenge', 'Key proof', 'Reason/Result', 'Timeout'.
RemedyEnd:  

Response:  
PROPOSED REJECT. The committee feels that although this proposal provides flexibility, it would have a negative impact on the complexity of the hardware.  Also, there was a concern that this would increase the overhead to the commands.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  295
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5
Page:  110
Line:  17
CommentType:  T

Comment:  
Some of the commands have the settings specified for the MAC header fields, while other commands do not.
CommentEnd:  

SuggestedRemedy:  
Add a sentence that says that the MAC header fields are set as appropriate unless otherwise specified.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1503
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5
Page:  110
Line:  18
CommentType:  E

Comment:  
"No command frame shall be transmitted to or by an unassociated DEV within a piconet."  If no command frames are allowed by an unassociated DEV, you couldn't associate since association is a command frame!
CommentEnd:  

SuggestedRemedy:  
Change to:  "No command frame except association request and response shall be transmitted to or by an unassociated DEV within a piconet."  And Add:  Alternate PNC announcement and pullout are allowed during piconet initialization.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  325
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5
Page:  110
Line:  18
CommentType:  T

Comment:  
The restriction on transmitting command frames is too restrictive.  It would not allow an unassociated DEV to associate.
CommentEnd:  

SuggestedRemedy:  
Change "No command ... within a piconet." to be "Other than the association request, association response, alternate PNC selection command and new PNC announcement command, no command frame shall be transmitted to or by and unassociated DEV within a piconet."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1505
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5
Page:  111
Line:  33
CommentType:  TR

Comment:  
We cannot understand the be3nefit of sending more than one command in a frame.  Are we going to queue commands until we get enough to send?  How long are they held?  Won't this create latency?
CommentEnd:  

SuggestedRemedy:  
For the good of the protocol, only allow one command per command frame.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1000
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5
Page:  111
Line:  33
CommentType:  E

Comment:  
add the word "the"
CommentEnd:  

SuggestedRemedy:  
... 2-octet boundary within the frame body.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1001
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.1
Page:  111
Line:  44
CommentType:  E

Comment:  
grammatical ... add a colon as shown below
CommentEnd:  

SuggestedRemedy:  
... PNC selection commands: the alternate PNC ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  326
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.1
Page:  111
Line:  47
CommentType:  T

Comment:  
There are no more directed frames in the PNC selection process, so the ACK policy shall always be No-ACK.  In addition, the stream control field should be set to 0 in these commands.
CommentEnd:  

SuggestedRemedy:  
Change "set to request ... zero." to be "set to No-ACK."  Change "frame control field of the MAC header" to be "frame control field and the stream control field of the MAC header"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1506
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.1
Page:  111
Line:  50
CommentType:  TR

Comment:  
Why set the frag start and frag end bits to zero and ignore?  this creates an exceptionb at the receiver.  Why not set both to one, then the receiver has the OPTION of ignoring, rather than forcing the receivver to ignore.
CommentEnd:  

SuggestedRemedy:  
Change frag start and frag end to 1 for PNC selection and handover.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  328
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.1
Page:  112
Line:  11
CommentType:  T

Comment:  
Reserved fields are no longer used in the commands or information elements.
CommentEnd:  

SuggestedRemedy:  
Delete the reserved field and move the 3 1 byte fields to the end of the command so that the other fields end on 2 byte boundaries.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  327
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.1
Page:  112
Line:  2
CommentType:  T

Comment:  
Directed frames are no longer used in the PNC selection process.
CommentEnd:  

SuggestedRemedy:  
Change the sentences "The DA is set to the ... upon reception." to read "The DA is set to the broadcast address." (i.e. change first sentence and delete the two that follow).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1507
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.1
Page:  112
Line:  25
CommentType:  TR

Comment:  
Tx power level should be PHY dependant.  Some PHYs may be regulated as powerspectral density, not power.
CommentEnd:  

SuggestedRemedy:  
Makd Tx Poweer level PHY dependant and move the description of this field to Clause 11.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1508
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.1
Page:  112
Line:  34
CommentType:  T

Comment:  
"A late joining, new DEV may extend this time via its frame which shall be adopted by all the currently participating DEVs."  What if all teh other DEVs can't hear?  How does it get propagated?
CommentEnd:  

SuggestedRemedy:  
Explain how this change impacts the process.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  670
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.1.1
Page:  112
Line:  36
CommentType:  TR

Comment:  
Alternate PNC announcement command unneeded.
CommentEnd:  

SuggestedRemedy:  
Please delete clause 7.5.1.1
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  329
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.1.2
Page:  112
Line:  42
CommentType:  T

Comment:  
The alternate PNC pullout command was deleted from the functional description a couple of revisions ago.  This command is no longer used.
CommentEnd:  

SuggestedRemedy:  
Delete the entire sub-clause 7.5.1.2 and all other references to the command in the draft, especially in Table 65, renumbering as necessary.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  671
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.1.2
Page:  112
Line:  42
CommentType:  TR

Comment:  
Alternate PNC pullout command unneeded given the change in Clause8.2.3 p139 line30-32.
CommentEnd:  

SuggestedRemedy:  
Please delete this clause 7.5.1.2
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  738
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.1.2
Page:  112
Line:  4247
CommentType:  TR

Comment:  
There was agreement by the meeting to remove this section.
CommentEnd:  

SuggestedRemedy:  
Remove.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  330
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.1.3
Page:  112
Line:  48
CommentType:  T

Comment:  
The new PNC announcement command doesn't need to use all of the bytes in the other PNC commands.  It really only needs the new beacon timeout parameter.
CommentEnd:  

SuggestedRemedy:  
Add to the text, following "as PNC in the piconet." on line 52 with "This command is also used at the end of a PNC handover by the new PNC of the piconet to signal the end of PNC handover. The new PNC announcement command shall be formatted as illustrated in Figure 38."   Octets: 2      2               2  Type       Length (=2)  New beacon timeout Figure 38 -- New PNC announcement frame body  (delete old paragraph beginning "At the end of ... hand over." and change the paragraph "The CSTimeout ... in the channel." to read as follows:)  "The new beacon timeout field indicates the time offset in milliseconds before which the first beacon shall be sent by the winning AC, in the case of PNC selection, or by the new PNC, in the case of PNC handover."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  672
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.1.3
Page:  112
Line:  51
CommentType:  E

Comment:  
An AC uses this action type to ...
CommentEnd:  

SuggestedRemedy:  
Please change to: " An AC uses this frame type to ..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1003
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.1.3
Page:  113
Line:  1
CommentType:  E

Comment:  
grammatical correction
CommentEnd:  

SuggestedRemedy:  
At the end of a PNC handover, the new PNC of the piconet uses the PNC selection frame with this action type to signal the end of the PNC handover.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1005
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.1.4
Page:  113
Line:  28
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
replace "hand over" with "handover"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  331
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.1.4
Page:  113
Line:  9
CommentType:  T

Comment:  
The PNC handover command has unnecessary items in the frame format and adds a redundant and therefore evil definition of how the frame will be used.
CommentEnd:  

SuggestedRemedy:  
Change "The PNC shall use this command" to be "The PNC uses this command" and delete the following fields from both the frame format and the definitions that follow:  superframe duration - every DEV associated with the piconet is required to know this anyway. PNC device ID - every DEV knows this from the beacon. AC device ID - The DEV already knows its own device ID  Change the command length from 18 to 4 octets.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  725
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.10.1
Page:  130
Line:  21
CommentType:  TR

Comment:  
The Channel Time request command is inadequately defined for the functions required of it in this protocol.
CommentEnd:  

SuggestedRemedy:  
The Channel Time request command clause in doc 02/037r0 provides detailed resolution to this issue.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  770
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.10.1
Page:  130
Line:  23
CommentType:  E

Comment:  
Length(n*10)+pad should be (n*12)
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  837
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.10.1
Page:  130
Line:  2333
CommentType:  TR

Comment:  
wrong length indicated
CommentEnd:  

SuggestedRemedy:  
replace at the end of line 23: '9' by '12' correct in Figure 71: Length(n*12)
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1085
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  130
Line:  24
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
octets corresponds to a channel time ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  750
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.10.1
Page:  130
Line:  24
CommentType:  E

Comment:  
'Each block of 9' is incorrect.
CommentEnd:  

SuggestedRemedy:  
Change to 'Each block of 12'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1086
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  130
Line:  25
CommentType:  E

Comment:  
grammatical ... at the end of the sentence strike out the words "format of a" as shown below
CommentEnd:  

SuggestedRemedy:  
... with the target DEV.  The channel time request block ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1332
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  
CommentType:  TR

Comment:  
2 fields had to be added to the CTREZB, plus 7 paragraphs to attempt to explain their usage.
CommentEnd:  

SuggestedRemedy:  
This type of complexity in the name of powermangement is unwarranted.  Revisit power management.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  46
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  12
CommentType:  E

Comment:  
extra words
CommentEnd:  

SuggestedRemedy:  
remove "PNC it the"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1122
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  12
CommentType:  T

Comment:  
The current text allows for changing an ACTIVE CTA to an EPS CTA or vice versa.  This should not be allowed to simplify the PNC.
CommentEnd:  

SuggestedRemedy:  
Add the following text after the end of the sentence:  A channel time request for an exitsting stream shall not change an ACTIVE CTA to an EPS CTA, nor vice versa. A channel time request for an existing stream may modify the persistence of an ACTIVE CTA.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  838
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  12
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
at the beginning of line 12 delete 'the PNC it'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  3
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  12
CommentType:  E

Comment:  
extra words present
CommentEnd:  

SuggestedRemedy:  
remove "PNC it the"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  2
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  12
CommentType:  TR

Comment:  
A DEV requesting switch to ACTIVE CTA expects the PNC to grant previously requested QoS upon receipt of the switch command. This is a "should" and not a "shall" as is appropriate. However, the expectation is that the PNC shall do the switch in the very next superframe beacon even if the requested bandwidth is not immediately available. This lets the EPS DEV make the switch to ACTIVE in anticipation of bandwidth becoming available in the next few superframes as the PNC is able to juggle requirments. The comment is located here because of adjacent text that might lead the implementer to error.
CommentEnd:  

SuggestedRemedy:  
Add - The PNC shall provide the switch to ACTIVE operation even if it is unable to return the full CTR allocation.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  358
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  14
CommentType:  T

Comment:  
The frame format description contains a redundant (evil) functional description.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "The PNC shal create and retain this EPS CTR based on this request."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1593
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  14
CommentType:  E

Comment:  
The first time EPS Channel Time Request is used, it should say (EPS CTR)
CommentEnd:  

SuggestedRemedy:  
Change from "The CTRB type value of 2 is used to create an EPS channel time request." to "The CTRB type value of 2 is used to create an EPS channel time request (EPS CTR)."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1089
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  18
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... shall be a member of the EPS set before ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  256
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  19
CommentType:  E

Comment:  
The following sentence does not end in a period: The use of this field for EPS CTRs is described in 8.13.3.4
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  359
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  22
CommentType:  T

Comment:  
Need to add clarification for the stream index setting when this command is used to allocate a non-stream CTA.
CommentEnd:  

SuggestedRemedy:  
After the paragraph that ends "This field is defined in 7.2.4." add the following:  "For a new channel time request, the stream index shall be 0x00 for this command.  All time requests that are for non-zero stream indices use the stream management command, 7.5.10.3, to initiate the request."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1090
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  26
CommentType:  T

Comment:  
The line on 26 seems to indicate that the CTRB type field indicates a request for the EPS mode; however, in the paragraph starting at line 8 we saw that a device in EPS could have CTRB=0 or 1 ... so how can the CTRB field alone indicate the EPS mode?
CommentEnd:  

SuggestedRemedy:  
Have power management subcommittee clarify line 26.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  47
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  27
CommentType:  E

Comment:  
the text mentions EPS slots. Clearer wording would be wake superframes.
CommentEnd:  

SuggestedRemedy:  
change "EPS slots" to "wake superframes"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1345
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  28
CommentType:  T

Comment:  
"A zero value is not allowed ... to be ignored by the recipient" is not correct. A requested edit did not make this draft.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence and add the following replacement:  A zero value shall be treated as "never", which will have the effect that the only EPS CTA elements generated by the PNC will be the result of the EPS DEV sending a Momentary EPS CTA command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1091
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  31
CommentType:  T

Comment:  
Restructure sentence assuming the technical comment is correct
CommentEnd:  

SuggestedRemedy:  
It appears thta CTRB=0 indicates the active mode ... is this correct?  If so then rewrite the sentence of line 31 as  If the CTRB type field is zero, the allocation period is for an ACTIVE ...  (i.e. delete the word "otherwise")
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  48
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  32
CommentType:  T

Comment:  
we should be talking about microseconds and not milliseconds. If we stay consistent, the resolution should be 8 us and range is 0 to 524280
CommentEnd:  

SuggestedRemedy:  
change to 8 us and 0 - 524280
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1333
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  41
CommentType:  TR

Comment:  
Since the PNC clock and the application clocks on the DEV won't be perfectly synchronized, the superframe and the application clock will slip with respect to each other.  Therefore, the applications need to be able to handle at least a superframe worth of jitter.  By limiting the max superframe size to 65.535 ms, we put a 65.535 ms bound on delay variation.  This should be suitable for most applications.  If not, 65 ms of buffering can smooth out the jitter.
CommentEnd:  

SuggestedRemedy:  
Remove maximum allocation delay variaion from the CTRB.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1088
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.1
Page:  131
Line:  8
CommentType:  TR

Comment:  
poor sentence structure.
CommentEnd:  

SuggestedRemedy:  
There is something wrong at the end of the sentence that lies between lines 8 and 12.  Since I'm having trouble understanding the EPS mode I don't want to guess at the fix.  Have the power management subgroup fix this sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1336
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.2
Page:  132
Line:  
CommentType:  TR

Comment:  
What is the CTA element set to if it is not the same in every superframe?
CommentEnd:  

SuggestedRemedy:  
Need to define what the CTA is set to in the chanel time grant if it is not the same for every SF.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  360
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.10.2
Page:  132
Line:  17
CommentType:  T

Comment:  
Informal language defines the CTA elements.
CommentEnd:  

SuggestedRemedy:  
Change "element is defined" to be "element shall be formatted as illustrated in Figure 30 and is defined"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1747
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  07
Subclause:  7.5.10.2
Page:  132
Line:  22
CommentType:  E

Comment:  
b16-b9 (typo)
CommentEnd:  

SuggestedRemedy:  
b16-b19
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1347
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.2
Page:  132
Line:  30
CommentType:  T

Comment:  
Incorrect term used
CommentEnd:  

SuggestedRemedy:  
Change: "...start time of next GTS" to ... superframe of next GTS.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  50
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.10.2
Page:  132
Line:  31
CommentType:  T

Comment:  
I don't understand the use of the grant status field format. Isn't the SFNext a short form of the next beacon that an EPS DEV will wake on? It would seem that what we want in Figure 74 is the start time of the adjacent GTS as the text in line 31 states.
CommentEnd:  

SuggestedRemedy:  
change from SFNext to adjacent GTS start time in Figure 74 and then use adjacent GTS start time instead of SFNext on line 31.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1115
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.3
Page:  
Line:  
CommentType:  T

Comment:  
1. The stream QoS parameters field of the stream management command, connection request cause the generation of GTS slots specified by a subset of the QoS parameters.  The channel time request command specifies GTS slots using the CTRB shown in 7.7.5.10.1.  The corresponding parameters are named differently and defined differently, obfuscating their equivalency.   2. The CTA Type and EPS set parameter are missing in the QoS specification and are required to assign a stream to and EPS CTA.
CommentEnd:  

SuggestedRemedy:  
Change QoS parameters to match CTRB parameters as follows: inter slot duration --> allocation period Min. time per slot --> Min GTS time Max. time per slot --> Desired GTS time Max Tx delay variation  --> Maximum allocation delay  Add the following QoS parameters before the allocation period EPS Type, 1 octet EPS Set, 1 octet
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1096
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  132
Line:  
CommentType:  T

Comment:  
line 51
CommentEnd:  

SuggestedRemedy:  
replace the 4th word in line 51 (index) with the word "identifier"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  726
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.10.3
Page:  132
Line:  36
CommentType:  TR

Comment:  
The Stream managment command is an inordinately complicated frame command for the functions it is needed in this draft.
CommentEnd:  

SuggestedRemedy:  
Replace the Stream managment command with the upgraded Channel Time request command described in doc 02/037r0.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1748
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  07
Subclause:  7.5.10.3
Page:  132
Line:  44
CommentType:  E

Comment:  
20 (typo, Stream QoS parameters should be 23 octets long, cf. Fig. 77 in page 134)
CommentEnd:  

SuggestedRemedy:  
23
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  839
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.10.3
Page:  132
Line:  4451
CommentType:  TR

Comment:  
some inconsistencies
CommentEnd:  

SuggestedRemedy:  
Correct number of octets for 'Stream QoS parameters' to '23' Correct: Length(=29) Use either 'stream request identifier' or 'stream request index' in the Figure 75 AND the text below (line 51)
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change 23 to 22 in Figure 75. Move MaxReTXVariation up to below the MaxTXDelayVariation replacing the reserved field in Figure 77. Change the text to be "stream request identifier". Change 26 to 28 for Length.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1533
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  132
Line:  45
CommentType:  TR

Comment:  
Stream management command should use the 48 bit address instead of the 8 bit address.  Even though each DEV should have the latest table, it may get out of sync.  Using the 48 bit address will prevent problems.
CommentEnd:  

SuggestedRemedy:  
Have stream management command use the 48 bit address.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1337
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  132
Line:  51
CommentType:  E

Comment:  
"stream request index" is not consistent with Figure 75.
CommentEnd:  

SuggestedRemedy:  
Change to stream request index.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1116
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.3
Page:  132
Line:  51
CommentType:  T

Comment:  
stream request indes is the wrong term
CommentEnd:  

SuggestedRemedy:  
change "stream request index" to stream request identifier
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1121
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  13
CommentType:  T

Comment:  
The Action Type field cannot encode 0-5
CommentEnd:  

SuggestedRemedy:  
Change to 3 bits, 0 - 2 in Figure 76 and change line 20 from "2-bit" to 3-bit
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  840
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  1420
CommentType:  TR

Comment:  
For Action Type more than 2 bits are required
CommentEnd:  

SuggestedRemedy:  
change action type length to 3 bits
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  361
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  20
CommentType:  T

Comment:  
The action type requires a 3 bit field, not a 2 bit field.
CommentEnd:  

SuggestedRemedy:  
Change the text from "a 2-bit" to "a 3-bit" and re-number the bits accordingly in figure 76
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  751
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  20
CommentType:  TR

Comment:  
Text specifies a 2 bit field, yet there are 6 outcomes (6 values).
CommentEnd:  

SuggestedRemedy:  
Expand action type.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The action type will be expanded to 3 bits and the field indicated correctly in the future.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1117
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  27
CommentType:  T

Comment:  
This will tie into a proposed change to the text in 8.6. The stream connection process involves communication between the PNC and each of the two peers (originaor of the stream connection request and the target) destined to use the stream.  The stream connection process involves the PNC to determine if it can provide the GTS slot allocation requested, and the two peers must agree on a set of QoS parameters.  As currently proposed the communication flow is Originator->PNC->Target->PNC->Originator. The originator will then reply to only to the PNC if it rejects the Targets modified QoS values. The trigger for PNC generation of time slots should be a response from the Target to the PNC confirming acceptance of the final QoS parameters relayed from the Target.
CommentEnd:  

SuggestedRemedy:  
At line 36 add the following text to create a final confirmation or acceptance of the stream connection which is the trigger to the PNC to begin creating GTS: -- A value of "6" indicates that the frame is sent by the originator DEV to the PNC as a final confirmation or acceptance of the steam connecton.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  257
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  3234
CommentType:  E

Comment:  
The following sentences do not end in a period: — A value of “4” indicates that the frame is sent by one of the DEVs to the PNC to reject or disconnect the stream — A value of “5” indicates that the frame is sent by the PNC to one of the DEVs to reject or disconnect the stream
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1097
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  38
CommentType:  TR

Comment:  
Line 38 contains a TBD
CommentEnd:  

SuggestedRemedy:  
Resolve TBD ... security subcommittee
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  362
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  38
CommentType:  T

Comment:  
Security is not defined on a stream by stream basis, but rather for the piconet as a whole.
CommentEnd:  

SuggestedRemedy:  
Delete the security bits in the control information field and delete the sentence "The security field is a 3 bit field that <TBD>.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1119
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  39
CommentType:  T

Comment:  
TBD present
CommentEnd:  

SuggestedRemedy:  
must be removed or replaced with spec. I ask guidance from the security subcommittee members.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  75
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  39
CommentType:  TR

Comment:  
Security field not required.
CommentEnd:  

SuggestedRemedy:  
Remove "The security field is a 2 bit field defined in 7.2.1.2.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  294
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  39
CommentType:  T

Comment:  
The security field is a 3-bit field that <TBD>
CommentEnd:  

SuggestedRemedy:  
Security is applicable on a piconet basis, not a stream-by-stream basis.  Delete the sentence and the associated bits in figure 76 (b4-b6).  Reassign the bits as reserved and move the other bits foward so that the reserved bits are contiguous.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Also closes 1097, 1787, 1743, 1752, 1769, 1352, 1119, 52.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  52
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  40
CommentType:  T

Comment:  
there is a TBD for the security field
CommentEnd:  

SuggestedRemedy:  
define the TBD
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1339
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  133
Line:  41
CommentType:  E

Comment:  
This sentence is unclear "The direction field value of ‘1’ means that the stream is being transmitted from the DEV that sent the command.  The value of ‘0’ means that the stream is being received."
CommentEnd:  

SuggestedRemedy:  
Modify the sentence as follows:  "The direction field value of ‘1’ means that the stream is being transmitted from the DEV that originated the stream requeest.  The value of ‘0’ means that the stream is being received by the oriiginator of the stream request."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1118
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.10.3
Page:  134
Line:  48
CommentType:  T

Comment:  
"frequency" is the wrong term.
CommentEnd:  

SuggestedRemedy:  
change "frequency" to period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1341
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  134
Line:  52
CommentType:  TR

Comment:  
Setting the resolution of the channel time to 8 us will result in inefficient CTAs.  This should be change to 1 us resolution.
CommentEnd:  

SuggestedRemedy:  
Change CTA resolution to 1 us.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  737
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.10.3
Page:  134
Line:  56
CommentType:  E

Comment:  
'11' is used twice. '16' is not available from a 4 bit field.
CommentEnd:  

SuggestedRemedy:  
Correct.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1342
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  135
Line:  
CommentType:  TR

Comment:  
All of these parameters have use K which is 1024.  They should be small k, which according to the definitions is 1000.
CommentEnd:  

SuggestedRemedy:  
Change K to k.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1099
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.10.3
Page:  135
Line:  18
CommentType:  T

Comment:  
In line 18 ... in the middle of the sentence is the word "over" ... would a better word be "after"
CommentEnd:  

SuggestedRemedy:  
... the time, in Kus, after which the retransmission ...  Review by MAC people.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1510
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.1
Page:  113
Line:  41
CommentType:  TR

Comment:  
Why set the frag start and frag end bits to zero and ignore?  this creates an exceptionb at the receiver.  Why not set both to one, then the receiver has the OPTION of ignoring, rather than forcing the receivver to ignore.
CommentEnd:  

SuggestedRemedy:  
Change frag start and frag end to 1 for Association Request Command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  332
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.2.1
Page:  113
Line:  43
CommentType:  T

Comment:  
Need to add a definition of the stream control field (0x00).  Best place to put this is 7.5 since all commands are non-stream data.  Also need to delete the redundant and therefore evil definition of what goes in the PNID field (that is defined much earlier, 7.2.2)
CommentEnd:  

SuggestedRemedy:  
Add the sentence to 7.5 at the end of the first paragraph, "All commands shall have the stream index field in the MAC header set to 0x00 and shall be ignored upon reception."  Delete the sentence "The PNID values ... to associate."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1509
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.1
Page:  113
Line:  43
CommentType:  TR

Comment:  
Ignoring the header fields should be optional and not mandatory.  Setting the bits should be mandatory, ignoring them on reception should be optional.
CommentEnd:  

SuggestedRemedy:  
change to "may be ignored upon reception"  This applies to all of the commands.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1007
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.1
Page:  114
Line:  14
CommentType:  E

Comment:  
add definitive article
CommentEnd:  

SuggestedRemedy:  
... capability field is the same ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1008
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.1
Page:  114
Line:  16
CommentType:  E

Comment:  
add definitive article
CommentEnd:  

SuggestedRemedy:  
... if the frames from the PNC ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1009
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.1
Page:  114
Line:  18
CommentType:  E

Comment:  
grammatical, add definitive
CommentEnd:  

SuggestedRemedy:  
larly, if the PNC did not ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  333
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.2.1
Page:  114
Line:  19
CommentType:  T

Comment:  
A DEV that fails ATP will not neccessarily re-associate and so the PNC should not expect that to happen.  The PNC does not need to expect anything.
CommentEnd:  

SuggestedRemedy:  
Change "the DEV and expect the DEV to associate again." to be "the DEV."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1511
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.2
Page:  114
Line:  38
CommentType:  TR

Comment:  
Why set the frag start and frag end bits to zero and ignore?  this creates an exceptionb at the receiver.  Why not set both to one, then the receiver has the OPTION of ignoring, rather than forcing the receivver to ignore.
CommentEnd:  

SuggestedRemedy:  
Change frag start and frag end to 1 for Association Response Command.  This applies to all commands.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1011
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.2
Page:  114
Line:  42
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... association address; hence, this command ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  334
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.2.2
Page:  114
Line:  42
CommentType:  T

Comment:  
The ACK policy for the association response command is defined in three places and therefore is evil.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "Hence this command shall not be ACKed"  Also delete "If there is a match, ... future communications." on line 48 since this is already defined in clause 8.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1512
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.2
Page:  115
Line:  10
CommentType:  T

Comment:  
Why is "DEV wishes to disassociate" a reason code?
CommentEnd:  

SuggestedRemedy:  
Need to explain this.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  335
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.2.2
Page:  115
Line:  11
CommentType:  T

Comment:  
The condition code "DEV wishes to disassociate" is not possible in the PNC's response.  However, we do not have a code for when the PNC does not wish to allow neighbor piconets.
CommentEnd:  

SuggestedRemedy:  
Change reason code 5 from "DEV wishes to disassociate" to "Neighbor piconet not allowed"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1513
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.2
Page:  115
Line:  14
CommentType:  TR

Comment:  
Security required should be a reason code.
CommentEnd:  

SuggestedRemedy:  
Add "security requered" as a reason code.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  820
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.2.2
Page:  115
Line:  6
CommentType:  TR

Comment:  
Add possibility for reject, without giving a detailed reason
CommentEnd:  

SuggestedRemedy:  
add a reason code 'reject'
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add "request denied, no reason given" as a possible reason code.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  245
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.2.3
Page:  115
Line:  22
CommentType:  E

Comment:  
The following sentence does not end in a period: command shall be formatted as illustrated in Figure 41
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  678
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.2.3
Page:  115
Line:  33
CommentType:  T

Comment:  
Text between lines 33 and 43 is not needed if the DeviceAddress, ReasonCode, and Reserved fields are deleted.
CommentEnd:  

SuggestedRemedy:  
Please remove the indicated text.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1514
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.3
Page:  115
Line:  37
CommentType:  T

Comment:  
What does "DEV state has expired" mean?  Does this mean that ATP timeout?
CommentEnd:  

SuggestedRemedy:  
Describe what this means.  If this does not mean ATP, add ATP expired as a valid reason code.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  336
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.2.3
Page:  115
Line:  37
CommentType:  T

Comment:  
Reason code 0 and 2 are not well defined.  There is no way for the PNC to know 2, unless it monitors all GTSs.  Compliant DEVs are not allowed to overshoot their allocated channel time.
CommentEnd:  

SuggestedRemedy:  
Change reason code 0 to read "ATP has expired, DEV needs to re-associate".  Delete reason code 2 and re-number the reason codes.  As an alternative, perhaps allow reason code 2 to be "PNC unable to service DEV" as a catch-all for any problems the PNC might encounter.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1013
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.2.3
Page:  115
Line:  37
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
Channel is too severe to serve the DEV
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  821
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.2.3
Page:  115
Line:  38
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'Channel is servere ..' by  'Channel is too servere ..'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  337
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.3
Page:  115
Line:  48
CommentType:  T

Comment:  
The definition of the role of the PNC as PSM redundant and is therefore an abomination to the technical editor.
CommentEnd:  

SuggestedRemedy:  
Delete the two sentences "In all cases ...maager in a piconet."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1015
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3
Page:  115
Line:  49
CommentType:  TR

Comment:  
Piconet Security Manager
CommentEnd:  

SuggestedRemedy:  
Add text to clause 10 the details of the Piconet Security Manager - security subcommittee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1014
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3
Page:  115
Line:  49
CommentType:  T

Comment:  
acronym PSM
CommentEnd:  

SuggestedRemedy:  
add PSM to clause 4
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1516
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.1
Page:  116
Line:  11
CommentType:  TR

Comment:  
What is the maximum size of a public key object?  If it won't fit in a max frame size, the command frame would need to be fragmented.  Fragmenting command frames won't work becasue of single sequence counter.
CommentEnd:  

SuggestedRemedy:  
Need to sensure max key object size is less than the max frame size or figure out how to fragement commands.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1515
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.1
Page:  116
Line:  11
CommentType:  T

Comment:  
Public Key Object Length and Length are redundant.
CommentEnd:  

SuggestedRemedy:  
Delete Public Key Object Length.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  823
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.1
Page:  116
Line:  18
CommentType:  E

Comment:  
reorder the paragraphes
CommentEnd:  

SuggestedRemedy:  
Move sentence in line 18 up to be directly below Figure 42.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  246
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.3.1
Page:  116
Line:  5
CommentType:  E

Comment:  
The following sentence does not end in a period: The authentication request command frame structure shall be formatted as illustrated in Figure 42
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  822
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.1
Page:  116
Line:  810
CommentType:  TR

Comment:  
Include the possibility for authentication of the PNC in the authentication request.
CommentEnd:  

SuggestedRemedy:  
Include the 'Public Key Challenge' as optional information in the authentication request command.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.  The possibility of PNC authentication will be addressed by the proposals.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1022
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  29
CommentType:  TR

Comment:  
in correct figure number
CommentEnd:  

SuggestedRemedy:  
change figure 50 to figure 43
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  771
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  29
CommentType:  E

Comment:  
Pointing Figure should be 43 insted of 50
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  247
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  29
CommentType:  E

Comment:  
The following sentence does not end in a period: The authentication response command frame structure shall be formatted as illustrated in Figure 50
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  741
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  30
CommentType:  E

Comment:  
incorrect figure reference.
CommentEnd:  

SuggestedRemedy:  
should be figure 43
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  824
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  3235
CommentType:  TR

Comment:  
Include the possibility for authentication of the PNC.
CommentEnd:  

SuggestedRemedy:  
Include the 'Public Key Proof' as conditional information in the authentication response command.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.  The possibility of PNC authentication will be addressed by the proposals.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  338
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  35
CommentType:  T

Comment:  
Move the Authentication timeout field to be prior to AuthenticationInfo in the command format so that the variable field is last.
CommentEnd:  

SuggestedRemedy:  
Change as indicated.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1518
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  38
CommentType:  T

Comment:  
AuthenticationInfoLength is redudant with Length
CommentEnd:  

SuggestedRemedy:  
Delete AuthenticationInfoLength
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  825
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.2
Page:  116
Line:  41
CommentType:  E

Comment:  
To avoid confusion the term 'cipher suite' should only be used for the privacy service (encryption, ciphering).
CommentEnd:  

SuggestedRemedy:  
replace 'cipher suite' by 'authentication algorithm'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  772
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.3.2
Page:  117
Line:  5
CommentType:  E

Comment:  
Pointing Figure should be 44 insted of 50
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  826
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.3
Page:  116
Line:  50
CommentType:  E

Comment:  
To avoid confusion the term 'cipher suite' should only be used for the privacy service (encryption, ciphering).
CommentEnd:  

SuggestedRemedy:  
replace 'cipher suite' by 'authentication algorithm'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  339
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.3.3
Page:  117
Line:  10
CommentType:  T

Comment:  
Move the AuthenticateFailueTimeout to be the first field so that the variable length field is last in the command format.
CommentEnd:  

SuggestedRemedy:  
Change as indicated in the figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1519
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.3
Page:  117
Line:  10
CommentType:  T

Comment:  
PublicKeyChallengeLength is redundant with Length
CommentEnd:  

SuggestedRemedy:  
Delete PublicChallengeLength
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  827
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.3
Page:  117
Line:  17.18
CommentType:  E

Comment:  
To avoid confusion the term 'cipher suite' should only be used for the privacy service (encryption, ciphering).
CommentEnd:  

SuggestedRemedy:  
replace 'cipher suite' by 'authentication algorithm'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  79
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  07
Subclause:  7.5.3.3
Page:  117
Line:  2021
CommentType:  TR

Comment:  
AuthenticateFailureTimeout is not sent with the Challenge command. It is used within the MAC to limit the amount of time the MAC will wait for an Authentication response.
CommentEnd:  

SuggestedRemedy:  
Remove the last field (AuthenticationFailureTimeout) from Figure 44 on page 117. Remove lines 20-22 on page 117.
RemedyEnd:  

Response:  
PROPOSED ACCEPT.    
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  Security
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1023
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.3
Page:  117
Line:  5
CommentType:  TR

Comment:  
in correct figure number
CommentEnd:  

SuggestedRemedy:  
should be figure 44
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  743
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.3.3
Page:  117
Line:  5
CommentType:  E

Comment:  
incorrect figure reference.
CommentEnd:  

SuggestedRemedy:  
Should be figure 44.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  828
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.4
Page:  117
Line:  2644
CommentType:  E

Comment:  
To avoid confusion the term 'cipher suite' should only be used for the privacy service (encryption, ciphering).
CommentEnd:  

SuggestedRemedy:  
replace 'cipher suite' by 'authentication algorithm'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  773
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.3.4
Page:  117
Line:  32
CommentType:  E

Comment:  
Pointing Figure should be 45 insted of 50
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  248
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.3.4
Page:  117
Line:  32
CommentType:  E

Comment:  
The following sentence does not end in a period: The challenge response command frame structure shall be formatted as illustrated in Figure 50
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  744
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.3.4
Page:  117
Line:  32
CommentType:  E

Comment:  
incorrect figure reference.
CommentEnd:  

SuggestedRemedy:  
Should be figure 45.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1024
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.4
Page:  117
Line:  32
CommentType:  TR

Comment:  
in correct figure number
CommentEnd:  

SuggestedRemedy:  
figure should be 45
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1520
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.4
Page:  117
Line:  37
CommentType:  T

Comment:  
PublicKeyProofLength is redundant with Length
CommentEnd:  

SuggestedRemedy:  
Eliminate PublicKeyProofLength
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1521
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.5
Page:  117
Line:  47
CommentType:  E

Comment:  
Request key request command is redundant.
CommentEnd:  

SuggestedRemedy:  
Change to Key Request command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1030
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.5
Page:  118
Line:  1
CommentType:  TR

Comment:  
incorrect figure number
CommentEnd:  

SuggestedRemedy:  
should be figure 46
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  774
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.3.5
Page:  118
Line:  1
CommentType:  E

Comment:  
Pointing Figure should be 46 insted of 50
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  745
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.3.5
Page:  118
Line:  1
CommentType:  E

Comment:  
incorrect figure reference.
CommentEnd:  

SuggestedRemedy:  
Should be figure 46.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  249
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.3.5
Page:  118
Line:  1
CommentType:  E

Comment:  
The following sentence does not end in a period: The request key request command frame structure shall be formatted as illustrated in Figure 50
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  829
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.5-7.5.3.7
Page:  118
Line:  
CommentType:  TR

Comment:  
could not find the details of the cipher suite list
CommentEnd:  

SuggestedRemedy:  
clarify contents of cipher suit list
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.  The possibility of PNC authentication will be addressed by the proposals.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1297
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.6
Page:  118
Line:  16
CommentType:  E

Comment:  
request key response command dosen't sound right.
CommentEnd:  

SuggestedRemedy:  
change to Key Response command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  250
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.3.6
Page:  118
Line:  21
CommentType:  E

Comment:  
The following sentence does not end in a period: The request key response command frame structure shall be formatted as illustrated in Figure 50
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  775
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.3.6
Page:  118
Line:  21
CommentType:  E

Comment:  
Pointing Figure should be 47 insted of 50
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1031
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.6
Page:  118
Line:  21
CommentType:  TR

Comment:  
incorrect figure number
CommentEnd:  

SuggestedRemedy:  
should be figure 47
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  746
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.3.6
Page:  118
Line:  22
CommentType:  E

Comment:  
incorrect figure reference.
CommentEnd:  

SuggestedRemedy:  
Should be figure 47.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1298
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.7
Page:  118
Line:  43
CommentType:  E

Comment:  
Since there is no Distribute Key Response command, this can just be distribute Key command.
CommentEnd:  

SuggestedRemedy:  
Change to Distribute Key command
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1033
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.7
Page:  118
Line:  43
CommentType:  TR

Comment:  
Incomplete specification for usage of distribute key request
CommentEnd:  

SuggestedRemedy:  
Clause 10 needs detail on usage and specs for distribute key request - security subcommittee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  251
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.3.7
Page:  119
Line:  1
CommentType:  E

Comment:  
The following sentence does not end in a period: The distribute key request command frame structure shall be formatted as illustrated in Figure 50
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  747
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.3.7
Page:  119
Line:  1
CommentType:  E

Comment:  
incorrect figure reference.
CommentEnd:  

SuggestedRemedy:  
Should be figure 48.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1034
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.7
Page:  119
Line:  1
CommentType:  TR

Comment:  
incorrect figure number
CommentEnd:  

SuggestedRemedy:  
should be figure 48
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  340
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.3.7
Page:  119
Line:  6
CommentType:  T

Comment:  
Change the order of the fields so that the variable length field is last, in particular put the DistributeKeyFailureTimeout as the first field following the length field.
CommentEnd:  

SuggestedRemedy:  
Change as indicated.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  776
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.3.7
Page:  120
Line:  1
CommentType:  E

Comment:  
Pointing Figure should be 48 insted of 50
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1037
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.8
Page:  119
Line:  23
CommentType:  TR

Comment:  
Deauthenticate Request Command Usage
CommentEnd:  

SuggestedRemedy:  
Security subcommittee to provide details on Deauthenticate Request command in clause 10
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1299
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.8
Page:  119
Line:  24
CommentType:  TR

Comment:  
Not sure what the deauthenticate request command does.  It does not appear aywhere in the text except in clause 6 and 7.5.3.8.  If PNC is going to deauthenticate a DEV, why not just disassociate it.
CommentEnd:  

SuggestedRemedy:  
This command should be deleted unless someone can find a use for it.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1038
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.3.8
Page:  119
Line:  29
CommentType:  TR

Comment:  
wrong figure number
CommentEnd:  

SuggestedRemedy:  
figure 49
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  748
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.3.8
Page:  119
Line:  29
CommentType:  E

Comment:  
incorrect figure reference.
CommentEnd:  

SuggestedRemedy:  
Should be figure 49.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  252
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.3.8
Page:  119
Line:  29
CommentType:  E

Comment:  
The following sentence does not end in a period: The deauthenticate request command frame structure shall be formatted as illustrated in Figure 50
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  830
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.3.8
Page:  119
Line:  34
CommentType:  TR

Comment:  
correct length value
CommentEnd:  

SuggestedRemedy:  
Lengt(=0)
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Length=0
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  777
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.3.8
Page:  120
Line:  29
CommentType:  E

Comment:  
Pointing Figure should be 49 insted of 50
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  679
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.4.1
Page:  119
Line:  45
CommentType:  T

Comment:  
The title of clause 7.5.4.1 Probe request command is incorrect.  This command requests and delivers  specific device information elements and is used to communicate DEV to DEV, DEV to PNC, or PNC to DEV.
CommentEnd:  

SuggestedRemedy:  
Please change the clause title to Device Information request command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  680
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.4.1
Page:  119
Line:  46
CommentType:  T

Comment:  
Text between line 46 and 49 referencing the probe name command is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please replace all instances of probe request with device information request.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  341
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.4.1
Page:  119
Line:  49
CommentType:  T

Comment:  
The stream control field should be defined once for all commands in 7.5 (as indicated in an earlier comment).  Hence it should be deleted from this location.  Redundancy is evil.  This sentence also occurs in 7.5.4.2 and should be deleted from there as well.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "The stream control ... ignored upon reception." which ends on the top of the next page.  Also delete the sentence "The stream control .. ignored upon reception." on page 120, line 33, sub-clause 7.5.4.2.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1044
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.1
Page:  120
Line:  
CommentType:  TR

Comment:  
So how is the MSB of the information request filed mapped (ref. Figure 50)?  Suggestion below.
CommentEnd:  

SuggestedRemedy:  
1=binary coded 0=bit map
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  681
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.4.1
Page:  120
Line:  1
CommentType:  T

Comment:  
Text between line 1 and 27 referencing the probe name command is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please replace all instances of probe request with device information request.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1300
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.1
Page:  120
Line:  12
CommentType:  E

Comment:  
These two paragraphs are confusing.  The first paragraph says that the 15 LSBs are a bitmap.  Then, the second paragraph says "The most significant bit of information request field indicates that the rest of the bits in the field are not bit maps, instead they are binary coded to indicate the element ID of the information element that is being requested by the sender of this command from its intended recipient."  This is very confusing.  IF the MSB is a what?
CommentEnd:  

SuggestedRemedy:  
The MSB action should be first, followed by a description of what the LSBs are in either case.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1043
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.1
Page:  120
Line:  16
CommentType:  E

Comment:  
grammmatical
CommentEnd:  

SuggestedRemedy:  
... request field corresponds to the information ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  253
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.4.1
Page:  120
Line:  2
CommentType:  E

Comment:  
The following sentence does not end in a period: frame structure shall be formatted as illustrated in Figure 50
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1301
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.1
Page:  120
Line:  27
CommentType:  TR

Comment:  
Why does the probe request command contain information elements?  This is requesting IEs not sending them.
CommentEnd:  

SuggestedRemedy:  
Remove Information Elements from the probe request command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  342
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.4.2
Page:  120
Line:  26
CommentType:  T

Comment:  
Clarify what is the purpose of the information elements field.
CommentEnd:  

SuggestedRemedy:  
Change "information elements, described in 7.4." to be "information elements, 7.4, about the source DEV that is being provided to the destination DEV."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  682
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.4.2
Page:  120
Line:  29
CommentType:  T

Comment:  
The title of clause 7.5.4.2 Probe response command is incorrect. This command requests and delivers  specific device information elements and is used to communicate DEV to DEV, DEV to PNC, or PNC to DEV.
CommentEnd:  

SuggestedRemedy:  
Please replace all instances of probe response with device information response.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  254
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.4.2
Page:  120
Line:  34
CommentType:  E

Comment:  
The following sentence does not end in a period: The probe response command frame structure shall be formatted as illustrated in Figure 51
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  343
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.4.2
Page:  120
Line:  44
CommentType:  T

Comment:  
The information request field is not used in the probe response command.
CommentEnd:  

SuggestedRemedy:  
Delete the field from figure 51 and the sentence referencng it on line 44.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  255
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  07
Subclause:  7.5.4.2
Page:  120
Line:  44
CommentType:  E

Comment:  
The following sentence does not end in a period: The information request field is defined in 7.5.4.1
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1046
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.3
Page:  121
Line:  4
CommentType:  E

Comment:  
misspelling ... wrong word
CommentEnd:  

SuggestedRemedy:  
... DEV in the piconet to any other DEV ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1305
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.3
Page:  121
Line:  40
CommentType:  T

Comment:  
Specify that the frames received in error wer from the destination of this command.
CommentEnd:  

SuggestedRemedy:  
Modify the sentence as followe:  "The RX error frames count is the total number of frames, not including Imm-ACK frames, that were received in error by the sender of this command from the destination of this command."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1309
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.4
Page:  121
Line:  
CommentType:  TR

Comment:  
Channel status gives no more information to the transmitter than if acknowledgements are used.
CommentEnd:  

SuggestedRemedy:  
Eliminate channel status request and response altogether an just use ACKs if you want to determine channel status.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1303
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.4
Page:  121
Line:  29
CommentType:  T

Comment:  
Max window sizeshould be an integer number of superframes, not ms.
CommentEnd:  

SuggestedRemedy:  
Change max window size to be an integer number of superframes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1049
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.4
Page:  121
Line:  37
CommentType:  TR

Comment:  
Question to PHY subcommittee about which directed frames should be counted.
CommentEnd:  

SuggestedRemedy:  
Is it that we should only count frames from the probe response source?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1304
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.4
Page:  121
Line:  37
CommentType:  T

Comment:  
Should specify that the frame counts was for frames feceived from the destination of the command.
CommentEnd:  

SuggestedRemedy:  
Modify the sentence as follows  "by the sender of this command from the destianation of this command."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1307
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.4
Page:  121
Line:  43
CommentType:  T

Comment:  
This paragraph is inconsistent.  First it says the frame loss count is frames that were not successfully received on their first attempt.  Then it says that missing frames (a gap in sequence number) is the way that lost frames are determined.  However, successful retries will not show up as a gap in sequence number.  Then it says that frames with retry bit set are not included in the calculation.
CommentEnd:  

SuggestedRemedy:  
Redo this paragraph and remove inconsistencies so that we have a solid definition of what frame loss count means.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1306
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.4
Page:  121
Line:  44
CommentType:  T

Comment:  
How do we know if a frame was received on its first attempt or a subsequent attempt?  Is this what the retyr bit is used for?
CommentEnd:  

SuggestedRemedy:  
Explain how it is determined gthat a frame was received correctly on its first attempt.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1308
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.4.4
Page:  121
Line:  49
CommentType:  T

Comment:  
"These numbers are accumulated for all streams at a DEV and sent as receive frame loss count."  It is not clear that these are only the streams from one particular DEV.
CommentEnd:  

SuggestedRemedy:  
Modify the sentence as follows:  "These numbers are accumulated for all streams from one DEV to the other DEV and sent as receive frame loss count."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  831
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.5.1
Page:  122
Line:  
CommentType:  E

Comment:  
'transmit power change' is an element and not a command
CommentEnd:  

SuggestedRemedy:  
move 7.5.5.1 into section 7.4
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1310
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.6.1
Page:  122
Line:  
CommentType:  TR

Comment:  
The DEV requesting repeater service will not know the amount of channel time required for the PNC to the destination DEV.  Also, it does not make sense to have the transmitting DEV send to both the receiver and the PNC.  This will waste too much channel time by forcing the DEV to use the lowest TxRate.  Also, Immediate ACKs can not be not used.
CommentEnd:  

SuggestedRemedy:  
If we keep repeater service, the PNC will need to determine the channel time required itself.  I recommend eliminating the repeater service.  If repeater service is needed then it should be handled by the higher layers.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  344
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.6.1
Page:  122
Line:  33
CommentType:  T

Comment:  
The repeater services request command has incorrect fields and fields that are not needed.  The PNC will repeat all communications between the two DEVs and it knows all of the CTRB's that have been allowed between the two.  Also, the device ID should not be used, but rather the AD-AD.  Since this is used for the repeater service grant command, adopting this change will require changes in 7.5.6.2 as well.
CommentEnd:  

SuggestedRemedy:  
Change the destination device ID field to be the destination AD-AD field and change the definition from "The destination device ID is the 48 bit IEEE 802 address" to be "The destination AD-AD is the addresss".  Change the length of this field to 2 octets.  Delete all of the CTRBs from the figure.  Delete the sentences "The format of channel time ... destination device ID."  Change the command length to be 2  In 7.5.6.2, change "The destination device ID is that" to be "The destination AD-AD is that"  Delete the sentences "The format of channel time ... repeater service."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  749
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  07
Subclause:  7.5.6.1
Page:  122
Line:  43
CommentType:  E

Comment:  
Incomplete wording: 'channel time'
CommentEnd:  

SuggestedRemedy:  
Change to 'channel time request block'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1052
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.6.2
Page:  122
Line:  
CommentType:  TR

Comment:  
Symmetric Repeater Channel
CommentEnd:  

SuggestedRemedy:  
This clause should be rewritten so that during the repeater operation the up/down channel being repeated by the PNC is symmetric (in terms of passed data frames) so that the PNC does not have to do any buffering when providing the repeater service.  This means the slowest PNC link (up or down) will determine the speed of the corresponding matching link.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  345
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.6.2
Page:  123
Line:  1
CommentType:  T

Comment:  
The last sentence defines functional requirements that are already defined in clause 8.  The redundant definition is therefore evil and shall be exorcised.
CommentEnd:  

SuggestedRemedy:  
Move the sentence "If the DEV ... next becomes available" to clause 8.11 or delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  346
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.6.3
Page:  123
Line:  12
CommentType:  T

Comment:  
The AD-AD should be used instead of the destination device ID.
CommentEnd:  

SuggestedRemedy:  
Change "destination device ID" to be "destination AD-AD" in the table and in one place in each of the two paragraphs that follow the figure.  Change the field size to 2 octets and the command size to 3 octets.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1054
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.6.3
Page:  123
Line:  34
CommentType:  E

Comment:  
6th reason code
CommentEnd:  

SuggestedRemedy:  
word should be "handover" and not "hand over"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  708
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.7
Page:  123
Line:  37
CommentType:  TR

Comment:  
The current Power managment commands add an inordinate level of complexity to this protocol to make it unreasonable to implement in a WPAN device. Consequently, they are inappropriate for this protocol.
CommentEnd:  

SuggestedRemedy:  
Please remove clauses 7.5.7 through 7.5.7.6.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1108
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  123
Line:  38
CommentType:  TR

Comment:  
When a DEV who wants to use EPS (the slave) asks the PNC to form an EPS set with a particular DEV who will be the "master", how does the "master" DEV get informed that he is now member of an EPS master/slave set?
CommentEnd:  

SuggestedRemedy:  
I'm having trouble following how all this works so I need the power management folks to help me on this one.  Refer to power management folks.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1169
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  123
Line:  41
CommentType:  T

Comment:  
Add reference to a clause for clarity
CommentEnd:  

SuggestedRemedy:  
In the sentence at line 41, a statement is made "When an EPS set is confirmed as created ...".  Add in this sentence reference to the clause in the text which describes how EPS sets are created.  I need help from the power management folk on this one.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  347
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.7.1
Page:  123
Line:  41
CommentType:  T

Comment:  
There is a redundant and therefore evil definition of functional requirements in this frame format section.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "When and EPS set is .. for that EPS set." since this requirement is already in clause 8.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1313
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  
CommentType:  TR

Comment:  
How does a DEV know what EPS sets are out there and which to join?
CommentEnd:  

SuggestedRemedy:  
Proponets of this power management scheme need to specify how a device knows what ESP sets are out there, who the members are so it can decide which to join.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1314
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  19
CommentType:  TR

Comment:  
"The EPS set value is a octet that is assigned by the PNC to a group of DEVs that share the same EPSTime and EPSNext."  Are all DEVs with the same EPSTime and EPSNext in a single EPS set?
CommentEnd:  

SuggestedRemedy:  
This needs to be fully clarified.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  832
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  19
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'is a octet' with 'is an octet'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1315
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  22
CommentType:  E

Comment:  
It is redundant to say "A value of zero indicates that the DEV is waking for each superframe." and to say "Depending on the value of superframe duration parameter, values of EPSTime that are less than the current value of superframe duration indicate that the DEV wakes for each superframe." Also, it is undlear why saying that "Depending on the value of the superframe duration parameter."  These words provide absolutely no value.
CommentEnd:  

SuggestedRemedy:  
It would suffice to replace both those sentences with the following: "Values of EPSTime that are less than the current value of superframe duration indicate that the DEV wakes for each superframe."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1057
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  24
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
the current value of the superframe ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1316
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  25
CommentType:  TR

Comment:  
This is all but unreadable:  "Since the wake time is bounded by superframe beacon location, the beacon start point immediately preceding the completion of EPSTime shall be the wake point."
CommentEnd:  

SuggestedRemedy:  
Replace with: "The wake point is the start of the beacon immediately preceding the completion of EPSTime."  I am putting this as a TR because I honestly don't know what was meant by the original sentence and I want to make sure I am not changing the meaning.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1059
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  28
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... beacon number as defined in the piconet synchronization ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1061
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  30
CommentType:  T

Comment:  
Rewrite sentence as shown below
CommentEnd:  

SuggestedRemedy:  
The current beacon number, as received by the DME, is used to calculate the beacon number for the next EPSTime event; that is, it is inserted into EPSNext field of the EPS action request command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1317
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  30
CommentType:  TR

Comment:  
"For this command, the value of EPSNext is taken from the EPSSync parameter in the MLME-POWERMGT.request primitive."  EPSSync is a boolean value.  How can the 2 Octet EPSNext be taken from a boolean parameter?
CommentEnd:  

SuggestedRemedy:  
The aauthors need to explain this.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1060
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.1
Page:  124
Line:  31
CommentType:  TR

Comment:  
Reference to SME
CommentEnd:  

SuggestedRemedy:  
Change to DME
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  833
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.7.2
Page:  124
Line:  36
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'action request command' by 'action response command'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  348
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.7.2
Page:  124
Line:  37
CommentType:  T

Comment:  
Again, there is a redundant and evil inclusion of functional description in the frame formats clause.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "When an EPS set is confirmed ... for that EPS set."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  349
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.7.3
Page:  124
Line:  49
CommentType:  T

Comment:  
The sentences "Each DEV in the piconet  using either EPS or RPS modes ... as is the priority information." adds no useful information about the frame format.  The first sentence is incomplete and is a functional definition that is already in clause 8. (redundancy = evil) The fact that mode and priority are provided is obvious from the frame format.
CommentEnd:  

SuggestedRemedy:  
Delete the two sentences.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1319
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.3
Page:  124
Line:  50
CommentType:  TR

Comment:  
Why should a device have to notify the PNC that it is going to be using RPS mode?  RPS just says that you can save power by not listening to GTS slots that are not assigned to you.  You will never send or receive frames in a slot that is not assigned to you, so why does the PNC need to know that you won't be listening.  Having RPS mode is an unnecessary complication of this protocol.
CommentEnd:  

SuggestedRemedy:  
Remove the reference to RPS mode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1062
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.3
Page:  124
Line:  51
CommentType:  E

Comment:  
grammatical ... rewrite sentence as shown below.
CommentEnd:  

SuggestedRemedy:  
The command shall be sent prior to the corresponding channel time request command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  350
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.7.3
Page:  125
Line:  22
CommentType:  T

Comment:  
The DEV to PNC PS command shall only be sent by associated devices and therefore shall not be sent during the association process.  Heck, it can't be sent before the DEV is associated since it doesn't know its AD-AD yet.
CommentEnd:  

SuggestedRemedy:  
Change the sentence "The command ... requirements change" to be "The command may be repeated while a DEV is associated in the piconet if the DEV requirements change."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1063
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.3
Page:  125
Line:  23
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
piconet if the DEV requirements change.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1171
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.3
Page:  125
Line:  23
CommentType:  TR

Comment:  
Add to the exisiting sentence ending at line 23 the following:
CommentEnd:  

SuggestedRemedy:  
If the EPS action response type is #9 (power savings mode not supported) then the DEV to PNC PS information command shall not be sent by a DEV.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1321
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.3
Page:  125
Line:  34
CommentType:  TR

Comment:  
Why is PowerManagementMode of 1 (rps) allowed but mode 0 (PM_Off) not allowed?    What will RPS do with EPS actions?
CommentEnd:  

SuggestedRemedy:  
Explain why an rps device would send an EPS action, but not a PM_OFF device.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1322
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.3
Page:  125
Line:  36
CommentType:  TR

Comment:  
Use of PowerManagementPriority to specify power sensitivity is open to abuse by manufacturers and should be eliminated.
CommentEnd:  

SuggestedRemedy:  
remove PowerManagementPriority completely.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  31
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.7.4
Page:  125
Line:  41
CommentType:  T

Comment:  
There is a possible authentication question with EPS and switch to ACTIVE mode or EPS mode commands. The use of these commands requires agreements between peers (after association and authentication). There may be an opportunity for an unauthorized DEV to control another DEVs power use. Sending DEVs are normally responsible for the mode shift to have the destination DEV react to changes in data transmission flow that the destination is not directly aware of. I am not clear on the security mechanisms to understand if this is an issue or not.
CommentEnd:  

SuggestedRemedy:  
This may be as simple as adding a note in this subclause that the destination DEV may reject the operation if not setup in a stream managment command sequence. The offended DEV would then send a switch command to the PNC to let the PNC and other network DEVs know its correct state.  The intent is to not burden the PNC with filtering unless this is a simple fit into existing PNC filtering operations (e.g., CTRs are not processed unless they match to an existing stream setup). If this is simple then the PNC should reject the operation.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1065
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.4
Page:  126
Line:  1
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... DEV addresses operating with the same EPS ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1066
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.4
Page:  126
Line:  2
CommentType:  T

Comment:  
reference to "self wake"
CommentEnd:  

SuggestedRemedy:  
Power management committee needs to supply definition of what a "self wake" is ... I don't understand what is being implied here.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  351
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.7.5
Page:  126
Line:  16
CommentType:  T

Comment:  
The structure of the command is not stated in formal language (missed in the last update).
CommentEnd:  

SuggestedRemedy:  
Change the sentences "The structure of the ... DEV.  The use is to instruct" to be "The switch to EPS CTA mode command shall be formatted as illustrated in Figure 60.  The command is used to instruct"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  834
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.7.5
Page:  126
Line:  16
CommentType:  E

Comment:  
2nd sentence is not clear.
CommentEnd:  

SuggestedRemedy:  
Delete 'To indicate to the PNC' or clarify what is indicated to the PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1068
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.5
Page:  126
Line:  18
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... DEV addresses operating with the same
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  352
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.7.5
Page:  126
Line:  19
CommentType:  T

Comment:  
A DEV should not be able to force other DEVs to sleep.  Thus, the swich to EPS CTA should only apply to the DEV that is sending the command.  The PNC already knows which CTAs to change from the information that was given when the CTAs were set up.
CommentEnd:  

SuggestedRemedy:  
Delete the sentences "Additional destination... for self sleep only."  Delete the field "Destination DEV addresses" from the figure and change the command length to 0.  Delete the sentence "The destination DEV ... to EPS mode." on line 30.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1069
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.5
Page:  126
Line:  20
CommentType:  T

Comment:  
Clairfication of self sleep
CommentEnd:  

SuggestedRemedy:  
Ask power management guys what self sleep is ... I don't understand.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1349
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  07
Subclause:  7.5.7.5
Page:  126
Line:  20
CommentType:  T

Comment:  
This applies also to 7.5.7.4., p126, line 3.  The use of the Destination DEV address is not arbitrary and should be indicated.
CommentEnd:  

SuggestedRemedy:  
A DEV issuing a Switch to EPS (ACTIVE) mode command shall only use the Destination DEV Address if the Destination DEV and the issuing DEV agree amoung themselves that this is allowed.  The mechanism for this negotiation is beyond the scope of this standard.  Otherwise a DEV shall issue the command without any Destination DEV addresses indicating that only its own mode will change.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  21
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  7.5.7.6
Page:  126
Line:  32
CommentType:  TR

Comment:  
Momentary should have had two additional fields in the d0.9 that didn't make it into the draft. The destination DEV address and stream index are required.
CommentEnd:  

SuggestedRemedy:  
make the change to figure 61 - Momentary EPS CTA command format. Add the stream index and destination DEV address.  The text is correct already.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The command that is going to be used to wake up a DEV should contain the stream index and  DevID parameters.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  353
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.7.6
Page:  126
Line:  34
CommentType:  T

Comment:  
The command format is specified in formal language (missed in the last round of updates).
CommentEnd:  

SuggestedRemedy:  
Change "The structure ... as illustrated in Figure 61." to "The momentary EPS CTA command shall be formatted as illustrated in Figure 61."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1071
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.6
Page:  126
Line:  35
CommentType:  TR

Comment:  
The sentence says that the EPS CTR is contained within the EPS CTA.
CommentEnd:  

SuggestedRemedy:  
The EPS CTR is NOT contained within the EPS CTA.  Clarify what is intended here.  (power management subcommittee)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1072
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.6
Page:  126
Line:  36
CommentType:  TR

Comment:  
The sentence beginning with "If the wave beacon ..." is poorly written and I don't understand.
CommentEnd:  

SuggestedRemedy:  
Please have power management subcommittee rewrite the sentence to clarify the text.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1641
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.7.6
Page:  126
Line:  38
CommentType:  E

Comment:  
Need to define null CTA the first time it is used.  It is defined in 8.13.3.4, but it is used several times before that.
CommentEnd:  

SuggestedRemedy:  
Define null CTA the first time it is used.  Also, add it to the definitions.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  683
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8
Page:  126
Line:  48
CommentType:  TR

Comment:  
The title of clause 7.5.8 Device Information is incorrect.  The commands described under this sub clause are commands requesting PNC information or responding with PNC information.
CommentEnd:  

SuggestedRemedy:  
Please change this clause title to: PNC information.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  697
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8
Page:  126
Line:  48
CommentType:  TR

Comment:  
Clauses 7.5.8 through 7.5.8.3 do not belong in the MAC command frame format section of this document. These clauses would be better served being defined as control plane frame formats for the convergence layer defined in the Annex.  The data to be requested is better served being passed as a unitdata payload than as part of a MAC command frame.
CommentEnd:  

SuggestedRemedy:  
See document 01469r3 for details regarding resolution to this comment.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  684
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8
Page:  126
Line:  50
CommentType:  TR

Comment:  
The text between lines 50 and 51 is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the text between lines 50 and 51 to: "This group of commands is used to request information from the PNC or to enable the PNC to respond with information it uses to manage the piconet."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  685
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8.1
Page:  127
Line:  1
CommentType:  TR

Comment:  
The title of clause 7.5.8.1 Device Information request command is incorrect. The purpose of this command is to query the PNC regarding the organized information it uses to manage the piconet.
CommentEnd:  

SuggestedRemedy:  
Please change the title of this clause to "Probe PNC request command"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  687
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8.1
Page:  127
Line:  14
CommentType:  TR

Comment:  
The text between lines 14 and 15 is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to: " The queried device AID is the DeviceAID of the DEV whose information is being requested from the PNC. ..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  354
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.8.1
Page:  127
Line:  3
CommentType:  T

Comment:  
The first sentence is a redundant (aka evil) definition of the functional use of the device information request command that already is in clause 8.  Also, the AD-AD should be used instead of the device ID
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "Only a DEV shall send the device information request command."  Change "device ID" to be "AD-AD" in the figure, change the field length to 2 and the command length to 2.  Change "The queried device ID is the device ID" to be "The queried AD-AD is the address" on line 14.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  688
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8.2
Page:  127
Line:  17
CommentType:  TR

Comment:  
The title of clause 7.5.8.2 Device information response command is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the title to PNC information response command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  689
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8.2
Page:  127
Line:  19
CommentType:  TR

Comment:  
The text between lines 19 and 22 is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please replace all instances of device information  with PNC information .
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  355
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.8.2
Page:  127
Line:  22
CommentType:  T

Comment:  
The command structure is not indicated in formal language.  In addition, the introductory paragraph gives a redundant and therefore evil functional description in the frame formats clause that belongs the functional description clause.
CommentEnd:  

SuggestedRemedy:  
Replace the sentences "Only the PNC ... all DEVs in the piconet." with "The device information response command shall be formatted as illustrated in Figure 63."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1324
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.8.2
Page:  127
Line:  36
CommentType:  TR

Comment:  
It is not clear why a DEV would need to know the CTRBs for another DEV.
CommentEnd:  

SuggestedRemedy:  
Remove all CTRBs from the device information response command records.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1076
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.8.2
Page:  127
Line:  49
CommentType:  T

Comment:  
Line 49 says, "The device ID is for the DEV whose allocations are given in the record".
CommentEnd:  

SuggestedRemedy:  
How is broadcast mode supported?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1077
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.8.2
Page:  127
Line:  53
CommentType:  T

Comment:  
Line 54 says, "The number of TX slots is the number of allocated transmission lsots for the DEV within each superframe".
CommentEnd:  

SuggestedRemedy:  
what is done for the broadcast mode?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  696
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  30
CommentType:  TR

Comment:  
Text between lines 30 and 39 is inconsistent with the text on page 131 between lines26 and 44.
CommentEnd:  

SuggestedRemedy:  
Please make consistent.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. 7.5.8.3 has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1079
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  31
CommentType:  T

Comment:  
KuS seems too coarse
CommentEnd:  

SuggestedRemedy:  
Suggest in Figure 66 we make the "duration between time slots" a 2 octet field which whould give a resolution of 4 uS.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1080
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  34
CommentType:  TR

Comment:  
resolution of 32 mS
CommentEnd:  

SuggestedRemedy:  
Should this not be 32 uS?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  836
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  34
CommentType:  TR

Comment:  
32ms is too long
CommentEnd:  

SuggestedRemedy:  
replace '32ms' by '32us'
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  356
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  4
CommentType:  T

Comment:  
This information response command is out of sync with the CTR and stream management commands.  However, there is only one piece of information that is not explicitly given in a regular device information response command, and that is the neighbor PNC device ID.  However, this is returned if a DEV requests the device information of a DEV with a neighbor PNC AD-AD.  DEVs know when there is a neighbor piconet because of the AD-AD in the CTA blocks in the beacon.  Likewise, a private GTS of an associated DEV indicates a child piconet.  All of the information in this command is already taken care of with the device information response command.  Thus this command is redundant and should be deleted.
CommentEnd:  

SuggestedRemedy:  
Delete sub-clause 7.5.8.3 and all references to the child or neighbor information response command.  If not, the sub-clause needs to be synchronized to use CTRBs like the DEV info response command.  Also needs a "shall be formatted".
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete sub-clause 7.5.8.3 and all references to the child or neighbor information response command. Also satisfies 696, 695, 694 and 693.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  835
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  6
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'same response rules a the device' with 'same response rules as the device'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  693
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  6
CommentType:  TR

Comment:  
The sentence fragment "... the device information response command,..." is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the indicated fragment to: "... the PNC information response command,..."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolved as in comment 356.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1325
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.8.3
Page:  128
Line:  6
CommentType:  E

Comment:  
"rulses a the device"  should be "rules as the device"
CommentEnd:  

SuggestedRemedy:  
Change to "rules as the device"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1082
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.9.1
Page:  129
Line:  25
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... 1-octet field that identifies the stream of the ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  855
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.9.1
Page:  129
Line:  27
CommentType:  E

Comment:  
grammatical ... remove the comma after the word frame
CommentEnd:  

SuggestedRemedy:  
frame if more than 32 ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1330
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.9.1
Page:  129
Line:  32
CommentType:  TR

Comment:  
Sequence number provides no useful information.
CommentEnd:  

SuggestedRemedy:  
Remove this sentence about end sequence number.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  357
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  07
Subclause:  7.5.9.1
Page:  129
Line:  38
CommentType:  T

Comment:  
Informal language defines the field settings.
CommentEnd:  

SuggestedRemedy:  
Change "bits set to 1 indicate" to be "bits shall be set to 1 to indicate" in line 38 and change "bits set to 0 indicate" to be "bits shall be set to 0 to indicate" in line 39.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  778
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  07
Subclause:  7.5.9.2
Page:  129
Line:  
CommentType:  E

Comment:  
Length=4*m should be 3*m
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1331
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.9.2
Page:  129
Line:  44
CommentType:  E

Comment:  
should say "unicast stream with ACK policy of Immediate ACK."
CommentEnd:  

SuggestedRemedy:  
Change to "unicast stream with ACK policy of Immediate ACK."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1084
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.5.9.2
Page:  130
Line:  11
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... field that identifies the stream that is ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1058
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  7.7.7.1
Page:  124
Line:  25
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
time is bounded by the superframe ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1713
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  Fig. 74
Page:  132
Line:  
CommentType:  TR

Comment:  
SFNext field also used in CTA elemnet (Fig. 73 & 30), this is redundant.
CommentEnd:  

SuggestedRemedy:  
Remove SFNext field
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Remove SFNext field from figure 74 and the sentence on line 30-31 "The SFNext … in 7.4.10."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1717
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  07
Subclause:  Fig.64
Page:  127
Line:  
CommentType:  TR

Comment:  
What can a requesting DEV use for the pending CTRB information of each stream and Number of TX slots, since the channel time allocation is solely determined by PNC? The information should provide characteristcs about queried device and allow  the requesting DEV to make decision about whether to initiate communication with a particular DEV
CommentEnd:  

SuggestedRemedy:  
Remove CTRB and no. of TX slot or replace with something else
RemedyEnd:  

Response:  
PROPOSED REJECT. This command is used to enable PNC handover, not request application specific device information. The name is being changed to better reflect the use.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  153
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  Figure 11
Page:  94
Line:  13
CommentType:  T

Comment:  
Where is the PHY preamble and PHY header in this figure?
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1477
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 15
Page:  100
Line:  23
CommentType:  T

Comment:  
Don't really need two octets for command type.  One is more than adequate.
CommentEnd:  

SuggestedRemedy:  
Change command type to 1 octet.  Update all relevant references to 2 octets.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  970
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 18
Page:  102
Line:  
CommentType:  T

Comment:  
Explicitly provide element ID
CommentEnd:  

SuggestedRemedy:  
0x00
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  702
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 18
Page:  102
Line:  20
CommentType:  TR

Comment:  
Device ID field name is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change indicated field name to: Device Address and make the necessary change in parameter description following the figure.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change indicated field name to: DEV Address and make the necessary change in parameter description following the figure.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  971
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 19
Page:  102
Line:  
CommentType:  T

Comment:  
Explicitly provide element ID
CommentEnd:  

SuggestedRemedy:  
0x01
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  978
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 21
Page:  103
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x02
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  975
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 23
Page:  104
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x03
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  976
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 24
Page:  104
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x04
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  979
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 25
Page:  105
Line:  
CommentType:  T

Comment:  
Provide element ID
CommentEnd:  

SuggestedRemedy:  
0x05
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  974
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 25
Page:  105
Line:  
CommentType:  TR

Comment:  
Figure 25 indicates that the supported data rates is represented by up to 8 octets, one octet for each data rate.  Reference is provided in the tesxt to clause 11.7.  In clause 11.7, Table 94 is a 5 bit mapping to a given data rate.  How does the 5 bits map to the octet?
CommentEnd:  

SuggestedRemedy:  
Suggest the 5 bits of table 94 represent the 5 LSBs and that the upper 3 bits of the octet be zeros.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  R
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  43
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  figure 25
Page:  105
Line:  1
CommentType:  T

Comment:  
The task group has indicated before that 8 supported rates will be sufficient for PHYs other than the current one described in clause 11. However, it would seem that the limit be somewhat higher. 16 seems too high but perhaps that would be a good ceiling.
CommentEnd:  

SuggestedRemedy:  
change Figure 25 in clause 7.4.6 to allow up to 16 supported rates.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  981
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 26
Page:  105
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x06
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  984
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 27
Page:  105
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x07
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  986
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 28
Page:  106
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x09
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  987
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 29
Page:  106
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x0A
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  988
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 30
Page:  106
Line:  
CommentType:  T

Comment:  
In figure 30 do two things:  1. name the last column as "slot location field" 2. Add SFNext to acronym list in clause 4
CommentEnd:  

SuggestedRemedy:  
As shown above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  164
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  Figure 30
Page:  106
Line:  46
CommentType:  T

Comment:  
Where is SFNext defined?  Did not find reference to it in the following text.  Is it a specific value?  Or based on system design and is specified in the  PIB?
CommentEnd:  

SuggestedRemedy:  
Need more information.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  699
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 30
Page:  106
Line:  47
CommentType:  TR

Comment:  
Figure 30 is missing a slot duration field.
CommentEnd:  

SuggestedRemedy:  
Please add the slot duration field to figure 30.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  698
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 30
Page:  106
Line:  47
CommentType:  T

Comment:  
The Source DEV address and Destination DEV Address fields are incorrectly named and inconsistently located in the figure.
CommentEnd:  

SuggestedRemedy:  
Please change the indicated fields to Source DEV AID and Destination DEV AID. Move the Destination DEV AID to the first field and the Source DEV AID to the second field.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.   Please change the indicated fields to Source DevID and Destination DevID. Move the Destination DevID to the first field and the Source DevID to the second field.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  993
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 32
Page:  108
Line:  
CommentType:  TR

Comment:  
Modifications to Figure 32 as shown below
CommentEnd:  

SuggestedRemedy:  
element ID = 0x0B use full name "MACPIBMaxAssignedCTAs" use full name "MACPIBMaxProcessedCTAs"
RemedyEnd:  

Response:  
PROPOSED REJECT. Use of generic name preferred by technical editor.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  995
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 33
Page:  108
Line:  
CommentType:  T

Comment:  
Provide explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x0C
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  996
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 34
Page:  109
Line:  
CommentType:  T

Comment:  
Provide explicit ID
CommentEnd:  

SuggestedRemedy:  
0x0D
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  998
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 36
Page:  109
Line:  
CommentType:  T

Comment:  
Explicit element ID
CommentEnd:  

SuggestedRemedy:  
0x0E
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1002
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 37
Page:  112
Line:  
CommentType:  T

Comment:  
Provide explicit commands types
CommentEnd:  

SuggestedRemedy:  
0x000B "Alternate PNC announcement command" 0x000C "Alternate PNC pullout command" 0x000D "PNC handover command"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  669
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 37
Page:  112
Line:  12
CommentType:  T

Comment:  
DeviceID parameter name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to DeviceAddress.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to DEVAddress.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1004
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 38
Page:  113
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x000E
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  673
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 38
Page:  113
Line:  15
CommentType:  T

Comment:  
PNC-device-id and AC-device-id parm names are incorrect.
CommentEnd:  

SuggestedRemedy:  
please change to PNC-device-address and AC-device-address.  Also rename the parameter names given in the text to describe the figure 38 parms .
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. please change to PNC-DEVAddress and AC-DEVAddress.  Also rename the parameter names given in the text to describe the figure 38 parms .
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1006
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 39
Page:  114
Line:  
CommentType:  T

Comment:  
Provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0012
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  674
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 39
Page:  114
Line:  6
CommentType:  T

Comment:  
DeviceID parm name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to DeviceAddress and its related text describing the parm.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change to DEVAddress and its related text describing the parm.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1010
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 40
Page:  114
Line:  
CommentType:  T

Comment:  
explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0013
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  676
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 40
Page:  114
Line:  30
CommentType:  T

Comment:  
DeviceAID ( aka AD-AD) is mislocated in the figure.
CommentEnd:  

SuggestedRemedy:  
Please move DeviceAID to the ReasonCode location in the table and the ReasonCode to the former DeviceAID table location.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1517
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  FIgure 40
Page:  114
Line:  30
CommentType:  TR

Comment:  
Need to specify the security parameters information element in the association response so that the DEV knows what cipher suite to use for association.
CommentEnd:  

SuggestedRemedy:  
Add security parameters IE into the association response command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  675
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 40
Page:  114
Line:  30
CommentType:  T

Comment:  
Device ID and AD-AD parm names are incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to DeviceAddress and DeviceAID.  Also make the necessary text changes in the text describing the parms in this figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1012
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 41
Page:  115
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0014
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  677
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 41
Page:  115
Line:  28
CommentType:  T

Comment:  
The DeviceID, ReasonCode, and Reserved fields of the Disassociation request command are unnecessary.
CommentEnd:  

SuggestedRemedy:  
Please remove the indicated fields.  Also set the Length parm = 0.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Leave reason code in the frame.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1016
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 42
Page:  116
Line:  
CommentType:  T

Comment:  
Do folllowing to Figure 42
CommentEnd:  

SuggestedRemedy:  
1. explicit command type = 0x001C
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1017
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 42
Page:  116
Line:  
CommentType:  TR

Comment:  
DEVPublicKeyObject
CommentEnd:  

SuggestedRemedy:  
In clause 10, provide technical details for the DEVPublicKeyObject
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1019
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 43
Page:  116
Line:  
CommentType:  TR

Comment:  
AuthenticationInfo
CommentEnd:  

SuggestedRemedy:  
In clause 10, please provide details of the AuthenticationInfo - security subcommittee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1018
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 43
Page:  116
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x001D
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1021
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 44
Page:  117
Line:  
CommentType:  TR

Comment:  
technical detail
CommentEnd:  

SuggestedRemedy:  
security subcommittee to provide detail of PublicKeyChallenge
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1020
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 44
Page:  117
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x001E
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1025
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 45
Page:  117
Line:  
CommentType:  T

Comment:  
see below
CommentEnd:  

SuggestedRemedy:  
provide explicit command type = 0x001F
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1026
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 45
Page:  117
Line:  
CommentType:  TR

Comment:  
PublicKeyProof
CommentEnd:  

SuggestedRemedy:  
Security subcommittee needs to provide technical detail in clause 10 on the PublicKeyProof
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1028
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 46
Page:  118
Line:  
CommentType:  TR

Comment:  
KeyPurpose
CommentEnd:  

SuggestedRemedy:  
Security subcommittee to provide technical detail in clause 10 about the KeyPurpose
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1027
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 46
Page:  118
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0020
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1029
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 47
Page:  118
Line:  
CommentType:  T

Comment:  
explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0021
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1032
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  figure 47
Page:  118
Line:  
CommentType:  TR

Comment:  
incomplete specification on EncryptedKeyObject
CommentEnd:  

SuggestedRemedy:  
Security subcommittee to provide detailed text in clause 10 about the EncryptedKeyObject
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1035
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  figure 48
Page:  119
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0022
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1036
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  figure 48
Page:  119
Line:  
CommentType:  TR

Comment:  
lack of detail on usage
CommentEnd:  

SuggestedRemedy:  
security subcommittee needs to provide details on DistributeKeyFailureTimeout in clause 10
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1831
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  07
Subclause:  Figure 48
Page:  119
Line:  
CommentType:  TR

Comment:  
In Figure 48 (Distribute Key Format), the DistributeKeyTimeout parameter is included. I don't think it should be passed in the frames, just used in the MAC to timeout a pending command that may not come back within the allotted time. I don't see any reason why the other MAC could make any use of this value since it the entity which is producing the result.
CommentEnd:  

SuggestedRemedy:  
Remove the timeout parameter from the frame.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1039
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 49
Page:  119
Line:  
CommentType:  TR

Comment:  
Incomplete command?
CommentEnd:  

SuggestedRemedy:  
Security subcommittee to review the command of figure 49 ... seems it is incomplete.  Is this all there is to this command?  Need reason codes?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1040
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  figure 49
Page:  119
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0023
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1041
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 50
Page:  120
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0004
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1042
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 50
Page:  120
Line:  
CommentType:  T

Comment:  
No margin on information request
CommentEnd:  

SuggestedRemedy:  
From Table 63, there are exactly 15 defined commands to date with 241 element IDs reserved for future use.  Yet, in the informatioin request field of the probe request commmand we only have room for 16 commands.  Increase to 3 octets to allow some growth or get rid of the extra 241 element IDs.  If this is done then in line 12, replace 15 bits with 23 bits.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1045
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 51
Page:  120
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0005
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1047
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 52
Page:  121
Line:  
CommentType:  T

Comment:  
explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0009
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1302
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 52
Page:  121
Line:  7
CommentType:  TR

Comment:  
The Channel Status request command should specify a window size, not leave it up to the responer
CommentEnd:  

SuggestedRemedy:  
Add channel status request window field and the appropriate descriptive text.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1048
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 53
Page:  121
Line:  
CommentType:  T

Comment:  
explicit command type
CommentEnd:  

SuggestedRemedy:  
0x000A
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1050
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 54
Page:  122
Line:  
CommentType:  T

Comment:  
explicit element ID type
CommentEnd:  

SuggestedRemedy:  
0x08  By the way, why is this information element sitting in the middle of the commands.  Should it be moved over with the other information element types?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1051
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 55
Page:  122
Line:  
CommentType:  T

Comment:  
Explicit command types
CommentEnd:  

SuggestedRemedy:  
0x0006 = Repeater service request command 0x0007 = Repeater service grant command
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1053
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 56
Page:  123
Line:  
CommentType:  T

Comment:  
Write in the command type
CommentEnd:  

SuggestedRemedy:  
0x0008
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1055
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 57
Page:  123
Line:  
CommentType:  T

Comment:  
Provide the command type number
CommentEnd:  

SuggestedRemedy:  
0x0015 = EPS action request 0x0016 = EPS action response
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1311
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 57
Page:  123
Line:  48
CommentType:  E

Comment:  
The number of octets for EPSTIme and EPS next should be 0-2 and 0-4 because they are not always present
CommentEnd:  

SuggestedRemedy:  
Change the number of octets for EPSTime and EPS next should be 0-2 and 0-4.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1172
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 58
Page:  125
Line:  
CommentType:  TR

Comment:  
Question for Power Management folks
CommentEnd:  

SuggestedRemedy:  
How does a DEV desiring RPS mode operation notify the PNC of this desire?  Does it just send the DEV to PNC PS informaiton command?  Does it have to first send a EPS action request command?  I am confused.  Please clarify and then I can generate text to prevent future readers from being confused also.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1064
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 58
Page:  125
Line:  
CommentType:  T

Comment:  
provide command type
CommentEnd:  

SuggestedRemedy:  
0x0017
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1067
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 59
Page:  126
Line:  
CommentType:  T

Comment:  
provide command number
CommentEnd:  

SuggestedRemedy:  
0x0018
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1070
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 60
Page:  126
Line:  
CommentType:  T

Comment:  
use command type number
CommentEnd:  

SuggestedRemedy:  
0x0019
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1073
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 61
Page:  126
Line:  
CommentType:  T

Comment:  
provide command type number
CommentEnd:  

SuggestedRemedy:  
0x001A
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1074
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 62
Page:  127
Line:  
CommentType:  T

Comment:  
use command number
CommentEnd:  

SuggestedRemedy:  
0x000F
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  686
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 62
Page:  127
Line:  9
CommentType:  T

Comment:  
The Queried Device ID field is incorrectly named and reserves to many octets.
CommentEnd:  

SuggestedRemedy:  
Change the Queried Device ID to Queried Device AID and the length of the field to 1 octet. Since there is no need to pass the MAC address or addresses.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change the Queried Device ID to Queried DevID and the length of the field to 1 octet. Since there is no need to pass the MAC address or addresses.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1075
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 63
Page:  127
Line:  
CommentType:  T

Comment:  
Use command number
CommentEnd:  

SuggestedRemedy:  
0x0010
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  690
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 63
Page:  127
Line:  31
CommentType:  TR

Comment:  
The caption for figure 63 is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to PNC information response command format.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  691
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 64
Page:  127
Line:  38
CommentType:  TR

Comment:  
The AD-AD and Device ID fields are incorrectly named
CommentEnd:  

SuggestedRemedy:  
Change the AD-AD field to DeviceAID and the Device ID field to Device Address.  Also change references to these fields at lines 44 and 49.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change the AD-AD field to DevID and the Device ID field to DEV Address.  Also change references to these fields at lines 44 and 49.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  692
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 64
Page:  127
Line:  41
CommentType:  E

Comment:  
The caption for figure 64 is incorrect
CommentEnd:  

SuggestedRemedy:  
Please change the caption to: Format of a record in the PNC information response command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1078
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 65
Page:  128
Line:  
CommentType:  T

Comment:  
Use command number
CommentEnd:  

SuggestedRemedy:  
0x001B
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  695
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 66
Page:  128
Line:  23
CommentType:  TR

Comment:  
The Channel Time Request fields (Duration between..., Min.requested chnl time, Requested channel time)in figure 66 are not the same as the Channel Time Request fields( Allocation period, Min GTS time, Desired GTS time, Max Allocation delay) in Figure 72.
CommentEnd:  

SuggestedRemedy:  
Please make consistent.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Resolve as in comment 356.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  694
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Figure 66
Page:  128
Line:  23
CommentType:  T

Comment:  
The Neighbor PNC Device ID field name is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change the indicated field to: PNC DeviceAddress
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Please change the indicated field to: PNC DEVAddress
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1081
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 67
Page:  129
Line:  
CommentType:  T

Comment:  
List actual command number
CommentEnd:  

SuggestedRemedy:  
0x0000
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1083
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 69
Page:  129
Line:  
CommentType:  T

Comment:  
provide explicit command type
CommentEnd:  

SuggestedRemedy:  
0x0001
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1087
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 71
Page:  130
Line:  
CommentType:  T

Comment:  
give command number
CommentEnd:  

SuggestedRemedy:  
0x0002
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1092
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 73
Page:  132
Line:  
CommentType:  T

Comment:  
Use command number
CommentEnd:  

SuggestedRemedy:  
0x0003
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1335
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 73
Page:  132
Line:  
CommentType:  E

Comment:  
Grant Status is 3 octets, not 1.
CommentEnd:  

SuggestedRemedy:  
set grant status size to 3 octets.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1334
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 73
Page:  132
Line:  8
CommentType:  TR

Comment:  
We never voted to include a grant status field. What if the grant is queued and either is sent or resent after the beacon number of the SFNext?  Then the DEV thins it doesn't have a slot for 2^16 superframes.
CommentEnd:  

SuggestedRemedy:  
Remove grant status from the channel time grant.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  49
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  figure 74
Page:  132
Line:  22
CommentType:  E

Comment:  
in the second field, the range of bits should be b16 to b19
CommentEnd:  

SuggestedRemedy:  
change b9 to b19
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1093
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 75
Page:  132
Line:  
CommentType:  T

Comment:  
Use command number
CommentEnd:  

SuggestedRemedy:  
0x0011
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1094
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 75
Page:  132
Line:  
CommentType:  TR

Comment:  
Width of Stream QoS parameters
CommentEnd:  

SuggestedRemedy:  
Figure 75 shows this field as being 20 octets wide but adding up the octets in Figure 77 we get 23 octets.  Which width is correct?  Assign to MAC subcommittee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1095
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 75
Page:  132
Line:  
CommentType:  E

Comment:  
grammatical ... missing left bracket on Del-ACK
CommentEnd:  

SuggestedRemedy:  
add bracket
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  51
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  07
Subclause:  figure 75
Page:  132
Line:  46
CommentType:  E

Comment:  
need right )
CommentEnd:  

SuggestedRemedy:  
add ) for max frames (Del-ACK)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1338
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 75
Page:  132
Line:  47
CommentType:  E

Comment:  
(Del-ACK should be (Del-ACK) - missing )
CommentEnd:  

SuggestedRemedy:  
change (Del-ACK to (Del-ACK)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  76
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  07
Subclause:  Figure 76
Page:  133
Line:  15
CommentType:  TR

Comment:  
Security field is not required.
CommentEnd:  

SuggestedRemedy:  
Remove Security field from the control information field and shift other fields left increasing size of reserved field by 2 bits.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Closed as in 294.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1340
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 77
Page:  134
Line:  
CommentType:  TR

Comment:  
We should not be negotiation for all of these parameters in the stream management command.  The PNC cannot control the minimum,peak, rate, average rate, max burst size, average frame size.  The PNC can only guaranteee access to the channel
CommentEnd:  

SuggestedRemedy:  
Remove all of the stream parameters and only request channel time.  This will greatly simplify the protocol.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1098
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure 77
Page:  134
Line:  
CommentType:  TR

Comment:  
Figure 77 lists the QoS parameters but it doesn't implicitly show which order the parameters are sent.
CommentEnd:  

SuggestedRemedy:  
Add a figure that shows how to put the QoS VECTOR together and where are the MSBs.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  170
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  Figure 77
Page:  134
Line:  36
CommentType:  T

Comment:  
What does "ReTX" mean?  It also appears on page 135, line 18.
CommentEnd:  

SuggestedRemedy:  
Need a definition to understand.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  174
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  Figure 78
Page:  139
Line:  
CommentType:  T

Comment:  
Diagram hard to read.  How does this diagram relate to the previous paragraph?  Where are the terms aCSFrameRepeat and aCSFrameBroadcast in this diagram?  I would like to see their timing relationships.
CommentEnd:  

SuggestedRemedy:  
See above.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1463
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure11
Page:  94
Line:  10
CommentType:  E

Comment:  
Adding a bracket covering the frame body and FCS and saying <aMaxFameSize would be helpful.
CommentEnd:  

SuggestedRemedy:  
Add a bracket covering the frame body and FCS and saying <aMaxFameSize would be helpful.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1484
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure27
Page:  105
Line:  44
CommentType:  E

Comment:  
Length field says "Length(=2)" but there are 3 octets.
CommentEnd:  

SuggestedRemedy:  
Change to "Length(=3)"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1488
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure30
Page:  106
Line:  45
CommentType:  TR

Comment:  
Add Duration field back into the CTA.
CommentEnd:  

SuggestedRemedy:  
I give in!  Duration should be put back into the CTA.  Add a 2 octet field to the CTA called slot duration.  We agreed on this a while back, but the person who was supposed to provide the text never did.  This will alow guard time to be added on a slot by slot  basis.  I will provide the text since on one else has.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Adopt, verify if the beacon needs to be fragmented because of this change. Reference comments 502, 505.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1490
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure31
Page:  107
Line:  15
CommentType:  TR

Comment:  
There is no reason for a key change bit to be in the CTA control block.  This will only cause problems when a station misses a beacon.  Since we have key number in the Piconet Synchronization parameters information element in the Beacon, this bit is not needed in the CTA.  It is a bad idea to reserve a bit for possible future use.
CommentEnd:  

SuggestedRemedy:  
Remove the Key change bit from the CTA control boock, and remove line 36 on page 107 about the key change bit.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1323
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure64
Page:  127
Line:  38
CommentType:  E

Comment:  
The number of TX slots does not necessarily equal the number of channel time request slots.  One CTRB can request mulotiple slots per superframe.  Conversely, multiple CTRBs can be allocated a single slot.
CommentEnd:  

SuggestedRemedy:  
Change the name form "number of TX slots" to "Number of active CTRBs"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1326
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure65
Page:  128
Line:  13
CommentType:  E

Comment:  
The figure should have "Record for child or neighbor PNC-1, Record for child or neighbor PNC-2, Record for child or neighbor PNC-n
CommentEnd:  

SuggestedRemedy:  
Change figure to say "Record for child or neighbor PNC-1, Record for child or neighbor PNC-2, Record for child or neighbor PNC-n
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1329
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure67
Page:  129
Line:  9
CommentType:  TR

Comment:  
The figure says Record for stream 1, 2, ...n, but you could have multiple records for the same stream.
CommentEnd:  

SuggestedRemedy:  
Add text that says that that there could be multiple records for the same stream.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1328
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Figure68
Page:  129
Line:  18
CommentType:  TR

Comment:  
Why is End sequence number needed?  The start sequence number and the RxStatus bitmap is all that is needed.
CommentEnd:  

SuggestedRemedy:  
Remove the End Sequence number.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1474
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 60
Page:  98
Line:  
CommentType:  TR

Comment:  
Need to add DEV GTS Status ie in table 60.  This  appears in every beacon.
CommentEnd:  

SuggestedRemedy:  
Add DEV GTS status to table 60.  It appears in every beacon.  It is described in 7.4.12
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1475
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 61
Page:  99
Line:  9
CommentType:  TR

Comment:  
Frage start and frag end should be set to 1, not zero in the beacon.  This should follow the rul so it CAN be ignored, rather than breaking the rull so that it MUST be ignored.
CommentEnd:  

SuggestedRemedy:  
Change frag-start and frag-end to 1 in the beacon in table 61
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  159
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  07
Subclause:  Table 61 and 62
Page:  99
Line:  
CommentType:  E

Comment:  
Title should read: "Frame and stream control field settings ..."
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1476
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 62
Page:  99
Line:  36
CommentType:  TR

Comment:  
Frag start and frag end should be set to 1, not zero in the ACK.  This should follow the rule so it CAN be ignored, rather than breaking the rull so that it MUST be ignored.
CommentEnd:  

SuggestedRemedy:  
Change frag-start and frag-end bits to "1" in the immediate ACK.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  700
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Table 63
Page:  101
Line:  10
CommentType:  TR

Comment:  
Missing from the Information elements table are these new information elements:  PicoNet Shutdown and New Associated DEV
CommentEnd:  

SuggestedRemedy:  
Please add these information elements to Table 63:  Piconet Shutdown (see info element description in 02/037r0)  New Associated DEV (see info element description in 02/037r0)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  701
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Table 63
Page:  101
Line:  14
CommentType:  TR

Comment:  
The Device Identifier info element is misnamed.
CommentEnd:  

SuggestedRemedy:  
Please change to Device Address info element
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  Please change to DEV Address info element
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  999
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 65
Page:  110
Line:  
CommentType:  T

Comment:  
Why do we need 16 bit commands?
CommentEnd:  

SuggestedRemedy:  
MAC subcommittee needs to justify 16 bit commands ... prefer to replace with 8 bit commands
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  703
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Table 65
Page:  110
Line:  31
CommentType:  TR

Comment:  
Probe Request command and Probe response commands are incorrect.  Also the xref in the table are incorrect.
CommentEnd:  

SuggestedRemedy:  
Please Rename the indicated commands to Probe-PNC-Request command and Probe-PNC-Response command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  704
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Table 65
Page:  110
Line:  42
CommentType:  TR

Comment:  
Alternate PNC announcement command and Alternate PNC pull out command are not needed.
CommentEnd:  

SuggestedRemedy:  
Please remove the indicated commands and their xrefs.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  705
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Table 65
Page:  110
Line:  42
CommentType:  TR

Comment:  
The Remote-Scan-Request and Remote-Scan-Response commands are missing from this table.  These commands are needed to fill in a notable missing capability in the Dynamic Channel Selection function.
CommentEnd:  

SuggestedRemedy:  
Place the Remote-Scan-Request and Remote-Scan-Response commands into the table entries previously occupied by the deleted Alternate PNC Anouncement and PNC pullout commands.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  706
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Table 65
Page:  110
Line:  48
CommentType:  TR

Comment:  
The xrefs for the Device information request and response commands is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please have the xref point to the clause previously known as Probe request and response respectively.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  707
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  07
Subclause:  Table 65
Page:  111
Line:  7
CommentType:  TR

Comment:  
The power managment frame commands introduce an inordinate amount of complexity into D09. Consequently, they are not needed.
CommentEnd:  

SuggestedRemedy:  
Remove from this table all references to EPS action request/response, Swith to Active, Switch to EPS, Momentary EPS
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1504
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 65
Page:  111
Line:  8
CommentType:  TR

Comment:  
6 commands were added just for power management.  Something is wrong when so many new commands are needed just for power management.
CommentEnd:  

SuggestedRemedy:  
Simplify power management.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1056
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 66
Page:  124
Line:  
CommentType:  T

Comment:  
Better terminology
CommentEnd:  

SuggestedRemedy:  
Instead of saying "place in set" how about instead "add to set".  Make a universal replacement.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1170
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 67
Page:  125
Line:  
CommentType:  TR

Comment:  
Add a 9th action type value
CommentEnd:  

SuggestedRemedy:  
In table 67, add 9th action type value ...  Power Saving Modes Not Supported ... 9
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1320
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table 67
Page:  125
Line:  5
CommentType:  E

Comment:  
I assume that "release confirm," "New Confirm," "place in set confirm and Return information on the EPS set response" are sent in response to the "release request", "new request", "place in set"  and "information request"  but that is not clear.
CommentEnd:  

SuggestedRemedy:  
Add text to clarify that these action types correspond to the corresponding request action types.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1494
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table64
Page:  108
Line:  10
CommentType:  TR

Comment:  
Forcing the receiver to interpret a slot start time of zero as "no GTS"  is a complication.  This CTA will need to be the first CTA because the previous CTA will use this CTA start time as it's start time.
CommentEnd:  

SuggestedRemedy:  
Another reason to add the duration field back into the CTA.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Duration field has been added in comment 505.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1312
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  07
Subclause:  Table66
Page:  124
Line:  
CommentType:  TR

Comment:  
There is no text to describe what each of these action types mean. In fact, the words "release request", "new request", "place in set"  don't even appear in any text in the entire draft.  "information request"  does not appear in any power management text.
CommentEnd:  

SuggestedRemedy:  
Need to describe what each of these action types do and when they are used.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1651
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
How do you know what EPS Sets are active?  If you want to interrogate all DEVs in all EPS sets, you first have to know what EPS sets are active.  I don't see a way to ask for the set of active EPS sets.
CommentEnd:  

SuggestedRemedy:  
Need a command and MLME to request which EPS sets are active (in use).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1656
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
Can any DEV that is not a member of an EPS set make a request for active channel time with an EPS DEV?
CommentEnd:  

SuggestedRemedy:  
Please clarify
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1594
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
"For EPS channel time requests, N = 0 is a special case in which the PNC shall create all EPS CTA slots with zero length. The zero length, or null CTA identifies that the EPS DEV shall listen to this beacon, and that the EPS DEV does not have GTS time allocated for data transmission."  I don't understand this at all.  If N=0, then every superframe has a CTA with duration 0?  Why make an exception like this and not say channel time =0 and N=1?
CommentEnd:  

SuggestedRemedy:  
Clarify what is meant by this paragraph.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1653
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
Need to clearly explain the relationship between The EPS CTRB parameters of slot size and N, and the EPS set time of EPSTime.
CommentEnd:  

SuggestedRemedy:  
Please clarify the relationship.  A picture would be helpful.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1657
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Can the PNC negotiate EPSTime and EPS N.  IF not, and all EPS sets choose a different EPSTime, periodically they will all occur on the same beacon and may use a tremendous amount of channel time.
CommentEnd:  

SuggestedRemedy:  
Address what happens when all EPS Wake beacons happen together.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1724
CommenterName:  Rofheart, Martin
CommenterEmail:  Martin@xtremespectrum.com
CommenterPhone:  703-269-3007
CommenterFax:  240-463-3306
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The power management method is overly complex and vague.
CommentEnd:  

SuggestedRemedy:  
Refer to the remedy indicated by Bill Shvodian
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1542
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
I provided 3 pages of text on Guard Times in document 01/439 that I thought we included in the draft. I don't know how it fell through the cracks.  I think it was becasuse we decided to put slot duration back into the CTAs on a Con Call and no one ever updated the text.
CommentEnd:  

SuggestedRemedy:  
Add Guard Time Text from 01/439 after I update it to add slot durations back into the channel time request.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1573
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
Should point out that the PNC broadcasts the device information table after disassociation.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence:  "After Disassociation is complete, the PNC broadcasts an update of the device information table as described in 8.2.7."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1638
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  E

Comment:  
"Any DEV using the same EPS Set have a WAKE superframe" should say has
CommentEnd:  

SuggestedRemedy:  
change to "Any DEV using the same EPS Set has a WAKE superframe"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1639
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
If higher layers are setting up the EPS Sets, how does a new DEV find the EPS set to join?  Does it have to wake up every single EPS DEV in every EPS set in order to find the DEV with the higheer layer "master or peer" that it wants to talk to?
CommentEnd:  

SuggestedRemedy:  
Need to add text to explain how a new EPS DEV finds the higher layer entity that it wishes to communicate with.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1640
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Can the PNC overbook CTAs for DEVs in EPS state?   If so, what happens if there is no chanel time available when a DEV wants to switch to use teh ACTIVE CTA?
CommentEnd:  

SuggestedRemedy:  
If this can happen, we need a command to tell the upper layers "Channel tiem not currently available."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  173
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  1
Page:  137
Line:  11
CommentType:  E

Comment:  
"sub-clause 8.2.7."  - Shouldn't this be 8.2.4?
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  188
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  11
Page:  160
Line:  33
CommentType:  E

Comment:  
Reference to Figure 8.12 should be a reference to Figure 92.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  540
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  13.1.1
Page:  163
Line:  2630
CommentType:  TR

Comment:  
This para referes to an "higher layer protocol" that takes the responsibility of tradeoff between multiple slots v/s power saving. Which higher layer protocol that is in existence has this feature? Where is it published? This entire section (8:13.1.1) is an illusion.  What happens when there are more than one device that is in EPS? doesn't all the devices except the first one have to wait for their GTS anyway no matter how PNC allocates GTSs?
CommentEnd:  

SuggestedRemedy:  
Remove 8.13.1.1 and Remove all references to "slot positioning" (example 8.13.2.2) from the draft Add a line in 8.4.3.1 as follows "PNC shall try its best to allocate the GTSs of all EPS power management devices first and then others. some of the exceptions to this are MTS for PNC commands, some Qos streams that need mulitple GTS within a superframe and requests from child/neighbor piconets"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  541
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  13.2
Page:  163
Line:  
CommentType:  TR

Comment:  
some more inconsistencies that can potentially lead to non-interoperable implementations
CommentEnd:  

SuggestedRemedy:  
1. line 48, page 163: change "assigned to it for reception." to "assigned to it for reception, and all the GTSs allocated for BC/MC reception"  2. line 49, page 163: change " within 25 percent of the slot time" to "within 25 percent of the slot time that does not show any channel activity as indicated by CCA"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1710
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  08
Subclause:  13.2
Page:  163
Line:  
CommentType:  TR

Comment:  
RPS mode appears to be an implementation issue. It doesn't require commands exchange with PNC.
CommentEnd:  

SuggestedRemedy:  
Remove this mode in draft
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. RPS mode will be removed. Informative text concerning the ability of a DEV to only be active when  required to receive or transmit will be kept in the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  542
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  13.2
Page:  163
Line:  
CommentType:  E

Comment:  
lines 11:12, page 164: tool? MTS or GTS is not a tool. it can be used effectively by devices to save power.
CommentEnd:  

SuggestedRemedy:  
Please rephrase this
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  543
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  13.3
Page:  
Line:  
CommentType:  TR

Comment:  
This clause is a standing proof for the complexity of EPS. EPS is affecting control of network, quality of service for all DEVs, adding significant overhead through transactions related to EPS states and most importantly making PNC implementation very complex and an high-cost one. Transactions listed in figure-94, 95 and 96 provide this picture, although not completely.  Then there are combinations of EPS devices and additional traffic to EPS devs and exception conditions described in 8.13.3.8, 9 and 10 which further complicate the management of these EPS devices After all this complexity, 1. There is no mechanism described for BC/MC traffic from an RPS/EPS device to another EPS device is handled? 2. There is no mechanism described for isoch or asynch traffic flow from DEVs in one EPS set to DEV in another EPS set? 3. How does a DEV from one EPS set transmit to or receive from DEV from multiple EPS devices each being in different EPS set for other reasons?  Answer to this can be one of two things either (a) they use repeater service through PNC and/or (b) PNC, knowing who is asleep, avoids providing a GTS with that DEV as rx-DEV. In either of these case we do not need this highly complex mechanism. As the mechanisms get more complex and affect all the other aspects of the standard, there is an higher risk of creating corner cases which can not be visualized easily at the time of standard, but are certain to haunt us in the field. There are proven examples in this within 802-wireless standards. Let's learn from those examples and avoid any one mechanism to affect deeply all the other mechanism in the standard. OR for any mechanism to be too complex that the implementors do not implement it, but instead they are forced to find some other solution. In any case, I am absolutely convinced that the EPS mechanism asa defined in this draft does not belong in 802.15.3. It has to be absolutely, positively simplified before we move further with this draft.
CommentEnd:  

SuggestedRemedy:  
Simplify power management to the following - Request for sleep time by DEV - Accept/Reject by PNC - Broadcast the addresses of sleeping DEV in Beacon - Allocation/modification of GTS by PNC depending on who is awake
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  544
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  16
Page:  
Line:  
CommentType:  TR

Comment:  
Table 73 has some "ms". please make them Kus for ease of implementation
CommentEnd:  

SuggestedRemedy:  
Table 73 has some "ms". please make them Kus for ease of implementation
RemedyEnd:  

Response:  
The committee has decided to change all Kus to ms as previously agreed. It was felt that there is liitle advantage to use Kus (1024) instead of ms (1000) for these values.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  o
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  800
CommenterName:  Kinney, Patrick
CommenterEmail:  pat.kinney@ieee.org
CommenterPhone:  724-425-7952
CommenterFax:  
CommenterCo:  Invensys
Clause:  08
Subclause:  2
Page:  137
Line:  
CommentType:  T

Comment:  
There is a possibility of duplicate network id's.  A device will check to see if there are any similar ids but this search cannot be 100% sure, additionally, a PAN may walk into another's coverage area.  I did not see any detection nor resolution of this event
CommentEnd:  

SuggestedRemedy:  
describe the techniques to detect network id duplication and the procedures to resolve it.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  176
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  2.4
Page:  141
Line:  2
CommentType:  T

Comment:  
I would like to see an example of the handover process in relationship to other traffic.  This should provide a system overview of the timing.
CommentEnd:  

SuggestedRemedy:  
Provide new figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  531
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  2.5
Page:  
Line:  
CommentType:  TR

Comment:  
the restriction for forming child piconet is not clear, although it might have been the intent.
CommentEnd:  

SuggestedRemedy:  
Add "Only an AC that is associated to a PNC in an existing piconet shall form a child piconet"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1705
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  08
Subclause:  2.5
Page:  141
Line:  22
CommentType:  TR

Comment:  
What is the meaning of private GTS in terms of various fields in CTRB(Fig. 72) for using channel time request command to setup a child piconet? Suppose stream index=0, what are appliacable values for others?
CommentEnd:  

SuggestedRemedy:  
Clarify the meaning of "private GTS" and usage of channel time request command for child piconet
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. In 8.2.5, following "private GTS." add "A private GTS is a GTS that has the same source and destination DevID." Also insert in 5.3.7 following the first occurrence of "private GTS". Add the following information in 8.2.5: "In the channel time request command, the CTRBtype shall be set to active, the EPSset parameter is not used, the stream index shall be set to 0, the remaining parameters are set to the time required to contain the child superframe, and are discussed in B.2."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  U
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  532
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  2.6
Page:  
Line:  
CommentType:  TR

Comment:  
the restriction on transactions with neighboring piconet is not clear, although it might have been the intent.
CommentEnd:  

SuggestedRemedy:  
Clearly list all the commands that can be exchanged between the parent and neighbor piconets and state that other commands and frame types shall not be exchanged between them.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  180
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  2.6
Page:  142
Line:  
CommentType:  TR

Comment:  
Need to add a figure similar to Figure 80 to describe a neighbor piconet.  What is different?  Why are they not the same?
CommentEnd:  

SuggestedRemedy:  
Clarification needed on neighbor piconets.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add an additional figure depicting a neighbor piconet as any wireless network that respects the time bounds associated with its relationship to the parent piconet. Bob Huang will provide the figure and any associated text.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1704
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  08
Subclause:  2.6
Page:  142
Line:  28
CommentType:  TR

Comment:  
1. It appears that there is not much difference between Neighbor piconet and Child piconet. A DEV can still request to asscociate with a PNC if it can not find a free channel.   2. Fig. 82 is the same as Fig. 81 if the association process of child piconet is taken into account.  3. Fig. 80 is the same for both child and neighbor piconet.  4. No communication between PNC of neighbor piconet and parent piconet provides doesn't seem to provide additional merits for operations of WPAN  5. What's the reason for limiting the no. of neighbor piconet to 3 special AD-DA?
CommentEnd:  

SuggestedRemedy:  
Remove 8.2.6 neighbor piconet and all related materials in the draft standard.
RemedyEnd:  

Response:  
PROPOSED REJECT.  The neighbor piconet is to allow networks that either are not 802.15.3 compliant or do not wish to join with the resident piconet to effectively share the channel with resident piconet. This is one of the 802.11b coexistence methods required.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  U
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  178
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  2.6
Page:  142
Line:  28
CommentType:  TR

Comment:  
During the proposal selection process of the standard process, I remember discussions about the fact that devices operating in an ISM band could not be coordinated.  This neighbor piconet seems to be a method for coordinating between different types of devices (such as an 802.11b or g system with 802.15.3 awareness capability - i.e. minimal DEV capability).  I thought this was illegal within the FCC part 15 rules.  I see this a minimal attempt at coexistence, but will it met the current regulations.
CommentEnd:  

SuggestedRemedy:  
This issue needs to be discussed by the group.  If it does not met current FCC regulations, an assessment should be presented on current initiatives within the FCC to change rules that will enable this capability.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. This only applies to FH devices operating under 15.247. 802.15.3 will apply to 15.249 rule.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  533
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  2.6
Page:  142
Line:  30
CommentType:  E

Comment:  
missing word
CommentEnd:  

SuggestedRemedy:  
chnage "no channels" to "no free channels"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  179
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  2.6
Page:  142
Line:  31
CommentType:  TR

Comment:  
"... a neighbor piconet within an existing piconet."  I thought the neighbor piconet was independent from an existing piconet.  How could it be within an existing piconet?
CommentEnd:  

SuggestedRemedy:  
This does not present a clear understanding of a neighbor piconet.  Clarification needed.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Replace "within an existing piconet" with "on the same channel as the existing piconet".
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  182
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  2.6
Page:  143
Line:  30
CommentType:  T

Comment:  
"... it is neither authenticated nor associated) ..." - but figure 82 shows an association sequence.
CommentEnd:  

SuggestedRemedy:  
If diagram is not wrong, paragraph is wrong.  Make the two consistent.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  183
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  3.2
Page:  144
Line:  17
CommentType:  T

Comment:  
You define what an associated response is not ... "directed frame".  So what is an associated response?  A broadcast frame?
CommentEnd:  

SuggestedRemedy:  
Please clarify
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  185
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  4
Page:  146
Line:  1
CommentType:  E

Comment:  
"... CAP is used for non-QoS frames."  - So what is it used for?  Control and asynchronous data frames?
CommentEnd:  

SuggestedRemedy:  
State what it is, not just what it is not.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  534
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  4.1
Page:  
Line:  
CommentType:  TR

Comment:  
Clearly state the relation between SIFS and RIFS
CommentEnd:  

SuggestedRemedy:  
change "SIFS < RIFS" to "RIFS = SIFS + aBackoffSlot" change "actual values of IFSs are" to "actual value of aBackoffSlot is"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  535
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  4.2
Page:  
Line:  
CommentType:  TR

Comment:  
Backoff or IFS for beacon transmission is not clear. Either Beacon tx should be after a small backoff or reasonably long IFS.
CommentEnd:  

SuggestedRemedy:  
At the end of line 39, add " instead the beacon is transmitted at the beginning of superframe by the PNC after waiting for the channel to be idle, as indicated by the CCA, for at least RIFS+aBackoffSlot time.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  536
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  4.3.3
Page:  151
Line:  822
CommentType:  TR

Comment:  
If SA is broadcast and anybody could start tx, how's collision handled? What is the point in getting devices to collide here instead of making this MTS part of CAP and letting devices freely use CAP as already defined. This is useless and adds unnecessary complexity
CommentEnd:  

SuggestedRemedy:  
Remove lines 8:22 on page 151 and all references to "MTS/GTS with BC/MC-SA" from the draft
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  537
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  4.3.4
Page:  151
Line:  
CommentType:  TR

Comment:  
What is the point in having slotted aloha access in addition to the backoff in CAP, TDMA in CFP? Why is this complexity being thrusted on the implementors of this "low cost", "low complexity" and "low power" standard? I don;t see any justification in having yet another access scheme with WPAN.
CommentEnd:  

SuggestedRemedy:  
Remove slotted aloha scheme in 8.4.3.4 and all references to it from the draft.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1714
CommenterName:  Young, Song-Lin
CommenterEmail:  syoung@sharplabs.com
CommenterPhone:  360-817-7509
CommenterFax:  
CommenterCo:  Sharp Labs. of America
Clause:  08
Subclause:  6.1, & Fig.88, 89
Page:  153
Line:  
CommentType:  T

Comment:  
This paragraph falls short of mentioning that streme connection is not completed until DEV receives Beacon from PNC with CTA. Fig. 3, 4 should be referred instead of using Fig. 88, 89, which do not give the complete process.
CommentEnd:  

SuggestedRemedy:  
Modify text that matches MSC of Fig. 3 and 4
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Delete Figure 88. Replace the cross references to 88  with Figure 3. Figure 89 refers to a PNC initiated stream between two other DEVs.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1343
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.1
Page:  137
Line:  
CommentType:  E

Comment:  
This clause neweds to be rearranged.  Clause 8.6 is mentioned before clause 8.5  Also, Clause 8.9 and 8.3 are not mentioned.
CommentEnd:  

SuggestedRemedy:  
DEescribe clause 8.5 before 8.6 and add a description of 8.9 and 8.3.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1100
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.1
Page:  137
Line:  11
CommentType:  TR

Comment:  
Reference to sub-clause 8.2.7
CommentEnd:  

SuggestedRemedy:  
Should be sub-clause 8.2.4
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1344
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.1
Page:  137
Line:  11
CommentType:  E

Comment:  
Sub Clause 8.2.7 does not exist.
CommentEnd:  

SuggestedRemedy:  
change to 8.2.4
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  841
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  08
Subclause:  8.1
Page:  137
Line:  12
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'If there are no alternate PNCs are available' to 'If there are no alternate PNCs available'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1101
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.1
Page:  137
Line:  20
CommentType:  TR

Comment:  
wrong sub-clause reference
CommentEnd:  

SuggestedRemedy:  
reference to 8.6 but should be 8.4?  Have MAC people verify.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1346
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  08
Subclause:  8.1
Page:  146
Line:  2
CommentType:  T

Comment:  
The text should elaborate on the Non-CAP case, especially with regards to processing time for the beacon. If the CAP is not present there must be a gap or unallocated time slot allocated to allow all deviecs to process the information in the beacon. If the amout time is not specified, a PNC may assign slots before a device can interpret its CTA.
CommentEnd:  

SuggestedRemedy:  
Indicate in the text that a minimum size CAP will be assigned even for the MTS only case, where the CAP will serve only as a gap between the Beacon and the GTS slots.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1158
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.10
Page:  159
Line:  42
CommentType:  E

Comment:  
There are a number of problems with the paragraph starting at line 42, of which the most serious is a reference to a wrong command.  I'd suggest the following modifications:
CommentEnd:  

SuggestedRemedy:  
1. at the end of line 43, put the word "optional" so as to read "support optional rates" 2. at the end of line 44, put the word "optional" so as to read "supported optional data rate" 3. at the end of line 45, put the word "optional" so as to read "supported optional rates" 4. in line 47, change to ... piconet shall use the proble request ... 5. in line 47, the clause reference is 7.5.4.1 (not 7.5.8.1) 6. in line 48, change to ... that it is interested in establishing communications. 7. in line 48, change to ... each DEV shall periodically use the channel ... 8. in line 49, change to ... from other DEVs of interest ... (replace the phrase "that it is interested") 9. in line 50, ... transmissions to those other DEVs. (replace the word "that")
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  714
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.10
Page:  159
Line:  47
CommentType:  TR

Comment:  
The sentence fragment in line 47 is incorrect: "Each DEV in a piconet shall use probe request command,..."
CommentEnd:  

SuggestedRemedy:  
Please change the sentence fragment to: " Each DEV in a piconet shall use the Device-Information-request command,..." where Device-Information-Request was previously known as Probe-request.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1157
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.10
Page:  159
Line:  47
CommentType:  TR

Comment:  
There are a number of problems with the paragraph starting at line 42, of which the most serious is a reference to a wrong command.
CommentEnd:  

SuggestedRemedy:  
On line 47 the probe request command is found at clause 7.5.4.1, not at 7.5.8.1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1571
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.10
Page:  159
Line:  47
CommentType:  TR

Comment:  
The DEV should not have to do a probe to determin eht PHY capability for the DEV it wants to communicate with.  That is in the DEV infor table that is broadcast by the PNC.
CommentEnd:  

SuggestedRemedy:  
Change as follows:  "Each DEV in a piconet shall check the DEV capabilities from the device information table that is broadcast by the PNC when a DEV associates  to obtain the supported rates from other DEV(s) that it is interested in communicating.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  389
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.10
Page:  159
Line:  48
CommentType:  T

Comment:  
Should not require the DEV to check the channel status.
CommentEnd:  

SuggestedRemedy:  
Change "each DEV shall periodically" to "each DEV may periodically"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1576
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.10
Page:  159
Line:  50
CommentType:  TR

Comment:  
ACK feedback can be used to determine if rate or power change is required.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence:  "Additionally, the channel quality can be judged by the presence of ACKs on transmitted frames.  This ACK feedback can be used to determine if rate of transmssion or the power level needs to change."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1575
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.10
Page:  159
Line:  50
CommentType:  E

Comment:  
"to that other DEVs" should be "to the other DEVs."
CommentEnd:  

SuggestedRemedy:  
Change to "to the other DEVs"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  390
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.10
Page:  159
Line:  52
CommentType:  T

Comment:  
The first sentence is redundant and therefore evil since the requirement is in the table.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "All group ... receive these frames."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  392
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.10
Page:  160
Line:  14
CommentType:  T

Comment:  
We should allow the lower rate modes to be used in the CAP for more reliable communications.
CommentEnd:  

SuggestedRemedy:  
Change in 2 places: "In a GTS or MTS: ... the base rate." to be "Any rate supported by both the source and destination."  Second location is at line 20.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  391
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.10
Page:  160
Line:  5
CommentType:  T

Comment:  
Group addressed frames are not supported in the standard.
CommentEnd:  

SuggestedRemedy:  
Change "group addressed" to "broadcast" in table 69.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1581
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.11
Page:  
Line:  
CommentType:  T

Comment:  
"If the decision is made by the PNC to change the channel, the PNC shall keep the piconet quiet by not transmitting any beacon for one or more beacon interval."  The quiet command was eliminatd before pseudo-static GTS slots were introduced.  With pseudo-static GTS a DEV is allowed to transmit even if it does not hear a liminted number of beacons.  The quiet command should be added back.
CommentEnd:  

SuggestedRemedy:  
Add back the quiet command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1579
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.11
Page:  160
Line:  
CommentType:  TR

Comment:  
There is no mention of what happens to repeater service when handover occurs.  Since there is no reasona ble way to know if the new PNC link will be adequate, all repeater service should be dropped when PNC handover occurs.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence: "When PNC handover occurs, all repeater service is discontinued and must be renegotiated with the new PNC."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1580
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.11
Page:  160
Line:  
CommentType:  TR

Comment:  
It is not clear how a DEV or the PNC knows what rate to transmit at when Repeater Service is used.  If the DEV is transmitting to BOTH the DEV and the PNC as is described here, It may choose the lowest rate, even though the link to the PNC may be very clear.  This will waste resources.  Likewaise, the PNC won't get ACKs from the receiving DEV, so it will not be able to monitor the quality of the link from the PNC to the receiving DEV.
CommentEnd:  

SuggestedRemedy:  
Delete repeater service althgether because it will be too complex to implement.  Repeater service should be left to the upper layers to implement.  That way immediate ACK can be used between the devices and the PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  711
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.11
Page:  160
Line:  26
CommentType:  TR

Comment:  
The text in clause 8.11 between lines 28 and 41 leaves out essential functional information required to establish a repeater function among DEV-2, PNC/DEV-1, and DEV-3.
CommentEnd:  

SuggestedRemedy:  
See the repeater function clause in doc 02/037 for a detailed resolution.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  393
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.11
Page:  160
Line:  31
CommentType:  T

Comment:  
The current text does not give the PNC the option of rejecting the repeater service request.
CommentEnd:  

SuggestedRemedy:  
change "The PNC shall" to be "If the PNC wishes to grant the repeater service, it shall" and change "the DEVs.  The sequence" to be "If the PNC does not grant the service it shall send the repeater service reject command, 7.5.6.3, to the DEV with the appropriate result code set."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  847
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  08
Subclause:  8.11
Page:  160
Line:  33
CommentType:  E

Comment:  
wrong figure number
CommentEnd:  

SuggestedRemedy:  
replace 'Figure 8.12' with 'Figure 92'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1159
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.11
Page:  160
Line:  33
CommentType:  TR

Comment:  
Wrong Figure number
CommentEnd:  

SuggestedRemedy:  
Figure 92, not figure 8.12
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  394
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.11
Page:  160
Line:  37
CommentType:  T

Comment:  
It is not specified what the SA and DA of the repeated frames is.  To avoid confusion (e.g. the DEV and the PNC ACKing the same packet), the addressing should go throught the PNC (see resolution).
CommentEnd:  

SuggestedRemedy:  
Change "its frames as before." to be "its frames as before except that the DA of the frames is set to the PNC's address." and change "and repeat them in the time slot" with "and repeat them with the SA set to the PNC's address in the time slot"  Also need to check the impact on 7.5.6.x
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1160
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.11
Page:  160
Line:  45
CommentType:  T

Comment:  
Add clause reference
CommentEnd:  

SuggestedRemedy:  
... repeater service reject command (7.5.6.3) to the PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  395
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.11
Page:  161
Line:  4
CommentType:  T

Comment:  
The current repeater service request commands do not support the establishment of streams.  The DEV needs to request the channel time first and then the repeater service.
CommentEnd:  

SuggestedRemedy:  
Change the MSC in Figure 92 to indicate that the channel time has already been negotiated prior to the repeater service setup.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1161
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.12
Page:  161
Line:  37
CommentType:  E

Comment:  
grammatical ... delete the phrase "in return"
CommentEnd:  

SuggestedRemedy:  
... provide their channel status via the channel status ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  396
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.12
Page:  161
Line:  40
CommentType:  T

Comment:  
The PNC cannot keep the piconet quiet since psuedostatic timeslots still operate even without the beacon.
CommentEnd:  

SuggestedRemedy:  
Change "The PNC shall keep the piconet quiet by not" to "The PNC shall not" on line 40, change "The PNC may change" to "The PNC shall change" on line 41, change "beacon to cancel the quiet state of the piconet." to "beacon." on line 46, change "beacon following the cancellation of quiet state of the piconet." to "beacon."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1163
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.12
Page:  161
Line:  41
CommentType:  E

Comment:  
grammatical ... add an s onto the word interval.
CommentEnd:  

SuggestedRemedy:  
... for one or more beacon intervals.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1162
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.12
Page:  161
Line:  41
CommentType:  T

Comment:  
In the opening line of the paragraph starting at line 41, we are informed of a desire to quiet the piconet.
CommentEnd:  

SuggestedRemedy:  
The scheme to quiet the piconet, by stopping beacons, will not quiet pseudo-static GTS slots.  MAC committee to clarify if this is a problem and modify text if needed.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  28
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.12
Page:  161
Line:  41
CommentType:  T

Comment:  
The dynamic channel selection text does not mention the pseudo-static operation allows a DEV to continue to operate for up to 4 superframes without seeing a beacon. I don't think that this is a problem because the pseudo-static is limited to the peer-to-peer transfer in a CTR or stream setup and does not extend to commands to the PNC.
CommentEnd:  

SuggestedRemedy:  
Make mention that specific DEV to DEV operations are allowed during the quiet time but that no DEV to PNC traffic is allowed
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  710
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.12
Page:  161
Line:  41
CommentType:  TR

Comment:  
The text between lines 41 and 47 describing how the PNC determines the availablity of a more suitable channel is incorrect.
CommentEnd:  

SuggestedRemedy:  
See text in doc 02/037 for details regarding a more reasonable approach to determining the suitability of another channel.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1164
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.12
Page:  161
Line:  42
CommentType:  E

Comment:  
The sentence starting on line 42 to 43 needs to be rewrite, as shown below.
CommentEnd:  

SuggestedRemedy:  
Within that quiet time the PNC may change to one or more other channels to check if one of the other channels are better than the current, after which it returns to the current channel.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1165
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.12
Page:  161
Line:  44
CommentType:  T

Comment:  
add reference to the association response command
CommentEnd:  

SuggestedRemedy:  
... association response command (7.5.2.2), the DEVs ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1166
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.12
Page:  161
Line:  49
CommentType:  T

Comment:  
The sentence on line 49, starting with "The DEVs that ...", indicates a channel switch can take place.
CommentEnd:  

SuggestedRemedy:  
What happens to those devices that are in a power save mode.  Is this going to be a problem for them?  Power management to comment.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1629
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13
Page:  
Line:  
CommentType:  TR

Comment:  
A complex power management solution has been specified, but we need a very simple approach that will be useful for very low power devices that are not.  If the current apprach stays it sould be optional, and we should add a low-complexity solution as an alternative.
CommentEnd:  

SuggestedRemedy:  
I will be proposing a low complexity power management solution.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1585
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13
Page:  162
Line:  
CommentType:  TR

Comment:  
If anything RPS should be a state, not a mode.  No DEV should ever listen to GTS slots that are not assigned to it, so there is no difference between EPS and ACTIVE mode.
CommentEnd:  

SuggestedRemedy:  
Remove all references to EPS mode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  767
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.13
Page:  162
Line:  
CommentType:  TR

Comment:  
General comment: I believe that the power management section is confusing and overly complicated.  While low power consumption is a key goal of 802.15.3, the ability to reliably interoperate using a power save mode is dependent on a clear and consice standard.
CommentEnd:  

SuggestedRemedy:  
Clarity needs to be brought to the text before technical merit can be adequately assessed.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The power management text will be updated based on the minutes, document 01/138r2 and 02/067r1.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1586
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13
Page:  162
Line:  
CommentType:  TR

Comment:  
Remove this sentence "ACTIVE mode devices may use the capabilities defined in RPS mode to provide a modest power reduction."  This only proves that ACTIVE mode and EPS mode are one and the same.
CommentEnd:  

SuggestedRemedy:  
Remove this sentence (along with RPS mode).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1584
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13
Page:  162
Line:  
CommentType:  TR

Comment:  
How is broadcast traffic handled when a device is in EPS mode?  Is the PNC forced to perform repeater service to every DEV that is in EPS
CommentEnd:  

SuggestedRemedy:  
Need to decide how to handle broadcast traffic when devices are in EPS mode since TCP/IP uses broadcast.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  709
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.13
Page:  162
Line:  29
CommentType:  TR

Comment:  
The current power managment clauses 8.13 through8.13.3.12 introduce a level of complexity to make them unsuitable for implementation in a WPAN.
CommentEnd:  

SuggestedRemedy:  
Remove clauses 8.13 through 8.13.3.12.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1168
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13
Page:  162
Line:  29
CommentType:  TR

Comment:  
A general comment about power management.  I can not support power management being mandatory; in other words, power management must be an optional mode ... not only for a DEV but also for a PNC.  A method must be included that allows a piconet to indicate that power management is not supported.  A DEV already has the option to not support power management.  One method to "not support power management" at the PNC level is:  1. In table 67, add a 9th action type value for the EPS action response command, and that is "EPS mode not supported"
CommentEnd:  

SuggestedRemedy:  
Modify table 67 as shown above and then add text to 8.13 at the end of line 31 that says:  In the case where a PNC does not support any power management mode, the EPS action response command "action type value" (Table 67) shall be value 9, "EPS mode not supported".  Those DEVs desiring RPS mode will not get slot assignments friendly to RPS mode of operation.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1173
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13
Page:  162
Line:  29
CommentType:  TR

Comment:  
In general, I can not support a power savings mode where a DEV "must" "pair up" with another DEV in some power savings "master-slave" mode of operation.  A DEV needs to have the option of telling another DEV "I don't want to do a power management mode pairing with you".
CommentEnd:  

SuggestedRemedy:  
I need input from the power management folks and then I'll be happy to generate the required text to indicate how a DEV declines power mode pairing with another DEV.  This text should be added to the introductory clause, 8.13.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  263
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  8.13
Page:  162
Line:  4344
CommentType:  E

Comment:  
The sentence "The table information will be described in sub-clauses of the power management clause." and the text reference to a unique 'power management clause' seems incorrect.  I can not find a clause titled power management, however, I do note that this sentence is in subclause 8.13 Power management.
CommentEnd:  

SuggestedRemedy:  
Correct text reference and possibly add a cross-reference for the reader.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1587
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.1
Page:  162
Line:  51
CommentType:  TR

Comment:  
I asked many hardware designers both at XtremeSpectrum at other companies if the position of the GTS close to the beacon would have any impact at all on power savings.  The answer I got was a unanimous "Any power savings from GTS slot location in the superframe will be negligible."
CommentEnd:  

SuggestedRemedy:  
Delete all of 8.13.1 and 8.13.1.1
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1174
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.1
Page:  162
Line:  51
CommentType:  TR

Comment:  
Reference to CAP without reference to associate MTS
CommentEnd:  

SuggestedRemedy:  
I need some help here from the MAC folks ... in paragraph 8.13.1, we reference an event relative to the CAP (lines 50 and 51).  Should this be rewritten to include the MTS ... for example, replace the two instances of CAP with  CAP --> CAP or associate MTS
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  740
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.13.1
Page:  163
Line:  56
CommentType:  E

Comment:  
SRC and DST are not defined.
CommentEnd:  

SuggestedRemedy:  
Define.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  70
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  08
Subclause:  8.13.1.1
Page:  163
Line:  2830
CommentType:  T

Comment:  
PNC does not negotiate nor allocate bandwidth. Use of bandwidth in this paragraph does not match other parts of the specification.
CommentEnd:  

SuggestedRemedy:  
Replace 'bandwidth' with 'channel time' in this paragraph. Bandwidth occurs twice.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1175
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.1.1
Page:  163
Line:  47
CommentType:  TR

Comment:  
Reference to CAP without reference to associate MTS
CommentEnd:  

SuggestedRemedy:  
I need some help here from the MAC folks ... in paragraph 8.13.2, we reference an event relative to the CAP (line 47).  Should this be rewritten to include the MTS ... for example, replace the instance of CAP with  CAP --> CAP or associate MTS
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  411
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.12
Page:  171
Line:  25
CommentType:  T

Comment:  
The sentence "It is the responsibility ... is to wake." is redundant, adds no new information or requirements and is evil.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1588
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.2
Page:  163
Line:  
CommentType:  TR

Comment:  
Delete all of clauses 8.13.2, 8.13.21.1 and 8.13.2.2.  There is no need to have an RPS mode since it is identical to PM_OFF mode.
CommentEnd:  

SuggestedRemedy:  
Remove all of 8.13.2, 8.13.21.1 and 8.13.2.2.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  264
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  8.13.2.1
Page:  164
Line:  14
CommentType:  E

Comment:  
The term "net" in the sentence "...searching for this net or attempting to locate an empty channel." is jargon.
CommentEnd:  

SuggestedRemedy:  
Change "net" to "piconet".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1176
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.2.1
Page:  164
Line:  14
CommentType:  E

Comment:  
Completely delete the sentence locate between lines 14 and 15.
CommentEnd:  

SuggestedRemedy:  
Delete as shown above.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  397
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.2.1
Page:  164
Line:  14
CommentType:  T

Comment:  
What is changed is not listed here.
CommentEnd:  

SuggestedRemedy:  
Change "Latency to change is" to "Latency to change channel time allocations is"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  398
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.2.2
Page:  164
Line:  20
CommentType:  T

Comment:  
Redundant and therefore icky description of slot positioning.
CommentEnd:  

SuggestedRemedy:  
Delete the text "Slot positioning ... used by RPS and EPS DEVs." (lines 20 through 23).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1177
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.2.2
Page:  164
Line:  23
CommentType:  E

Comment:  
Delete the line contained in line 23, the one that begins as "This is provided ...".
CommentEnd:  

SuggestedRemedy:  
Delete as shown above.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  399
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3
Page:  164
Line:  33
CommentType:  T

Comment:  
The sentence "When DEVs exit EPS mode ... as dictated by the DEV-host." does not add any useful information and does not make sense.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1178
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3
Page:  164
Line:  34
CommentType:  T

Comment:  
Reference to "power resources as dictated by the DEV-host".
CommentEnd:  

SuggestedRemedy:  
I don't understand what this means (see above).  Please clarify the sentence, prehaps with an example.  Assigned to power management folks.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1590
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.1
Page:  164
Line:  
CommentType:  E

Comment:  
"When both initialization and channel time allocation is complete, then clause 8.13.3.5 describes the operations that allow data transfer for EPS DEVs."  Does this mean that clause 8.13.3.5 does not describe anything until both initialisation and channel time allocation is complete?
CommentEnd:  

SuggestedRemedy:  
Change to:  "Clause 8.13.3.5 describes the operations that allow data transfer for EPS DEVs when both initialization and channel time allocation is complete."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1185
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.1
Page:  164
Line:  36
CommentType:  T

Comment:  
We talk about EPS sets ... but this is still vague.  Perhaps a figure should be added to illustrate the concept.  This figure should go into clause 8.13.3.1.
CommentEnd:  

SuggestedRemedy:  
The figure can be generated with help from the Power Management subcommittee
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1188
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.1
Page:  164
Line:  36
CommentType:  T

Comment:  
In clause 8.13.3.3 we see terms such as WAKE beacon and WAKE superframe.  In clause 8.13.3.1 a figure needs to be generated that helps visualize how these beacons & superframes are used in the EPS mode
CommentEnd:  

SuggestedRemedy:  
Help is needed by the power management committee to generate this figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1644
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.1
Page:  164
Line:  39
CommentType:  E

Comment:  
"wake beacon" is discussed without being defined.  It is defined in the definitions, but it needs an introduction in the text
CommentEnd:  

SuggestedRemedy:  
add an introduction to wake beacon
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1645
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.1
Page:  164
Line:  45
CommentType:  TR

Comment:  
EPS mode has states ACITVE and EPS.  ACTIVE is not a mode according to Table 2.  This type of inconsistency makes this clause unreadable.
CommentEnd:  

SuggestedRemedy:  
Be consistent: ACTIVE and EPS are EPS States.  They are not modes.   EPS and PM_OFF ate PowerManagementModes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1589
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.1
Page:  164
Line:  46
CommentType:  TR

Comment:  
"For DEVs configured for EPS mode of operation, specific operation of channel time allocation is necessary for both EPS mode and when EPS DEVs operate in ACTIVE mode."  According to Table 2, ACTIVE is an EPS status not a mode.  Modes are EPS (RPS) and PM_OFF.  Mixing the terminoloogy makes this cluse impossible to read.
CommentEnd:  

SuggestedRemedy:  
Remove all references to "ACTIVE mode" and replace with "ACTIVE state"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1210
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.11
Page:  171
Line:  10
CommentType:  TR

Comment:  
Line 10 indicates that the EPS DEVs recognize an error condition.
CommentEnd:  

SuggestedRemedy:  
How is this done?  Via Table 2 ReasonCode?  The ReasonCodes in Table 2 are not defined.  Refer to Power Management folks.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1211
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.11
Page:  171
Line:  12
CommentType:  T

Comment:  
Reference to a clause
CommentEnd:  

SuggestedRemedy:  
Reference to clause6.3.1 should be 6.3.1.1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1212
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.11
Page:  171
Line:  12
CommentType:  E

Comment:  
add definite article
CommentEnd:  

SuggestedRemedy:  
... defines the recovery operation ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1213
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.11
Page:  171
Line:  12
CommentType:  T

Comment:  
Line 12 refers to a "recovery operation"
CommentEnd:  

SuggestedRemedy:  
Where is this recovery operation described.  Supply reference clause.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  42
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.13.3.11
Page:  171
Line:  13
CommentType:  E

Comment:  
exra "a"
CommentEnd:  

SuggestedRemedy:  
drop extra "a"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1214
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.11
Page:  171
Line:  13
CommentType:  E

Comment:  
remove the word "a"
CommentEnd:  

SuggestedRemedy:  
... recover from an error ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  41
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.13.3.11
Page:  171
Line:  18
CommentType:  T

Comment:  
Should provide clarification on recovery from incorrect beacon.
CommentEnd:  

SuggestedRemedy:  
Add: This may as simple as dealing with a PNC that is checking another channel for better rf conditions. It may also be that the PNC has changed the superframe duration while a DEV was not awake. Procedures outside of EPS power management process are used to recover.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1179
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.2
Page:  164
Line:  53
CommentType:  E

Comment:  
The sentence starting at 53 is very wordy.  It can be improved as shown below.
CommentEnd:  

SuggestedRemedy:  
EPS devices operate either in an ACTIVE mode, where the EPS DEV is receiving each superframe, or in an EPS mode, where the EPS DEV receives information at a very much reduced rate.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1646
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.2
Page:  164
Line:  54
CommentType:  E

Comment:  
change ACTIVE mode to ACTIVE state.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  40
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.13.3.2
Page:  164
Line:  54
CommentType:  E

Comment:  
channel time allocation command rather than channel time request.
CommentEnd:  

SuggestedRemedy:  
change allocation to request
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  400
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.2
Page:  165
Line:  11
CommentType:  T

Comment:  
The formal definition here is redundant and therefore evil.
CommentEnd:  

SuggestedRemedy:  
Change "operation shall use the" to "operation uses the"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1647
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.2
Page:  165
Line:  12
CommentType:  E

Comment:  
change EPS mode to EPS state.
CommentEnd:  

SuggestedRemedy:  
Do a globeal change to be consistent what is EPS mode, and what is EPS state.   Be consistent: ACTIVE and EPS are EPS States.  They are not modes.   EPS and PM_OFF ate PowerManagementModes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1180
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.2
Page:  165
Line:  2
CommentType:  E

Comment:  
Delete the line contained in line 2 and replace with alternate text
CommentEnd:  

SuggestedRemedy:  
Delete the line starting with "There are three ..." and replace with "Three illustrative usage scenarios are:"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1631
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.2
Page:  165
Line:  4
CommentType:  TR

Comment:  
If the ACTIVE bandwidth needs to be reserved for these EPS devices, why complicate the protocol by adding these mechansisms?  Just allocate the channel time, and let the DEVs not use it until they need it.
CommentEnd:  

SuggestedRemedy:  
Simplyfy power management by just allocating the needed channel time and then letting the DEVs not use it if response time is absolutely critical.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1182
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.2
Page:  165
Line:  4
CommentType:  E

Comment:  
In the three paragraphs between lines 4 and 16, delete the following sentences:
CommentEnd:  

SuggestedRemedy:  
At line 6, delete the sentence beginning with "Both the transmitting ..."  At line 10, delete the sentence beginning with "This doesn't suggest ..."  At line 14, delete the sentence beginning with "This uses the EPS ..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1181
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.2
Page:  165
Line:  4
CommentType:  E

Comment:  
Enumerate the three parameters contained between lines 4 and 15 as shown below
CommentEnd:  

SuggestedRemedy:  
1. The first is a scenario where ...  2. A Second requirement is an application ...  3. A third application is for a persistent ...  (note: include the nurmeric bullets)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1634
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  
Line:  
CommentType:  E

Comment:  
This could be better written: "Once configuration as defined in this clause, and presented in Figure 94, Illustration of EPS control process is complete, DEVs shall..."
CommentEnd:  

SuggestedRemedy:  
"Once configuration of the EPS control process is complete, as defined in this clause and presented in Figure 94, DEVs shall...  "
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1632
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  
Line:  
CommentType:  TR

Comment:  
I don't see anything in Annex B about how the EPS-Hosts provide anything through the MLME interface.
CommentEnd:  

SuggestedRemedy:  
Fix this or remove this statement.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1183
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  20
CommentType:  E

Comment:  
Delete the sentence starting in line 20 as "The information in this ..."
CommentEnd:  

SuggestedRemedy:  
see above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1630
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  20
CommentType:  TR

Comment:  
"The information in this primaiive"  does not agree with the previous sentence which was taling about primitives.
CommentEnd:  

SuggestedRemedy:  
change to "The information in these primaiives"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1184
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  23
CommentType:  T

Comment:  
For the paragraph contained between lines 23 and 26, rewrite as shown below.
CommentEnd:  

SuggestedRemedy:  
DEVs, operating as EPS "sets", determine the basic operating EPS parameters at a peer-to-peer level and configure the PNC so that it provides the necessary tinekeeping operations.  Annex B provides informative text on how EPS-hosts provide setup information through the MLME interface.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  754
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  25
CommentType:  TR

Comment:  
What is an EPS set?  How is it defined? When does it come into existance: when the Dev makes or send the PNC configuration operations or when the PMC established the basic timekeeping operations?
CommentEnd:  

SuggestedRemedy:  
Clarify
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. The power management section is being re-written, the EPS set text will be based on 02/067r1.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1186
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  28
CommentType:  E

Comment:  
delete the phrase "the occurrence"
CommentEnd:  

SuggestedRemedy:  
... time base for periodic EPS time slots.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1187
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  34
CommentType:  T

Comment:  
grammatical ... incomplete command name
CommentEnd:  

SuggestedRemedy:  
in line 34 ...  ... using the EPS Action request command ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1633
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  35
CommentType:  TR

Comment:  
The beacon count of the next awake beacon for every member of the EPS set will not be synchronized.  By the time the requestor gets the information, the Beacon pointed to may already have passed.  The requesting DEV will think that it has to wait for 2^16 cycles of the beacon counter.
CommentEnd:  

SuggestedRemedy:  
Find a way to eliminate the need to use a frame request that ties to real time data like a beacon number.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1189
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  39
CommentType:  T

Comment:  
The paragraph between line 39 to 47 needs to be rewritten.  A suggestion is shown below.
CommentEnd:  

SuggestedRemedy:  
Figure 94 is an illustration of the EPS control process.  THe EPS action request command (7.5.7.1), and EPS action response (7.5.7.2), initiate the configuration process.  THe EPS action request command parameters are EPS set, EPSTime and EPSNExt.  A DEV which wants to form an EPS set shall issue the EPS action request command using the EPS set parameter to request a new set and provide the parameters of EPSTime and EPSNext.  The EPS action response command from the PNC shall provide an EPS set value that is not in use.  Following this exchange, additional EPS set members may request and receive acknowledgement that they have joined the EPS set.  This is followed by use of the DEV to PNC PS infomration command (7.5.7.3) to provide the parameters PowerManagementMode and PowerManagementPriority to the PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  401
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  40
CommentType:  T

Comment:  
The sentence "The EPS action command ... and EPSNext parameters." is redundant an therefore really annoying.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  402
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  48
CommentType:  T

Comment:  
DEVs should be able to enter EPS mode when they finish configuration and should not have to wait for a command.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "Once configuration ... further commands."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  752
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  49
CommentType:  E

Comment:  
Not clear
CommentEnd:  

SuggestedRemedy:  
Change 'configuration' to 'configured' change 'process' to 'process,'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1190
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  49
CommentType:  E

Comment:  
Modify the sentence between lines 49 to 53.
CommentEnd:  

SuggestedRemedy:  
Once the configuration process is complete, DEVs shall remain in the ACTIVE mode awaiting further commands.  A single DEV may select EPS mode as described in 8.13.3.6.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1635
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  50
CommentType:  TR

Comment:  
"awaiting further commands."  Are they waiting for command frames or for MLME.requests from the DME?
CommentEnd:  

SuggestedRemedy:  
Clarify  what type of commands they are waiting for.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1636
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  5153
CommentType:  TR

Comment:  
It is not clear that the lone DEV creates and uses its own EPSSet.
CommentEnd:  

SuggestedRemedy:  
Clarify if a lone DEV creates it's own EPSSet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1637
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  5153
CommentType:  TR

Comment:  
If a DEV goes into it's own EPSSet, how doesn anyone else ever communicate with it?  Do they have to request a GTS to put them into AWAKE state so they can interroget them? What happens if a broadcast message like an ARP comes in?  Doe EPS DEVs ignore broadcast?
CommentEnd:  

SuggestedRemedy:  
Need to explain how another DEV communicates with a Solo EPS dev.  Does it as for a CTA to each Solo EPS DEV?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  265
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  8.13.3.3
Page:  165
Line:  53
CommentType:  E

Comment:  
The following sentence does not end in a period: information command, it may select EPS mode as described in 8.13.3.6
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1191
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  166
Line:  1
CommentType:  T

Comment:  
The text between lines 1 to 9 need to be rewritten.  Suggest text is shown below.
CommentEnd:  

SuggestedRemedy:  
EPS configuration between DEVs occurs following association as required by changing requirements. DEVs requiring a change in EPS operation that will change EPSTime and EPSNext shall return to ACTIVE mode during the renegotiation operation.  An EPS action request command requesting EPS set termination shall be issued by the last DEV in an EPS set using the parameters EPSTime and EPSNext.  A DEV requiring EPSTime and EPSNext information for a specific EPS set may use the EPS action request commmand.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1649
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  166
Line:  13
CommentType:  T

Comment:  
Is renegotiation N-way, if there are N DEVs in the EPS set?  N way negotiation will be very complex.
CommentEnd:  

SuggestedRemedy:  
Describe if this is just peer to peer negotiation, N way negotiation with the N DEVs in the EPS set.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  753
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.13.3.3
Page:  166
Line:  3
CommentType:  T

Comment:  
This speaks of 'during the renegotation operation'.  I find the negotation in Annex B (informative).  The negotation should be in the main text..  Confusing.
CommentEnd:  

SuggestedRemedy:  
Clarify
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1650
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.3
Page:  166
Line:  56
CommentType:  T

Comment:  
"An EPS action command requesting release shall be used by the last DEV in an EPS set to remove the EPS set time keeping of EPSTime and EPSNext from PNC activities."  I am not quite sure what this is trying to say.
CommentEnd:  

SuggestedRemedy:  
Here is my attempt to simplify:  An EPS action command requesting release shall be used by the last DEV in an EPS set.  The free the PNC from the EPS set time keeping of EPSTime and EPSNext.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  32
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.13.3.4
Page:  166
Line:  45
CommentType:  T

Comment:  
Much of the EPS operation is predicated on CTR operation to establish EPS and ACTIVE channel times that are keep in "memory" by the PNC. What is lacking is a relationship to the stream operation in the standard. The stream command does not have the same parameters as the CTR.
CommentEnd:  

SuggestedRemedy:  
Update the stream command in clause 7 and clause 6 primitives to provide a match between the stream operations and CTR.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1193
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  166
Line:  51
CommentType:  E

Comment:  
Rewrite the paragraph between lines 51 to line 2 on page 167.
CommentEnd:  

SuggestedRemedy:  
A DEV shall be a member of at least one EPS set prior to the creation of the EPS CTA.  A DEV, which is a member of an EPS set, may issue an EPS CTR indicating the number of the EPS set to which it belongs.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1652
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  166
Line:  5152
CommentType:  E

Comment:  
"by the PNC" doesn't add any value.  All Beacons are from the PNC.
CommentEnd:  

SuggestedRemedy:  
Eliminate "by the beacon" from both line 51 and 52
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1196
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  10
CommentType:  E

Comment:  
Rewrite the sentence that starts with "If instead, the value of N ..."
CommentEnd:  

SuggestedRemedy:  
Suggest the following ...  "Likewise, if the value of N is 4 then 1 EPS ..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1197
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  15
CommentType:  E

Comment:  
Rewrite as shown below ...
CommentEnd:  

SuggestedRemedy:  
... or null CTA identifies that the EPS DEV shall listen to this beacon and that ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1198
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  18
CommentType:  E

Comment:  
Replace word "After" with the word "If"
CommentEnd:  

SuggestedRemedy:  
see above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1199
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  21
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
at the end of line 21, rewrite as shown ...  ... a member of the specified EPS set,
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1200
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  23
CommentType:  E

Comment:  
rewrite fragment as shown below ...
CommentEnd:  

SuggestedRemedy:  
... containing the reject code indicating "not a member of the requested EPS set" as shown in clause 7.5.10.3.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1642
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  6
CommentType:  E

Comment:  
"The size of teh EPS time slots used for data" - what does "used for data add to this sentence?  Id there part of the EPS time slot that is not used for data?
CommentEnd:  

SuggestedRemedy:  
Change to "The size of the EPS time slots"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  267
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  6
CommentType:  E

Comment:  
The following sentence does not end in a period: 1) The size of the EPS time slots used for data
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1592
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  7
CommentType:  T

Comment:  
I am not sure what this is supposed to mean: "The value of N such that a proportion 1:N of EPS time slots that will be of that length."
CommentEnd:  

SuggestedRemedy:  
Reword so that it is readable: "The value of N specifies the fraction of EPS time slots (1/N) that will be of that length."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1194
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  7
CommentType:  T

Comment:  
On bullet number 2 ... what is meant bu N such that a proportion 1:N?
CommentEnd:  

SuggestedRemedy:  
Power management to clarify and rewrite this sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1195
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.4
Page:  167
Line:  9
CommentType:  E

Comment:  
Rewrite the sentence that begins with "If the value of N ..."
CommentEnd:  

SuggestedRemedy:  
Replace with ...  "For example, if the value of N ..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1655
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.5
Page:  
Line:  
CommentType:  T

Comment:  
"If a DEV does not have an ACTIVE or EPS slot in a particular superframe,"  Does this mean a slot where it is the source or destination, or only where it is the source.
CommentEnd:  

SuggestedRemedy:  
Please clarify.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1203
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.5
Page:  168
Line:  15
CommentType:  E

Comment:  
add a definite article
CommentEnd:  

SuggestedRemedy:  
... CTA blocks that have the time-beacon ....
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1204
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.5
Page:  168
Line:  17
CommentType:  E

Comment:  
modify sentence as shown below
CommentEnd:  

SuggestedRemedy:  
in line 17 ==> ... EPS mode, the EPS set ...  in line 18 ==> ... create the EPS CTSs and time slots ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  404
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.5
Page:  168
Line:  24
CommentType:  T

Comment:  
DEV-A should not be able to switch DEV-B to sleep mode.  Instead the PNC should only switch DEV-A/DEV-B slots to EPS sleep, not all of DEV-B's slots.
CommentEnd:  

SuggestedRemedy:  
Change the text to indicate that only the DEV-A/DEV-B slots are put into EPS sleep mode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  403
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.5
Page:  168
Line:  3
CommentType:  T

Comment:  
The sentence "The PNC shall create ... their slot time." is redundant, evil and adds no new information.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence, the PNC is already required to do this.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1205
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.5
Page:  168
Line:  33
CommentType:  E

Comment:  
add a definite article
CommentEnd:  

SuggestedRemedy:  
... DEV by sending it in the superframe
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  405
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.5
Page:  168
Line:  34
CommentType:  T

Comment:  
The PNC should not be required to create the EPS CTA if the piconet is too busy.
CommentEnd:  

SuggestedRemedy:  
Change "The PNC shall create" to be "If the channel time is available, the PNC shall create"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1202
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.5
Page:  168
Line:  8
CommentType:  E

Comment:  
add a comma
CommentEnd:  

SuggestedRemedy:  
after the word "network", place a comma ...  ... member of the network, that has missed ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  406
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.7
Page:  170
Line:  18
CommentType:  T

Comment:  
The paragraph "The MLME-POWERMGT.request ... to its DEV-host." describes layer managment operation and does not belong here.  It is also redundant and nasty.
CommentEnd:  

SuggestedRemedy:  
Delete the paragraph.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1208
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.8
Page:  170
Line:  36
CommentType:  T

Comment:  
In clause 8.13.3.8 new terminology is used to describe combinations of EPS DEV; that is, master and slave.  This concept needs to be introduced in clause 8.13.3.1 with prehaps a figure.
CommentEnd:  

SuggestedRemedy:  
Power Management committee to provide introductory figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  407
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.8
Page:  170
Line:  36
CommentType:  T

Comment:  
Master and slave are not defined in this context and the sentence does not add useful information.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "Likely combinations ... and is an EPS DEV."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  408
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.9
Page:  170
Line:  43
CommentType:  T

Comment:  
Multicast is not supported in this standard.
CommentEnd:  

SuggestedRemedy:  
Change "piconet wide multicast and broadcast to" to be "broadcast frames to"
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  1209
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.13.3.9
Page:  170
Line:  44
CommentType:  T

Comment:  
In line 170, reference is made that the "PNC shall save these for the next superframe".
CommentEnd:  

SuggestedRemedy:  
Does this mean these have to be buffered by the PNC?  Refer to the power management folks.  How is the size limit of this buffer specified?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  409
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.9
Page:  170
Line:  46
CommentType:  T

Comment:  
The sentence "The EPS DEV shall interpret ... directed to it." is redundant and annoying.  This is already required of all DEVs.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  410
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.13.3.9
Page:  170
Line:  48
CommentType:  T

Comment:  
A formal requirement is listed without listing all of the required activity.
CommentEnd:  

SuggestedRemedy:  
Change the sentence to read "if network wide ... from the PNC." to be "if the DEV receives a channel change indication or PNC handover command from the PNC."  List any more commands that would require this action.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1595
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.14
Page:  171
Line:  32
CommentType:  TR

Comment:  
fixed maximum power applies to the CAP, and to shared and association MTSs.
CommentEnd:  

SuggestedRemedy:  
Change to: "systems, a fixed maximum power in the CAP and shared and association MTSs, and adjustable power in the GTS."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1597
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.14.1
Page:  171
Line:  37
CommentType:  E

Comment:  
Title should be "Fixed maximum transmitter power for CAP and beacon and Shared MTSs"
CommentEnd:  

SuggestedRemedy:  
Change title to "Fixed maximum transmitter power for CAP and beacon and Shared MTSs"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1596
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.14.2
Page:  171
Line:  49
CommentType:  E

Comment:  
"Communicating with the GTS" should be "communicating within the GTS."
CommentEnd:  

SuggestedRemedy:  
Change "Communicating with the GTS" should be "communicating within the GTS."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1598
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.14.2
Page:  172
Line:  1
CommentType:  T

Comment:  
the chosen power level should be the closest on that is greater than the requested one.
CommentEnd:  

SuggestedRemedy:  
Change to "change is not supported by the other DEV, it shall use the closest implemented TX power level that is greater than the requested level provided that is within the allowable range."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1599
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.14.2
Page:  172
Line:  6
CommentType:  TR

Comment:  
This exxample fails to point out that rate and power level are related.  If the power level is significantly higher than required, the first thing that should happen is that the receiver should ask the transmitter to tranmit at a higher rate to conserve resources.
CommentEnd:  

SuggestedRemedy:  
In this example, point out that the transmitting DEV is already transmitting at the highest PHY rate supported by both DEVs before reduucing power.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1215
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.15
Page:  172
Line:  20
CommentType:  T

Comment:  
provide explicit reference to the tables.
CommentEnd:  

SuggestedRemedy:  
A list of the rules are specified in Tables 71 and 72.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  24
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.15
Page:  172
Line:  20
CommentType:  E

Comment:  
A specific reference to tables 71 and 72 should be included. Although the text refers to tables below, table 72 has floated to a point after the next section (8.16) and the "tables below" could refer to table 73 as well.
CommentEnd:  

SuggestedRemedy:  
change "tables below" to "tables 71 and 72"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  412
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.15
Page:  172
Line:  30
CommentType:  T

Comment:  
Association response has no ACK.
CommentEnd:  

SuggestedRemedy:  
Delete the reference to the ACK and change the number of frames to be 1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  413
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.15
Page:  172
Line:  36
CommentType:  T

Comment:  
Group addressed frames are not supported in this standard.
CommentEnd:  

SuggestedRemedy:  
Change "Group addressed" to be "Broadcast" in figures 71 and 72
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1216
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.16
Page:  173
Line:  26
CommentType:  E

Comment:  
Put a page break after Table 72
CommentEnd:  

SuggestedRemedy:  
Keep Table 73 all on the same page.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  414
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.16
Page:  173
Line:  46
CommentType:  T

Comment:  
The aProbeResonseDelay is too short, a DEV should have at least 1 superframe to respond.
CommentEnd:  

SuggestedRemedy:  
Change 8 ms to be aMaxSuperframeDuration.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  415
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.16
Page:  173
Line:  48
CommentType:  T

Comment:  
aFragThreshold is not a constant and should be defined earlier in 8 as indicated in another comment.
CommentEnd:  

SuggestedRemedy:  
Delete the constant.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  416
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.16
Page:  174
Line:  8
CommentType:  T

Comment:  
aBroadcastDEVInfoDuration is repeated twice, use first definition.
CommentEnd:  

SuggestedRemedy:  
Delete the definition on line 8, page 174.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  37
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.2
Page:  137
Line:  44
CommentType:  TR

Comment:  
It is not clear as to the optionality of a DEV to not offer PNC services. It is not acceptable for the standard to effectively allow DEVs to not support PNC roles. There must be a provision to allow certain classes of DEVs the opportunity to be free of PNC burden base on their requirement for low complexity. However, specific language and a SHALL statement would require that a PNC-less character must be matched by having a partner in an application that SHALL provide PNC capability.
CommentEnd:  

SuggestedRemedy:  
Add in 8.2 as a distinct subclause: Responsibility to assure that a piconet may be formed. -- Classes of simple devices may be implemented without providing support for PNC role in a piconet. These classes are permitted if the device is required to be used in conjuntion with a device that shall support PNC opertion.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add in 8.2 a distinct subclause. Non-PNC Capable Devices.  Simple devices may be implemented without providing support for PNC role in a piconet. The implication of this is that is possible for these devices to be unable to form a piconet by themselves. Therefore, these devices would be a type that are normally use in conjunction with a device that provides PNC capability. An example of this would be wireless speakers expected to be used with a receiver.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  724
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.2.1
Page:  137
Line:  50
CommentType:  TR

Comment:  
Text between lines 50 and 54 of page 137 and lines 1 and 22 of page 138 describing the scanning and piconet startup process is broken.
CommentEnd:  

SuggestedRemedy:  
The scanning clause and the Start Piconet clause of doc 02/037 describes in detail the resolution to this problem.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1522
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.1
Page:  137
Line:  51
CommentType:  TR

Comment:  
DEVs use passive scan to detect an active piconet, but they COULD also use passive scan to detect interferers like 802.11.  This would help coexistence.
CommentEnd:  

SuggestedRemedy:  
Add the mechanism to scan for interference as well as just scanning for piconets.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The proposed informative Annex (00000r0P802-15-3-Annex_Coexistence.pdf) has a description of the coexistence methods that are available in the draft. Also see 02/041r2 for a presentation and additional text on this issue. For 802.15.4 compatibility see subclause 6.9 in 00000D13P802-15-4__Draft_Standard.pdf.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1102
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.1
Page:  138
Line:  13
CommentType:  T

Comment:  
add some words to exclude open scan mode ... as shown below
CommentEnd:  

SuggestedRemedy:  
While searching, and not in open scan mode, if the DEV receives ...  (the reason is we need to prevent our equipment from joining the neighbors piconet)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1523
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.1
Page:  138
Line:  17
CommentType:  E

Comment:  
PNID is should be are (frames are)
CommentEnd:  

SuggestedRemedy:  
change is to are
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  29
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.2.1
Page:  138
Line:  19
CommentType:  E

Comment:  
A clarification that the a new piconet should be started in a vacant channel rather than an occupied.  Although, it would seem that some tie in to child piconet should also be mentioned
CommentEnd:  

SuggestedRemedy:  
add the word "vacant" between "choose a" and "channel"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  30
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.2.1
Page:  138
Line:  7
CommentType:  TR

Comment:  
The text that relates to staying on the channel of a desired PNID should be changed. The idea that a random number would be of interest is hard to grasp. The text should omit the PNID reference.  Also, and this is the TR reason, there is no clear guidance on how to "really" decide what channel is the correct one. Maybe I missed it!
CommentEnd:  

SuggestedRemedy:  
Change the text to read: ... received, the searching DEV ....  next: add text either at this point in clause 8 or elsewhere that provides some guidance on how a DEV might determine what piconet to join.
RemedyEnd:  

Response:  
PROPOSED REJECT. Delete "with the desired PNID" line 7, page 138. Without a clear proposed solution, the committee cannot determine how to accept the full comment.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  U
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1524
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.2
Page:  138
Line:  27
CommentType:  TR

Comment:  
Piconet randomization does not address if the PNID is the same each time the piconet starts, or if it chooses a different random PNID each time.
CommentEnd:  

SuggestedRemedy:  
Clarify if each PNC calculates the same random number each time they generate a PNID, or if it is different each time.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1675
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.2
Page:  138
Line:  2728
CommentType:  E

Comment:  
If we are not specifying randomization, we should not have a shall in the section.
CommentEnd:  

SuggestedRemedy:  
The section should read "The seed for generating a randomized PNID should include the 48-bit PNC device ID in order to aid in the likelihood of a unique PNID, however the randomization process required to choose a unique PNID is beyond the scope of this standard."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1572
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.2
Page:  145
Line:  40
CommentType:  E

Comment:  
Should point out that the PNC broadcasts the device information table after association.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence:  "After Association is complete, the PNC broadcasts an update of the device information table as described in 8.2.7."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1526
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.3
Page:  138
Line:  
CommentType:  TR

Comment:  
Why bother with PNC selection at all?  Now that we can do handover if a better PNC shows up, Just wait a random time and start sending out beacons.  This would be a much simpler process.  Also, the odds of turning on a bunch  of machines all at the exact time is small
CommentEnd:  

SuggestedRemedy:  
Eliminate PNC selection and simplify by just waiting a reandom amount of time then start sending out beacons.  Then, handover if more qualified PNC.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  723
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.2.3
Page:  138
Line:  30
CommentType:  TR

Comment:  
The PNC selection process described between lines 32 and 38 on p138, lines 26 and 33 of page 139, and lines 1 and 11 of page 140 is inefficient and broken.
CommentEnd:  

SuggestedRemedy:  
the PNC challenge and handover clause in doc 02/037r0 contains detailed text describing a more efficient approach.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  36
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.2.3
Page:  138
Line:  30
CommentType:  E

Comment:  
We need to reference where the fields are defined. aCSFrameRepeat and aCSFrameBroadcast
CommentEnd:  

SuggestedRemedy:  
add the xrefs
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  38
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.2.3
Page:  138
Line:  30
CommentType:  TR

Comment:  
At least one of the table 68 entries, designated mode bit, seems to require more than a two-state value. As I understand it, an AC with the Des-mode set is the winner, but more than a single device type may believe that it qualifies to be the Designated PNC. I clearly believe that a video distribution AC such as a settop box with the implication of great demands on the piconet should be the highest priority. Below that would be other important devices such as cablemodem/DSL internet distribution device.
CommentEnd:  

SuggestedRemedy:  
Make the Des-mode be a two-bit field and set guidelines on the classes of device for at least three of the values.
RemedyEnd:  

Response:  
PROPOSED REJECT. The DesMode can be changed under user control to determine which one will be the PNC.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  297
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.2.3
Page:  138
Line:  32
CommentType:  T

Comment:  
The PNC selection process does not define a channel access method for the ACs that are broadcasting their messages.
CommentEnd:  

SuggestedRemedy:  
Change the text in 8.2.3 to require the ACs to use the backoff procedure defined in 8.4.2.1 for channel access during the PNC selection process.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  842
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  08
Subclause:  8.2.3
Page:  138
Line:  3234
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'PNC selection command' with 'PNC announcement command'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1525
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.3
Page:  138
Line:  35
CommentType:  E

Comment:  
Should clarify that aCSFrameRepeat is an integer.
CommentEnd:  

SuggestedRemedy:  
change from "command for at least aSCFrameRepeat" to "command at least aCSFrameRepeat times"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  769
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.2.3
Page:  139
Line:  
CommentType:  E

Comment:  
It is difficult to understand that the following sentence A is described after the sentense B. A: Indicated coordinator-announcement timeout B: First Beacon transmission time after the indicated timeout The figure seems correct but 3 kinds of "timeout" including "Indicated Timeout", "Indicated new TImeout" and "Indicated coordinator-announcement Timeout" confuse the situation.
CommentEnd:  

SuggestedRemedy:  
Clarify the description as well as replace "coordinator" to "PNC".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  363
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.2.3
Page:  139
Line:  31
CommentType:  T

Comment:  
Informal language use for required action.
CommentEnd:  

SuggestedRemedy:  
Change "selection command and wait for the piconet" to "selection conmmand and shall wait for the piconet"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  728
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.2.3
Page:  139
Line:  7
CommentType:  E

Comment:  
In the first column, the word 'alternate' is misspelled.
CommentEnd:  

SuggestedRemedy:  
correct.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1529
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  
Line:  
CommentType:  TR

Comment:  
What happens if the PNC wants to shut down, but there is no other alternate PNC available.  Does the PNC just go away?
CommentEnd:  

SuggestedRemedy:  
Add a PNC shutdown command or IE in the beacon to inform the piconet the at the PNC is shutting down.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1527
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  15
CommentType:  E

Comment:  
"If during the life of a piconet the PNC decides to leave the piconet," should say "If during the life of a piconet the PNC decides to leave the piconet or a more capa ble PNC joins the piconet,"
CommentEnd:  

SuggestedRemedy:  
"If during the life of a piconet the PNC decides to leave the piconet or a more capa ble PNC joins the piconet,"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1105
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  17
CommentType:  TR

Comment:  
line 17 (going into line 18) refers to a table in clause 7.5.8.  There is no table in clause 7.5.8.
CommentEnd:  

SuggestedRemedy:  
MAC folks ... where is this table?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1123
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  20
CommentType:  T

Comment:  
line 20 refers to aMinHandOvrTO
CommentEnd:  

SuggestedRemedy:  
I don't understand why we need a aMinHandOvrTO ... have MAC folks verify it is needed.  If not then delete.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1124
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  21
CommentType:  T

Comment:  
In line 21 we have a parameter aMaxHandOvrTO
CommentEnd:  

SuggestedRemedy:  
Question is what happens if aMaxHandOverTO occurs.  Refer to the clause in the text where the next action is indicated after a time out.  MAC folks.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  734
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  24
CommentType:  T

Comment:  
As stream transmission need not be inturrpted during coordinator handover, it would be useful to add that the PNID remains the same.
CommentEnd:  

SuggestedRemedy:  
insert text ', using the original PNID,' between the words 'beacon at'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  364
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  26
CommentType:  T

Comment:  
Need clarification of when the new PNC begins using the PNC address.
CommentEnd:  

SuggestedRemedy:  
Change "The new PNC shall begin using address of 0x00 for all" to be "Following its first beacon, the new PNC shall use the PNC address, 7.2.3, for all"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  755
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  28
CommentType:  TR

Comment:  
Says that reassociation is not required (after successful PNC handover).  However, 10.3.3.3 (page 184) says that after PNC handover 'each device shall authenticate'. Authentication comes before association, therefore reassociation is required. Note: contridiction.
CommentEnd:  

SuggestedRemedy:  
Fix
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  1/24/2002
VoterStatus: 

-----------
CommentID:  1125
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  140
Line:  29
CommentType:  TR

Comment:  
On a coordinator handover, do all the authentication certificates also transfer or does each DEV need to re-authenticate?
CommentEnd:  

SuggestedRemedy:  
Add text after line 29 to clarify.  Security folks.    (BTW - I hope all the certificates transfer).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1530
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  
CommentType:  TR

Comment:  
What happens when two piconets wander withing range of each other?  They will not know that the other PNC is there.
CommentEnd:  

SuggestedRemedy:  
Need to have the PNCs do a periodic scann to look for traffic from other piconets including beacons in their channel.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1528
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  
CommentType:  TR

Comment:  
What happens to repeater treaffic when a handover takes place?  Is it all dropped?
CommentEnd:  

SuggestedRemedy:  
All repeater traffic should be dropped and renegotiated whan a PNC handover takes place.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  783
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  10
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1127
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  10
CommentType:  TR

Comment:  
The paragraph starting at line 10 and ending at line 17 is not consistent.  The first two lines of this paragraph set down conditions under which a PNC SHALL handover control.  But then in the last sentence, we have this "re-authentication issue" that says a PNC running security, under some conditions,  "should not" perform a PNC handover.  Can't have it both ways folks ... need to fix this paragraph.
CommentEnd:  

SuggestedRemedy:  
Refer to Security/MAC committees for resolution.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  784
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  12
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1128
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  13
CommentType:  TR

Comment:  
Wrong table reference.
CommentEnd:  

SuggestedRemedy:  
Should be Table 68, NOT table 79.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  843
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  7
CommentType:  E

Comment:  
There is no DEV information table in 7.5.1.4
CommentEnd:  

SuggestedRemedy:  
Correct reference
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1126
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.4
Page:  141
Line:  7
CommentType:  TR

Comment:  
Line 7 refers to a "DEV information table" in clause 7.5.1.4
CommentEnd:  

SuggestedRemedy:  
Clause 7.5.1.4 does not contain any tables.  Where is the table located?  Assign to MAC subcommittee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  779
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.2.5
Page:  141
Line:  21
CommentType:  E

Comment:  
There are 2 descriptions of "alternative coordinator". They should be AC.
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1350
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  08
Subclause:  8.2.5
Page:  141
Line:  21
CommentType:  E

Comment:  
Term AC not correct.
CommentEnd:  

SuggestedRemedy:  
The term AC should be changed to child piconet PNC or child PNC for all instances.  If this is confusing, then the term child piconet representative might be considerd.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  365
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.2.5
Page:  142
Line:  11
CommentType:  T

Comment:  
The directed frame with Private GTS is optional and should be noted as such in Figure 81.
CommentEnd:  

SuggestedRemedy:  
Add the word "Optional" to "Directed frame with Private GTS".  Also, change the direction of the child beacon, it is not sent to the Parent PNC.  Add to the paragraph ending "its capabilities and security policy." the following:  "If the PNC allocates the private GTS, it may also send a directed channel time grant to the child PNC to confirm the allocation."  Make the same changes with Figure 82.  On page 142, 8.4.2, line 46, change "destination addresses.  After receiving" to be "destination addresss.  The PNC may also send a directed channel time grant to the neighbor PNC to confirm the allocation.  After receiving"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  780
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.2.6
Page:  142
Line:  30
CommentType:  E

Comment:  
neighbor alternate coordinator should be neighbor AC.
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  739
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  08
Subclause:  8.2.6
Page:  142
Line:  32
CommentType:  E

Comment:  
Clarify wording.
CommentEnd:  

SuggestedRemedy:  
Insert 'new client' before 'association address...'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1129
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.6
Page:  142
Line:  33
CommentType:  T

Comment:  
It will help to clarify by adding the actual address
CommentEnd:  

SuggestedRemedy:  
association address (0xFE), 7.2.3, as the ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1130
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.6
Page:  142
Line:  39
CommentType:  T

Comment:  
In the line straddling line number 39, we are instructed what the PNC is to do if the request is not accepted.
CommentEnd:  

SuggestedRemedy:  
MAC folks ... add a sentence to indicate what the neighbor is suppose to if the request is not accepted.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1532
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.6
Page:  143
Line:  
CommentType:  T

Comment:  
In a neighbor piconet, hwo does the parent decide how much time to allocate to the neighbor?  Does it have to allocat any?
CommentEnd:  

SuggestedRemedy:  
Need to figure out a policy for allocation bandwidth to neighbor piconets and how to enforce the rules.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  844
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  08
Subclause:  8.2.6
Page:  143
Line:  21
CommentType:  E

Comment:  
wrong text in Figure 82
CommentEnd:  

SuggestedRemedy:  
replace 'Child' by 'Neighbor'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  258
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  8.2.6
Page:  143
Line:  4
CommentType:  E

Comment:  
The xref field in FrameMaker has the 'Figure n' in the field but the Editor has also typed "figure" i.e., "...shown in figure Figure 82."
CommentEnd:  

SuggestedRemedy:  
Either delete the first occurence or edit the FrameMaker field, thus requiring a Clause 8 global edit on the paragraph tag for figure cross-reference formats.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  720
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.2.7
Page:  143
Line:  34
CommentType:  T

Comment:  
The title of this clause is incorrect.
CommentEnd:  

SuggestedRemedy:  
Please change to Broadcasting PNC information.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1574
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.2.7
Page:  143
Line:  41
CommentType:  TR

Comment:  
The PNC should wait until after the authentication if authentication is required for the piconet.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence: "If autentication is required for the piconet, the PNC shall wait until after authentication is complete to broadcast the device information table.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1131
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.3.1
Page:  143
Line:  46
CommentType:  TR

Comment:  
There is no point in having a reference to authentication in clause 8.3 that simply says "go see clause 10".
CommentEnd:  

SuggestedRemedy:  
Please remove the words "and authentication" from the 8.3 clause heading and completely delete clause 8.3.1.  Add the appropriate clause to the security section; that is, in clause 10.0
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1534
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.3.1
Page:  143
Line:  48
CommentType:  E

Comment:  
Authentication clause should follow association (and probably disassociation).
CommentEnd:  

SuggestedRemedy:  
Move authentication claust to after association and disassociation.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  786
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  
CommentType:  E

Comment:  
2 pieces of coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  367
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  10
CommentType:  T

Comment:  
Need to clarify how the PNC acknowledges the association request commands.
CommentEnd:  

SuggestedRemedy:  
Change "an Imm-ACK frame." to be "an Imm-ACK frame with the DA set to the association address."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  719
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  17
CommentType:  TR

Comment:  
The text between lines 17 and 33 describe an broken Association process.
CommentEnd:  

SuggestedRemedy:  
Text in the Association clause of doc 02/037r0 provides a detailed resolution to this problem.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  368
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  33
CommentType:  T

Comment:  
There is no exit criteria for the PNC in doing an association response and directed rame.
CommentEnd:  

SuggestedRemedy:  
Limit it to an integer number of attempts, I suggest 10.  Change text from "the PNC shall repeat the sequence of association response and directed frame as illustrated in Figure 83." to be "the PNC shall repeat the sequence of association response and directed frame as illustrated in Figure 83 up to aMaxAssocRespRepeat times.  If the PNC does not receive an ACK after aMaxAssocRespRepeat attempts, it shall consider the association process for the DEV to have failed."  Add aMaxAssocRespRepeat to the table at the end of clause 8 with a value of 10.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  366
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  5
CommentType:  T

Comment:  
Association may happen in the CAP or in an association MTS.
CommentEnd:  

SuggestedRemedy:  
Change "during the CAP of an existing piconet." to be "during the CAP or association MTS of an existing piconet."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1535
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  5
CommentType:  E

Comment:  
Association can be sent in an association MTS.
CommentEnd:  

SuggestedRemedy:  
Change sentence to "An unassociated DEV initiates the association process by sending an association request command, defined in 7.5.2.1, during the CAP or association MTS of an existing piconet. "
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  845
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  5
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'a association request' by 'an association request'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1132
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  5
CommentType:  TR

Comment:  
Need to indicate that the MTS can also be used for association.  Modify as shown below.
CommentEnd:  

SuggestedRemedy:  
... during the CAP or MTS of an existing piconet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  39
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.3.2
Page:  144
Line:  6
CommentType:  E

Comment:  
"... and its AD-AD or that the request has been rejected ..." doesn't read well.
CommentEnd:  

SuggestedRemedy:  
not sure how it should read! perhaps that " its AD-AD has been assigned or that the ..."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1537
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.3.2
Page:  145
Line:  29
CommentType:  E

Comment:  
"The addresses (AD-ADs)" should be "The allocated addresses (AD-ADs)"
CommentEnd:  

SuggestedRemedy:  
Change "The addresses (AD-ADs)" to "The allocated addresses (AD-ADs)"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  787
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.3.2
Page:  145
Line:  32
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  788
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.3.2
Page:  145
Line:  35
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  789
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.3.2
Page:  145
Line:  38
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  716
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.3.3
Page:  145
Line:  41
CommentType:  T

Comment:  
The text between lines 42 and 45 contains these sentence fragments which are no longer needed "... with a reason code."
CommentEnd:  

SuggestedRemedy:  
Remove the indicated sentence fragments from clause 8.3.3.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1538
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.3.3
Page:  145
Line:  48
CommentType:  T

Comment:  
Are Disassociation requests retried?
CommentEnd:  

SuggestedRemedy:  
Specifiy that association requests are retried 3 times.
RemedyEnd:  

Response:  
PROPOSED REJECT. The retransmission policy already indicates that frames may be retried up to aMaxRetransmissionLimit times.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  785
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.3.4
Page:  141
Line:  13
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1628
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4
Page:  145
Line:  
CommentType:  TR

Comment:  
Need to add a text on how asynchronus data will be efficiently handled.
CommentEnd:  

SuggestedRemedy:  
Need to aspecify how asynchronous data will be handled in a scheme that is both power and bandwidth efficient.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1539
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4
Page:  145
Line:  54
CommentType:  T

Comment:  
Should mention that the CAP is optional
CommentEnd:  

SuggestedRemedy:  
Change sentence to say "The superframe is composed of three major parts: the beacon, the optional CAP and the CFP,"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1544
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4
Page:  146
Line:  
CommentType:  TR

Comment:  
In claause 11 it says SIFS =aRXTXTurnAourndTime.  Yet, aRXTXTurnAroundTime is a range of between 10 and 11 us.  SIFS is never talked of as being a range in clasue 8.  Should it be?
CommentEnd:  

SuggestedRemedy:  
Clarify if SIFS is a range or a single value.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1540
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4
Page:  146
Line:  2
CommentType:  T

Comment:  
Change "CAP is used for non-QoS frames." to "CAP can be used for non-QoS frames as regulated by the PNC."
CommentEnd:  

SuggestedRemedy:  
Change "CAP is used for" to "CAP can be used for"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1543
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4
Page:  146
Line:  22
CommentType:  TR

Comment:  
Figure 84 says AKC at the END of a SIFS, but line 22 says "Both in the CAP and the CFP, a response frame (ACK) transmission over the medium shall start within a SIFS duration after the end of the transmission of the previous frame for which the response is intended."  Which is it?  Does the ACK come before a SIFS or after a SIFS?
CommentEnd:  

SuggestedRemedy:  
Need to decide on the exact timing of a SIFS and document it carefully.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  493
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  8.4
Page:  157
Line:  
CommentType:  TR

Comment:  
Allowing the use of Del-Ack Req bit set in a frame that has ack-policy set to implied-ack to obtian the del-acks is an efficient use of implied-ack policy.
CommentEnd:  

SuggestedRemedy:  
Remove the restriction of "only data" in 8.8.4 and add the following at the beginning. When directed frame has ack-policy bits set to implied-ack, the intended receiver can respond with a command frame or data frame that may or may need immediate-ack or no-ack.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Remove the restriction of "only data" in 8.8.4 and add the following at the beginning of the paragraph in 8.8.4 on line 2:. "When a directed frame has the ack-policy set to implied-ack, the intended receiver may respond with a command frame or data frame that may use either immediate-ack or no-ack."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1110
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.1
Page:  146
Line:  22
CommentType:  TR

Comment:  
Both in the CAP and the CFP, a response frame (ACK) transmission over the medium shall start within a SIFS duration after the end of the transmission of the previous frame for which the response is intended.  From table 76, the SIFS is between 10 uS and 11 uS.
CommentEnd:  

SuggestedRemedy:  
The above sentence from line 22 is not clear.  Does it mean the ACK has to start between 10 uS to 11 uS after the previous frame - or - does it mean the ACK has to start <10 uS after the previous frame.  If the meaning is the latter than this becomes the RX-to-TX turnaround time that should be used in clause 11.2.6.2.  MAC & PHY committee to advise.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1133
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.1
Page:  146
Line:  22
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
Replace the words "Both in" with "In both"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1545
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.1
Page:  146
Line:  27
CommentType:  E

Comment:  
"an RIFS" should be "a RIFS."
CommentEnd:  

SuggestedRemedy:  
change "an RIFS" to "a RIFS" in line 27 and 28
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  790
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.4.2
Page:  146
Line:  39
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1546
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.2
Page:  146
Line:  41
CommentType:  TR

Comment:  
If each DEV is only alowed to transit one frame at a time during the CAP with backoff time applied to every frame, then what is the "CAP MaxBurstDuration" in 6.3.12.1 used for
CommentEnd:  

SuggestedRemedy:  
Get rid of CAP MaxBurstDuration in clause 6.3.12.1
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1547
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.2
Page:  146
Line:  46
CommentType:  TR

Comment:  
Transmtting station needs to allow for Guard Time.
CommentEnd:  

SuggestedRemedy:  
Change sentence to "If an Imm-ACK is expected for that frame, the remaining time in CAP needs to be large enough to accommodate the current frame, 2 SIFS periods and the Imm-ACK frame at the same PHY rate as the transmitted frame and the guard time.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1134
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.2
Page:  146
Line:  52
CommentType:  TR

Comment:  
Line 52 refers to a "CAP mode field" that is in clause 7.4.2
CommentEnd:  

SuggestedRemedy:  
There is not CAP mode field reference in clause 7.4.2.  What is meant here?  Refer to MAC folks.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  259
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  8.4.2.1
Page:  147
Line:  1214
CommentType:  E

Comment:  
The following sentences do not end in a period: — backoff_window(retry_count): A table which has values [7, 15, 31, 63] ... channel. For the 2.4 GHz PHY, this is defined in 11.2.6.1
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  846
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  08
Subclause:  8.4.2.1
Page:  147
Line:  1525
CommentType:  E

Comment:  
bw_random(retry_count) is there two times
CommentEnd:  

SuggestedRemedy:  
combine the 2 descriptions or delete one
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1550
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.2.1
Page:  147
Line:  21
CommentType:  E

Comment:  
The pseudo random sequence consists of integers and not bits.
CommentEnd:  

SuggestedRemedy:  
Change to:"Note that the current state of the PRNG should be maintained and subsequent backoffs should use subsequent integers in the pseudo-random sequence."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  369
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.4.2.1
Page:  147
Line:  23
CommentType:  T

Comment:  
bw_random(retry_count) is defined twice.
CommentEnd:  

SuggestedRemedy:  
Delete "-- bw_random(retry_count): A pseudorandom integer ... [0,backoff_windo(retry_count)]."  Move the sentence "It is important that ... among DEVs." to the end of the previous paragraph.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1551
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.2.1
Page:  147
Line:  47
CommentType:  TR

Comment:  
When is the retry counter decremented?
CommentEnd:  

SuggestedRemedy:  
Specify when retry counter is decremented.  I think there is disagreement about this.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  53
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.4.3.1
Page:  148
Line:  1
CommentType:  T

Comment:  
maybe not the correct location but it seems that there should be mention that for pseudo-static, that the PNC shall not change the superframe duration while devices are presuming a location for their slot don't get confused.
CommentEnd:  

SuggestedRemedy:  
Add wording: The PNC shall not vary any paramters, such as superframe length, that would invalidate the pseudo-static GTS assigned to one or more DEVs in the piconet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1552
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.1
Page:  148
Line:  22
CommentType:  E

Comment:  
coordinate should be coordinates
CommentEnd:  

SuggestedRemedy:  
Change to: "However, the PNC uses the channel time grant command and coordinates the channel time grants with the CTAs in the beacon."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  370
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.4.3.2
Page:  149
Line:  30
CommentType:  T

Comment:  
The sentence "In addition to this the PNC ... connection process." does not add any information to the present discussion.  In addition, the PNC is supposed to make use of this, but we don't say how.  For example, an implementation may use the information as an input to a PRNG to generate the slot assignments and still be considered conformant.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  371
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.4.3.2
Page:  149
Line:  33
CommentType:  T

Comment:  
The sentences "The slot assignments ... as described in 8.4.3.1" is a repeat of earlier requirements and so is an evil redundancy.
CommentEnd:  

SuggestedRemedy:  
Delete the sentences since this behavior has already been adequately defined.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  791
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.4.3.2
Page:  149
Line:  43
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  792
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.4.3.2
Page:  149
Line:  44
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  793
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.4.3.2
Page:  149
Line:  45
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  794
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.4.3.2
Page:  149
Line:  46
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1135
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  149
Line:  53
CommentType:  E

Comment:  
grammatical - add definitve article two places
CommentEnd:  

SuggestedRemedy:  
Rewrite as ...  ... for that channel-time with the PNC.  When the PNC grants ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1555
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  15
Line:  12
CommentType:  T

Comment:  
Need to be clear that a DEV that does not hear the Beacon cannot transmit during dynamic GTS, but it can still listen.
CommentEnd:  

SuggestedRemedy:  
Change the sentence as follows: "If a DEV did not receive the beacon, it shall not transmit in any dynamic GTSs during the CFP but it can still receive."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1554
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  150
Line:  10
CommentType:  E

Comment:  
Random Noise will also cause Beacons to be received in error.
CommentEnd:  

SuggestedRemedy:  
Chang esentence as follows:"This may not happen to the same DEV all the time but may happen to different DEVs at different times depending upon their location and type of interference to which they are subjected, as well as random nooise."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  372
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.4.3.2
Page:  150
Line:  16
CommentType:  T

Comment:  
The channel time grant does not enable a DEV to access its GTS if it loses the beacon.  The previous paragraph clearly states that a DEV shall not access a dynamic GTS if it misses the beacon.  Likewise, a psuedostatic GTS does not need a channel time grant to access its slot.  All of the text in the draft makes the beacon the one authoritative indication of channel time allocation.
CommentEnd:  

SuggestedRemedy:  
Delete the entire paragraph.  If we want to keep the usefulness of the channel time grant supplementing the beacon, then the text in other places needs to be modified to allow this.  For example, this would require changes in the prior paragraph of the sort: "did not receive the beacon, it shall not" changed to "did not receive either the beacon or a directed channel time grant command, it shall not"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1556
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  150
Line:  1623
CommentType:  T

Comment:  
Remove this entire paragraph.  The use of channel time grants for stations that cannot hear the NC well is no longer needed.  It has been replaced by pseudostatic GTS slots.
CommentEnd:  

SuggestedRemedy:  
Remove the paragraph
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1136
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  150
Line:  2
CommentType:  T

Comment:  
Is believe that line 2 also needs to reference the MTS slot but I need the MAC folks to verify this.
CommentEnd:  

SuggestedRemedy:  
Should line 2 read ...  ... DEV shall use only the CAP or MTS for sending ...  (If this still is not correct then how do we fix this sentence?)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1553
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  150
Line:  2
CommentType:  T

Comment:  
Using the CAP for delayed ACK is a bad idea.  Should allocate a GTS.
CommentEnd:  

SuggestedRemedy:  
Alwasys allocate a GTS for delayed ACK frames.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1557
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  150
Line:  2531
CommentType:  TR

Comment:  
Guard time is not mentioned here.
CommentEnd:  

SuggestedRemedy:  
We need to explicitly state how guard time is used or teh TDMA scheme will not work.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1558
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.2
Page:  150
Line:  46
CommentType:  T

Comment:  
Private GTSs will always be pseudo-static.
CommentEnd:  

SuggestedRemedy:  
Change to "Private GTSWs will always be pseudo-static GTSs,"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  57
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.4.3.3
Page:  150
Line:  50
CommentType:  T

Comment:  
In the absence of CAP, the first GTS is bumped against the end of the beacon. The development of real implementations of this standard may be hindered if the parsing of the beacon body must occur in the very few microseconds available.
CommentEnd:  

SuggestedRemedy:  
Provide guidance to implementers but also place a minimum time till the beginning of the first GTS in the absense of CAP. If a PNC to DEVs MTS is always present, then this would not be a problem.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  55
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.4.3.3
Page:  150
Line:  50
CommentType:  T

Comment:  
I will put the comment here but it may impact other clauses. If the CAP is reduced to zero length and MTS used in its place, some of the text that we still may have regarding use of the CAP for small amounts of data are not correct.
CommentEnd:  

SuggestedRemedy:  
correct the data in a non-existant CAP issue in this clause with a note that in this case, data must be handled in GTS only.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1348
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  08
Subclause:  8.4.3.3
Page:  150
Line:  52
CommentType:  T

Comment:  
There does not appear to be a guarantee that MTS only mode will have the same performance as a network with a CAP
CommentEnd:  

SuggestedRemedy:  
Either a minimum latency in superframes must be specified or some equivalent to the CAP should be provided to insure that devices can communicate with the PNC in a timely fashion.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  56
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.4.3.3
Page:  151
Line:  1
CommentType:  T

Comment:  
Is there a case where an open MTS is less than one per superframe? If so, is there appropriate wording to change the responsivness of the PNC to requests for change. I believe that up to 4 superframes may pass from CTR till CTA reflecting the change. The 4 superframe lag is long already. It should not go beyond that.
CommentEnd:  

SuggestedRemedy:  
put the appropriate SHALL to keep the lag from CTR (or Stream) till CTA from getting higher than 4 superframes when MTS is used.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  373
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.4.3.3
Page:  151
Line:  18
CommentType:  T

Comment:  
Uplink MTS has not been defined.
CommentEnd:  

SuggestedRemedy:  
Change "uplink MTS within" to "MTS with the new DEVs AD-AD as the SA within".  Else, define uplink and downlink MTSs where they are first referred to (i.e. around line 3 on page 151).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  54
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  08
Subclause:  8.4.3.3
Page:  151
Line:  6
CommentType:  T

Comment:  
Considering that the aMTSAssocPeriod is 0.6 milliseconds, there is a question that the sub 1 second begin scan to payload ready interval may be attained. The unspecified authentication must be considered as well as the extensive number of message exchanges necessary for the typical DEV to get ready to deliver payload.
CommentEnd:  

SuggestedRemedy:  
Understand the numbers and then set the aMTSAssocPeriod accordingly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1138
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.4.3.4
Page:  151
Line:  38
CommentType:  T

Comment:  
The paragraph between lines 38 and 45 implies that the DEV knows where the MTS's are located by passive monitoring.  Should this be explicitly stated?
CommentEnd:  

SuggestedRemedy:  
refer to MAC folks.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  374
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.4.3.4
Page:  151
Line:  39
CommentType:  T

Comment:  
Should clarify what sort of RNG is to be used.
CommentEnd:  

SuggestedRemedy:  
Re-use the text from the backoff algorithm.  Replace "While the random number generator is not specified, it is important" with   "The method for choosing the random integer should be unique for each DEV and use the random number generator resident on the DEV. If the DEV does not possess a random number source, the random integer should be generated using its unique 48-bit device ID (and any other information that the implementer wishes to use) and a pseudo-random number generator (PRNG) such as MGF1 as defined in IEEE Std 1363-2000. Note that the current state of the PRNG should be maintained and subsequent backoffs should use subsequent bits in the pseudo-random sequence. It is important"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  375
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.4.3.4
Page:  151
Line:  48
CommentType:  T

Comment:  
The variable r_a is overloaded.  It means both the random number that is to be counted up to as well as the current MTS count.
CommentEnd:  

SuggestedRemedy:  
Either use r for the count variable (i.e. r=1 rather than r_a=1 for the start and r=r_a for the access slot) or replace "r_a=1" with "1"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1139
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.5
Page:  152
Line:  28
CommentType:  T

Comment:  
modify line 28 to reflect a tolerance and not an absolute
CommentEnd:  

SuggestedRemedy:  
... to be less than or equal to +- 25 ppm.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1559
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.5
Page:  152
Line:  3
CommentType:  TR

Comment:  
Devs are synchronized to the Beacon interval, not the PNC's clock.
CommentEnd:  

SuggestedRemedy:  
Change to "All DEVs within a single piconet shall be synchronized to the Beacon Interval."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  376
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.5
Page:  152
Line:  9
CommentType:  T

Comment:  
All DEVs need to reset their clocks based on the best estimate of the beacon timing if they did not hear the beacon.
CommentEnd:  

SuggestedRemedy:  
Change "it should reset" to "it shall reset"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1140
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.5.4
Page:  152
Line:  36
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... allocations contained in the beacon to start ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1560
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.5.4
Page:  152
Line:  46
CommentType:  TR

Comment:  
This sentence makes it sound like a DEV only needs to stop transmitting once no beacon is heard for ATP diration.  The DEV still needs to follow the rules for dynamic or pseudostatic GTS.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence between "PNC." and "If a DEV":  If a Beacon is not correctly received, a DEV shall forllow the rules for transmitting in a GTS, depending on whether it is a dynamic or pseudo-static GTS.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1561
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.5.4
Page:  152
Line:  48
CommentType:  TR

Comment:  
Need to add that the DEV will send a Beacon Lost MLME to the DME to indicate that the Beacon is lost and the DEV is disassociated.
CommentEnd:  

SuggestedRemedy:  
Add the following: "The DEV shall send the BeaconLost.indication MLME to the DME to indicate that the Beacon has been lost.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1141
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.6
Page:  153
Line:  2
CommentType:  E

Comment:  
grammatical ... add comma
CommentEnd:  

SuggestedRemedy:  
... desires to source and sink, including those ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  379
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.6
Page:  153
Line:  4
CommentType:  T

Comment:  
The roles and terms for the stream negotiation are not clear.  They should be clarified here.
CommentEnd:  

SuggestedRemedy:  
Add the following text at the end of 8.6 prior to 8.6.1.  "In the negotiation of stream connection, the following entities and roles are used:  - PNC: the arbiter of channel time allocation  - originator/originating DEV: The DEV that initiates the stream negotiation process.  The originator may be either the source or the receiving DEV.  - target/target DEV: the DEV (or broadcast address) with which the originator wants to open communications.  The targe may be either the source or receiving DEV.  - sending DEV: The DEV that provides the source of the data in the stream.  - receiving DEV: The DEV that will receive the data in the stream."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1120
CommenterName:  Schrader, Mark
CommenterEmail:  mark.e.schrader@kodak.com
CommenterPhone:  585-253-5241
CommenterFax:  
CommenterCo:  Eastman Kodak Co.
Clause:  08
Subclause:  8.6.1
Page:  153
Line:  12
CommentType:  T

Comment:  
This comment supplements as suggestion for adding stream management command in section 7.5.10.3, page 133 for final confirmation or acceptance of stream connection.  One of the primary purposes of the stream connection process is to determine if the originator and the target agree on a single set of QoS parameters.  As currently proposed the communication flow is: Originator->PNC->Target->PNC->Originator. The originator will then reply to only to the PNC only if it rejects the Targets modified QoS values. The trigger that starts PNC generation of time slots should be a response from the Originator to the PNC conThe stream connection process involves the PNC to determine if it can provide the GTS slot allocation requested, and the two peers must agree on a set of QoS parameters.  As currently proposed the communication flow is Originator->PNC->Target->PNC->Originator. The originator will then reply to only to the PNC if it rejects the Targets modified QoS values. The trigger for PNC generation of time slots should be a response from the Target to the PNC confirming acceptance of the final QoS parameters relayed from the Target, not the absence of any negative response.
CommentEnd:  

SuggestedRemedy:  
The following is a rewrite of lines 12-27 on page 153.  Either the sending DEV or the intended recipient DEV for the new stream may send a stream management command with the request for stream connection. The process of stream connection is illustrated in Figure 88. In this figure, DEV A is the originator of stream connection request and DEV B is the target, consistent with the stream management command section 7.5.10.3.  In all stream management communications from the PNC to the other involved DEV, the PNC appropriately changes the value of the direction field to imply the same direction of the stream as originally requested.  The values for direction, security, stream type and priority shall be non negotiable and are decided by the DEV A that is sending the stream connection request. These values shall not be changed anytime after the first transmission of the command frame containing the request for that stream.  The target DEV B responding to the forwarded stream connection request may modify the remaining QoS parameters including bandwidth and latency requirements.  All the bandwidth and latency related requirements of the stream shall be confirmed or rejected by the originator of the stream connection request in response to the final PNC acceptance message. The PNC decision on the values of the stream QoS parameters that are supported in the piconet shall be final. If the originating DEV A does not accept the PNCs final stream parameters, then DEV A shall send a stream management command to the PNC with action type set to disconnection/rejection as specified in 7.5.10.3. Then the PNC shall then send a stream management command to the target DEV B with action type set to disconnection/rejection. Otherwise, DEV A shall send a stream management command with a final confirm/accept action type, and the PNC shall then begin generating ACTIVE type CTA elements and GTS timeslots as specified upon receipt of this command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  378
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.6.1
Page:  153
Line:  14
CommentType:  T

Comment:  
Since the direction field is constant during the negotiation (since the target and originator addresses are now included), this sentence is incorrect.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "In all stream management ... as originally requested."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  68
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  08
Subclause:  8.6.1
Page:  153
Line:  18
CommentType:  TR

Comment:  
This sentence references values that are not defined in the frame commands used to establish stream connections.
CommentEnd:  

SuggestedRemedy:  
Change "The values for direction, security, stream type and priority ..." to "The values for direction, stream type, priority, and GTS type ...".
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  69
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  08
Subclause:  8.6.1
Page:  153
Line:  22
CommentType:  T

Comment:  
'Bandwidth' is not specifically negotiated, channel time is negotiated.
CommentEnd:  

SuggestedRemedy:  
Change "All the bandwidth and latency ..." to "All the channel time and latency ...".
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1563
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.6.1
Page:  153
Line:  24
CommentType:  TR

Comment:  
"All the bandwidth and latency related requirements of the stream shall be negotiated between the sender of the stream and the PNC. The PNC decision on the values of the stream QoS parameters that are supported in the piconet shall be final."
CommentEnd:  

SuggestedRemedy:  
The PNC knows nothing about bandwidth.  It only knows about channel time.  I don't think these QoS parameters should be negotiated at the MAC, but if they are the other DEV should have the oportunity to negotiate the values down.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  377
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.6.1
Page:  153
Line:  8
CommentType:  T

Comment:  
There is no multicast capabilities in the current standard, so only broadcast should be referenced.  In addition, the implication of negotiating a broadcast slot is not indicated.
CommentEnd:  

SuggestedRemedy:  
Delete "or multicast"  Change "is precluded." to be "is precluded and so the negotiation is bipartite."
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  1142
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.6.1
Page:  153
Line:  9
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... the involvement of the intended receiver ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1145
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.6.1
Page:  155
Line:  2
CommentType:  E

Comment:  
... for the connection of the stream.                                                                                                                                                                   R_ALFVIN-NOTE: THIS COMMENT WAS SUBMITTED INCOMPLETE AS SHOWN.                                                                                R_ALFVIN-NOTE: THE COMMENT TYPE WAS NOT SELECTED BY THE SUBMITTER.
CommentEnd:  

SuggestedRemedy:  
R_ALFVIN-NOTE: NO REMEDY WAS SUBMITTED WITH THIS COMMENT.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  260
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  8.6.1
Page:  155
Line:  2
CommentType:  E

Comment:  
The following sentence does not end in a period: This is illustrated in Figure 89
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  380
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.6.1
Page:  155
Line:  26
CommentType:  T

Comment:  
The use of the channel time request and channel time grant to get non-stream CTAs is not described.
CommentEnd:  

SuggestedRemedy:  
Add a short description of the frames that are exchanged to get a non-stream CTA via the channel time request and channel time grant commands.  Also, the commands that are exchanged to disconnect a non-stream CTA.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  795
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.6.1 Fig 88
Page:  154
Line:  5
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  796
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  08
Subclause:  8.6.1 Fig.89
Page:  155
Line:  4
CommentType:  E

Comment:  
coordinator should be PNC
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1147
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.6.2
Page:  155
Line:  38
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... to the othre DEV via the same command.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1564
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.7
Page:  156
Line:  1
CommentType:  TR

Comment:  
Fragmentation ad defragmentation should not be in the MAC.  It will overly complicate the designs and require large per-stream buffers.  Fragmentation should be done at the convergence layer.
CommentEnd:  

SuggestedRemedy:  
Move Fragmenation to the convergence layer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1148
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.7
Page:  156
Line:  11
CommentType:  T

Comment:  
add a reference to clause 7.2.1 ... suggested text below.
CommentEnd:  

SuggestedRemedy:  
... in the frame control field (clause 7.2.1) set to "1".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  382
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.7
Page:  156
Line:  31
CommentType:  E

Comment:  
The sentence "If the stream does not ... is No-ACK" is redundant.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1149
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.7
Page:  156
Line:  31
CommentType:  E

Comment:  
grammatical ... replace the phrase "at all" with the word "then"
CommentEnd:  

SuggestedRemedy:  
see above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1150
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.7
Page:  156
Line:  34
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... reception of a new frame ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  381
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.7
Page:  156
Line:  5
CommentType:  T

Comment:  
aFragThreshold is not a constant and so should loose the a and the reference in the table at the end of Clause 8.  Also, we need to require that FragThreshold shall be less than the biggest allowed frame.
CommentEnd:  

SuggestedRemedy:  
Change aFragThreshold to FragThreshold.  Delete aFragThreshold from Table 73.  Change "and change them as desired." to be "and change them as desired provided that FragThreshold shall be less than aMaxFrameSize."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  383
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.8.1
Page:  157
Line:  1
CommentType:  T

Comment:  
No group addressing is supported in this standard.
CommentEnd:  

SuggestedRemedy:  
Change "group addressed" to "broadcast"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1565
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.2
Page:  157
Line:  8
CommentType:  TR

Comment:  
"within a SIFS"  needs clarification.  In some places it says that ACK comes before a SIFS and others it says after a SIFS.
CommentEnd:  

SuggestedRemedy:  
Throroughly describe be the ACK timing with a detailed description including SIFS complete with drawings.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1151
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.3
Page:  157
Line:  18
CommentType:  T

Comment:  
In general, this paragraph deals with sending the delayed ack.  The sentence at line 18 that beguns "However the recipient ..." since it implies a DEV should send a delayed ACK at the expiration of the retransmission window.  My question is this ... do you sent this at the expiration only if not previously send or do you send it again regardless.
CommentEnd:  

SuggestedRemedy:  
MAC committee to comment and clarify text if necessary.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1566
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.3
Page:  157
Line:  22
CommentType:  TR

Comment:  
Need to specify that non-stream data cannot used delayed ACK
CommentEnd:  

SuggestedRemedy:  
Add the following sentence:  "Non Stream data cannot use the delayed ACK policy for a couple of reasons.  There is no opportunity for the reeiving DEV to negotiate the window size.  Also, since all non stream data uses stream number zero, they all use the same sequence number counter so delayed ACK is not possible."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1567
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.4
Page:  157
Line:  30
CommentType:  TR

Comment:  
"The start of transmission of the response data frame shall start at the end of a SIFS, like an Imm-ACK frame transmission."  This is inconsistent with the previous section which says that Immediate ACK is sent within a SIFS.
CommentEnd:  

SuggestedRemedy:  
Need to clarify the use of SIFS.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  385
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.8.5
Page:  158
Line:  35
CommentType:  T

Comment:  
The retransmission for Imm-ACK is defined with in two incompatible methods.
CommentEnd:  

SuggestedRemedy:  
Either:  1) Delete "either Imm-ACK or the" from line 35.  Here, the Imm-ACK retransmission starts after the Imm-ACK would have been finished.  2) Delete the sentence "When and Imm-ACK is ... attempting another transmission."  Here, the Imm-ACK retransmission begins with the same timing as for implied-ACK, i.e. when the channel has been idle for the wait time.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  384
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.8.5
Page:  158
Line:  38
CommentType:  T

Comment:  
The text "at the end of RIFS" only partially describe the timing for the re-transmission and neglects to mention the SIFS that is indicated further down.
CommentEnd:  

SuggestedRemedy:  
Delete the text "at the end of RIFS" since it is better described at the end of the paragraph.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1569
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.5
Page:  158
Line:  41
CommentType:  TR

Comment:  
Transmitting station must wait for immediate ACK time plus 2 SIFS to retransmit
CommentEnd:  

SuggestedRemedy:  
Change the sentence as follows:  "it shall wait for the duration of Imm-ACK frame plus two SIFSs before attempting another transmission."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  386
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.8.5
Page:  158
Line:  43
CommentType:  T

Comment:  
Clarify when the retransmission begins.
CommentEnd:  

SuggestedRemedy:  
After "of the time slot." add the sentence "That is, the retransmission begins RIFS+SIFS following the last transmission."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1152
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.5
Page:  158
Line:  46
CommentType:  T

Comment:  
In line 46, reference is made to "the negotiated retransmission window".
CommentEnd:  

SuggestedRemedy:  
Please add to the sentence reference to the clause where this negotiation is described.  (assigned to MAC committee)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  387
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.8.5
Page:  158
Line:  50
CommentType:  T

Comment:  
Redundant (and therefore evil) information on collision detection that is better defined in 8.4.2.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "A collision during the ... for that frame."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1568
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.5
Page:  158
Line:  50
CommentType:  TR

Comment:  
Movee this sentence:  "A collision during the transmission of a directed frame in the CAP is detected by the absence of the acknowledgement for that frame." to the first paragraph is 8.8.5
CommentEnd:  

SuggestedRemedy:  
Move the sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1153
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.5
Page:  159
Line:  2
CommentType:  E

Comment:  
grammatical ... add a comma as shown below.
CommentEnd:  

SuggestedRemedy:  
However, a DEV might ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1570
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.8.5
Page:  45
Line:  45
CommentType:  TR

Comment:  
DEVS cannot reject a delayed ACK.  This must be from when we were calling them "retransmission requests"
CommentEnd:  

SuggestedRemedy:  
Change the paragraph as follows:  "When Del-ACK is used for a stream, the DEV transmitting the data frame may abort retransmssion attempts once the negotiated retransmission window for the stream has been reached. When retransmissions are aborted, the DEV transmitting the stream shall send transmission sequence sync command, as defined in 7.5.9.2, to the recipient of the stream in order to synchronize the delayed-ACKs."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  715
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  8.9
Page:  159
Line:  17
CommentType:  TR

Comment:  
All references to Probe-request/response between lines 17 and 38 are incorrect.
CommentEnd:  

SuggestedRemedy:  
Please replace all references to Probe-request/response between lines 17 and 38 with DEVICE-INFORMATION-REQUEST/RESPONSE.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1154
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.9
Page:  159
Line:  18
CommentType:  E

Comment:  
Grammatical ... modify the sentence as shown below.
CommentEnd:  

SuggestedRemedy:  
In addition, the DEV may use the probe request ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1155
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.9
Page:  159
Line:  26
CommentType:  T

Comment:  
This sentence describes an algorithm with an exponential increasing time interval.
CommentEnd:  

SuggestedRemedy:  
Does this algorithm need an upper limit on the time delay.  MAC committee to provide comment.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1156
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  8.9
Page:  159
Line:  32
CommentType:  T

Comment:  
Add reference to text
CommentEnd:  

SuggestedRemedy:  
Power management ... what is the reference that describes the process of returning a DEV to the EPS mode.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  388
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  08
Subclause:  8.9
Page:  159
Line:  34
CommentType:  T

Comment:  
This paragraph should list the commands that are used to wake and sleep DEVs.
CommentEnd:  

SuggestedRemedy:  
Change "into ACTIVE mode" to "into ACTIVE mode using the switch to ACTIVE CTA mode command, 7.5.7.4" and change "to EPS mode after" to be "to EPS mode using switch to EPS CTA mode command, 7.5.7.5, after"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  538
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  9
Page:  159
Line:  2938
CommentType:  TR

Comment:  
Another "special case" as admitted in line 29. Why should power management create a special case for every corner of this standard? What justification is there to add this mega-complex scheme into the so called low-cost standard?
CommentEnd:  

SuggestedRemedy:  
Remove lines 29:38 on page 159 Simplify power management to the following - Request for sleep time by DEV - Accept/Reject by PNC - Broadcast the addresses of sleeping DEV in Beacon - Allocation/modification of GTS by PNC depending on who is awake
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  539
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  9
Page:  159
Line:  2938
CommentType:  TR

Comment:  
Another "special case" as admitted in line 29. Why should power management create a special case for every corner of this standard? What justification is there to add this mega-complex scheme into the so called low-cost standard?
CommentEnd:  

SuggestedRemedy:  
Remove lines 29:38 on page 159 Simplify power management to the following - Request for sleep time by DEV - Accept/Reject by PNC - Broadcast the addresses of sleeping DEV in Beacon - Allocation/modification of GTS by PNC depending on who is awake
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1137
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Equation 1
Page:  151
Line:  35
CommentType:  E

Comment:  
Palce a white space before number 256
CommentEnd:  

SuggestedRemedy:  
see above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1578
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 69
Page:  160
Line:  7
CommentType:  TR

Comment:  
Immediate ACK has no frame body, only a header.  Since the header is always transmitted at the base rate, the table should say that Imm. ACK is transmitted at base rate.
CommentEnd:  

SuggestedRemedy:  
Change to base rate.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  530
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  08
Subclause:  Figure 78
Page:  
Line:  
CommentType:  E

Comment:  
caption is inconsistent
CommentEnd:  

SuggestedRemedy:  
Change "coordination" to "PNC"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1103
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 78
Page:  139
Line:  
CommentType:  E

Comment:  
Several editorial problems with Figure 78 ... see below
CommentEnd:  

SuggestedRemedy:  
1. In the first column, the word "alternate" is misspelt 2. in the 4th column, relace "New" with "new" 3. In last column, the arrows are too long, shorten the arrows
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  175
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  Figure 79
Page:  140
Line:  
CommentType:  T

Comment:  
Diagram hard to read.  Where are the terms aMinHandOvrTo, aMaxHandOvrTo, aCHFrameRepeat and aBroadcastDEVInfoDuration in this diagram?  I would like to see their timing relationships.
CommentEnd:  

SuggestedRemedy:  
See above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  722
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  Figure 79
Page:  140
Line:  32
CommentType:  T

Comment:  
The PNC handover process illustrated in this figure  is poorly represented.
CommentEnd:  

SuggestedRemedy:  
The MLME-Handover message sequence chart in doc 01410r1 provides a much clearer representation of the handover function.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  177
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  Figure 81, 82
Page:  142
Line:  10
CommentType:  T

Comment:  
What is a directed frame?  The allocated private GTS response?
CommentEnd:  

SuggestedRemedy:  
Need clarification.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  181
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  Figure 82
Page:  143
Line:  
CommentType:  E

Comment:  
Child beacon referenced here.
CommentEnd:  

SuggestedRemedy:  
Should be referencing the neighbor beacon.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1531
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 82
Page:  143
Line:  21
CommentType:  E

Comment:  
The last arrow should say "Neighbor Beacon"  not "Child Beacon"
CommentEnd:  

SuggestedRemedy:  
Change to Neighbor Beacon.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  184
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  Figure 83
Page:  144
Line:  
CommentType:  T

Comment:  
The section words do not indicate a SIFS time before an ACK
CommentEnd:  

SuggestedRemedy:  
State what is intended consistently in words and figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  717
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  Figure 83
Page:  144
Line:  38
CommentType:  TR

Comment:  
The message sequence chart in figure 83 illustrates a broken association protocol.
CommentEnd:  

SuggestedRemedy:  
The MLME-ASSOCIATION message sequence chart in clause 6.3 illustrates a validatable association protocol.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1536
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 83
Page:  144
Line:  44
CommentType:  TR

Comment:  
Figure 83 shows a SIFS between Association reauest and ACK.  Is this a time that is at least 1 SIFS, Less than 1 SIFS or equal to 1 SIFS /- some delta (like .11 does).  In clause 11, SIFS may actually a range (aTXRXTurnAroundTime = between 10 and 11 us)??? This same comment applies to Figure 84
CommentEnd:  

SuggestedRemedy:  
Decided exactly what 1 SIFS means and document it. I think it will be =1 SIFs +/- some delta.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  718
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  Figure 84
Page:  145
Line:  1
CommentType:  TR

Comment:  
The message sequence chart in figure 84 provides another perspective of the   broken association protocol.
CommentEnd:  

SuggestedRemedy:  
The MLME-ASSOCIATION message sequence chart in clause 6.3 illustrates a validatable association protocol.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  186
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  Figure 86
Page:  149
Line:  
CommentType:  T

Comment:  
It is hard to know what this figure represents.  Is there a legend on the shade meanings?  Are TX and RX the same slots?  What is the difference in each frame?  Is it an advance of time?
CommentEnd:  

SuggestedRemedy:  
Clarify what the figure is showing.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1562
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 88
Page:  
Line:  
CommentType:  E

Comment:  
The font is hard to read in Figure 88
CommentEnd:  

SuggestedRemedy:  
Choose a more readable font
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  261
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  Figure 88
Page:  153
Line:  29
CommentType:  E

Comment:  
The following sentence in Figure 88 does not end in a period: suggested value for size of Retx window
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1144
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 88
Page:  154
Line:  
CommentType:  T

Comment:  
In general Figure 88 is in poor shape.  The font appears distorted and the arrows are falling on top of text.  This figure needs to be corrected.
CommentEnd:  

SuggestedRemedy:  
reformat drawing
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1143
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 88
Page:  154
Line:  3
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
... retransmission window, the samller of ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  187
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  Figure 89
Page:  155
Line:  
CommentType:  E

Comment:  
The grayed box seems to attempt to tell the reader to reference the previous figure (88).
CommentEnd:  

SuggestedRemedy:  
State reference explicitly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1146
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 89
Page:  155
Line:  
CommentType:  T

Comment:  
In the shaded box at the bottom of Figure 89, modify the text as shown below
CommentEnd:  

SuggestedRemedy:  
Rest of the sequence follows as if the sender of the stream intiated the stream connnection process, as shown in Figure 88.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  262
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  Figure 89
Page:  155
Line:  1519
CommentType:  E

Comment:  
The following sentences in Figure 89 do not end in a period: Use all-zero stream index in the request ... Rest of the sequence follows as if the sender of the stream initiating the stream connection process  also I would drop the grey color in the box at the bottom of the figure.
CommentEnd:  

SuggestedRemedy:  
Add the period and delete the color from the box at the bottom of the figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  712
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  Figure 92
Page:  161
Line:  4
CommentType:  TR

Comment:  
The message sequence chart in figure 92 is inadquately illustrates the Repeater function protocol.
CommentEnd:  

SuggestedRemedy:  
The Message sequence chart provided in the MLME_REPEATER MSC clause of doc 01/410r1 provides a much clearer illustration.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1583
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 93
Page:  162
Line:  
CommentType:  T

Comment:  
Instead of "PNC stops sending beacons"  should say "PNC issues quiet command and stops sending beacons"
CommentEnd:  

SuggestedRemedy:  
Change "PNC stops sending beacons"  to "PNC issues quiet command and stops sending beacons"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1167
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 93
Page:  162
Line:  
CommentType:  E

Comment:  
The fonts in the figure are distorted.
CommentEnd:  

SuggestedRemedy:  
Reformat the figure.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  713
CommenterName:  Heberling, Allen
CommenterEmail:  aheberling@xtremespectrum.com
CommenterPhone:  703-269-3022
CommenterFax:  571-220-1211
CommenterCo:  XtremeSpectrum, Inc.
Clause:  08
Subclause:  Figure 93
Page:  162
Line:  4
CommentType:  TR

Comment:  
The message sequence chart in figure 93 illustrates a Dynamic channel selection process that is broken.
CommentEnd:  

SuggestedRemedy:  
The MLME-CHANNEL-STATUS, MLME-REMOTE-SCAN, and MLME-CHANGE-CHANNEL msc clause in doc 01/410r1 provides a much better Dynamic channel selections process that does not require the PNC beacon to go silent while devices are transitioning to the new channel.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Break up the message sequence charts so that the remote scan commands are in, but not tied to channel change, rather they are one method that may be used.  Make as optional, in 8.12, that the PNC turns off the beacon to scan other channels.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1192
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 94
Page:  166
Line:  1
CommentType:  E

Comment:  
Figure 94 needs to be reformatted.  Also, replace the "place in set" with "add to set".
CommentEnd:  

SuggestedRemedy:  
See above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  266
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  Figure 94
Page:  166
Line:  38
CommentType:  E

Comment:  
The Editor might want to consider Figure 94 and the sentence "Note: PNC will begin..." most of the notes up to this page in the D09 are "Note that..." vs. "Note: ...".  The issue is normative vs. informative; respectively.
CommentEnd:  

SuggestedRemedy:  
I defer to the Editor but it is likely that it should be changed to "Note that...".  If you choose to leave as-is then remember - Notes always start with the word "NOTE" in capital letters, followed by a dash, and are set in 9-point type.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1201
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 95
Page:  167
Line:  
CommentType:  T

Comment:  
Figure needs to be reformatted to remove change bars.  Also, in the second phrase on the right is the word "[repeating] ... what does this mean?
CommentEnd:  

SuggestedRemedy:  
What does [repeating] mean?  Refer to Power Management committee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1654
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 95
Page:  167
Line:  31
CommentType:  T

Comment:  
"DEVs are associated and operations of Figure 95 have been completed."  This is in FIgure 95
CommentEnd:  

SuggestedRemedy:  
I think that this should be Figure 94, but who knows.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  268
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  08
Subclause:  Figure 95
Page:  167
Line:  4748
CommentType:  E

Comment:  
The Editor might want to consider Figure 95 and the sentence "Note: DEVs do not enter EPS operation at this point" most of the notes up to this page in the D09 are "Note that..." vs. "Note: ...".  The issue is normative vs. informative; respectively.  Also, adding a period completes the sentence.
CommentEnd:  

SuggestedRemedy:  
I defer to the Editor but it is likely that it should be changed to "Note that...".  If you choose to leave as-is then remember - Notes always start with the word "NOTE" in capital letters, followed by a dash, and are set in 9-point type.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1207
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 96
Page:  169
Line:  
CommentType:  T

Comment:  
In figure 96, on the last message exchange
CommentEnd:  

SuggestedRemedy:  
should the last message go from the PNC and terminate at DEV B instead of DEV A.  Refer to Power Management committee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1206
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure 96
Page:  169
Line:  
CommentType:  E

Comment:  
Reformat to remove change bars
CommentEnd:  

SuggestedRemedy:  
see above
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1582
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Figure93
Page:  
Line:  
CommentType:  E

Comment:  
Fonts is hard to read
CommentEnd:  

SuggestedRemedy:  
Change the font in Figure 93.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1648
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  General
Page:  
Line:  
CommentType:  TR

Comment:  
EPS is so complex that I am afraid that no one will implement it.  Also, the number of commands, MLME parameters, states, etc is overwhelming.  The complexity is overkill for a WPAN.  I will propose something that meets the requirements with much lower complexity.
CommentEnd:  

SuggestedRemedy:  
Adopt a new power management Scheme.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1605
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Tabble73
Page:  174
Line:  12
CommentType:  TR

Comment:  
If we change aMaxSuperframeDuration to 65535 us, then we can use 1 uS resolution.
CommentEnd:  

SuggestedRemedy:  
Change a MaxSuperframeDuration to 65535 uS
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1104
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table 68
Page:  139
Line:  
CommentType:  T

Comment:  
Need to add two acronyms to clause 4
CommentEnd:  

SuggestedRemedy:  
1. PSRC 2. PSAVE
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  189
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  08
Subclause:  Table 70
Page:  163
Line:  
CommentType:  T

Comment:  
Where is RPS listed?  It seems to be missing.  Does this mean the definition of RPS is incomplete?
CommentEnd:  

SuggestedRemedy:  
Complete RPS definition
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1217
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table 73
Page:  173
Line:  
CommentType:  TR

Comment:  
Wrong reference
CommentEnd:  

SuggestedRemedy:  
For the SIFS parameter, the value is defined in 11.2.6.1 (not 11.2.6.2)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1218
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table 73
Page:  173
Line:  
CommentType:  T

Comment:  
Add clause reference for clarity
CommentEnd:  

SuggestedRemedy:  
For the parameter aMinTPCLevel, the value is defined in 11.5.9
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1219
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table 73
Page:  173
Line:  
CommentType:  TR

Comment:  
Add an item to MAC PIB?
CommentEnd:  

SuggestedRemedy:  
In Table 73, for the parameter aFragThreshold, the value is shown to be "DEV chooses this value".  In this case, this should be added to the MAC PIB in clause 6.5 as MACPIBFragThreshold.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1601
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table 73
Page:  173
Line:  45
CommentType:  TR

Comment:  
A AssocRespConfirmTime of 5 ms is too short.  There may not be any CAP or GTS slot time to respond and the PNC may be busy.
CommentEnd:  

SuggestedRemedy:  
Change  AssocRespConfirmTime to 2 superframe durations.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1220
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table 73
Page:  174
Line:  
CommentType:  T

Comment:  
PHY dependent parameters that should be defined in clause 11
CommentEnd:  

SuggestedRemedy:  
The following three items should have values that are PHY dependent and should be defined in clause 11 as added clauses 11.2.9, 11.2.10, and 11.2.11.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1603
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table 73
Page:  174
Line:  5
CommentType:  TR

Comment:  
8196 octet aMaxTransferUnitSize of 8196 octets may sound like a lot, but we should increase it to 65536 octets for future PHYs.
CommentEnd:  

SuggestedRemedy:  
change aMaxTransferUnitSize to 65536 octets
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1600
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table73
Page:  173
Line:  31
CommentType:  T

Comment:  
aMinChannelScan should probably be twice the MaxSuperframeDuration
CommentEnd:  

SuggestedRemedy:  
Change aMinChannelScan to 2*MaxSuperframeDuration
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1602
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table73
Page:  173
Line:  46
CommentType:  TR

Comment:  
aProbeResponseDelay of 8 ms is too short.  Should be at least 2 superframe durations.  But, responding DEV may have no channel time.
CommentEnd:  

SuggestedRemedy:  
Increase aProbeResponseDelay to 5 superframes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1604
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  08
Subclause:  Table73
Page:  174
Line:  10
CommentType:  TR

Comment:  
512 us is too short for aMinSuperframeDuration.
CommentEnd:  

SuggestedRemedy:  
Change aMinSuperframeDuration 1 ms
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  545
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  09
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
This clause seems to be standing by itself with no support from other clauses, neither is it seem to be supporting any other clause in the draft. BTW, it also uses lot of terms that are not used anywhere else (example SFID)
CommentEnd:  

SuggestedRemedy:  
There are two options here. 1. Remove this clause 2. For every description (flow, paramter, mechanism) connect them with its relavant counterpart in clauses 6, 7 and 8 (most importantly 7 and 8).
RemedyEnd:  

Response:  
PROPOSED ACCEPT. Clause 9 will be removed. Remove references to SFID in Figure A.3 and other occurrances.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1729
CommenterName:  Liang, Jie
CommenterEmail:  jliang@ieee.org
CommenterPhone:  214 480 4105
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  09
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
QoS is very important for the applications intended for this standard, however is very lacking in details. Clause 9 needs to be beefed up in terms of details.
CommentEnd:  

SuggestedRemedy:  
Additional work to provide the details needed to support QoS.
RemedyEnd:  

Response:  
PROPOSED REJECT. Clause 9 has been deleted. SSCS's will be added as a follow on to the draft  to clarify how 802.15.3 capabilities can be used to provide QoS.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1749
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  09
Subclause:  
Page:  175
Line:  
CommentType:  E

Comment:  
The QoS policy is not clearly defined in this section.
CommentEnd:  

SuggestedRemedy:  
Please address the QoS policy clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1740
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 668
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  09
Subclause:  
Page:  175
Line:  
CommentType:  E

Comment:  
The QoS policy is not clearly defined in this section.
CommentEnd:  

SuggestedRemedy:  
Please address the QoS policy clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1766
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  09
Subclause:  
Page:  175
Line:  
CommentType:  E

Comment:  
The QoS policy is not clearly defined in this section.
CommentEnd:  

SuggestedRemedy:  
Please address the QoS policy clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1784
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  09
Subclause:  
Page:  175
Line:  
CommentType:  E

Comment:  
The QoS policy is not clearly defined in this section.
CommentEnd:  

SuggestedRemedy:  
Please address the QoS policy clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1354
CommenterName:  Seals, Michael
CommenterEmail:  mseals@intersil.com
CommenterPhone:  (321) 724-7172
CommenterFax:  
CommenterCo:  Intersil
Clause:  09
Subclause:  
Page:  175
Line:  3
CommentType:  T

Comment:  
How QoS is maintained during PNC handover or an abrupt termination of PNC functions (e.g. PNC unplugged)?
CommentEnd:  

SuggestedRemedy:  
Think about this and propose a solution or point me to it.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. In case of PNC handover, streams are maintained as defined in 8.2.4. In case of PNC unplugged, there is no remaining piconet so QoS is lost. See 5.5.6. Section 8.5 defines what a DEV does when it fails to see a beacon.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  1/21/2002
VoterStatus: 

-----------
CommentID:  190
CommenterName:  DuVal, Mary
CommenterEmail:  m-duval@ti.com
CommenterPhone:  972-575-2330
CommenterFax:  
CommenterCo:  Texas Instruments
Clause:  09
Subclause:  00
Page:  175
Line:  
CommentType:  E

Comment:  
A figure showing the elements of the QoS parameter set would be helpful for a reader trying to determine parameters that will be set.
CommentEnd:  

SuggestedRemedy:  
Include frame format figure for QoS parameter set
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1353
CommenterName:  Seals, Michael
CommenterEmail:  mseals@intersil.com
CommenterPhone:  (321) 724-7172
CommenterFax:  
CommenterCo:  Intersil
Clause:  09
Subclause:  1
Page:  175
Line:  31
CommentType:  TR

Comment:  
The stream index is undefined and of an unknown length.
CommentEnd:  

SuggestedRemedy:  
At a minimum, define the length of the stream index.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Clause 9 has been deleted. The length of stream index is defined in 7.2.4.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  417
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  09
Subclause:  9
Page:  175
Line:  1
CommentType:  T

Comment:  
The clause on QoS policies is incomplete and provides little useful information that is not already present in other clauses.  In addition, it relies on an SFID which occurs in only one other place in the draft (in a figure in Annex A.)  In addition, although provisioned service flows are indicated, none are defined.  This entire process should be left to the implementer anyway.
CommentEnd:  

SuggestedRemedy:  
Since the definition is incomplete and relies on a non-existent parameter, the clause should be deleted.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  33
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  09
Subclause:  9.0
Page:  175
Line:  1
CommentType:  T

Comment:  
This is a general comment on the Quality of service clause. There is a lack of introduction, relationships to rest of draft, helpful diagrams, and mention of EPS power management QoS.
CommentEnd:  

SuggestedRemedy:  
Provide additional text on introduction, relationships to rest of draft, helpful diagrams, and if possible at least a xref to power management QoS of 8.13.
RemedyEnd:  

Response:  
PROPOSED REJECT. Clause 9 has been deleted. SSCS's will be added as a follow on to the draft  to clarify how 802.15.3 capabilities can be used to provide QoS.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1734
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  09
Subclause:  9.0
Page:  175
Line:  1
CommentType:  T

Comment:  
QoS section is far from complete for implementation.
CommentEnd:  

SuggestedRemedy:  
Provide necessary detail to implement the QoS policy
RemedyEnd:  

Response:  
PROPOSED REJECT. Clause 9 has been deleted. SSCS's will be added as a follow on to the draft  to clarify how 802.15.3 capabilities can be used to provide QoS.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1606
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.1
Page:  175
Line:  29
CommentType:  T

Comment:  
The difference between service flow ID and Stream Index is not clear.  Why do we need both.
CommentEnd:  

SuggestedRemedy:  
Clarify the difference between service flow ID and Stream Index.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Clause 9 has been deleted.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  80
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  09
Subclause:  9.1
Page:  175
Line:  31
CommentType:  T

Comment:  
Stream index should be 8-bits in length, not TBD.
CommentEnd:  

SuggestedRemedy:  
Change TBD to 8.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Clause deleted. Defined in 7.2.4.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  298
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  09
Subclause:  9.1
Page:  175
Line:  31
CommentType:  T

Comment:  
TBD in "b) Stream index: A unique value, TBD bits in length, used to identify a connection and to associate it with an active service flow." needs to be changed to 16 bits.  Was supposed to be changed in D09, but got missed.
CommentEnd:  

SuggestedRemedy:  
Change "TBD" to "16 bits"
RemedyEnd:  

Response:  
PROPOSED REJECT.  Clause 9 deleted.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1221
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.1
Page:  175
Line:  31
CommentType:  TR

Comment:  
TBD to be resolved
CommentEnd:  

SuggestedRemedy:  
MAC committee needs to resolve the TBD in line 31
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Clause deleted. Defined in 7.2.4.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1222
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.2
Page:  175
Line:  39
CommentType:  E

Comment:  
remove stray comma
CommentEnd:  

SuggestedRemedy:  
provisioned and active.  (no comma after provisioned)
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1223
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.2.1
Page:  175
Line:  43
CommentType:  E

Comment:  
remove stray comma
CommentEnd:  

SuggestedRemedy:  
remove commma as shown below ...  ... service flow is one which has been ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1224
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.2.1
Page:  175
Line:  44
CommentType:  E

Comment:  
rewrite as shown below
CommentEnd:  

SuggestedRemedy:  
... the PNC has not yet reserved the QoS ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1225
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.2.1
Page:  175
Line:  46
CommentType:  E

Comment:  
rewrite sentence lin line 46 as shown below ...
CommentEnd:  

SuggestedRemedy:  
... QoS parameters, the benefit of which ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1228
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.2.2
Page:  176
Line:  12
CommentType:  E

Comment:  
remove American English idiom
CommentEnd:  

SuggestedRemedy:  
instead of "created from scratch" use "originated"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1226
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.2.2
Page:  176
Line:  7
CommentType:  E

Comment:  
rewrite as shown below
CommentEnd:  

SuggestedRemedy:  
An active service flow is one which has ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1227
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  09
Subclause:  9.2.2
Page:  176
Line:  7
CommentType:  E

Comment:  
Rewrite sentence as shown below
CommentEnd:  

SuggestedRemedy:  
In addition, an active service flow is one which has a non-NULL set of ActiveQoSParameters and one which indicates that the PNC has reserved the piconet resources requested.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1845
CommenterName:  Dydyk, Michael
CommenterEmail:  Michael.Dydyk@Motorola.com
CommenterPhone:  480-775-7020
CommenterFax:  480-570-2841
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  T

Comment:  
Not enough details on security/authentication
CommentEnd:  

SuggestedRemedy:  
Specify enough details on security/authentication that vendors can build 802.15.3 devices that can communicate securely while being interoperable with other vendor's products. This includes the choice of a mandatory cipher suite as required by the vote in Austin.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/24/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  547
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
This section is described as if this is a requirement without any details, whatsoever, on the actual algorithm used for authentication and privacy. Without those two mechanisms the reader can not comment on the description provided in this clause since depending on the algorithm these descriptions ought to change.
CommentEnd:  

SuggestedRemedy:  
Specify authentication and privacy algorithms.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1833
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Currently, only the broadcast communication scenario is being elaborated upon. This conflicts with Sub-clause 10.1.1, Page 177, lines 25-26 (which specifies both peer-to-peer and broadcast communications); this should be corrected.
CommentEnd:  

SuggestedRemedy:  
Incorporate a mechanism for secure multicasting within the piconet setting.   A general solution the multicasting communication scenario (i.e., communication for any specified subset of the devices that constitute the piconet) will be presented during the Dallas meeting, January 2-25, 2002. (Document No: 02029r0, 02030r0).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  781
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
As it is well understood, security is one of the most sensitive subjects in the wireless communications. Even though the mechanism using security suites is described in the current draft but there is no clear default mode description. Secured environment is made by a solid decsription including the very first association.  Otherwise, it may fall another prey of criticism from the industry.
CommentEnd:  

SuggestedRemedy:  
Need to specify a default security mode.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1832
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Currently, the mapping of roles to devices that is in effect is static in nature (see 10.3.2.2 on Page 182). Moreover, the role of the security manager is identified with that of the current piconet controller. This approach, although simple, has its drawbacks, since it assumes each device to trust the piconet controller and, more importantly, to trust each subsequent piconet controller for its security needs. This might be especially undesirable in the event of an automatic piconet hand over, since the devices constituting the piconet exercise no control over the election process of the new piconet controller. From an implementation viewpoint, the drawback is that each change of the piconet controller now invokes by definition a change of security manager, thus potentially requiring an expensive re-establishment of keying relationships between all devices and the new security manager.
CommentEnd:  

SuggestedRemedy:  
Incorporate a more flexible security model.  Currently, all trust in the piconet is concentrated in a single device, the PNC, which poses some restrictions one should be very well aware of. A more general security model will be presented during the Dallas meeting, January 2-25, 2002. (Document No: 02029r0, 02030r0). This more general security model prevents the disadvantages of the approach we had to take in draft D09, while still allowing that approach, as a special case. The general security model allows for a relaxation of the amount of trust that needs to be concentrated in a single device while at the same time allowing a speed up of authentication and a more robust architecture, if the PNC changes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1830
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Symmetric keys of a particular type shall be used for the associated usage only, e.g., keys intended for securing the exchange of data keys shall not be used for securing the exchange of user data, and vice versa. Symmetric keys of a particular usage type shall be used for the associated usage only, e.g., keys intended for usage with an encryption algorithm shall not be used with a keyed hash function, and vice versa. Public keys of a particular type shall be used for the intended usage only, e.g., public keys intended for securing the establishment of symmetric keying material shall not be used for authenticity verification purposes, and vice versa. Expired or archived keys should not be used for, e.g., encryption and for the provision of data integrity any more, but might still be used for, e.g., decryption and for the verification of data integrity. The type of keying material, its intended usage, and the status as to its life cycle should become available during the generation or during the transfer of the key. Subsequent versions of the same key should be distinguishable via a key sequence number, such as to prevent the usage of old keys, when new keys have been issued, or vice versa. At any moment of time, the binding between the key value and all the key aspects discussed above should be stored in an authentic way.
CommentEnd:  

SuggestedRemedy:  
Incorporate a classification of key life cycle and key usage aspects, both for public keying material and for symmetric keying material, and adapt key data objects accordingly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. We need to add the possibility of tieing key generation to authentication. Change all text to informative language and place in ANNEX B.3.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1725
CommenterName:  Rofheart, Martin
CommenterEmail:  Martin@xtremespectrum.com
CommenterPhone:  703-269-3007
CommenterFax:  240-463-3306
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The security clause lacks encryption detail for the default cipher algorithm.
CommentEnd:  

SuggestedRemedy:  
Refer to the remedy indicated by Rick Roberts
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1835
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Admission to a piconet is now based on evidence regarding the true identity (device Id) of a communicating party only (via an authentic public key). Since this is the Id of a chip that could potentially be used in a wide variety of devices (invisible to the user), the user is left pretty much in the dark on what device capabilities are present in the piconet and whom (i.e., which human operators of the devices) it is actually talking to. This might lead to inclusion of devices one does not want to participate in communications. Instead, access control should be based on the actual user or usages of the device.
CommentEnd:  

SuggestedRemedy:  
Incorporate a more refined access control mechanism than presently described in the draft.  One also has to associate users or usages with the device Id, rather than just a public key. Moreover, one has to incorporate access control lists based on these. I will try and sketch how the user or the usage of a device could be securely associated with the Id of the device, thus defining the relationship User/usage - Device Id - Public key in a more explicit way. This would also allow access control lists to be implemented based on the user's attributes associated with the device Id in question.One distinguishes the following entities:·	physical device;·	device Id;·	public key; ·	user;·	user and device attributes.One distinguishes the following bindings at the device level:·	Device & device Id: physical tying of the device to its identity (to prevent identity theft)·	User & device: binding between the device and its user, via authentication techniques (e.g., PIN code, password, biometrics).·	Device Id & public key: cryptographic binding of the device Id to the public key (e.g., via a public key certificate).·	Device Id & device attributes: binding between the device Id and personalization attributes (e.g., via attribute certificate).·	User & user attributes: binding between a user and personalization attributes hereof (e.g., via attribute certificate).Within the current specification, authentication is based on the proper Id of the device only. If each device has some device and user attributes associated with it, one can achieve a more refined access control as follows:At personalization of the device, one could securely associate device and user attributes with a device. At usage of a device, one could maintain an access control list of those devices that are allowed to communicate with it in a piconet. At device authentication, one also passes the attribute certificate that securely binds the device to user and device attributes. Access control is then based on these attributes as well, rather than on an authentic public key only. One can modify the access control list via a procedure similar to an 'address book' on a PDA. The implementation hereof requires a user interface. If one has no user interface (e.g., 'speaker-receiver'-type application), the access control list might be established via an automatic mechanism, e.g., during set-up of this equipment.The specification should provide the mechanisms and formats to allow implementation of dynamic access control lists and of user and device attributes and the like. Currently, this is completely lacking in the draft.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1823
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Keying material should be handled at the MAC layer only, unless this is technically unfeasible. Comment: Currently, all cryptographic operations seem to be handled outside the MAC layer (hence, all the MLME interfaces required). It seems that public key verification and execution of cryptographic protocols could be handled in the MAC layer only, thus making for a very thin interface with other layers (and allows use of 802.15.3 services without changes to the hardware and/or software at different layers).
CommentEnd:  

SuggestedRemedy:  
An example security architecture that allows for handling of all keying material and cryptographic operations at the MAC/PHY layer will be presented during the Dallas meeting, January 2-25, 2002. (Document No: 02029r0, 02030r0).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1643
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
If we are going to leave the Access control list to the upper layers, we need to add teh MLMEs
CommentEnd:  

SuggestedRemedy:  
Sorry if this is a repeat.  It is getting late (again)
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  We need to add the MSCs for the security related items (e.g., authentication, deauthentication, key distribution) and ensure that all the required MLMEs are present. The ACLs are outside of the MAC.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1834
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Currently, anonymity is not considered in the draft. Lack of anonymity was a major criticism of the original Bluetooth specification. It led to a change requirement by Ericcson, after this privacy issue had been advertised on the front cover of the NY Times). One distinguishes a number of anonymity issues, including (1) tracking of devices and thereby their users; (2) trace-ability of the manufacturer of the WPAN-chip, which might lead to passively monitoring which devices are owned by whom (e.g., for device theft).
CommentEnd:  

SuggestedRemedy:  
Investigate whether anonymity would be required (e.g., as a distinguishing feature for WPAN vs. Bluetooth). Investigate how this could be realized technically, if at all, and what changes this would require to the specification of the security framework and of data objects (device Id format and the-like).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1362
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  10
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The standard does not include a specification for either authentication or encryption.
CommentEnd:  

SuggestedRemedy:  
Add a specification for both authentication and encryption.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The draft will include directions on available cipher suites, the method of determine which cipher suite is used for a piconet, and the method used to incorporate a cipher suite to perform authentication and payload protection.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1767
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  10
Subclause:  
Page:  175
Line:  
CommentType:  TR

Comment:  
There is neither security/authentication details nor a cipher suite defined for the sake of interoperability among devices built by different vendors.
CommentEnd:  

SuggestedRemedy:  
Please provide the details and the cipher suite clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1785
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  10
Subclause:  
Page:  177
Line:  
CommentType:  TR

Comment:  
There is neither security/authentication details nor a cipher suite defined for the sake of interoperability among devices built by different vendors.
CommentEnd:  

SuggestedRemedy:  
Please provide the details and the cipher suite clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1741
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 668
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  10
Subclause:  
Page:  177
Line:  
CommentType:  TR

Comment:  
There is neither security/authentication details nor a cipher suite defined for the sake of interoperability among devices built by different vendors.
CommentEnd:  

SuggestedRemedy:  
Please provide the details and the cipher suite clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  802
CommenterName:  Kinney, Patrick
CommenterEmail:  pat.kinney@ieee.org
CommenterPhone:  724-425-7952
CommenterFax:  
CommenterCo:  Invensys
Clause:  10
Subclause:  
Page:  177
Line:  
CommentType:  T

Comment:  
The security section looks thin.  Specifically I do not believe that I can implement security according to this section in an unambiguous manner.
CommentEnd:  

SuggestedRemedy:  
Detail out the mechanisms to implement security in such a manner that interoperability will be assured.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1750
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  10
Subclause:  
Page:  177
Line:  
CommentType:  TR

Comment:  
There is neither security/authentication details nor a cipher suite defined for the sake of interoperability among devices built by different vendors.
CommentEnd:  

SuggestedRemedy:  
Please provide the details and the cipher suite clearly.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1838
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  184
Line:  1012
CommentType:  E

Comment:  
Add the following (informative) paragraph hereafter:"First, however, we give a general overview.The system comprises of ordinary devices, a single piconet controller, and a fixed external trusted party (see the mapping of roles to devices as defined in 10.3.2.2). The piconet controller acts as the security manager of the operational network. As such, it authenticates devices that would like to join the piconet and facilitates the distribution of data keys, to be used for securing communications between devices in the piconet. In addition, it allocates time slots for these message exchanges to each piconet device (see the role model of 10.3.2.1). Finally, it enforces the security rules as formulated in 10.3.3. Device authentication and the initial establishment of keying material are based on public key techniques. Evidence regarding the authenticity and validity of these public keys is corroborated via the external trusted party, who facilitates the generation of authentic public keying material for each device and the verification hereof during system operations (see 10.3.1.3 and 10.3.2.1). The role of the external trusted party is limited to the system initialization phase." Comment: this informative text illuminates some of the design rationale behind the current security architecture and should prove useful, esp. to non-specialists.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1839
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  
Page:  184
Line:  26
CommentType:  E

Comment:  
Replace 'the it would' by 'it would'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1798
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  1
Page:  177
Line:  23
CommentType:  TR

Comment:  
One might need a different identifying string than the IEEE MAC address, in the event that anonymity of devices is required as an additional security objective.
CommentEnd:  

SuggestedRemedy:  
Delete '(the IEEE MAC Address)'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1795
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  1
Page:  177
Line:  25
CommentType:  E

Comment:  
Add that the nodes operate on close distance from one another.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1796
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  1
Page:  177
Line:  25
CommentType:  E

Comment:  
The PNC has local address 0, neighbor piconets and child piconets have local addresses 0xFA-0xFC, and one has reserved addresses for broadcast (0xFF), temporary during association (0xFE), and for multicast (0xFD). Thus, the range of local addresses assigned to entities in a piconet setting is 0x00-0xFC, which adds up to 253 (254, if one includes the temporary local address).
CommentEnd:  

SuggestedRemedy:  
Replace '252' by '253'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1797
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  1
Page:  177
Line:  3435
CommentType:  TR

Comment:  
The current wording does not cover the admission of devices to a piconet and the handling of child and neighbor piconets.
CommentEnd:  

SuggestedRemedy:  
Replace 'This standard describes only the communication behavior between DEVs in the piconet' by 'This standard describes only the communication behavior between WPAN-enabled devices and -entities'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1799
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  1
Page:  177
Line:  50
CommentType:  E

Comment:  
The current wording does not cover, e.g., neighbor and child piconets.
CommentEnd:  

SuggestedRemedy:  
Replace 'DEVs' by 'entities'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1794
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  1
Page:  177
Line:  6
CommentType:  E

Comment:  
The characteristics of the 802.15.3 WPAN define the context and the constraints the security framework has to live with. In itself issues like communication bandwidth are not related to security, but do impose restrictions here on (e.g., selected encryption mechanisms must guarantee sufficient throughput).
CommentEnd:  

SuggestedRemedy:  
Replace 'security-related' by 'security-relevant'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1800
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  1
Page:  178
Line:  3
CommentType:  E

Comment:  
The current wording does not cover, e.g., neighbor and child piconets.
CommentEnd:  

SuggestedRemedy:  
Replace 'DEVs' by 'entities'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  546
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  10
Subclause:  1.1
Page:  
Line:  
CommentType:  E

Comment:  
This subclause does not belong here. it is better suited in clause-5
CommentEnd:  

SuggestedRemedy:  
move it to clause 5
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  801
CommenterName:  Kinney, Patrick
CommenterEmail:  pat.kinney@ieee.org
CommenterPhone:  724-425-7952
CommenterFax:  
CommenterCo:  Invensys
Clause:  10
Subclause:  1.1
Page:  177
Line:  
CommentType:  E

Comment:  
This section, Characteristics of the IEEE 802.15.3 WPAN; seems to be out of place, it's a duplicate entry.
CommentEnd:  

SuggestedRemedy:  
eliminate it
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1609
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.
Page:  177
Line:  
CommentType:  TR

Comment:  
General Comment:  Given that the entire piconet uses the same Keys, it is imperative that we choose a mandatory cipher suite as voted on in Austin.
CommentEnd:  

SuggestedRemedy:  
choose and document the mandatory cipher suite.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1229
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.
Page:  177
Line:  1
CommentType:  T

Comment:  
Retitle this section
CommentEnd:  

SuggestedRemedy:  
Instead of "Privacy and Security" call this section "Authentication and Security" and move all the authentication text out of clause 8.3.1 over to this section.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  418
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  10
Subclause:  10.1
Page:  177
Line:  4
CommentType:  E

Comment:  
This section is interesting, but distracts from the requirements of this clause.  Move everything up to, but not including, 10.2.2 to an informative annex that provides the rationale for the security implementation.  Also move 10.3.2 through 10.3.3 to the same area
CommentEnd:  

SuggestedRemedy:  
Move the sections to an new annex.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1608
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.1.1
Page:  177
Line:  13
CommentType:  E

Comment:  
this section belongs in clause 5.
CommentEnd:  

SuggestedRemedy:  
Consider moving to clause 5
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1607
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.1.1
Page:  177
Line:  15
CommentType:  E

Comment:  
objects are typically within 10 m apart, not around 10 m apart.
CommentEnd:  

SuggestedRemedy:  
Change to "moving objects that are typically within 10 m apart.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1230
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.1.1
Page:  177
Line:  25
CommentType:  T

Comment:  
Number of DEVs is listed as 252
CommentEnd:  

SuggestedRemedy:  
Should this be 256?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  71
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  10
Subclause:  10.1.1
Page:  177
Line:  27
CommentType:  T

Comment:  
PNC does not allocate bandwidth, only channel time.
CommentEnd:  

SuggestedRemedy:  
Change 'bandwidth' to 'channel time'.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  269
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  10
Subclause:  10.1.1
Page:  177
Line:  30
CommentType:  E

Comment:  
The word ad-hoc is spelled incorrectly here, subclause 10.1.2, page 178, line 3, and subclause 10.2.2, page 179, line 13.
CommentEnd:  

SuggestedRemedy:  
Ad hoc (please, no hyphen) has been an English word for over a hundred years (and yes, it has to do with Latin).  Change all occurences of this word to ad hoc.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1677
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.1.2
Page:  177
Line:  3741
CommentType:  E

Comment:  
The constraints described in this section are possible limitations and are discussed to give rationale about why we chose what we did and what dangers there are for implementers.  These are not strict constraints since not all devices will have these problems.
CommentEnd:  

SuggestedRemedy:  
Replace section title with "Security Limitations in an IEEE 802.15.3 WPAN".  Replace first line to: "The security of an 802.15.3 WPAN is dependent on the devices having certain properties.  When implementing 802.15.3 security in a device, the user should take into account the following possible constraints, which may limit the capability of the device to perform in a secure manner."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1611
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.1
Page:  178
Line:  
CommentType:  TR

Comment:  
Even if access control is provided at a higher layer for the piconet, we need some way to ensure that devices do not join the wrong piconet.
CommentEnd:  

SuggestedRemedy:  
Add a mechanism to control which piconet a DEV joins.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  757
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  10
Subclause:  10.2.1
Page:  178
Line:  1617
CommentType:  T

Comment:  
Refers to identity of 'its communication party'.  Is this a person or a host deevice?
CommentEnd:  

SuggestedRemedy:  
Clarify.  If it is a host device, what assurance is there that the (new) device should be allowed to enter the network?  i.e., device could belong to a neighbor.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1612
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.1
Page:  178
Line:  18
CommentType:  T

Comment:  
We should make it cleat that the "communicating party" is the piece of equipment and not the human using it.
CommentEnd:  

SuggestedRemedy:  
Add text that makes it clear that the "communicating party" is the piece of equipment and not the human using it.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1678
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.1
Page:  178
Line:  2324
CommentType:  E

Comment:  
Non-repudiation is more properly defined as "Prevention of an entity claiming that a DEV performed an action that it did not perform."  This is the other side of the coin of what is described in the text, but the point is that an entity that cannot deny it has done certain things also gets the benefit that it cannot be claimed that it did something that it did not do.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1610
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.1
Page:  178
Line:  34
CommentType:  TR

Comment:  
We do authentication of the DEV, but not he owner or user.  We need to have some way of controlling access to the piconet based on the owner of the equipment.
CommentEnd:  

SuggestedRemedy:  
If access control is done at a higher layer, we need to at least provide the MLMEs to make it possible.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1613
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.2
Page:  179
Line:  13
CommentType:  T

Comment:  
met is probably not the best term to use.
CommentEnd:  

SuggestedRemedy:  
change met to communicated
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1614
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.2
Page:  179
Line:  13
CommentType:  TR

Comment:  
Need to add reference to the access control list.
CommentEnd:  

SuggestedRemedy:  
Change to "Regulation of admission of these DEVs requires evidence as to the true identity of the DEVs that comprise the piconet, and membership in the access control list."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1615
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.2
Page:  179
Line:  30
CommentType:  T

Comment:  
need to add "and access control list."
CommentEnd:  

SuggestedRemedy:  
Change to "The authentication of the DEV will be based upon evidence regarding its true identity and proof that the DEV itself corroborated this evidence and that the DEV is also in the access control list."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1679
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.3
Page:  179
Line:  25
CommentType:  T

Comment:  
If the piconet implements security, it always requires authentication (number 1) and sometimes requires payload protection (number 2), not just a combination of the two.
CommentEnd:  

SuggestedRemedy:  
Replace this line by: "The cipher suite in use determines the currently enforced security requirements.  If security is in use, the cipher suite shall enforce requirement 1 below and may enforce requirement 2."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1680
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.2.3
Page:  179
Line:  31
CommentType:  T

Comment:  
The heading is misleading and not accurate to the requirement.
CommentEnd:  

SuggestedRemedy:  
Change heading to "Payload protection for authenticated parties only."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1681
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.1.1
Page:  180
Line:  1213
CommentType:  TR

Comment:  
Requiring that the device not have a user interface for the input of secret keying material negates the possibility of using methods where a password/passphrase is input as a shared secret and that is used for keying material.  This may prevent the use of other mechanisms such as 802.1x and 802.11b security.
CommentEnd:  

SuggestedRemedy:  
Recommend the removal of the second sentence in this paragraph (leaving the parenthetical comment in some form may be okay).  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1616
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.1.1
Page:  180
Line:  18
CommentType:  E

Comment:  
change the acronym from RNG to PRNG.
CommentEnd:  

SuggestedRemedy:  
Make a global change from RNG to PRNG
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1682
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.1.3
Page:  
Line:  
CommentType:  TR

Comment:  
It is unclear whether this section is normative or informative, but it seems to imply the use of a certificate authority, which should not be a requirement in the standard.  The use of certificates and the method for verifying the validity of a public key should be outside the scope of the standard.  Some arguments for this point of view include: 1) If two devices do not share a common CA, they cannot set up a piconet using security. 2) Certificates should have limited lifetimes and be revocable in order to provide the expected security of certificates.  Since this section assumes that keys are never revoked, this limits the practical usefulness of certificates. 3) A device may want to act as its own CA and sign keys of devices it trusts rather than relying on an "external" trusted party. 4) A device may want to have a list of public keys that it trusts without using certificates.  Certificates have the drawbacks in that they are computationally more expensive to use than to not use and they may require more storage space than needed (even using implicit certificates).
CommentEnd:  

SuggestedRemedy:  
It should be made clear that this section is informative and other alternatives should be suggested such as low power PHY transmission, user interface input and 802.1x methods.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1683
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.1.3
Page:  180
Line:  4047
CommentType:  TR

Comment:  
Implicit certificates are simply a special form of public-key certificate that is proprietary to Certicom Corp.  There is no reason to explicitly describe them in the document as they provide exactly the same functionality as other certificates.
CommentEnd:  

SuggestedRemedy:  
Recommend removing this paragraph.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  419
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  10
Subclause:  10.3.1.3
Page:  180
Line:  48
CommentType:  T

Comment:  
Since we can assume physical control of the DEVs in a PAN as well as close proximity, we should allow the verification of the public keys to use a physical connection combined with a user action.
CommentEnd:  

SuggestedRemedy:  
Add an enumeration item:  "3) Physical contact with user intervention: This provides a method for the public key certificates to be passed from one DEV to another without using the wireless link.  The user intervention would be required to complete the process, either by pressing a combination of buttons or in response to a prompt from the DEV.  In this case the trusted part is the user who has physical control of both DEVs."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  420
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  10
Subclause:  10.3.1.3
Page:  180
Line:  48
CommentType:  T

Comment:  
The external trusted part has not yet been defined.
CommentEnd:  

SuggestedRemedy:  
Indicate that the external trusted part is defined by the cipher suite.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1231
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.1.3
Page:  181
Line:  11
CommentType:  TR

Comment:  
Lacking detail on how authentication will be done for 802.15.3
CommentEnd:  

SuggestedRemedy:  
Security committee needs to provide details on authentication algorithm.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1684
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.1.3
Page:  181
Line:  57
CommentType:  TR

Comment:  
It should not be required that the trusted party's public key be stored in each device at all, much less only at manufacture time.  This should be a recommendation for those using certificates, but not a requirement.
CommentEnd:  

SuggestedRemedy:  
Recommend (at least) changing "will" to "should".  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1685
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.2.1
Page:  181
Line:  3639
CommentType:  TR

Comment:  
There may be more than one external trusted party (or none) and they may have control over different trust relationships.  The cipher suite determines what method is used to verify the authenticity of a public key, but this may or may not involve the use of an external trusted party.  In any case, the external trusted party is not a DEV role, so this role should not be included here.
CommentEnd:  

SuggestedRemedy:  
Recommend removing bullet 5).  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1686
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.2.1
Page:  181
Line:  41
CommentType:  TR

Comment:  
The role of the external trusted party is also beyond the scope of the document.
CommentEnd:  

SuggestedRemedy:  
Change to "Since this standard addresses PANs, the security implications of the roles of the portal and the external trusted party are beyond the scope."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1687
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.2.1
Page:  181182
Line:  838412
CommentType:  TR

Comment:  
The external trusted party may not be outside the network and we need not require that it be external to the network.
CommentEnd:  

SuggestedRemedy:  
Recommend removing bullet 3).  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1232
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.2.1
Page:  182
Line:  2
CommentType:  TR

Comment:  
In the sentence prior to line 2 we have a nice discussion about the external trusted party.
CommentEnd:  

SuggestedRemedy:  
Security committee needs to provide details on how this will be done for 802.15.3.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1688
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.2.2
Page:  182
Line:  2126
CommentType:  T

Comment:  
Discussion of the external trusted party should be made as general as possible and mention alternatives such as certificates, rather than stating what it will do.
CommentEnd:  

SuggestedRemedy:  
Recommend replacing the paragraph with "The security implications of the trusted party role should be addressed elsewhere and are considered to be out of scope."  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  81
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  10
Subclause:  10.3.2.2
Page:  182
Line:  22
CommentType:  E

Comment:  
Seems to be a dangling reference here.
CommentEnd:  

SuggestedRemedy:  
Remove or correct dangling reference. i.e. change "DEV,10.3.1.3" to "DEV".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1689
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.3
Page:  
Line:  
CommentType:  TR

Comment:  
The security policy section should be informative rather than normative.  It is not always desirable to enforce the policy that every time a DEV times out or wishes to leave the piconet that the keys must be changed.  This is a good policy in most cases and should be encouraged, but it does not affect interoperability and should not be mandated.
CommentEnd:  

SuggestedRemedy:  
Remove all shall and will statements from this section and make it informative.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1233
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.3.1
Page:  182
Line:  28
CommentType:  T

Comment:  
Clause 10.3.3 hints at a security policy.  Is this section complete?  Is the security policy completely presented here?
CommentEnd:  

SuggestedRemedy:  
Refer to security commmittee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  270
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  10
Subclause:  10.3.3.1
Page:  183
Line:  12
CommentType:  E

Comment:  
The note numbered list states "Notes:", most of the notes up to this page in the D09 are "Note that..." vs. "Notes: ...".  The issue is normative vs. informative; respectively.
CommentEnd:  

SuggestedRemedy:  
I defer to the Editor but it is likely that it should be changed to "Notes that...".  If you choose to leave as-is then remember - Notes always start with the word "NOTE" in capital letters, followed by a dash, and are set in 9-point type.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1234
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.3.3
Page:  184
Line:  1
CommentType:  T

Comment:  
During a PNC handover, why can't the old PNC just vouche for all the authenicated devices when they are handed over to the new PNC?
CommentEnd:  

SuggestedRemedy:  
Question for security committee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  421
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  10
Subclause:  10.3.3.3
Page:  184
Line:  4
CommentType:  T

Comment:  
The formal language is out of place here.  The definition of the required action occurs later in the clause.
CommentEnd:  

SuggestedRemedy:  
Change "each DEV shall" to "each DEV will"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  423
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  10
Subclause:  10.3.4
Page:  185
Line:  9
CommentType:  E

Comment:  
Some message sequence charts would really help explain the security operations.
CommentEnd:  

SuggestedRemedy:  
Add MSC's that reflect the formal language in the sub-clauses.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1690
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.1
Page:  184
Line:  1427
CommentType:  TR

Comment:  
The process for generating a public key and getting it registered with the external trusted party should be a recommended (alternative) method for initializing the public key on the device, not a mandatory method.
CommentEnd:  

SuggestedRemedy:  
The section should be called Security Initialization, rather than system initialization.  Once again, this section should be made informative, as it does not affect interoperability.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  848
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  10
Subclause:  10.3.4.1
Page:  184
Line:  26
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
replace 'initial state, the it would' with  'initial state, it would'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1235
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.1
Page:  184
Line:  26
CommentType:  E

Comment:  
remove stray word "the"
CommentEnd:  

SuggestedRemedy:  
... back to its intitial state it would then ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1236
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2
Page:  184
Line:  50
CommentType:  TR

Comment:  
Where is the cipher information.  In this line we talk about a cipher suite but I see no detail in clause 10.
CommentEnd:  

SuggestedRemedy:  
Security committee to supply detail on cipher algorithm.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1691
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2
Page:  184
Line:  5152
CommentType:  T

Comment:  
Why must the mode of operation and the cipher suite be fixed over the life cycle of the piconet?  What if the PNC changes and needs to use a different cipher suite or mode?  This requirement does not affect interoperability and should be removed.
CommentEnd:  

SuggestedRemedy:  
Recommend deleting the final sentence in the paragraph.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  83
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  
CommentType:  TR

Comment:  
This section does not describe how authentication may fail due to a timeout.
CommentEnd:  

SuggestedRemedy:  
Add message sequence charts from 02033r0 for "Timed out Authentication (DEV side)" and "Timed out Authentication {PNC side)" to this section following the normal authentication MSC.  Add following text prior to (DEV side): "When the DEV attempts to authenticate to the PNC, it sends an authenticate request.  Until the authentication process is completed, the DEV is not granted the rights of an authenticated DEV, so the DEV should not wait indefinitely to get an authentication response from the PNC.  While the DEV is waiting for the authentication response, it may participate in a challenge response protocol with the PNC or it may not.  In either case, if the DEV does not receive an authenticate response within a reasonable amount of time, the MLME shall return a timed out response after which the DME may choose to attempt a new authenticate request or choose not to authenticate to the PNC." Add the following text prior to the (PNC side): "During the authentication process for a particular DEV, the PNC sends a challenge to the DEV for it to prove it is who it says it is.  As with any other time a challenge is sent, the PNC sets a time limit for how long it will wait to receive the response.  One reason for this timeout is to free up the resources of the PNC that are being used to save the state of the challenge protocol.  If the challenge times out, the PNC shall send an authenticate response message to the DEV informing it that the authentication process failed."
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  82
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  0
CommentType:  TR

Comment:  
More complete explanation of Authentication of a DEV to the piconet is required.
CommentEnd:  

SuggestedRemedy:  
Add the Message Sequence Chart for successful DEV authentication figure from document 02033r0 to this section at line 33. Replace text in lines 30-32 on page 185 with the following: "When a device wishes to join a secure piconet, it must authenticate to the PNC.  The authentication process starts with an authentication request.  When the PNC receives the authentication request, it checks to see if it is willing to allow that device into the piconet and, if so, it generates a challenge for the DEV so that it can prove it is who it claims to be.  If the DEV provides a legitimate response to the challenge, the PNC sends back a confirmation that the DEV may join the piconet."
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add the Message Sequence Chart for successful DEV authentication figure from document 02033r0 to this section at line 33. Replace text in lines 30-32 on page 185 with the following: "When a device wishes to join a secure piconet, it shall authenticate to the PNC.  The authentication process starts with an authentication request.  When the PNC receives the authentication request, it checks to see if it is willing to allow that device into the piconet and, if so, it generates a challenge for the DEV so that it can prove it is who it claims to be.  If the DEV provides a legitimate response to the challenge, the PNC sends back a confirmation that the DEV may join the piconet."
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  758
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  1112
CommentType:  TR

Comment:  
From this, I believe that a device establishes its identy in na 'stand alone' fashion (i.e., true identity is established at the factory).  However, to join a piconet, the ownership of the device is what is at question.  How is that established.
CommentEnd:  

SuggestedRemedy:  
Clarify and reword as necessary.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1618
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  12
CommentType:  T

Comment:  
Need to add text about access control list.
CommentEnd:  

SuggestedRemedy:  
Change to "Admission of a DEV to the piconet is based upon evidence regarding its true identity and proof that the DEV itself corroborated this evidence and teh DEV is in the access control list."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1676
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  2124
CommentType:  T

Comment:  
The cryptographic evidence provided by the PNC and the DEV may give evidence of their identity, but identity alone doesn't necessarily permit a device to be in the piconet, or to act as a PNC. This decision is made on the basis of identity and other rules. Cryptographic evidence of identity isn't necessary or sufficient to identify the roles the devices are intended to assume.
CommentEnd:  

SuggestedRemedy:  
Change 2 bullets to: 1) The PNC shall have sufficient information to decide whether or not the DEV is authorized to join the piconet, and will have cryptographic material related to the DEV. 2) The joining DEV shall have sufficient information to decide whether or not the PNC is authorized to perform the role of security manager, and will have cryptographic material related to the PNC.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1238
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  41
CommentType:  TR

Comment:  
In line 41, mention is made of public key and symmetric key techniques ... yet not details for provided for either.
CommentEnd:  

SuggestedRemedy:  
Security committee needs to provide the details on public and private key generation.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1239
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  44
CommentType:  TR

Comment:  
In line 44 and line 45, mention is made of "key encryption key" and "entity authentication protocol", yet there are no details on either of these in the document.
CommentEnd:  

SuggestedRemedy:  
Security committee to provide details on key encryption key and also on the authentication protocol.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1240
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  46
CommentType:  TR

Comment:  
In line 46, mention is made of a "separate key agreement protocol", yet there are no details on this protocol.
CommentEnd:  

SuggestedRemedy:  
Security committee to provide details on the "separate key agreement protocol".  Also, details on its usage.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1241
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  53
CommentType:  T

Comment:  
In line 53 (carrying over to the next page) there is a list of key types.  Please include in this list references to the document clauses that describe these key types.
CommentEnd:  

SuggestedRemedy:  
Refer to security committee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1237
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  185
Line:  9
CommentType:  TR

Comment:  
In lines 21, 23, 50 and 52 we see the phrase "cryptographic evidence" used.
CommentEnd:  

SuggestedRemedy:  
Security committee needs to define exactly what cryptographic evidence means to a WPAN.  This sounds like a strong term ... how is it implemented in a WPAN?
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1243
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  186
Line:  1
CommentType:  TR

Comment:  
Mention is made of a combined encryption and integrity key.
CommentEnd:  

SuggestedRemedy:  
No detail is supplied as to how these combo is used and how this combo is generated.  Security committee to supply the detail.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1242
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.1
Page:  186
Line:  1
CommentType:  TR

Comment:  
Mention is made of an "integrity key".
CommentEnd:  

SuggestedRemedy:  
What is an integrity key.  How is it used and how is it generated.  This key is mentioned only in this sentence.  Security committee to supply the detail.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1244
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.2
Page:  186
Line:  18
CommentType:  TR

Comment:  
In line 18 mention is made of a "list of authenticated DEVs".
CommentEnd:  

SuggestedRemedy:  
Where is this list kept?  In the PNC?  Does this list need to be specified in clause 6?  Refer to security committee.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1246
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.2
Page:  186
Line:  20
CommentType:  T

Comment:  
Mention is made that the PNC can be in the "authentication and encryption mode" ... where is this mode described?
CommentEnd:  

SuggestedRemedy:  
Security committee to provide clause reference for the "authentication and encryption mode".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  84
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  10
Subclause:  10.3.4.2.2
Page:  186
Line:  20
CommentType:  E

Comment:  
Bad Grammar.
CommentEnd:  

SuggestedRemedy:  
Change "If the PNC in the ..." to "If the PNC is in the ...".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1245
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.2
Page:  186
Line:  20
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
Add the word "is" ...  If the PNC is in the ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  422
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  10
Subclause:  10.3.4.2.2
Page:  186
Line:  21
CommentType:  T

Comment:  
Only need to re-issue keys if the DEV was authenticated as well as associated.
CommentEnd:  

SuggestedRemedy:  
Change "in the piconet." to be "in the piconet if the DEV that is disassociated was also authenticated in the piconet."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1247
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.3.4.2.3
Page:  186
Line:  31
CommentType:  T

Comment:  
Mention is made of the "authentication process".
CommentEnd:  

SuggestedRemedy:  
Security committee to provide clause reference to the "authentication process".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1617
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  10
Subclause:  10.43.4.2
Page:  184
Line:  41
CommentType:  T

Comment:  
A low power DEV may belong to a piconet that has encryption on, but that DEV may wish to communicate without encryption to save power.  Sec is a field in the stream management.  We should allow streams to negotiate wheter they want to use encryption or not.
CommentEnd:  

SuggestedRemedy:  
Document the ability of DEVs to turn encryption off for a stream, or get the SEC bit out of stream management.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1837
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  2
Page:  
Line:  
CommentType:  TR

Comment:  
Currently, there are no references to communication behavior and security associations with child and neighbor piconets.
CommentEnd:  

SuggestedRemedy:  
Incorporate communication behavior and security associations with child piconets and neighbor piconets.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1801
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  2
Page:  178
Line:  37
CommentType:  E

Comment:  
Delete the comma behind 'capabilities'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1802
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  2
Page:  179
Line:  21
CommentType:  TR

Comment:  
The current wording does not cover the admission of devices to a piconet and the handling of child and neighbor piconets.
CommentEnd:  

SuggestedRemedy:  
Replace ' between DEVs in the piconet' by 'between WPAN-enabled devices and -entities'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1804
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  2.3
Page:  179
Line:  
CommentType:  TR

Comment:  
Currently, no mentioning is made to the peer-to-peer scenario, thus conflicting Sub-clause 10.1.1, Page 177, lines 25-26 (which specifies both peer-to-peer and broadcast communications); this should be corrected.
CommentEnd:  

SuggestedRemedy:  
Item 2 should make more precise what is meant by a 'group' of piconet devices. As a minimum, this should include peer-to-peer (end-to-end) communication, and broadcasting. Ideally, this should include multicasting to any subset of the devices that constitute the piconet.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1803
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  2.3
Page:  179
Line:  
CommentType:  TR

Comment:  
The current wording is not stated as a time-invariant property and does not cover the admission of child and neighbor piconets. Moreover, it conflicts with the intended operation described in Sub-clause 10.3.4.2.1 (Page 185, lines 11-13), since there unauthenticated devices are only denied time-slots and not denied association per se. Last, but not least, the security requirement should not specify which device (here, the PNC) should regulate the admission policy; this should rather depend on the role(s) associated with the devices (as elaborated upon in Sub-clause 10.3.2).
CommentEnd:  

SuggestedRemedy:  
Change Item 1 to the following: 'Joining of authenticated entities only. At any given moment of time, effective admission of an entity to the piconet (authenticated association) must be based upon evidence regarding its true identity and proof that the device itself corroborated this evidence. Here, effective admission refers to allocation of time slots to an associated device, and distribution of keying material hereto.'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1805
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  179
Line:  4142
CommentType:  TR

Comment:  
For the security architecture, the mapping between devices and their roles is essential. The security events trigger actions depending upon the role of a device. Without this role model, the security architecture is completely inflexible and security policy cannot be described correctly. Given the importance of this role model, rated this comment as a TR rather than 'Editorial' only.
CommentEnd:  

SuggestedRemedy:  
Replace 'security assumptions and' by 'security assumptions, a classification of devices according to role(s) these assume, and'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1808
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  11
CommentType:  E

Comment:  
Add the following sentence 'For details, we refer to Item 3 of 10.1.2.'
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1807
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  13
CommentType:  E

Comment:  
Add the following (informative) sentence hereafter: 'The actual procedure by which public key pairs are generated has important practical consequences, since it determines to what extent devices can be re-initialized after manufacturing and influences the level of trust required in the external trusted party. A more detailed discussion is beyond the scope of this document.'
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1809
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  20
CommentType:  E

Comment:  
The wording 'validity' implies a judgement. A mere enumeration is all that is needed here.
CommentEnd:  

SuggestedRemedy:  
Replace 'The following roles of DEVs are valid within the piconet setting' by 'One distinguishes the following roles of entities within the piconet setting'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1810
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  25
CommentType:  TR

Comment:  
The potential mapping of security functionality to the PNC is addressed in Sub-clause 10.3.2.2, and should not be addressed here; moreover, other mappings are conceivable. Given the importance of separating the role(s) of devices from the actual implementation hereof and avoiding confusion here, this comment is rated TR rather than 'Editorial' only.
CommentEnd:  

SuggestedRemedy:  
Delete the complete sentence 'The security manager shall be hosted by the current PNC'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1806
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  3
CommentType:  E

Comment:  
Replace '10.3.1.1' by 'see 10.3.1.1'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1811
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  3133
CommentType:  TR

Comment:  
The potential mapping of security functionality to the PNC is addressed in Sub-clause 10.3.2.2, and should not be addressed here; moreover, other mappings are conceivable. Given the importance of separating the role(s) of devices from the actual implementation hereof and avoiding confusion here, this comment is rated TR rather than 'Editorial' only.
CommentEnd:  

SuggestedRemedy:  
Delete the complete sentence 'The PNC hosts … security manager.'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1812
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  34
CommentType:  TR

Comment:  
The question whether this role is present in the piconet or not depends on the mapping of roles to devices and is addressed in Sub-clause 10.3.2.2, and should not be addressed here. Given the importance of separating the role(s) of devices from the actual implementation hereof and avoiding confusion here, this comment is rated TR rather than 'Editorial' only.
CommentEnd:  

SuggestedRemedy:  
Change 'If present, this entity ensures' by 'This entity is the sole source that ensures'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1813
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  41
CommentType:  E

Comment:  
Replace 'Since this standard address PANs' by 'Since this standard addresses communications between WPAN-enabled devices and -entities only'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1814
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  181
Line:  45
CommentType:  E

Comment:  
Item 2 of the current paragraph (on PNCs) confuses the role model with the mapping of roles to devices (as addressed in Section 10.3.2.2) and violates the security invariant formulated in the security model (as discussed in Section 10.3.2.2). Given the importance of separating the role(s) of devices from the actual implementation hereof and given the importance of sticking to a carefully defined security policy and avoiding any confusion here, a total rewrite of this paragraph is required.
CommentEnd:  

SuggestedRemedy:  
Replace this entire paragraph by a more appropriate text as follows:The role model is motivated as follows:1.	The roles in the security model are formulated in such a way as to allow a distributed implementation. In particular, there might be more than 1 piconet controller, more than 1 security manager, and more than 1 external trusted party. What is important is that these roles may conceptually be thought of as being centralized.2.	The roles in the security model are independent of the way these are actually implemented. In particular, this means that different roles may be implemented in a single device. An example of the latter would be the creation of a single device that assumes both the role of piconet controller and that of security manager.3.	The roles in the security model are separated from the actual devices that assume these roles, thus allowing for a dynamic mapping of roles to devices. An example of the latter would be changes to the piconet controller and to the security manager.4.	The roles in the security model are separated from the actual devices that assume these roles, thus allowing different devices to associate different roles with the same device, depending on their individual view on the role(s) this particular device should play. An example of the latter would be a device that assumes the role of security manager for one device and that of ordinary device for another device.5.	The piconet controller (PNC) need not be fixed in time and space. Since the device that is assigned the role of PNC might vary over time, it is not convenient to a priori assign any security functionality to it (for otherwise, trust might need to be established over and over again, at each change of PNC).6.	The external trusted party is assumed to be the sole source of global trust, since it is a party that is external to the network and might have facilities that are deemed necessary for proper key management (e.g., secure key generation facilities, proper authentic storage of keying material, availability, etc.).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1817
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  182
Line:  4046
CommentType:  TR

Comment:  
Without this additional sentence, the effect of composite security events is not defined.
CommentEnd:  

SuggestedRemedy:  
Add the following sentence hereafter: 'Simultaneous changes of the group structure and of the role are conceptually thought of as to take place subsequently, e.g., if the current PNC simply vanishes, this can be thought of as to have occurred in the order 'change role to ordinary device'; 'vanish'.'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1815
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  182
Line:  41
CommentType:  E

Comment:  
Replace 'exclusion' by 'to the exclusion'. Similarly, replace 'An example is' by 'An example hereof is'.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1816
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  182
Line:  45
CommentType:  TR

Comment:  
The current wording does not cover a device that will assume the (for him new) role of PNC.
CommentEnd:  

SuggestedRemedy:  
Replace 'a change of role of the PNC' by 'a role change from PNC to ordinary device, or vice versa'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1820
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  183
Line:  4
CommentType:  E

Comment:  
Add the following (informative) sentence hereafter: 'Compliance with the key storage rule rests upon 'benign' devices implementing this rule; it cannot be enforced upon devices. This provided yet another reason that the security rule should be strictly adhered to.'
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1818
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  183
Line:  9
CommentType:  E

Comment:  
This illuminates that a change of role as PNC to that of ordinary device (rather than the other way around).
CommentEnd:  

SuggestedRemedy:  
Replace 'PNC hand over' by 'PNC hand over (sign out)'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1819
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  183
Line:  9
CommentType:  TR

Comment:  
Currently, this security relevant event is lacking; this should be corrected.
CommentEnd:  

SuggestedRemedy:  
5Add the following item hereafter: '(2) PNC takeover (sign in). This refers to an alternate PNC device assuming the role of piconet controller'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1824
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  185
Line:  17
CommentType:  TR

Comment:  
Each of the communicating parties should provide evidence that it corroborated evidence regarding its true identity itself.
CommentEnd:  

SuggestedRemedy:  
Replace 'public keys' by 'public keys and evidence that each of these parties have access to the corresponding private keys'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1825
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  185
Line:  3032
CommentType:  TR

Comment:  
The current text does not cover the consequences of the execution of an authentication protocol.
CommentEnd:  

SuggestedRemedy:  
Include the following paragraph hereafter:  "The piconet controller will reject any commands other than an authentication request from associated devices for which the authentication protocol was not completed successfully. It will accept any commands from a positively authenticated device."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1826
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  185
Line:  47
CommentType:  TR

Comment:  
This is an obvious error in the current text.
CommentEnd:  

SuggestedRemedy:  
Replace 'piconet' by 'piconet controller'.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1827
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3
Page:  186
Line:  67
CommentType:  E

Comment:  
Include the following text herefore: "Special attention should be given to the fact that not all communication might be realized online, since one cannot assume that all devices are aware of each other (dormant mode)."
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1821
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3.3.3
Page:  184
Line:  36
CommentType:  TR

Comment:  
In the current draft, a change of PNC unnecessarily triggers a re-authentication procedure. This expensive (!) procedure is not required by the security policy, since the role change does not invoke a change to the key-sharing group, and should therefore be skipped. Granted, I also first thought otherwise. One can explain the phenomenon as follows in a more informal way. If one has a PNC hand over and encryption is on, the only devices that can read encrypted traffic are those that already had been authenticated by the previous PNC (otherwise, they had no way of getting any keying material, except by 'force' (breaking open the supposedly trusted module). Hence, one can safely continue broadcasting messages using these keys, since only those previously already authenticated devices can read traffic. If only authentication is on, then things might get tricky, since it depends on the proper and authentic hand over of the list of authenticated devices from the old PNC to the new one (This is handled in Sub-clause 10.3.4.2.3). To avoid confusion and violation of the security policy, a total rewrite of this paragraph is required.
CommentEnd:  

SuggestedRemedy:  
Replace this entire sub-clause by a more appropriate text as follows:'We consider the effect of changes to the roles of devices in the scenario where information shared between members of a group is secured via a common (symmetric) group key.A change of the role of the piconet controller due to a PNC hand over has no effect on the group structure, so it does not impact the group key.'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1829
CommenterName:  Rasor, Gregg
CommenterEmail:  Gregg.Rasor@motorola.com
CommenterPhone:  (561) 739-2952
CommenterFax:  
CommenterCo:  Motorola
Clause:  10
Subclause:  3.4.2.3
Page:  186
Line:  2538
CommentType:  TR

Comment:  
In the current draft, the change of PNC automatically triggers a re-authentication procedure. This (expensive!) re-authentication procedure is not required by the security policy (10.3.3), since the role change does not invoke a change to the key-sharing group, and should therefore be avoided altogether.
CommentEnd:  

SuggestedRemedy:  
Replace this entire sub-clause by a more appropriate text as follows:"A change of piconet controller is based on the election of an alternate piconet controller.The parting piconet controller transfers the list of authenticated piconet devices to the new piconet controller. If this list is received in proper order, the new piconet controller will take this list as to represent the authenticated devices in the piconet and will act accordingly. Hence, it will reject any commands other than an authentication request from associated devices that are not listed as being authenticated and it will accept any commands from a device that is listed as being authenticated. If this list of authenticated devices is not received properly, e.g., if the parting piconet controller has vanished, all devices must be assumed to be unauthenticated, thus requiring the piconet controller to engage in the same communications as described in §10.3.4.2.1 and re-authenticate each of the other devices in the piconet."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/21/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  764
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  10
Subclause:  all
Page:  177
Line:  
CommentType:  TR

Comment:  
Security, to protect artistic intellectual property of rich multimedia content, is key to the widespread adoption of 802.15.3 in a multiplicity of home consumer products. This draft does not provide a default baseline encryption algorithm through which different implementations of 802.15.3 can securely communicate. It is important that a single baseline algorithm be selected. Multiple options, increasing the cost of implementation, can not replace a default system.
CommentEnd:  

SuggestedRemedy:  
choose a baseline security algorythm.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  742
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  10
Subclause:  all
Page:  177
Line:  
CommentType:  TR

Comment:  
Three equally key promises of 15.3 are high bandwidth, low cost and low power consumption.  Of these, high bandwidth is the key differentor, opening the door to the possibility of rich multimedia applications. However, rich multimedia brings with it a strong requirement for high security (to protect enhanced digital video  content). 15.3 does not yet specify a security system with assured interoperability between implementations. Without assured interoperable security, the usefulness of 15.3 for transporting protected digital content in a consumer environment will be severely limited.
CommentEnd:  

SuggestedRemedy:  
A default (single) encryption system must be unambiguously specified. Additional encryptions options are acceptable.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  85
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  10
Subclause:  NA
Page:  0
Line:  0
CommentType:  T

Comment:  
Security description seems to be incomplete.
CommentEnd:  

SuggestedRemedy:  
Complete description of security interoperation for all of the designated security options that will be supported.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1723
CommenterName:  Rofheart, Martin
CommenterEmail:  Martin@xtremespectrum.com
CommenterPhone:  703-269-3007
CommenterFax:  240-463-3306
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
The coexistence mechanisms for the TG3 2.4 GHz are lacking.
CommentEnd:  

SuggestedRemedy:  
Refer to the remedy indicated by Rick Roberts
RemedyEnd:  

Response:  
PROPOSED ACCEPT. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt. Also see resolution of 1254.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  782
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  11
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
As we experienced at the ballot for 802.15.1, coexistence description need to be approached.  802.15.3 will not be an exception as far as we have 2.4GHz PHY.
CommentEnd:  

SuggestedRemedy:  
Need technical description for coexistence solution such as Dynamic Frequency Seleciton.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1249
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.1
Page:  187
Line:  27
CommentType:  T

Comment:  
Need to complete reference to clause 6.6.1
CommentEnd:  

SuggestedRemedy:  
The regulatory domains are enumerated in a vector called PHYPIB_RegDomainSupported (6.6.1) and are indicated by the parameter PHYPIB_CurrentRegDomain.  The domains are mapped to PHYPIB_CurrrentRefDomain as 0x00=Europe, 0x003=Japan, 0x01=USA and 0x02=Canada.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. Use this text:

The regulatory domains are enumerated in a vector called PHYPIB_RegDomainSupported (6.6.1) and are indicated by the parameter PHYPIB_CurrentRegDomain.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  424
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.1
Page:  187
Line:  42
CommentType:  T

Comment:  
Add 15.247 to the list of applicable US standards if the NPRM for digital modulation is approved.
CommentEnd:  

SuggestedRemedy:  
Add ", 15.247" at the right location.
RemedyEnd:  

Response:  
REJECT. The R&O has not been completed.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1257
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2
Page:  188
Line:  1
CommentType:  T

Comment:  
It was suggested previously in this letter ballot that the following items be PHY dependent.  They should be added to clause 11.2.
CommentEnd:  

SuggestedRemedy:  
11.2.9 MaxTransferUnitSize 11.2.10 MinSuperFrameDuration 11.2.11 MaxSuperframeDuration
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. 11.2.10 MinSuperFrameDuration 11.2.11 MaxSuperframeDuration

Note: MaxTransferUnitSize is a MAC to LLC description.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  272
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  11
Subclause:  11.2.1
Page:  188
Line:  67
CommentType:  E

Comment:  
The word "jurisdictions" is not advisable.
CommentEnd:  

SuggestedRemedy:  
I recommend the sentence "...jurisdictions that have allocated this band." be replaced with "...regulatory bodies that have designated this band.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1250
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.1
Page:  188
Line:  7
CommentType:  T

Comment:  
Add the following text.
CommentEnd:  

SuggestedRemedy:  
As indicated by Table 41, this is PHYPIB_Type value 0x00.
RemedyEnd:  

Response:  
PROPOSED REJECT. This information in already defined in clause 6. Does not need to be defined in two different places.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1251
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.2
Page:  188
Line:  12
CommentType:  TR

Comment:  
Clause 11.2.2 is misleading for deployment within the USA.  FCC Regs 15.249 indicate that the measurement of interest is 50 uV/meter at 3 meters; hence, just measuring at the antenna input is not conclusive.  If the power level is reduced by the amount of the maximum antenna directional gain then this is accurate.  Also, assuming a 0 dBi antenna is ok but a cop out.  For example, if the antenna is very inefficient (lossy) then you can actually increase the RF input power to the antenna to compenate for the antenna loss since the type acceptance metric is field strength measurements.
CommentEnd:  

SuggestedRemedy:  
A note needs to be added that indicates the implementor needs to refer to the rules of the country of deployment since type acceptance testing may require field strength measurements that are not the same as antenna input power.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change "power measurement," to "power measurement for the purpose of this standard,"
Also, 11.5.9 already states that the transmit power shall conform and be measured as defined by regulatory bodies.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1745
CommenterName:  Chen, Kwang-Cheng
CommenterEmail:  kc@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 668
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  
CommentType:  TR

Comment:  
The 2.4 GHz coexistence issue is not fully and clearly addresse
CommentEnd:  

SuggestedRemedy:  
Please address the coexistence issue/mechanism clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1754
CommenterName:  Chen, Hung-Kun
CommenterEmail:  hkchen@inprocomm.com
CommenterPhone:  +886-3-516-5106 ext 661
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  
CommentType:  TR

Comment:  
The 2.4 GHz coexistence issue is not fully and clearly addresse
CommentEnd:  

SuggestedRemedy:  
Please address the coexistence issue/mechanism clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1771
CommenterName:  Maa, Yeong-Chang
CommenterEmail:  ycmaa@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 201
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  
CommentType:  TR

Comment:  
The 2.4 GHz coexistence issue is not fully and clearly addresse
CommentEnd:  

SuggestedRemedy:  
Please address the coexistence issue/mechanism clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1789
CommenterName:  Liu, Shawn
CommenterEmail:  shawnliu@inprocomm.com
CommenterPhone:  +886-3-5165106 ext 865
CommenterFax:  
CommenterCo:  InProComm, Inc.
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  
CommentType:  TR

Comment:  
The 2.4 GHz coexistence issue is not fully and clearly addresse
CommentEnd:  

SuggestedRemedy:  
Please address the coexistence issue/mechanism clearly.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1253
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  18
CommentType:  T

Comment:  
The data in this section needs to be tied to the PHY PIB.  This can be done as shown below.
CommentEnd:  

SuggestedRemedy:  
PHYPIB_NumChannelsSupported = 3 or 5 (apparently it has two values)  PHYPIB_CurrentChannel=1 or 2 or 3 (or 4 or 5) as shown in first column of table 75.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Number of channels supported is 5. PHYPIB_Current Channel is CHNL_ID of the current channel. This is applied to table 93.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1252
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  18
CommentType:  TR

Comment:  
Clause 11.2.3 indicates there are two frequency plans.  What is the basis for picking one frequency plan over the other?  How is this selection made?  Is it done by the DME or is it done at manufacture time?  If it is done by the DME then how is having two frequency plans supported by the PLME and the PHY PIB?
CommentEnd:  

SuggestedRemedy:  
PHY group to comment and clarify.  Text may need to be generated for clause 11.2.3 to clarify.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. See resolution of 1109.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1254
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  18
CommentType:  TR

Comment:  
The table in clause 11.2.3 (Table 75) indicates an IEEE802.11b coexistence mode that puts the 802.15.3 transmissions directly on top of the 802.11b channels.  This is called coexistence mode.  I fail to understand how deliberately putting 15.3 transmissions on 802.11b channels is a coexistence mode.  Clause 11 needs a complete subsection that discusses coexistence with existing 802 PHY types in the 2.4 GHz band, especially given that the GTS slot assignments DO NOT listen before transmitting.  One suggestion is that even through a DEV has a GTS slot assignment, it still must listen before transmitting and reframe from transmitting if the channel is in use.  This "channel in use" data can be indicated back to the PNC by a command packet and the PNC can try to find a new channel.  The importance of coexistence, and the serious consideration being made by ExCom and SA, are exemplified by the comments that were generated by the first rejection of 802.15.1 by the SA.
CommentEnd:  

SuggestedRemedy:  
PHY committee to reconvene to work on coexistence mechanisms for 802.15.3 and supply text for letter ballot approval.  I'd withdraw this comment if the MAC and the PHY were split into two separate letter ballots.  Sample text can be found in TG4 draft text D13, in clauses 6.9.2 and 7.5.1.  These are copied below for reference.  6.9.2 802.15.4 2.4GHz as interferer The 802.15.4 devices have several characteristics that improves its coexistence with other wireless devices operating in the 2.4 GHz band. 802.15.4 devices are intended for low duty cycle applications (typically less than 1%) using CSMA/CCA mechanism for collision avoidance. Furthermore, it is defined to operate in two possible frequency bands (868/915 MHZ and 2.4 GHz). Finally, the low transmit power will minimize their effect on other 802.11/802.15 compliant devices.   7.5.1 Channel Access All devices must use the radio channel in such a way as not to obstruct the transmissions of other devices, which may already be transmitting. The mechanism for handling this requirement is called Carrier Sense Multiple Access - Collision Avoidance (CSMA-CA). A device wishing to transmit using CSMA-CA must first sense the channel for radio activity. If no activity is detected, the device may transmit. If activity is detected the device should back-off for some random period before beginning the CSMA-CA procedure again. A device that senses activity on the channel, repeatedly, a specified number of times may not transmit its message regardless but should consider its transmission attempt a failure. All transmission should abide by the CSMA-CA channel access mechanism.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. See comment 1109 for resolution. The PAR will not allow us to split the MAC/PHY ballot. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt. Rick Roberts will be providing additional text.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  766
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  2027
CommentType:  TR

Comment:  
Co-existance is very important in consumer products (refer ). While an alternate frequency plan, to enhance co-existance, is interesting, there seems to be no mechanism for automatically choosing a fewquency plan. Without some guidance in this area, it can not be said with assurance that an implementation conforming to this draft standard will have any degree of success in increasing co-existance.   Thus draft fails to meet an important and self proclaimed goal.
CommentEnd:  

SuggestedRemedy:  
Unfortunately, this comment is prepared while the deadline for comments draws near, preventing the extensive drafting required for an adequate solution.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  425
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.2.3
Page:  188
Line:  27
CommentType:  T

Comment:  
The current cnannel arrangement cannot be use with the TX PSD in under US 15.249 rules.  Ignore this if the 15.247 NPRM on digital modulation reaches report and order.
CommentEnd:  

SuggestedRemedy:  
Change the channel locations to the following frequencies, 2412, 2432, 2442, 2451 and 2461, all in MHz.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1255
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.5
Page:  188
Line:  44
CommentType:  T

Comment:  
Temperature Range ... seems ok for in the house but how about outside deployment, such as a PDA that has been lying in a car.
CommentEnd:  

SuggestedRemedy:  
PHY committee to consider increasing range from -20 to +40, or some suitable range given outside deployment.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  This was considered in detail by the committee, and the current values reflect the appropriate minimum requirements without adding excessive cost to all 802.15.3 implementations. This is the type I temperature range of 802.11b.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  426
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.2.6.1
Page:  189
Line:  8
CommentType:  T

Comment:  
Need to add a definition for RIFS
CommentEnd:  

SuggestedRemedy:  
Add a row to the table that has:  RIFS   aCCADetectTime + aRXTXTurnaroundTime   11.6.5 and 11.2.6.2
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add a row to the table that has:  RIFS   aCCADetectTime + aPHYSIFSTime in table 76   11.6.5 and 11.2.6.2.
APHYSIFSTime = 10 us to be defined in table 76.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1256
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.6.3
Page:  189
Line:  23
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
remove the hypen in the word "transmitted"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1621
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.6.3
Page:  23
Line:  
CommentType:  E

Comment:  
trans-mitted should not be hyphenated.
CommentEnd:  

SuggestedRemedy:  
unhyphenate.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1622
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.2.8
Page:  189
Line:  37
CommentType:  T

Comment:  
Details of the HCS should be provided to the level that they are in 7.2.8.
CommentEnd:  

SuggestedRemedy:  
Add CRC details here.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.   The IEEE would rather us use this by reference instead of duplicating the same information in multiple standards.
Include text and figure from 18.2.3.6 in 802.11b-1999.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  427
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.3
Page:  189
Line:  49
CommentType:  E

Comment:  
Add a reference for trellis coding here.
CommentEnd:  

SuggestedRemedy:  
Add a bibliograph reference following "with Trellis coding."  The reference is: Gottfried Ungerboeck, "Channel Coding with Multilevel/Phase and Signals", IEEE Trans. on Information Theory, Vol 28 January 1982.  Put this in the bibliography.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1258
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.3
Page:  190
Line:  3
CommentType:  TR

Comment:  
Add the following text at the end of the paragraph.
CommentEnd:  

SuggestedRemedy:  
The data rates are respectively the entries to the PHYPIB_DataRateVector.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  273
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  11
Subclause:  11.3.2
Page:  190
Line:  22
CommentType:  E

Comment:  
The words "air medium" are not advisable.
CommentEnd:  

SuggestedRemedy:  
I recommend the sentence ending "...through the air medium." be replaced with "through the common air interface."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1260
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.3.3
Page:  191
Line:  26
CommentType:  E

Comment:  
Rewite part of the sentence as shown below.
CommentEnd:  

SuggestedRemedy:  
In the table, the term +jw shall be defined ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  274
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  11
Subclause:  11.3.3
Page:  191
Line:  29
CommentType:  E

Comment:  
The following sentence does not end in a period: determined relative to the phase of the last symbol in the CAZAC sequence, 11.4.2
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1261
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.3.4
Page:  192
Line:  45
CommentType:  TR

Comment:  
Missing Figure reference
CommentEnd:  

SuggestedRemedy:  
... in Figure 99 and Figure 100, respectively.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  849
CommenterName:  Kleindl, Guenter
CommenterEmail:  guenter.kleindl@siemens.at
CommenterPhone:  43 51707 35738
CommenterFax:  
CommenterCo:  Siemens
Clause:  11
Subclause:  11.3.4
Page:  192
Line:  4546
CommentType:  E

Comment:  
missing figure number
CommentEnd:  

SuggestedRemedy:  
replace 'Figure and Figure 100' by 'Figure 99 and Figure 100'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1262
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.3.4
Page:  192
Line:  47
CommentType:  E

Comment:  
We have a formatting problem on some symbol scripts.  The same problem is in line 47, line 51, 52, and 53.
CommentEnd:  

SuggestedRemedy:  
Reformat math symbols.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  428
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.3.4
Page:  198
Line:  47
CommentType:  E

Comment:  
Is the QPSK-TCM 8-state or 4-state TCM?
CommentEnd:  

SuggestedRemedy:  
Change description to 4-state if it is true (and throughout clause 11).  Otherwise leave it alone.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1735
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  11
Subclause:  11.4.1
Page:  200
Line:  10
CommentType:  T

Comment:  
Tail symbols are not used for all modulation types
CommentEnd:  

SuggestedRemedy:  
Finish the first paragraph by saying "if necessary".
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1736
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  11
Subclause:  11.4.1
Page:  200
Line:  46
CommentType:  E

Comment:  
Repetition of the PHY and MAC header is not explained in the text. Also it is not clear that 22 Mbps DQPSK modulation applies to the second repetition of the PHY and MAC header in figure 108.
CommentEnd:  

SuggestedRemedy:  
See the comment
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  429
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.4.1
Page:  200
Line:  6
CommentType:  T

Comment:  
The frame format shows and refers to the HCS as separate from the MAC header, but in clause 7 and most of the rest of clause 11, the HCS is considered to be part of the MAC header.
CommentEnd:  

SuggestedRemedy:  
Lots of changes here either way.  If we change the MAC header definition to exclude the HCS, we need to update other spots in clause 11.  Otherwise, the following modifications need to be made in 11.4.1:  Change "and appends this to the" to be "and inserts this into the end of the" in line 7, page 200 and change "and is appended this to the combined PHY and MAC" to be "and is inserted into the end of the MAC" in line 7, page 201.  Change the MAC Header boxes to be MAC Header - HCS for the first two rows of figures 107 and 108.  Delete the HCS boxes and + HCS in the other rows.  Change "Calculate HCS" to be "Calculate and insert HCS" in one place in each figure 107 and figure 108.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change Figure 11 so that the MAC header does not include the HCS. In Figure 107 and 108, show the dummy HCS being passed down. Add the word insert as mentioned in the SuggRemedy. Change occurrances of MAC Header in clause 11 to be MAC Header + HCS as appropriate. E.g., change append to be insert into the dummy HCS field received from the MAC.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1623
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.4.1
Page:  201
Line:  
CommentType:  T

Comment:  
Sending the header twice raises some interesting questions:  What if the preamble is incorrect?  Does the PHY then always look at the payload to see if there is a 11 Mbps header?  If not, what is the purpose?
CommentEnd:  

SuggestedRemedy:  
Detail how the second header is processed.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Text needs to be added in clause 11 to clarify how dual headers are processed. If either correct, correct one passed up.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1624
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.4.1
Page:  201
Line:  1
CommentType:  T

Comment:  
What does the length field cover - the frame body, but not the second header?
CommentEnd:  

SuggestedRemedy:  
Clarify what the length field covers.  The additional header time must be accounted for by the MAC in calculating channel time.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add a table as an illustrative example of the length to be expected for all PHY data rates in clause 11. James Gilb will provide.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  430
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.4.2
Page:  201
Line:  3
CommentType:  T

Comment:  
Forgot to indicate that the header is repeated twice.
CommentEnd:  

SuggestedRemedy:  
Change "and MAC header, followed by" to be "and MAC header at the base rate, followed by a copy of the PHY and MAC header modulated at 11 Mb/s QPSK-TCM, followed by"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  431
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.4.3
Page:  202
Line:  35
CommentType:  T

Comment:  
The MAC header includes the HCS
CommentEnd:  

SuggestedRemedy:  
Change 3 occurances of "MAC header and the HCS" to be "MAC header" on lines 35, 37 and 38.
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1737
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  11
Subclause:  11.4.4
Page:  203
Line:  3
CommentType:  E

Comment:  
Figure 110 should be cleaned up .
CommentEnd:  

SuggestedRemedy:  
See the comment.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  275
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  11
Subclause:  11.4.5
Page:  204
Line:  13
CommentType:  E

Comment:  
The following sentence does not end in a period: defined in Table 82
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  432
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.4.5
Page:  204
Line:  18
CommentType:  T

Comment:  
Change the encoding of the frame body length to be sent LSb first in b5 with the MSb at b15.
CommentEnd:  

SuggestedRemedy:  
Change as indicated and change the examples as well.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1266
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.4.6
Page:  204
Line:  50
CommentType:  E

Comment:  
grammatical ... remove the "s" from the end of the word symbols as shown below.
CommentEnd:  

SuggestedRemedy:  
... of the bits/symbol that is to be used ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1267
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.4.7
Page:  205
Line:  7
CommentType:  E

Comment:  
add a definitive article as shown below
CommentEnd:  

SuggestedRemedy:  
... added to the end of the frame body ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1268
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.4.7
Page:  206
Line:  31
CommentType:  T

Comment:  
remove the phrase "2 and 3"
CommentEnd:  

SuggestedRemedy:  
... higher order bits, ...
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1269
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.4.7
Page:  206
Line:  31
CommentType:  E

Comment:  
Refomatting of math scripts
CommentEnd:  

SuggestedRemedy:  
The math scripts in lines 31 and 33 are in need of reformatting.  Some of the symbols appear to be "chopped off".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  433
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.4.7
Page:  206
Line:  34
CommentType:  T

Comment:  
While the trellis state is independent of the other bits, the symbol selection isn't.  Since it probably easier to find known symbols, lets define the last inputs as all zeros to the non-TCM portion.
CommentEnd:  

SuggestedRemedy:  
Indicate that the other bits (i.e. those not determined by the trellis encoder) shall be chosen to be 0 for the symbol selection.
RemedyEnd:  

Response:  
PROPOSED REJECT.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  434
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.4.7
Page:  207
Line:  44
CommentType:  T

Comment:  
The BPSK mode no longer exists.
CommentEnd:  

SuggestedRemedy:  
Delete the sentence "For the BPSK modulation, ... over the air."
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1271
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.5.2
Page:  209
Line:  14
CommentType:  T

Comment:  
This clause deals with the EVM.  Measurements are made on a "reference receiver".  It is well known that a reciever can cause EVM problems as well as the transmitter, so how does one define this "reference receiver"?  Do you deconvolve the EVM distortion caused by the receiver?
CommentEnd:  

SuggestedRemedy:  
PHY committee to comment on how a reference receiver is to be used.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Change 'reference receiver" to "ideal reference receiver" where used in clause 11.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  435
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.5.2
Page:  209
Line:  27
CommentType:  T

Comment:  
Should add EVM requirement for QPSK-TCM explicitly
CommentEnd:  

SuggestedRemedy:  
Change "DQPSK" to be "DQPSK/QPSK-TCM" in Table 87.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  436
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.5.9
Page:  210
Line:  51
CommentType:  T

Comment:  
It is not the standards job to require conformance to governmental regulations.
CommentEnd:  

SuggestedRemedy:  
Change "devices shall also" to "devices should also"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  276
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  11
Subclause:  11.5.9
Page:  211
Line:  19
CommentType:  E

Comment:  
The following sentence does not end in a period: The minimum TX power level required to support TPC, aMinTPCLevel, shall be 4 dBm
CommentEnd:  

SuggestedRemedy:  
Add the period.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1272
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.6.1
Page:  211
Line:  25
CommentType:  E

Comment:  
Replace "an" with "a"
CommentEnd:  

SuggestedRemedy:  
... less than 8% with a frame body ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1363
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  11
Subclause:  11.6.4
Page:  212
Line:  
CommentType:  TR

Comment:  
In Table 91 the adjacent channel rejection is only 0 dB, when running at 55 Mb/s.  This means that if the interferer, in an adjacent channel, is closer to the receiver than the source, then the receiver will not work.  I think this level of adjacent channel rejection is insufficient. This makes operation of multiple TG2 WPANs in the same area impractical. As a reference point, the IEEE 802.11b adjacent channel rejection, operating at 11 Mb/s is 35 dB.
CommentEnd:  

SuggestedRemedy:  
Increase the adjacent channel rejection, for all data rates, by 20 dB.
RemedyEnd:  

Response:  
PROPOSED REJECT. These performance requirements are roughly similar to 802.11a and are consistent with our low-cost target.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  437
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  11
Subclause:  11.6.4
Page:  212
Line:  51
CommentType:  T

Comment:  
Need formal langauge for the jamming requirements.
CommentEnd:  

SuggestedRemedy:  
Change "signal is to be" to be "signal shall be"
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1738
CommenterName:  Karaoguz, Jeyhan
CommenterEmail:  jeyhan@broadcom.com
CommenterPhone:  949 585 6168
CommenterFax:  
CommenterCo:  Broadcom Corp.
Clause:  11
Subclause:  11.6.5
Page:  213
Line:  9
CommentType:  T

Comment:  
The modes CCA detection should be clearly enumerated. It is not clear what constitutes CCA.
CommentEnd:  

SuggestedRemedy:  
Use the 802.11b CCA detection template in the standard.
RemedyEnd:  

Response:  
PROPOSED REJECT.  There is only one CCA mode.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1278
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.7
Page:  213
Line:  
CommentType:  T

Comment:  
Additional note to clause 11.7
CommentEnd:  

SuggestedRemedy:  
The items of Table 50 are implmentation dependent.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy objects from table 50 to table 93 with values implementation dependent.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1276
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.7
Page:  213
Line:  36
CommentType:  T

Comment:  
Need to supply mapping for TX power as per the text written in clause 6.6.4 and indicated in table 44.
CommentEnd:  

SuggestedRemedy:  
PHY committee to supply.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Copy objects from Table 44 and use implementation dependent as the values and use the mapping from the frame format.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1275
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.7
Page:  213
Line:  36
CommentType:  T

Comment:  
addition to clause 11.7
CommentEnd:  

SuggestedRemedy:  
Add the following text ...  Antenna diversity is an implementation specific issue.  For the PHY description of clause 11, it has been assumed that there is no diversiy; that is, PHYPIB_DiversitySupported has a value of one.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Add PIB parameter PHYPIB_DiversitySupported with value implementation dependent.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1277
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  11.7
Page:  213
Line:  36
CommentType:  TR

Comment:  
Need a note added to clause 11.7 to indicate that ranging is not supported by this PHY.
CommentEnd:  

SuggestedRemedy:  
11.7.x Ranging  The PHY description of clause 11 does not support the PHY PIB ranging group of clause 6.6.9.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. PHYPIB_Range in Table 93 is implementation dependent. Note that implementation is not specified for this PHY.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1355
CommenterName:  Seals, Michael
CommenterEmail:  mseals@intersil.com
CommenterPhone:  (321) 724-7172
CommenterFax:  
CommenterCo:  Intersil
Clause:  11
Subclause:  6.5
Page:  213
Line:  13
CommentType:  TR

Comment:  
I don't see any effort made to coexist with other 802 wireless standards or proposed standards in the 2.4 GHz band, other than selecting operation on 802.11b channels.  CCA done by ED alone requires a signal 20 dB above the minimum sensitivity defined in 11.6.2.  I do not believe this is sufficient for coexistence.  Coexistence should be a requirement, not a goal.
CommentEnd:  

SuggestedRemedy:  
Develop a method for coexistence with other 802 wireless standards in the 2.4 GHz band.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. See 00000r0P802-15-3-Annex_Coexistence.pdf and 02041r2P802-15_TG3-Coexistence-capabilities.ppt
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1264
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Equation 7
Page:  203
Line:  21
CommentType:  TR

Comment:  
Is this equation correct.  It does not seem to match Figure 110.  Figure 110 shows Xn as not being the quantity that bn is xor'ed with.
CommentEnd:  

SuggestedRemedy:  
Verify that the notation between Equation 7 and Figure 110 are correct.  Correct as needed.  Refer this to the PHY committee.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The figure does not reflect the equation. The figure will be corrected to reflect the equation.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/23/2002
DispatchDate:  
WrittenDate:  1/23/2002
Accept_RejectDate:  1/23/2002
Closed_UnsatisfDate:  1/23/2002
VoterStatus: 

-----------
CommentID:  1263
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Figure 110
Page:  203
Line:  
CommentType:  T

Comment:  
Add lables that help clarify equation 7
CommentEnd:  

SuggestedRemedy:  
Input serial data = bn  Output serial data = sn  add bn and sn to the figure.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  271
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  11
Subclause:  Table 74
Page:  187
Line:  14
CommentType:  T

Comment:  
The 802.15.3 PAR Purpose states: "The data rate will be high enough, 20 Mbps or more...".  I am still unclear why the QPSK modulation type for 11 Mb/s is allowable.  Additionally, the subclause 11.3.1, page 190, line 14-15 sentence "The QPSK-TCM mode is implemented in assigned GTS slots to help maintain connections of devices that are in range of the PNC, but which may be more distant from each other." suggests that the 11 Mb/s is used to make the WPAN a WLAN.
CommentEnd:  

SuggestedRemedy:  
Please advise the WG and/or myself why an 11 Mb/s is part of the IEEE Std 802.15.3 and why the 802.15.3 PAR does not require a corrigendum to allow this fifth type.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. We are only required to provide at least 20Mbps, other data rates are acceptable. Base mode of the 2.4GHz PHY is 22 Mbps which satisfies the PAR. The mode is provided to allow devices on opposite sides of the PNC coverage range to directly communicate.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1109
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 75
Page:  188
Line:  
CommentType:  TR

Comment:  
Table 75 shows two frequency plans.  How does a DEV know which frequency plan to use with a Piconet?  Is there a default frequency plan?  How does the PNC change the frequency plan if the 802.11b coexistence is needed?
CommentEnd:  

SuggestedRemedy:  
Refer to PHY subcommittee.  There will have to be commands added to the MAC to accommodate frequency plan switching.  Also, since the only frequencies in common are 2.408 and 2.468 GHz, all Piconets will have to start on one of these two frequencies and then switch to either the 5 frequency plan or the 3 frequency plan.
RemedyEnd:  

Response:  
ACCEPT IN PRINCIPLE. Document 02/041includes addional discussion of how to apply the frequency plans when 802.11b networks are detected. The MLMEScan and MLMEStart commands include selection of channel sets to utilize. Since a channel set is scanned completely, it does not matter on which channel that scan starts. Piconets are only started once the scans are completed and a determination of channel status has been obtained.
There is no default frequency plan.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1620
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 76
Page:  189
Line:  5
CommentType:  TR

Comment:  
aRXTXTurnaroundTime is a range.  I am not sure how SIFS can be a range..
CommentEnd:  

SuggestedRemedy:  
Specify if SIFS is a range.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.

Change aRXTXTurnaroundTime in Table 76 to be aPHYSIFSTime (See resolution of 426). Delete reference to aRXTXTurnaroundTime in 11.6.2 and any other occurances in the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1259
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 77
Page:  191
Line:  
CommentType:  E

Comment:  
Last three Kmod values are missing the left bracket.
CommentEnd:  

SuggestedRemedy:  
Supply left brackets as needed.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1265
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 82
Page:  203
Line:  
CommentType:  TR

Comment:  
In Table 82 we have the notation "Seed value".  Is this the same as Xinit in equation 6.  If so, then be consistent on names.  Pick one name for the other.
CommentEnd:  

SuggestedRemedy:  
PHY committee to review the comment.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Identify xinit as being the seed value.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1270
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 86
Page:  208
Line:  
CommentType:  E

Comment:  
Font problems in table 86 on the right two column headings
CommentEnd:  

SuggestedRemedy:  
Please reformat the headings in the right two columns.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1111
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 89
Page:  211
Line:  
CommentType:  T

Comment:  
Table 89 indicates that in the USA operation is under Part 15.249.  Given the changes in Part 15.247 (removal of processing gain) would this PHY qualify for operation under part 15.247?
CommentEnd:  

SuggestedRemedy:  
If part 15.247 is legal, increase the max output power in line 19 of page 211, clause 11.5.9.
RemedyEnd:  

Response:  
PROPOSED REJECT. 
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  Z
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  1273
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 93
Page:  214
Line:  
CommentType:  TR

Comment:  
Table 93 contains reference to two PHY PIB values that do not exist.  PHYPIB_NumbTxPowerLevels and PHYPIB_PowerLevelVector are not in clause 6.
CommentEnd:  

SuggestedRemedy:  
The available PHY PIB values that deal with TX power are listed in clause 6.6.4.  Table 93 needs to be regenerated using the PHY PIB values of clause 6.6.4.  Assigned to PHY committee.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Already resolved in 1276.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1274
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table 93
Page:  214
Line:  
CommentType:  TR

Comment:  
Addition to Table 93
CommentEnd:  

SuggestedRemedy:  
Add to table 93 PHYPIB_MPDULengthMax.  PHY committee to supply value information.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. In Table 47 change PHYPIB_MPDULengthMax to PHYPIB_FrameLengthMax and give it a value of aMaxFrameSize with a xref to 11.2.7 for the 2.4 PHY.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1619
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  11
Subclause:  Table75
Page:  188
Line:  28
CommentType:  T

Comment:  
Who makes the choice of which frequency plan to use?  The implementer or the user?
CommentEnd:  

SuggestedRemedy:  
Specify how the channel plan is chosen.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. Same resolution as in 1109.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1726
CommenterName:  McInnis, Michael D.
CommenterEmail:  michael.d.mcinnis@boeing.com
CommenterPhone:  435-865-2840
CommenterFax:  206-290-7758
CommenterCo:  The Boeing Company
Clause:  A
Subclause:  
Page:  229
Line:  
CommentType:  TR

Comment:  
Annex C Specification and Description Language (SDL) was not provided for voter comment and review.
CommentEnd:  

SuggestedRemedy:  
Povide Annex C content, SDL for voter comment and review
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  759
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  A
Subclause:  0
Page:  215
Line:  15
CommentType:  TR

Comment:  
Only receives from peer (does not send to peer).  Who then can send?
CommentEnd:  

SuggestedRemedy:  
change 'receiving' to 'receiving/sending'
RemedyEnd:  

Response:  
ACCEPT. 
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  438
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  A
Subclause:  A
Page:  215
Line:  40
CommentType:  T

Comment:  
Need to indicate that the intefaces described are only required if the interface is exposed.
CommentEnd:  

SuggestedRemedy:  
After the sentence ending "specified for 802.15.3" on line 18 add the following paragraph:   "If the SSCS-SAP interface is not exposed in an 802.15.3 device, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support the primitives described in this clause."
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1279
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.
Page:  215
Line:  
CommentType:  TR

Comment:  
Need consistent name for the Convergence Sublayer
CommentEnd:  

SuggestedRemedy:  
Let's use "sublayer".  On page 215 we have sublayer, sub layer, sub-layer, etc.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  34
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  A
Subclause:  A.0
Page:  215
Line:  1
CommentType:  T

Comment:  
This is a general comment for the Annex. It is noted that this annex is too standalone and doesn't provide tie in to the rest of the draft.
CommentEnd:  

SuggestedRemedy:  
Add xrefs as appropriate.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  278
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  A
Subclause:  A.1
Page:  215
Line:  1
CommentType:  E

Comment:  
The Annex Title "Service Specific Convergence Sub layer" is spelled wrong.  Also, the annex subclause numbering should start at the introduction or line 8.
CommentEnd:  

SuggestedRemedy:  
Change to "Service Specific Convergence Sublayer" and insert the word "Introduction" and use the paragraph tag AH1,A.1; forcing the A.1 to start.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  760
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  A
Subclause:  A.1
Page:  215
Line:  50
CommentType:  T

Comment:  
Only receives from peer (does not send to peer).  Who then can send?
CommentEnd:  

SuggestedRemedy:  
change 'receiving' to 'receiving/sending'
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1280
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.1.1
Page:  216
Line:  3
CommentType:  T

Comment:  
In line 3 we have "PDU" while in figure A.2 we show "SDU".  Is there an inconsistency here or is this OK.
CommentEnd:  

SuggestedRemedy:  
Refer to the MAC subcommittee
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  279
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  A
Subclause:  A.1.1
Page:  216
Line:  8
CommentType:  E

Comment:  
The word "Classification" should not be capitalized.
CommentEnd:  

SuggestedRemedy:  
Change word to lower case or "classification".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1281
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.2
Page:  217
Line:  1
CommentType:  TR

Comment:  
I'm confused about clause A.2 ... where are we at Figure A.1 ... are we at the SSCS SAP or at the MAC CPS SAP.  Please clarify.  Also, is there an inconsistency between clause A.2 and clause 6.8 on the names?
CommentEnd:  

SuggestedRemedy:  
Refer to MAC committee
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1282
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.2
Page:  217
Line:  12
CommentType:  E

Comment:  
Stray editor note
CommentEnd:  

SuggestedRemedy:  
Please remove the editorial note.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  439
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  A
Subclause:  A.2
Page:  217
Line:  12
CommentType:  E

Comment:  
Editorial comment left in.
CommentEnd:  

SuggestedRemedy:  
Delete the comment and apply the changes that are indicated (i.e. reformat the parameter definitions into a table).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  280
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  A
Subclause:  A.2
Page:  217
Line:  1213
CommentType:  E

Comment:  
There are Editor notes here, subclause A.2.2., page 219, line 4, and line 53.
CommentEnd:  

SuggestedRemedy:  
Delete the Editor notes.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1283
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.2.1
Page:  217
Line:  17
CommentType:  T

Comment:  
Is the LLC sublayer one of the SSCS options?
CommentEnd:  

SuggestedRemedy:  
MAC subcommittee to clarify and to add text to remove the confusion.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1284
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.2.2
Page:  218
Line:  49
CommentType:  E

Comment:  
The sentence that starts half way across line 49 needs to be modified as shown below.
CommentEnd:  

SuggestedRemedy:  
This MAC only reports success since all failures of reception are discarded without generating a MA-UNITDAT.indication.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1285
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.2.2
Page:  219
Line:  4
CommentType:  TR

Comment:  
We have an editorial note that needs to be resolved and removed.
CommentEnd:  

SuggestedRemedy:  
Refer to the MAC subcommittee
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  761
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  A
Subclause:  A.2.2
Page:  219
Line:  4
CommentType:  E

Comment:  
Editorial note
CommentEnd:  

SuggestedRemedy:  
Remove
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  440
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  A
Subclause:  A.2.2
Page:  219
Line:  5
CommentType:  T

Comment:  
Editorial comment left in, but still valid.
CommentEnd:  

SuggestedRemedy:  
Since .request supports reorderable multicast, we would have to support it on the .indication side as well.  However, it appears that the standard does not support multicast at all and so this could be deleted as an allowed service class from the .request side to fix this.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  762
CommenterName:  Huang, Bob
CommenterEmail:  robert.huang@am.sony.com
CommenterPhone:  201-358-4409
CommenterFax:  
CommenterCo:  Sony Electronics
Clause:  A
Subclause:  A.2.3
Page:  219
Line:  53
CommentType:  E

Comment:  
Editorial note
CommentEnd:  

SuggestedRemedy:  
Remove
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1286
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.2.3
Page:  219
Line:  53
CommentType:  TR

Comment:  
We have an editorial note that needs to be resolved and removed.
CommentEnd:  

SuggestedRemedy:  
Refer to MAC folks
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  441
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  A
Subclause:  A.2.3
Page:  219
Line:  54
CommentType:  T

Comment:  
Editorial comment left in but still valid.
CommentEnd:  

SuggestedRemedy:  
Add a condition, "9 - Undeliverable (channel conditions are too severe).
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1288
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  A.4
Page:  221
Line:  46
CommentType:  TR

Comment:  
Clause A.4 does not seem complete.  What is the point of having this clause in the standard.  If the clause is needed then it needs to be finished.  If it is not needed then it should be deleted.
CommentEnd:  

SuggestedRemedy:  
Refer to MAC folks
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1727
CommenterName:  McInnis, Michael D.
CommenterEmail:  michael.d.mcinnis@boeing.com
CommenterPhone:  435-865-2840
CommenterFax:  206-290-7758
CommenterCo:  The Boeing Company
Clause:  A
Subclause:  D
Page:  231
Line:  
CommentType:  TR

Comment:  
Annex D Protocol Implementation Conformance Statement (PICS) was not provided for voter comment and review.
CommentEnd:  

SuggestedRemedy:  
Povide Annex D content, PICS for voter comment and review
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1625
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  Figure A.1
Page:  215
Line:  20
CommentType:  T

Comment:  
In the rest of the document I think we are calling the MAC CPS the MAC and the MAC CPS SAP the MAC SAP.  We need to be consistent
CommentEnd:  

SuggestedRemedy:  
Clarify what we are calling the MAC and be consistent with the rest of the document.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  277
CommenterName:  Gifford, Ian
CommenterEmail:  giffordi@ieee.org
CommenterPhone:  +1 978 251 3451
CommenterFax:  +1 978 815 8182
CommenterCo:  Self
Clause:  A
Subclause:  Figure A.1
Page:  215
Line:  35
CommentType:  E

Comment:  
The term "PHY Sublayer", used in the Figure A.1 is spelled wrong.
CommentEnd:  

SuggestedRemedy:  
Change to "PHY Layer".
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1287
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  A
Subclause:  Table A.1
Page:  220
Line:  
CommentType:  T

Comment:  
What is the relationship between the information and the assignment of GTS slots.  Why is Table A.1 relavent to the standard?
CommentEnd:  

SuggestedRemedy:  
Refer to MAC folks
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1694
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  3.3.2
Page:  
Line:  
CommentType:  TR

Comment:  
The challenge response protocol as described in the standard is underspecified.  In some discussions, the idea was to use the challenge response protocol to allow for peer-to-peer authentication.  Below are some comments on this protocol:  1) There is no defined method for a DEV to send its public key to another DEV, so the protocol cannot be implemented as currently specified.   2) The challenge-response is an authentication protocol and, as such, it may require more passes than 2 (depending on the algorithms available in the cipher suite) and probably will require more if mutual authentication is desirable instead of single-party authentication.  Changing the number of passes will require a change to the MLME messages. 3) The purpose of this protocol is unclear.  Why does a device need to authenticate other devices in the piconet?  Is this because it will only trust the piconet if the security manager (PNC) and itself both authenticate all the other devices?  This policy would require a lot of overhead.  The use of this protocol should be clarified. 4) If devices wanted to authenticate each other individually, it stands to reason that they might want to exchange keys and communicate securely just between the two of them.  If this protocol is kept, it should be extended to include a method for exchanging keys.  Even better, the "authenticate" protocol, if it allows both parties to be authenticated, might be allowed between peer DEVs in the piconet.
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  35
CommenterName:  Bain, Jay
CommenterEmail:  jay.bain@timedomain.com
CommenterPhone:  256 428 6415
CommenterFax:  256 527 4778
CommenterCo:  Time Domain
Clause:  B
Subclause:  B.1
Page:  223
Line:  9
CommentType:  T

Comment:  
The informative annex relating to Power management is not complete. There is a key informative piece prior to use of the EPS action command that either should be in the annex or be located in clause 6.
CommentEnd:  

SuggestedRemedy:  
Add the summary of what happens after authentication and association and until the DEVs are ready to do EPS operations.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1289
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.1.2
Page:  223
Line:  18
CommentType:  T

Comment:  
Suggest a figure to clarify the master/slave relationship unique to EPS sets.
CommentEnd:  

SuggestedRemedy:  
Refer to power management folks.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1626
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.1.2
Page:  223
Line:  23
CommentType:  T

Comment:  
EPSPhase does not occur in the rest of the document.
CommentEnd:  

SuggestedRemedy:  
Delete reference to EPSPhase.  If this is the wrong workd, replace it.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  72
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  B
Subclause:  B.2
Page:  223
Line:  3
CommentType:  E

Comment:  
Resources in a piconet are allocated as channel time, not bandwidth.
CommentEnd:  

SuggestedRemedy:  
Change two occurrances of 'bandwidth' to 'channel time' in this sentence.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  797
CommenterName:  Akahane, Masa
CommenterEmail:  akahane@wcs.sony.co.jp
CommenterPhone:  81-3-6409-3238
CommenterFax:  
CommenterCo:  Sony
Clause:  B
Subclause:  B.2
Page:  223
Line:  48
CommentType:  E

Comment:  
piconet coordinator should be deleted
CommentEnd:  

SuggestedRemedy:  
correct
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1290
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.2
Page:  224
Line:  1
CommentType:  E

Comment:  
grammatical
CommentEnd:  

SuggestedRemedy:  
Remove the word "be" as shown below ...  ... GTS time is then calculated using ...
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1291
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.2
Page:  224
Line:  11
CommentType:  E

Comment:  
with in is one word
CommentEnd:  

SuggestedRemedy:  
replace "with in" with "within"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1292
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.2
Page:  224
Line:  47
CommentType:  E

Comment:  
add the definitive
CommentEnd:  

SuggestedRemedy:  
... indicating "anywhere in the CFP", 7.5.10.1.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1692
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.3
Page:  
Line:  
CommentType:  TR

Comment:  
Requirements and descriptions of the cipher suites should be part of section 10 in the main part of the document and should be normative in some capacity.  The standard needs to require that a cipher suite behave in a certain manner, otherwise there can be no guarantee that the selected cipher suite has the properties that are needed to satisfy the security requirements.
CommentEnd:  

SuggestedRemedy:  
Move cipher suite text to section 10 and clarify cipher suite requirements.  Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1293
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.3
Page:  225
Line:  3
CommentType:  TR

Comment:  
The text in B.3.1 implies there will be more than one cipher suite.  I will not be able to vote "yes" for a standard unless there is a default cipher suite.  Additonal cipher suits can be considered to be optional alternatives.  To do otherwise does the following:  1. without a default (mandatory) cipher suite then the only compatible security between all 802.15.3 devices is no security at all  2. When implementing hardware, I don't want to be burdened with having to put multiple cipher suites into the implementation.  That will be inefficient and expensive.
CommentEnd:  

SuggestedRemedy:  
The security subcommittee must select one cipher method as being the default, mandatory cipher method.  Additonal ciphers can be added as options.  I believe this is consistent with the motion made and passed in Austin.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1627
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.3.1
Page:  225
Line:  13
CommentType:  TR

Comment:  
In Austin we voted to have a mandatory cipher suite.  We need to include the mandatory cipher suite in the standard.
CommentEnd:  

SuggestedRemedy:  
Choose and document a mandatory cipher suite.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  727
CommenterName:  Herold, Barry
CommenterEmail:  epag03@email.mot.com
CommenterPhone:  847-538-2501
CommenterFax:  
CommenterCo:  Motorola
Clause:  B
Subclause:  B.3.1
Page:  225
Line:  6
CommentType:  T

Comment:  
A cipher suite needs to be chosen for the 15.3 standard. This would give a certain level of security for all devices which require security, and allow for interoperability for 15.3 devices. If higher levels of security, or differing cipher suites are needed for certain applications, then the application layer could implement its own security protocol by not using the 15.3 security, or by overlaying its protocol over the 15.3 security.
CommentEnd:  

SuggestedRemedy:  

RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE. The 802.15.3 committee is going to issue a CFP, evaluate and choose a mandatory cipher suite for DEVs that implement security.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/24/2002
DispatchDate:  
WrittenDate:  1/24/2002
Accept_RejectDate:  1/24/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1693
CommenterName:  Shvodian, William
CommenterEmail:  bshvodian@xtremespectrum.com
CommenterPhone:  703-269-3047
CommenterFax:  301-523-1538
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.3.2
Page:  225
Line:  13
CommentType:  E

Comment:  
The standard does not say what can't be in the MAC, so a more proper structure of the first sentence should be "The cipher suites are conceptually implemented outside of the MAC (although they may physically be implemented there), so . . ."
CommentEnd:  

SuggestedRemedy:  
Comment via Ari Singer.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1294
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.3.2.1
Page:  225
Line:  37
CommentType:  TR

Comment:  
Mention is made of a trusted relationship.
CommentEnd:  

SuggestedRemedy:  
The standard must explain how that trusted relationship is established.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1295
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.3.2.2
Page:  225
Line:  44
CommentType:  E

Comment:  
editorial
CommentEnd:  

SuggestedRemedy:  
add an s to key as shown below ...  ... needs to distribute keys to the DEVs ....
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1296
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  B
Subclause:  B.3.3.1
Page:  226
Line:  45
CommentType:  TR

Comment:  
In discussing authentication, mention is made of "using a processes defined by the cipher suite".
CommentEnd:  

SuggestedRemedy:  
The process used by the cipher suite has to take into consideration the WPAN environment.  That is, the cipher suite needs to accommodate WPAN and not the other way around.  I can not vote "yes" to a WPAN standard that does not have an authentication process that is suitable for WPAN deployments.
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1364
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  C
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Clause contains no content.
CommentEnd:  

SuggestedRemedy:  
Add content.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  The committee does not want to add normative content that may conflict with the other clauses. Informative content will not be available until at least 3 months after the final draft has been approved. 
SDL clause will be removed from the draft and left for a follow on project.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  1/22/2002
VoterStatus: 

-----------
CommentID:  548
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  C
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Without SDL there is an higehr risk of non-interoperable implementations
CommentEnd:  

SuggestedRemedy:  
Provide formal description of the MAC and PHY. SDL can be one option.
RemedyEnd:  

Response:  
PROPOSED REJECT. The committee does not want to add normative content that may conflict with the other clauses. Informative content will not be available until at least 3 months after the final draft has been approved. 
SDL clause will be removed from the draft and left for a follow on project.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  88
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  C
Subclause:  
Page:  229
Line:  1
CommentType:  TR

Comment:  
This annex is marked as NORMATIVE, yet nothing is present.  Any change to this section will be a significant technical change and require a new letter ballot not a recirculation.  If there are large holes like this in a draft, then it should not be even motioned to working group letter ballot. I have provided three suggested remedies.
CommentEnd:  

SuggestedRemedy:  
1) Remove the annex, but since the annex is normative. Note: this is a significant change removing somthing that is normative.  2) Changing the annex, from normative to informative.  Note: this does not solve the problem as it is still empty.  Even if SDLs are proposed as part of someone else's comments, I will consider these significant enough to warrant a new ballot. 3) Add the missing SDLs.  Note: this is a substantial technical change and will require a new ballot.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.   The committee does not want to add normative content that may conflict with the other clauses. Informative content will not be available until at least 3 months after the final draft has been approved. 
SDL clause will be removed from the draft and left for a follow on project.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  86
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  C
Subclause:  ALL
Page:  229
Line:  
CommentType:  T

Comment:  
SDL not included. SDL should be informative instead of normative.
CommentEnd:  

SuggestedRemedy:  
Add high level SDL for all mandatory portions for the specification.
RemedyEnd:  

Response:  
The committee does not want to add normative content that may conflict with the other clauses. Informative content will not be available until at least 3 months after the final draft has been approved. 
SDL clause will be removed from the draft and left for a follow on project.
ResponseEnd:  
CommentStatus:  R
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1106
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  C
Subclause:  C
Page:  229
Line:  
CommentType:  TR

Comment:  
There are no SDL's.  This is not a valid letter ballot with normative sections missing from the draft.
CommentEnd:  

SuggestedRemedy:  
The SDLs should not be considered normative and should be completely removed from the document.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. The committee does not want to add normative content that may conflict with the other clauses. Informative content will not be available until at least 3 months after the final draft has been approved. 
SDL clause will be removed from the draft and left for a follow on project.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  442
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  C
Subclause:  C
Page:  229
Line:  1
CommentType:  T

Comment:  
SDL is not defined and is not normative.
CommentEnd:  

SuggestedRemedy:  
Change normative to informative and get some SDL to put in here.  Or just delete the entire clause.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. The committee does not want to add normative content that may conflict with the other clauses. Informative content will not be available until at least 3 months after the final draft has been approved. 
SDL clause will be removed from the draft and left for a follow on project.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  549
CommenterName:  GUBBI, RAJUGOPAL
CommenterEmail:  rgubbi@broadcom.com
CommenterPhone:  408-543-3470
CommenterFax:  
CommenterCo:  Broadcom, corp
Clause:  D
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Without PICS there is an higehr risk of non-interoperable implementations
CommentEnd:  

SuggestedRemedy:  
Provide PICS for implementation description of the MAC and PHY.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. PICS content will be added as an informative clause as derived from the normative portion of the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1365
CommenterName:  Shellhammer, Steve
CommenterEmail:  shell@symbol.com
CommenterPhone:  (631) 738-4302
CommenterFax:  
CommenterCo:  Symbol Technologies
Clause:  D
Subclause:  
Page:  
Line:  
CommentType:  TR

Comment:  
Clause contains no content.
CommentEnd:  

SuggestedRemedy:  
Add content.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. PICS content will be added as an informative clause as derived from the normative portion of the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/22/2002
DispatchDate:  
WrittenDate:  1/22/2002
Accept_RejectDate:  1/22/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  89
CommenterName:  CYPHER, DAVID
CommenterEmail:  david.cypher@nist.gov
CommenterPhone:  1 301 975 4855
CommenterFax:  
CommenterCo:  NIST
Clause:  D
Subclause:  
Page:  231
Line:  1
CommentType:  TR

Comment:  
This annex is marked as NORMATIVE, yet nothing is present.  Any change to this section will be a significant technical change and require a new letter ballot not a recirculation.  If there are large holes like this in a draft, then it should not be even motioned to working group letter ballot. I have provided two suggested remedies. A PICS is not to contain any requirements that cannot be found in the descriptive text.  It has been my experience that this is not the case.  TG1's draft 802.15.1 is the best example of where a PICS makes requirements that are not part of the descriptive text.  The PICS in this case has become a product implementation time line, which marks items as optional, if the feature is not to be supported as a first released product.  A standard is never to be written as phases of a product roll out.  Requirements must be set and options well marked.  This is what a PICS contains.  If this is true that a PICS contains only what is fully stated in the text, then why could the PICS not have been part of the balloted text at this time?  Could it be that the requirements and options are not yet finalize in the text?  If this is the case then why was this draft motioned to working group letter ballot?
CommentEnd:  

SuggestedRemedy:  
1) Remove the annex, but since the annex is normative. Note: this is a significant change removing somthing that is normative.  2) Add the missing PICS.  Note: this is a substantial technical change and will require a new ballot.
RemedyEnd:  

Response:  
PROPOSED ACCEPT IN PRINCIPLE.  PICS content will be added as an informative clause as derived from the normative portion of the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  W
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  87
CommenterName:  Barr, John
CommenterEmail:  John.Barr@Motorola.com
CommenterPhone:  847-576-8706
CommenterFax:  847-651-6822
CommenterCo:  Motorola
Clause:  D
Subclause:  ALL
Page:  231
Line:  
CommentType:  E

Comment:  
PICS not defined. PICS section should be informative since it repeats items defined in earlier clauses and only servers to determine what portions of the specification to which paticular implementation conforms.
CommentEnd:  

SuggestedRemedy:  
Add PICS based on final content of the specification.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. PICS content will be added as an informative clause as derived from the normative portion of the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1107
CommenterName:  Roberts, Richard
CommenterEmail:  rroberts@xtremespectrum.com
CommenterPhone:  703-269-3043
CommenterFax:  301-613-5016
CommenterCo:  XtremeSpectrum
Clause:  D
Subclause:  D
Page:  231
Line:  
CommentType:  TR

Comment:  
There are no PICs.  This is not a valid letter ballot with normative sections missing from the draft.
CommentEnd:  

SuggestedRemedy:  
Add the PICs material.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. PICS content will be added as an informative clause as derived from the normative portion of the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  443
CommenterName:  Gilb, James
CommenterEmail:  gilb@ieee.org
CommenterPhone:  858-538-3903
CommenterFax:  858-213-6706
CommenterCo:  Appairent
Clause:  D
Subclause:  D
Page:  231
Line:  3
CommentType:  T

Comment:  
The PICS are derived from the text and so are informative rather than normative.
CommentEnd:  

SuggestedRemedy:  
Change the annex designation from normative to informative and add the PICS tables.
RemedyEnd:  

Response:  
PROPOSED ACCEPT. PICS content will be added as an informative clause as derived from the normative portion of the draft.
ResponseEnd:  
CommentStatus:  A
ResponseStatus:  C
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/21/2002
DispatchDate:  
WrittenDate:  1/21/2002
Accept_RejectDate:  1/21/2002
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1698
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  E
Subclause:  -
Page:  233
Line:  15
CommentType:  E

Comment:  
Excess blanks after [B4]
CommentEnd:  

SuggestedRemedy:  
remove the excess blanks
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1699
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  E
Subclause:  -
Page:  233
Line:  18
CommentType:  E

Comment:  
"Papoulis" should be "Athanasios Papoulis"
CommentEnd:  

SuggestedRemedy:  
use: "Athanasios Papoulis"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1700
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  E
Subclause:  -
Page:  233
Line:  20
CommentType:  E

Comment:  
"Proakis" should be "John G. Proakis"
CommentEnd:  

SuggestedRemedy:  
use "John G. Proakis"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1701
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  E
Subclause:  -
Page:  233
Line:  40
CommentType:  E

Comment:  
"Stallings" should be "William Stallings"
CommentEnd:  

SuggestedRemedy:  
use "William Stallings"
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1702
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  E
Subclause:  -
Page:  234
Line:  5
CommentType:  E

Comment:  
publication number missing in Ref [B19]
CommentEnd:  

SuggestedRemedy:  
fill in proper number for "ZZZ" in lines 5 and 6
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: 

-----------
CommentID:  1703
CommenterName:  Siwiak, Kazimierz
CommenterEmail:  kai.siwiak@timedomain.com
CommenterPhone:  954-755-6828
CommenterFax:  256-990-9062
CommenterCo:  Time Domain
Clause:  E
Subclause:  -
Page:  234
Line:  9
CommentType:  E

Comment:  
publication number missing in Ref [B20]
CommentEnd:  

SuggestedRemedy:  
fill in proper number for "#HMAC" in lines 9 and 10
RemedyEnd:  

Response:  

ResponseEnd:  
CommentStatus:  X
ResponseStatus:  O
Topic:  
CreateDate:  1/18/2002
LastModDate:  1/18/2002
DispatchDate:  
WrittenDate:  
Accept_RejectDate:  
Closed_UnsatisfDate:  
VoterStatus: