Skip to main content

Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11
draft-ietf-capwap-protocol-binding-ieee80211-12

Yes

(Dan Romascanu)

No Objection

(Chris Newman)
(Jari Arkko)
(Jon Peterson)
(Lars Eggert)
(Lisa Dusseault)
(Magnus Westerlund)
(Mark Townsley)
(Ron Bonica)
(Ross Callon)
(Russ Housley)
(Tim Polk)

Note: This ballot was opened for revision 12 and is now closed.

Dan Romascanu Former IESG member
Yes
Yes () Unknown

                            
Chris Newman Former IESG member
No Objection
No Objection () Unknown

                            
David Ward Former IESG member
No Objection
No Objection (2008-10-08) Unknown
Again support other DISCUSS positions
Jari Arkko Former IESG member
No Objection
No Objection () Unknown

                            
Jon Peterson Former IESG member
No Objection
No Objection () Unknown

                            
Lars Eggert Former IESG member
No Objection
No Objection () Unknown

                            
Lisa Dusseault Former IESG member
No Objection
No Objection () Unknown

                            
Magnus Westerlund Former IESG member
(was Discuss, No Objection) No Objection
No Objection () Unknown

                            
Mark Townsley Former IESG member
No Objection
No Objection () Unknown

                            
Pasi Eronen Former IESG member
(was Discuss) No Objection
No Objection (2008-10-20) Unknown
(Updated comment for version -11)

Section 1 says 802.11n is not supported by this specification, but
Section 6.25 defines a field for 802.11n?

Section 8.1: there probably should be IANA considerations text about
how the remaining bits are allocated (or explicitly say that the
remaining bits will not be allocated, and new capabilities require
defining a new WBID).

Section 8.1 should say that there's no bit for WEP because all WTPs
are required to support it (if that's the reason).

Section 10.2 (Message Types): the range to be managed by IANA is not
32 bits, but only 8 (i.e. the unassigned values are 3398915-3399167,
not 0-4294967295).

Section 10.2: message type 3398911 has Enterprise Number 13276, not
13277, so it's not part of the range to be managed by IANA.

Section 10.5 (QoS) says values 0-4 are allocated in this
specification, but Section 6.1 defines only values 0-3.

Section 10.7 (Antenna Combiner) says values 0 and 1 are allocated in
this specification, but Section 6.2 defines values 1-4.

Section 10.8 (Antenna Selection) says values 1-4 are allocated in this
specification, but Section 6.2 defines only values 1-2.

Section 10.9 (Session Key Flags) , "bits two (2) through sixteen"
should be "..through fifteen".

Section 10.10 (Tagging Policy) says bits 5-7 are defined in this spec;
but Section 6.22 defines bits 3-7.

Section 10.12 (WTP Radio Type) says bits 5-7 are defined in this spec,
but Section 6.25 defines bits 4-7.
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection () Unknown

                            
Tim Polk Former IESG member
No Objection
No Objection () Unknown