CommentID~CommenterName~CommenterEmail~CommenterPhone~CommenterFax~CommenterCo~Clause~Subclause~Page~Line~CommentType~Comment~SuggestedRemedy~Response~CommentStatus~ResponseStatus
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~03~2~5~20~T~Words of abbreviation do not match use in document~Change to signal to interference plus noise ratio~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~03~1~6~33~T~802.11b has many more channels than 3, so the statement is perhaps incorrect.~Please change the wording to "can support 3 non-overlapping channels in the ISM band."~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~04~3~8~45~E~The order of the collaborative and non-collaborative discussion in the overview does not match the order of the material in the main sections.~Please reverse the order of 4.3.1 and 4.3.2.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~04~3.1~8~45~E~The methods described are no longer proposals.~Please change the section heading of 4.3.1 to "non-collaborative methods"~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~04~3.2~9~13~E~The collaborative methods are no longer proposals.~Please change the section head of 4.3.2 to "collaborative methods."~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~04~3.2~9~15~TR~The paragraph here describing the two collaborative approachs does not seem to use the same vocabulary or be in synch with the detailed description of the collaborative methods presented in sections 10~Please review the summary paragraph contained in 4.3.2 and bring in line with the section 10. Consider writing it in the sytle of paragraph 4.3.1 which provides a nice highlevel overview of the non-collaborative methods. Please specifically use the vocabulary of section 10, namely the AWMA and the PTA technique.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~05~4.2~21~6~TR~I don't know what the sentence "The 1 and 11 Mpbs mdoes of IEEE 802.11b are implemented"  means. 802.15.2 Models corresponding to 1, 5.5, and 11 Mbps of 802.11b are described in 5.4.2.1 through 5.4.2.3. Results of interference simulation corresponding to 1, 2, 5.5, and 11 Mbps are presented in 5.4.3. The C code models for all modes appear to be included. And finally, 802.11b is implemented fully in the industry.~Change the sentence to state "802.15.2 contains system models of 802.11b 1, 2, 5.5, and 11 Mbps modes."~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~05~4.2~22~36~TR~No system model is presented or discussed for 802.11b 2 Mbps. Simulaiton results are displaeyd in 5.4.3.~Please describe the 802.11b system model by adding a new section in 5.4.2.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~06~~29~9~E~Incorrect word processor reference "~\cite{Bluet99}. ~Please fix the reference.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~~~40~47~E~It is not clear to the reader that PTA is the second MA layer technique.~Please change the first sentence to state" In the PTA technique, the second MAC layer technique, the 802.11b..."~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~10~2~42~10~TR~The contents of section 10 is making modificaitons to the 802.11 base document(s). It is very important that this material be presented in a clear format so that the base document can be very well understood by the hundreds of engineers currently extended it in all the various projects. It appears that the material in 10.2.2.1, 10.2.2.2, 10.2.2.3, 10.2.2.4, 10.2.2.5, 10.2.2.6.1, 10.2.2.6.2, and 10.2.2.6.3 make changes to the base document.10.2.2.6.1-3 state that the base document is 802.11.~Add somewhere near the top of the document that this 802.15.2 makes changed to the 802.11b-1999 document. Add other documents if you want them modified, too.Add a statement associated with the 10.2.2.x sections that they modify the 802.11b-1999 document.Change the statement associated with 10.2.2.6 to state it is ammending 802-11b-1999.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~10~2~42~10~E~This section contains much explanatory material as well as some normative functional material. This is difficult to know exactly what the new 802.11b document should look like.~Please take the functional material (plus any desired explanatory material) and gather it into an Annex or Appendix of 802.15.2. Include in this material a pro forma title Draft supplement to STandard for LAN/MAN Specific Requirements - PArt !!: MAC and PHY specifications: Specificaiton for Coexistesnce of Wireless Personal Area Networks in Unlicnesced Frequency Bands using the Alternating Wireless Medium Access (AWMA) Collaborative Method.Add pro-forma statments that "This supplement is based on the current edition of IEEE STD 802.11b, 1999. Note -- the editing instructions chaintedin thie supplement define how to merge the material contained herein into the existing base stnadard to form a new comprehensive standard as created by the addition of this Annex. The editing instrucitons are shown in bold italic. Three editing instructions are used: chagne, delete, and insert. [explain the terms as in 802.11d] Editorial notes will not be carried over into future editions.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~10~2.2.6.1~47~42~TR~The order 11 in a beacon frame body is defined by 802.11d already and conflicts with this definition.~The first unused item in approved 802.11 ammendments is 14; however, proposed 802.11h has already brought forward proposals for 14-18. I recommend changing the order of the item displayed in Table 16 in 802.15.2 to 19.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~02~2.2.6.2~48~3~TR~The order 11 items in a probe response frame has already been defined by 802.11d supplement.~802.11d defined element 13-n as being present in a probe response frame when the request information item (order 3) asks for them in a porbe request frame. Proposed 802.11h inserts new items 13-17 and defines 18-n as being those present in reponse to a reqeust information item. I recommend that we call the needed item for 802.15.2 order 18 and list 19-n as being present in response to the reqeust information item. ~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~02~2.2.6.3~48~18~TR~The information element with ID 8 has already been defined by 802.11d supplement.~The next available number not used in an approved 802.11 draft supplement is 11. PRoposed 802.11h has not used these (but has defined 32 to 41). I recommend that the element id as displayed in Table 18 be changed from 8 to 11. The note reserving elements should list 12-15 as reserved.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~10~2.4~50~22~TR~The draft described a method by which the 802.11b AP can sent out a false RTS/CTS to clear the air so that legacy stations will not transmit (freeing the air for the coordinated WPAN transmissions).This method may work. RTS/CTS without data transmission is not an allowed sequenced in the base document.~Add the RTS/CTS into the allowed sequences in Table 21 of the base document. Include editing instructions to insert this sequence in section 9.7. Include this in the Annex/Appendix of the 802.15.2 Supplement to 802.11b.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~10~2.4~50~22~T~The text describes a method of transmitting RTS/CTS to clear the eair of non-collaborating legacy 802.11b STAs so that collaborating WPAN may transmit.Another method that works and is fully within the sllowed scope of the 802.11b document is to trnamist a BEACON(CF) to start a contention free period. The collaborating AP will avoid polling during the time allocated for the WPAN.~Add this method to section 10.2.4.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~11~1.2~62~48~E~The first setence has independent clause.~Fix the grammar error (please).~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~11~2.1~64~10~E~Usage issue~Change the start of the sentence to "The key idea is to..."~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~11~3~66~46~E~Not a direct way to say this... ~Change the sentence to "Channel classification is described in 12.1"~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~11~Figure 47~67~13~TR~What are the frequencies being marked here with "yes" and "no" to indicate?~I think maybe the yes means "good" and the no means "bad" based on the information in 12.1.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~11~11.3~67~39~TR~By marking the frequencies is not sufficiently specific to guide implementation. Do we mean marking the freuqices as good or bad according to the frequency classification scheme defined in 12.1?~Add sufficient detail to support implementation at the slave.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~11~3~67~43~TR~Refresh the frequency usage table is not sufficient to guide implementation. Do we mean by updating the good/bad list at the master end as per 12.1? Do we mean more in terms of updating the slave frequency lists?~Provide sufficient desription to guide implementation and to ascertain interoperability between all master and slave implementations.~~X~O
0~Cole, Terry~terry.cole@amd.com~512-602 2454~512 543 2650~AMD~12~1~70~15~E~I would prefer to see the material in 12.1 introduced prior to the two methods that use it rather than inside the second method and after the first one.~Please consider movign the material in 12.1 to a standalone subsection prior to any reference to it. (Or after all references to it).~~X~O
