Capwap Mailing List: New issues: readability/ease of use/lack of specification

[Bob O'Hara (boohara) (boohara]

The -01 draft is a significant improvement over the -00 draft.  However,
I find it very difficult to easily find some information in the
document.  Following are some editorial and technical comments.

1. Please include a table of message element type values for the base
CAPWAP message elements in section 4.4.

2. Please include a table of message element type values for the 802.11
binding-specific elements in section 11.10.

3. Please describe how the binding-specific message element type values
are derived.  It appears that the 802.11 type values begin arbitrarily
at 1024.  Are the values for this field to be IANA controlled, or are
they able to be identified deterministically?

4. Please identify in which messages the nine additional message
elements in section 11.10 may appear, since they are not listed in the
table in section 11.9.3.

5. In 11.7, the Message Type Value for the two 802.11-specific messages
is given.  However, I don't see anywhere that describes how these values
were determined.  Please add a description of the derivation of the
message type values.

6. 11.8 says there are no 802.11-specific data message bindings.  I
think that the data packet containing an 802.11-encapsulated frame
should go here, along with its complete description.


 -Bob

Bob O'Hara
Cisco Systems - WNBU

Phone:  +1 408 853 5513
Mobile: +1 408 218 4025