Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Base MIB
RFC 5833

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

(Dan Romascanu) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lisa Dusseault) No Objection

(Pasi Eronen) (was Discuss) No Objection

(Adrian Farrel) (was Discuss) No Objection

Comment (2010-01-19)
No email
send info
Support Russ's Discuss about separating the protocol extensions from 
this MIB module specification. It seems that these protocol extensions
would be useful even if some other form of configuration (other than
SNMP) was used.


Section 9.1

   DataChannelKeepAlive:  A 16-bit value representing the time,
      in seconds, that is used by the WTP to determine the next
      must transmit the Data Channel Keep Alive. (see section 4.7.2 of

s/next/next time it/

   DataChannelDeadInterval:  A 16-bit value representing the minimum
      time, in seconds, a WTP MUST wait without having received a Data
      Channel Alive packets MAY be considered dead.  The value of this
      timer MUST be no less than 2*DataChannelKeepAlive seconds and
      no greater that 240 seconds (see section 4.7.3 of [RFC5415]).

s/packets MAY/packet before it MAY/


It would be nice to indicate the source RFCs in comments in the IMPORTS

(Russ Housley) (was Discuss) No Objection

(Cullen Jennings) No Objection

(Alexey Melnikov) No Objection

Comment (2010-01-16 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
capwapBaseNtfStationIdList OBJECT-TYPE
    SYNTAX      LongUtf8String (SIZE (6..1024))
    MAX-ACCESS  accessible-for-notify
    STATUS      current
        "Represents a list of station identifiers separated by
        "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415."

Is the section reference correct?
RFC 5415, Section 4.6.17 has title "Decryption Error Report".

    ::= { capwapBaseNotifyVarObjects 6 }

(Tim Polk) No Objection

(Robert Sparks) No Objection