----------- 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. IEEE 100, The Authoritative Dictionary of Standards Terms should be referenced for terms 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 Di