draft-ietf-capwap-base-mib-07.txt   draft-ietf-capwap-base-mib-08.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft Hangzhou H3C Tech. Co., Ltd. Internet-Draft Hangzhou H3C Tech. Co., Ltd.
Intended status: Informational D. Perkins, Ed. Intended status: Informational D. Perkins, Ed.
Expires: July 6, 2010 SNMPinfo Expires: July 15, 2010 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
January 2, 2010 January 11, 2010
CAPWAP Protocol Base MIB CAPWAP Protocol Base MIB
draft-ietf-capwap-base-mib-07 draft-ietf-capwap-base-mib-08
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it for use with network management protocols. In particular, it
describes the managed objects for modeling the Control And describes the managed objects for modeling the Control And
Provisioning of Wireless Access Points (CAPWAP) Protocol. Provisioning of Wireless Access Points (CAPWAP) Protocol.
Status of This Memo Status of This Memo
skipping to change at page 1, line 44 skipping to change at page 1, line 44
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 6, 2010. This Internet-Draft will expire on July 15, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 39 skipping to change at page 3, line 39
9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17
9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17
9.3.1. Configuration Status Response Message . . . . . . . . 17 9.3.1. Configuration Status Response Message . . . . . . . . 17
9.3.2. Configuration Update Response Message . . . . . . . . 18 9.3.2. Configuration Update Response Message . . . . . . . . 18
10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 76 11. Security Considerations . . . . . . . . . . . . . . . . . . . 76
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77
12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 77 12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 77
12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 77 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 77
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 77 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 77
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 77 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 78
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 78 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 78
15.1. Normative References . . . . . . . . . . . . . . . . . . . 78 15.1. Normative References . . . . . . . . . . . . . . . . . . . 78
15.2. Informative References . . . . . . . . . . . . . . . . . . 79 15.2. Informative References . . . . . . . . . . . . . . . . . . 79
Appendix A. Appendix A. Changes between -07 and -06 . . . . . . . 80 Appendix A. Appendix A. Changes between -08 and -07 . . . . . . . 80
1. Introduction 1. Introduction
The CAPWAP Protocol [RFC5415] defines a standard, interoperable The CAPWAP Protocol [RFC5415] defines a standard, interoperable
protocol, which enables an Access Controller (AC) to manage a protocol, which enables an Access Controller (AC) to manage a
collection of Wireless Termination Points(WTPs). collection of Wireless Termination Points(WTPs).
This document defines a MIB module that can be used to manage the This document defines a MIB module that can be used to manage the
CAPWAP implementations. This MIB module covers both configuration CAPWAP implementations. This MIB module covers both configuration
and WTP status-monitoring aspects of CAPWAP, and provides a way to and WTP status-monitoring aspects of CAPWAP, and provides a way to
skipping to change at page 19, line 40 skipping to change at page 19, line 40
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2,
Integer32, Unsigned32, Counter32, Gauge32, TimeTicks Integer32, Unsigned32, Counter32, Gauge32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
capwapBaseMIB MODULE-IDENTITY capwapBaseMIB MODULE-IDENTITY
LAST-UPDATED "201001020000Z" -- Jan 2th, 2010 LAST-UPDATED "201001110000Z" -- January 11th, 2010
ORGANIZATION "IETF Control And Provisioning of Wireless Access ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html" http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO CONTACT-INFO
"General Discussion: capwap@frascone.com "General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi (editor) Yang Shi (editor)
Hangzhou H3C Tech. Co., Ltd. Hangzhou H3C Tech. Co., Ltd.
Beijing R&D Center of H3C, Digital Technology Plaza, Beijing R&D Center of H3C, Digital Technology Plaza,
skipping to change at page 20, line 38 skipping to change at page 20, line 38
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2010 The Internet Society. This version of "Copyright (C) 2010 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself the MIB module is part of RFC xxx; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the CAPWAP Protocol." the CAPWAP Protocol."
REVISION "201001020000Z" REVISION "201001110000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual Conventions -- Textual Conventions
CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 67, line 42 skipping to change at page 67, line 42
::= { capwapBaseObjects 6 } ::= { capwapBaseObjects 6 }
capwapBaseChannelUpDownNotifyEnable OBJECT-TYPE capwapBaseChannelUpDownNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the Channel Up/Channel Down notification "Represents whether the Channel Up/Channel Down notification
should be generated. should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled" A value of false(2) means that the notification is disabled
The value of the object is persistent at restart/reboot."
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 1 } ::= { capwapBaseNotifyControlObjects 1 }
capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the decryption error notification should "Represents whether the decryption error notification should
be generated. be generated.
skipping to change at page 68, line 4 skipping to change at page 68, line 5
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 1 } ::= { capwapBaseNotifyControlObjects 1 }
capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the decryption error notification should "Represents whether the decryption error notification should
be generated. be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled" A value of false(2) means that the notification is disabled
The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 2 } ::= { capwapBaseNotifyControlObjects 2 }
capwapBaseJoinFailureNotifyEnable OBJECT-TYPE capwapBaseJoinFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of WTP join failure should "Represents whether the notification of WTP join failure should
be generated. be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled" A value of false(2) means that the notification is disabled
The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 3 } ::= { capwapBaseNotifyControlObjects 3 }
capwapBaseImageUpgradeFailureNotifyEnable OBJECT-TYPE capwapBaseImageUpgradeFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of WTP image upgrade "Represents whether the notification of WTP image upgrade
failure should be generated. failure should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled" A value of false(2) means that the notification is disabled
The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 4 } ::= { capwapBaseNotifyControlObjects 4 }
capwapBaseConfigMsgErrorNotifyEnable OBJECT-TYPE capwapBaseConfigMsgErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of configuration message "Represents whether the notification of configuration message
error should be generated. error should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled" A value of false(2) means that the notification is disabled
The value of the object is persistent at restart/reboot."
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 5 } ::= { capwapBaseNotifyControlObjects 5 }
capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of a radio's operational "Represents whether the notification of a radio's operational
state change should be generated. state change should be generated.
skipping to change at page 69, line 4 skipping to change at page 69, line 9
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 5 } ::= { capwapBaseNotifyControlObjects 5 }
capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of a radio's operational "Represents whether the notification of a radio's operational
state change should be generated. state change should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled" A value of false(2) means that the notification is disabled
The value of the object is persistent at restart/reboot."
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 6 } ::= { capwapBaseNotifyControlObjects 6 }
capwapBaseAuthenticationFailureNotifyEnable OBJECT-TYPE capwapBaseAuthenticationFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of authentication failure "Represents whether the notification of authentication failure
should be generated. should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled" A value of false(2) means that the notification is disabled
The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 7 } ::= { capwapBaseNotifyControlObjects 7 }
-- Module compliance -- Module compliance
capwapBaseCompliances OBJECT IDENTIFIER capwapBaseCompliances OBJECT IDENTIFIER
::= { capwapBaseConformance 1 } ::= { capwapBaseConformance 1 }
capwapBaseGroups OBJECT IDENTIFIER capwapBaseGroups OBJECT IDENTIFIER
::= { capwapBaseConformance 2 } ::= { capwapBaseConformance 2 }
skipping to change at page 81, line 15 skipping to change at page 81, line 22
[RFC5416] Calhoun, P., Montemurro, M., and D. [RFC5416] Calhoun, P., Montemurro, M., and D.
Stanley, "Control and Provisioning of Stanley, "Control and Provisioning of
Wireless Access Points (CAPWAP) Wireless Access Points (CAPWAP)
Protocol Binding for IEEE 802.11", Protocol Binding for IEEE 802.11",
RFC 5416, March 2009. RFC 5416, March 2009.
[I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C., [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C.,
and Y. Zhang, "CAPWAP Protocol and Y. Zhang, "CAPWAP Protocol
Binding MIB for IEEE 802.11", Binding MIB for IEEE 802.11",
draft-ietf-capwap-802dot11-mib-06 draft-ietf-capwap-802dot11-mib-06
(work in progress), Jan 2010. (work in progress), January 2009.
RFC Editor - please remove the appendix before publication of the RFC RFC Editor - please remove the appendix before publication of the RFC
Appendix A. Appendix A. Changes between -07 and -06 Appendix A. Appendix A. Changes between -08 and -07
1) Close IESG review issues raised by Bert Wijnen
--------------------------------------------------------------
Added some notification control objects such as
capwapBaseChannelUpDownNotifyEnable; Update the description to
explain the objects of RowStatus type; give the note in the object
description to explain why the object such as
capwapBaseWtpProfileWtpEcnSupport starting value is zero; Added the
MODULE IF-MIB.
2) Close Gen-ART review issues raised by David L. Black
--------------------------------------------------------------
Close some editorial problems such as using "index" instead of 1) Add the descriptions about persistence of the notification control
"handler"; Changed some text to make it clear. objects such as capwapBaseAuthenticationFailureNotifyEnable.
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
Hangzhou H3C Tech. Co., Ltd. Hangzhou H3C Tech. Co., Ltd.
Beijing R&D Center of H3C, Digital Technology Plaza, Beijing R&D Center of H3C, Digital Technology Plaza,
NO.9 Shangdi 9th Street,Haidian District, NO.9 Shangdi 9th Street,Haidian District,
Beijing Beijing
China(100085) China(100085)
 End of changes. 20 change blocks. 
36 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.37b. The latest version is available from http://tools.ietf.org/tools/rfcdiff/