CommentID~CommenterName~CommenterEmail~CommenterPhone~CommenterFax~CommenterCo~Clause~Subclause~Page~Line~CommentType~Comment~SuggestedRemedy~Response~CommentStatus~ResponseStatus
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~01~~~~~Who owns the trademark on "Wireless Personal Area Networks"??~Remove the (tm)~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~03~1~~~E~There's lots of "M Weik" in section 3.1~Add to reference section and make references by [1] rather than name.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~05~3.2~~~E~Figure 3 looks really naf.~I'll give you a wmf from my original drawing.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~05~Figures 9-15~~~E~These figures are too small.~Make them bigger.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~10~1~~~T~Last para of 10.1 doesn't mention that PTA should also be used when SCO needs to be supported.~Add " or when SCO links need to be supported." to the end of this para.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~10~2~~~T~Section 10.2 needs some work.  The T1 and one of the TWLAN/TWPAN need to be communicated. The other duraction can be calculated from TB.   This document should include changes to 802.11 in the form of editing instructions to a particular revision of 802.11(see the other 802.11 drafts for examples).~Signal T1 and TWLAN.Add "editing instructions" to this document for any required changes to 802.11.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~10~2.2~~~T~Section 10.2.2.  It is not necessary to have both an MLME and a MIB interface to these values.  Recommend just a MIB one (less text!).Should have just T1 and TWLAN variables.~Remove the MLME interface and add section saying that the MIB values are updated whenever a beacon is received.  Beacon transmitted contains latest MIB values of these variables.   Support T1 and TWLAN MIB variables (TWPAN is redundant and problemmatical if TWLAN+TWPAN != TB).~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~10~2.2.6.3~~~T~Don't select an element ID, but instruct the editor to find an unused one.You cannot be sure this value will be available.~Add editing instruction:"Add the following element to table 20 of ... and assign an available element ID".~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~10~2.4~~~T~"The Clear-to-Send (CTS) packet is addressed to its own 802.11 MAC address plus the group address bit is set to 1 (multicast group). This allows any other Access Point on the same channel to determine that this isa pseudo-reservation message and to not delay any of its own transmissions, such as CTSs or Beacons."No it doesn't.The current 802.1 makes no such interpretation on the CTS RA.~Remove this comment or add normative editing instructions to change 802.11.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~10~3.1~~~T~Table 19 has an error.  The adjacent "none" and "receive" cells near the bottom RH need to be swapped.~Swap them.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~11~1.2~~~E~Figure 43 needs to be re-drawn.~~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~11~3~~~T~I see packet scheduling only of value when a new master device talks to a legacy device.  A legacy device is unable to characterise the channel and report the frequency usage table.~Remove all mention of communication between slave and master in this section.  Make appropriate adjustments so that master operates only on the basis of local knowledge.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~11~2.1~~~T~There is no point defining behaviour requiring negotiation before use (such as setting up an EV3 connection) if there is no agreed means for 802.15.2 to define modifications to the connection setup process and LMP commands.~Remove all mention of EV3.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~12~1.1.4~~~T~This section is meaningless.  There is no NACK in 802.11 or 802.15.1.~Remove section~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~12~2~~~T~Section 12.2.  It is not clear from this section whether it is an alternative to the AFH that will be defined by the BT SIG, or is intended to be compatible with it.~Add a statement of compatibility to the BT SIG AFH mechanism.~~X~O
0~Stephens, Adrian~adrian.stephens@mobilian.com~+44 1954 204609~+44 771 276 3448~Mobilian Corporation~12~3~~~T~It is meaningless to define values contained in LMP commands unless there is a defined coordination between the BT SIG and 802.15.2 that permits 802.15.2 to define LMP commands and features.~In the absence of any such coordination,  remove section 12.3.~~X~O
