--- 1/draft-ietf-bfd-mib-11.txt 2012-12-18 00:35:15.108041177 +0100 +++ 2/draft-ietf-bfd-mib-12.txt 2012-12-18 00:35:15.167720000 +0100 @@ -1,19 +1,19 @@ Network Working Group T. Nadeau Internet Draft Juniper Networks Intended status: Standards Track Z. Ali -Expires: December 14, 2012 N. Akiya +Expires: June 17, 2013 N. Akiya Cisco Systems - June 14, 2012 + December 17, 2012 BFD Management Information Base - draft-ietf-bfd-mib-11 + draft-ietf-bfd-mib-12 Abstract This draft defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling Bidirectional Forwarding Detection (BFD) protocol. Status of this Memo @@ -23,24 +23,24 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on December 14, 2012. + This Internet-Draft will expire on June 17, 2013. Copyright Notice - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must @@ -50,43 +50,43 @@ Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Table of Contents - 1. The Internet-Standard Management Framework . . . . . . . . . . 3 + 1. The Internet-Standard Management Framework . . . . . . . . . . 2 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Brief Description of MIB Objects . . . . . . . . . . . . . . . 3 - 4.1. General Variables . . . . . . . . . . . . . . . . . . . . 4 - 4.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 4 + 4.1. General Variables . . . . . . . . . . . . . . . . . . . . 3 + 4.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 3 4.3. Session Performance Table (bfdSessionPerfTable) . . . . . 4 4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 4 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . . 4 5. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . . 4 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 31 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 - 8.1. Normative References . . . . . . . . . . . . . . . . . . . 33 - 8.2. Informative References . . . . . . . . . . . . . . . . . . 34 - Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 34 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 8.1. Normative References . . . . . . . . . . . . . . . . . . . 37 + 8.2. Informative References . . . . . . . . . . . . . . . . . . 37 + Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 38 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 Internet-Standard Management Framework, please refer to section 7 of [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, @@ -120,21 +120,21 @@ 4.1. General Variables The General Variables are used to identify parameters that are global to the BFD process. 4.2. Session Table (bfdSessionTable) The session table is used to identify a BFD session between a pair of nodes. - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 4.3. Session Performance Table (bfdSessionPerfTable) The session performance table is used for collecting BFD performance counters on a per session basis. This table is an AUGMENT to the bfdSessionTable. 4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) The BFD Session Discriminator Mapping Table maps a local @@ -165,47 +165,47 @@ FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF InterfaceIndexOrZero FROM IF-MIB InetAddress, InetAddressType, InetPortNumber FROM INET-ADDRESS-MIB - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, BfdDiagTC, BfdSessTypeTC, BfdSessOperModeTC, BfdCtrlDestPortNumberTC, BfdCtrlSourcePortNumberTC, BfdSessStateTC, BfdSessAuthenticationTypeTC, BfdSessionAuthenticationKeyTC FROM BFD-TC-STD-MIB; bfdMIB MODULE-IDENTITY - LAST-UPDATED "201204141200Z" -- 14 June 2012 12:00:00 EST + LAST-UPDATED "201212171200Z" -- 17 December 2012 12:00:00 EST ORGANIZATION "IETF Bidirectional Forwarding Detection Working Group" CONTACT-INFO "Thomas D. Nadeau Juniper Networks Email: tnadeau@lucidvision.com Zafar Ali Cisco Systems, Inc. Email: zali@cisco.com Nobo Akiya Cisco Systems, G.K. Email: nobo@cisco.com" DESCRIPTION "Bidirectional Forwarding Management Information Base." - REVISION "201204141200Z" -- 14 June 2012 12:00:00 EST + REVISION "201212171200Z" -- 17 December 2012 12:00:00 EST DESCRIPTION "Initial version. Published as RFC xxxx." -- RFC Ed.: RFC-editor pls fill in xxxx ::= { mib-2 XXX } -- RFC Ed.: assigned by IANA, see section 7.1 for details -- Top level components of this MIB module. bfdNotifications OBJECT IDENTIFIER ::= { bfdMIB 0 } @@ -215,21 +215,21 @@ bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } -- BFD General Variables -- These parameters apply globally to the Systems' -- BFD Process. bfdAdminStatus OBJECT-TYPE SYNTAX INTEGER { - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The global administrative status of BFD in this device. The value 'enabled' denotes that the BFD Process is active on at least one interface; 'disabled' disables @@ -265,21 +265,21 @@ "The BFD Session Table describes the BFD sessions." REFERENCE "Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2012." ::= { bfdObjects 2 } bfdSessEntry OBJECT-TYPE SYNTAX BfdSessEntry MAX-ACCESS not-accessible STATUS current - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 DESCRIPTION "The BFD Session Entry describes BFD session." INDEX { bfdSessIndex } ::= { bfdSessTable 1 } BfdSessEntry ::= SEQUENCE { bfdSessIndex BfdSessIndexTC, bfdSessVersionNumber Unsigned32, bfdSessType BfdSessTypeTC, @@ -315,21 +315,21 @@ bfdSessAuthenticationKeyID Integer32, bfdSessAuthenticationKey BfdSessionAuthenticationKeyTC, bfdSessStorageType StorageType, bfdSessRowStatus RowStatus } bfdSessIndex OBJECT-TYPE SYNTAX BfdSessIndexTC MAX-ACCESS not-accessible STATUS current - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 DESCRIPTION "This object contains an index used to represent a unique BFD session on this device." ::= { bfdSessEntry 1 } bfdSessVersionNumber OBJECT-TYPE SYNTAX Unsigned32 (0..7) MAX-ACCESS read-create STATUS current @@ -365,21 +365,21 @@ SYNTAX Unsigned32 (0 | 1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the session discriminator chosen by the remote system for this BFD session. The value may be zero(0) if the remote discriminator is not yet known or if the session is in the down or adminDown(1) state." REFERENCE "Section 6.8.6, from Katz, D. and D. Ward, Bidirectional - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 Forwarding Detection (BFD), RFC 5880, June 2012." ::= { bfdSessEntry 5 } bfdSessDestinationUdpPort OBJECT-TYPE SYNTAX BfdCtrlDestPortNumberTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the destination UDP port number @@ -415,21 +415,21 @@ permit the implementation to chose its own source port number." DEFVAL { 0 } ::= { bfdSessEntry 8 } bfdSessAdminStatus OBJECT-TYPE SYNTAX INTEGER { stop(1), start(2) } - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 MAX-ACCESS read-create STATUS current DESCRIPTION "A transition from 'stop' to 'start' will start the BFD state machine for the session. The state machine will have an initial state of down. A transition from 'start' to 'stop' will cause the BFD sesssion to be brought down to adminDown(1). Care should be used in providing @@ -465,21 +465,21 @@ DEFVAL { false } ::= { bfdSessEntry 11 } bfdSessDiag OBJECT-TYPE SYNTAX BfdDiagTC MAX-ACCESS read-only STATUS current DESCRIPTION "A diagnostic code specifying the local system's reason for the last transition of the session from up(4) - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 to some other state." ::= { bfdSessEntry 12 } bfdSessOperMode OBJECT-TYPE SYNTAX BfdSessOperModeTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies current operating mode that BFD @@ -515,21 +515,21 @@ bfdSessMultipointFlag OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the Multipoint (M) bit for this session. It is set to true(1) if Multipoint (M) bit is set to 1. Otherwise, the value is set to false(2)" DEFVAL { false } ::= { bfdSessEntry 16 } - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 bfdSessInterface OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "This object contains an interface index used to indicate the interface which this BFD session is running on. This value can be zero if there is no interface associated with this BFD session." @@ -564,21 +564,21 @@ bfdSessDstAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies IP address type of the neighboring IP address which is being monitored with this BFD session. Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4) have to be supported. The value of unknown(0) is allowed only when the session is singleHop(1) and the outgoing - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 interface is of type point-to-point, or when the BFD session is not associated with a specific interface. If any other unsupported values are attempted in a set operation, the agent MUST return an inconsistentValue error." ::= { bfdSessEntry 20 } bfdSessDstAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create @@ -614,21 +614,21 @@ this object SHOULD be set to maximum TTL allowed for single hop. The value of zero(0) indicates that bfdSessGTSM is disabled." REFERENCE "RFC5082, The Generalized TTL Security Mechanism (GTSM). RFC5881, Section 5" DEFVAL { 0 } ::= { bfdSessEntry 23 } bfdSessDesiredMinTxInterval OBJECT-TYPE - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 SYNTAX BfdIntervalTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the minimum interval, in microseconds, that the local system would like to use when transmitting BFD Control packets. The value of zero(0) is reserved, and should not be used." REFERENCE @@ -663,21 +663,21 @@ this is a multihop BFD session." ::= { bfdSessEntry 26 } bfdSessDetectMult OBJECT-TYPE SYNTAX BfdMultiplierTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the Detect time multiplier." ::= { bfdSessEntry 27 } - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 bfdSessNegotiatedInterval OBJECT-TYPE SYNTAX BfdIntervalTC MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the negotiated interval, in microseconds, that the local system is transmitting BFD Control packets." ::= { bfdSessEntry 28 } @@ -713,21 +713,21 @@ REFERENCE "Sections 4.2 - 4.4 from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2012." DEFVAL { false } ::= { bfdSessEntry 31 } bfdSessAuthenticationType OBJECT-TYPE SYNTAX BfdSessAuthenticationTypeTC MAX-ACCESS read-create - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 STATUS current DESCRIPTION "The Authentication Type used for this BFD session. This field is valid only when the Authentication Present bit is set. Max-access to this object as well as other authentication related objects are set to read-create in order to support management of a single key ID at a time, key rotation is not handled. Key update in practice must be done by atomic update using a set @@ -763,21 +763,21 @@ bfdSessAuthenticationKey OBJECT-TYPE SYNTAX BfdSessionAuthenticationKeyTC MAX-ACCESS read-create STATUS current DESCRIPTION "The authentication key. When the bfdSessAuthenticationType is simplePassword(1), the value of this object is the password present in the BFD packets. When the bfdSessAuthentication type is one of the keyed - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 authentication types, this value is used in the computation of the key present in the BFD authentication packet." REFERENCE "Sections 4.2 - 4.4 from from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2012." ::= { bfdSessEntry 34 } @@ -813,21 +813,21 @@ DESCRIPTION "This table specifies BFD Session performance counters." ::= { bfdObjects 3 } bfdSessPerfEntry OBJECT-TYPE SYNTAX BfdSessPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a BFD-enabled node - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 for every BFD Session. bfdSessPerfDiscTime is used to indicate potential discontinuity for all counter objects in this table." AUGMENTS { bfdSessEntry } ::= { bfdSessPerfTable 1 } BfdSessPerfEntry ::= SEQUENCE { bfdSessPerfCtrlPktIn Counter32, bfdSessPerfCtrlPktOut Counter32, @@ -853,53 +853,53 @@ } -- Ed Note: should we add per-diag code counts here, bfdSessPerfCtrlPktIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of BFD control messages received for this - BFD session. This value MUST be equal to the least - significant 32 bits of bfdSessPerfCtrlPktInHC." + BFD session. + + It MUST be equal to the least significant 32 bits of + bfdSessPerfCtrlPktInHC if supported, and MUST do so + with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 1 } bfdSessPerfCtrlPktOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only + BFD-STD-MIB December 17, 2012 + STATUS current DESCRIPTION "The total number of BFD control messages sent for this BFD - BFD-STD-MIB June 14, 2012 - session. It MUST be equal to the least significant 32 bits of - significant 32 bits of bfdSessPerfCtrlPktOutHC - if supported, and MUST do so the rules spelled out in - RFC 2863." - + bfdSessPerfCtrlPktOutHC if supported, and MUST do so + with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 2 } bfdSessPerfCtrlPktDrop OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of BFD control messages received for this session yet dropped for being invalid. It MUST be equal to the least significant 32 bits of - significant 32 bits of bfdSessPerfCtrlPktDropHC - if supported, and MUST do so the rules spelled out in - RFC 2863." + bfdSessPerfCtrlPktDropHC if supported, and MUST do so + with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 3 } bfdSessPerfCtrlPktDropLastTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which received BFD control message for this session was dropped. If no such up event exists, this object contains @@ -908,50 +908,50 @@ bfdSessPerfEchoPktIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of BFD echo messages received for this BFD session. It MUST be equal to the least significant 32 bits of - significant 32 bits of bfdSessPerfEchoPktInHC if - supported, and MUST do so the rules spelled out in - RFC 2863." + bfdSessPerfEchoPktInHC if supported, and MUST do so + with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 5 } - BFD-STD-MIB June 14, 2012 bfdSessPerfEchoPktOut OBJECT-TYPE + BFD-STD-MIB December 17, 2012 + SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of BFD echo messages sent for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktOutHC if supported, and MUST do so - the rules spelled out in RFC 2863." + with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 6 } bfdSessPerfEchoPktDrop OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of BFD echo messages received for this session yet dropped for being invalid. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktDropHC if supported, and MUST do so - the rules spelled out in RFC 2863." + with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 7 } bfdSessPerfEchoPktDropLastTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which received BFD echo message for this session was dropped. If no such up event exists, this object contains @@ -962,23 +962,23 @@ SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which the session came up. If no such up event exists this object contains a zero value." ::= { bfdSessPerfEntry 9 } bfdSessPerfLastSessDownTime OBJECT-TYPE - BFD-STD-MIB June 14, 2012 - SYNTAX TimeStamp + BFD-STD-MIB December 17, 2012 + MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which the last time communication was lost with the neighbor. If no such down event exist this object contains a zero value." ::= { bfdSessPerfEntry 10 } bfdSessPerfLastCommLostDiag OBJECT-TYPE @@ -1012,99 +1012,99 @@ The relevant counters are the specific instances associated with this BFD session of any Counter32 object contained in the BfdSessPerfTable. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value." ::= { bfdSessPerfEntry 13 } bfdSessPerfCtrlPktInHC OBJECT-TYPE SYNTAX Counter64 - BFD-STD-MIB June 14, 2012 - MAX-ACCESS read-only + BFD-STD-MIB December 17, 2012 + STATUS current DESCRIPTION "This value represents the total number of BFD control messages received for this BFD session. - It MUST be equal to the least significant 32 bits of - bfdSessPerfCtrlPktInHC if supported, and MUST do so + The least significant 32 bits MUST equal to + bfdSessPerfCtrlPktIn, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 14 } bfdSessPerfCtrlPktOutHC OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This value represents the total number of BFD control messages transmitted for this BFD session. - It MUST be equal to the least significant 32 bits of - bfdSessPerfCtrlPktOut if supported, and MUST do so + The least significant 32 bits MUST equal to + bfdSessPerfCtrlPktOut, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 15 } bfdSessPerfCtrlPktDropHC OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This value represents the total number of BFD control messages received for this BFD session yet dropped for being invalid. - It MUST be equal to the least significant 32 bits of - bfdSessPerfCtrlPktDrop if supported, and MUST do so + The least significant 32 bits MUST equal to + bfdSessPerfCtrlPktDrop, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 16 } bfdSessPerfEchoPktInHC OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This value represents the total number of BFD echo messages received for this BFD session. - It MUST be equal to the least significant 32 bits of - bfdSessPerfEchoPktIn if supported, and MUST do so - BFD-STD-MIB June 14, 2012 - + The least significant 32 bits MUST equal to + bfdSessPerfEchoPktIn, and MUST do so with the rules spelled out in RFC 2863." + BFD-STD-MIB December 17, 2012 + ::= { bfdSessPerfEntry 17 } bfdSessPerfEchoPktOutHC OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This value represents the total number of BFD echo messages transmitted for this BFD session. - It MUST be equal to the least significant 32 bits of - bfdSessPerfEchoPktOut if supported, and MUST do so + The least significant 32 bits MUST equal to + bfdSessPerfEchoPktOut, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 18 } bfdSessPerfEchoPktDropHC OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This value represents the total number of BFD echo messages received for this BFD session yet dropped for being invalid. - It MUST be equal to the least significant 32 bits of - bfdSessPerfEchoPktDrop if supported, and MUST do so + The least significant 32 bits MUST equal to + bfdSessPerfEchoPktDrop, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 19 } -- BFD Session Discriminator Mapping Table bfdSessDiscMapTable OBJECT-TYPE SYNTAX SEQUENCE OF BfdSessDiscMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -1112,23 +1112,23 @@ local discriminator value to associated BFD session's BfdSessIndexTC used in the bfdSessionTable." ::= { bfdObjects 4 } bfdSessDiscMapEntry OBJECT-TYPE SYNTAX BfdSessDiscMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The BFD Session Discriminator Map Entry describes - BFD-STD-MIB June 14, 2012 - BFD session that is mapped to this BfdSessIndexTC." + BFD-STD-MIB December 17, 2012 + INDEX { bfdSessDiscriminator } ::= { bfdSessDiscMapTable 1 } BfdSessDiscMapEntry ::= SEQUENCE { bfdSessDiscMapIndex BfdSessIndexTC, bfdSessDiscMapStorageType StorageType, bfdSessDiscMapRowStatus RowStatus } bfdSessDiscMapIndex OBJECT-TYPE @@ -1162,23 +1162,23 @@ table has a row in the active(1) state, no objects in this row can be modified except the bfdSessDiscMapRowStatus and bfdSessDiscMapStorageType." ::= { bfdSessDiscMapEntry 3 } -- BFD Session IP Mapping Table bfdSessIpMapTable OBJECT-TYPE SYNTAX SEQUENCE OF BfdSessIpMapEntry MAX-ACCESS not-accessible - BFD-STD-MIB June 14, 2012 - STATUS current + BFD-STD-MIB December 17, 2012 + DESCRIPTION "The BFD Session IP Mapping Table maps given bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType and bfdSessDstAddr to an associated BFD session's BfdSessIndexTC used in the bfdSessionTable." ::= { bfdObjects 5 } bfdSessIpMapEntry OBJECT-TYPE SYNTAX BfdSessIpMapEntry @@ -1212,23 +1212,23 @@ provided between these indexes and the BfdSessTable." ::= { bfdSessIpMapEntry 1 } bfdSessIpMapStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object. Conceptual rows having the value - BFD-STD-MIB June 14, 2012 - 'permanent' need not allow write-access to any + BFD-STD-MIB December 17, 2012 + columnar objects in the row." ::= { bfdSessIpMapEntry 2 } bfdSessIpMapRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table. When a row in this @@ -1262,23 +1262,23 @@ notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single bfdSessEntry, then the instance identifier (and values) of the two bfdSessDiag objects MUST be the identical." ::= { bfdNotifications 1 } bfdSessDown NOTIFICATION-TYPE OBJECTS { - BFD-STD-MIB June 14, 2012 - bfdSessDiag, -- low range value + BFD-STD-MIB December 17, 2012 + bfdSessDiag -- high range value } STATUS current DESCRIPTION "This notification is generated when the bfdSessState object for one or more contiguous entries in bfdSessTable are about to enter the down(2) or adminDown(1) states from some other state. The included values of bfdSessDiag MUST both be set equal to this new state (i.e: down(2) or adminDown(1)). The two instances @@ -1311,21 +1311,21 @@ -- Compliance requirement for fully compliant implementations. bfdModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support for the BFD-MIB module. Such devices can then be monitored and also be configured using this MIB module." - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 MODULE -- This module. MANDATORY-GROUPS { bfdSessionGroup, bfdSessionReadOnlyGroup, bfdSessionPerfGroup, bfdNotificationGroup } @@ -1360,23 +1360,22 @@ WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required." OBJECT bfdSessDiscMapRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not - BFD-STD-MIB June 14, 2012 - required." + BFD-STD-MIB December 17, 2012 OBJECT bfdSessIpMapRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required." ::= { bfdCompliances 1 } @@ -1409,21 +1408,21 @@ MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT bfdSessDestinationUdpPort MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT bfdSessSourceUdpPort MIN-ACCESS read-only DESCRIPTION "Write access is not required." - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 OBJECT bfdSessEchoSourceUdpPort MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT bfdSessAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT bfdSessOperMode @@ -1458,21 +1457,21 @@ MIN-ACCESS read-only DESCRIPTION "An implementation is only required to support unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." OBJECT bfdSessDstAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), ipv6z(4) } MIN-ACCESS read-only DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) support are required." - BFD-STD-MIB June 14, 2012 + BFD-STD-MIB December 17, 2012 OBJECT bfdSessDstAddr SYNTAX InetAddress (SIZE (0|4|16|20)) MIN-ACCESS read-only DESCRIPTION "An implementation is only required to support unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." OBJECT bfdSessGTSM MIN-ACCESS read-only DESCRIPTION "Write access is not required." @@ -1507,23 +1506,23 @@ OBJECT bfdSessAuthenticationKeyID MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT bfdSessAuthenticationKey MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT bfdSessStorageType - BFD-STD-MIB June 14, 2012 - MIN-ACCESS read-only + BFD-STD-MIB December 17, 2012 + DESCRIPTION "Write access is not required." OBJECT bfdSessRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT bfdSessDiscMapStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." @@ -1557,23 +1556,23 @@ bfdSessEchoSourceUdpPort, bfdSessAdminStatus, bfdSessOperMode, bfdSessDemandModeDesiredFlag, bfdSessControlPlaneIndepFlag, bfdSessMultipointFlag, bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, - BFD-STD-MIB June 14, 2012 - bfdSessDstAddr, + BFD-STD-MIB December 17, 2012 + bfdSessGTSM, bfdSessGTSMTTL, bfdSessDesiredMinTxInterval, bfdSessReqMinRxInterval, bfdSessReqMinEchoRxInterval, bfdSessDetectMult, bfdSessAuthPresFlag, bfdSessAuthenticationType, bfdSessAuthenticationKeyID, bfdSessAuthenticationKey, @@ -1607,23 +1606,23 @@ "Collection of read-only objects needed for BFD sessions." ::= { bfdGroups 2 } bfdSessionPerfGroup OBJECT-GROUP OBJECTS { bfdSessPerfCtrlPktIn, bfdSessPerfCtrlPktOut, bfdSessPerfCtrlPktDrop, bfdSessPerfCtrlPktDropLastTime, bfdSessPerfEchoPktIn, - BFD-STD-MIB June 14, 2012 - bfdSessPerfEchoPktOut, + BFD-STD-MIB December 17, 2012 + bfdSessPerfEchoPktDrop, bfdSessPerfEchoPktDropLastTime, bfdSessUpTime, bfdSessPerfLastSessDownTime, bfdSessPerfLastCommLostDiag, bfdSessPerfSessUpCount, bfdSessPerfDiscTime } STATUS current DESCRIPTION @@ -1655,23 +1654,24 @@ } STATUS current DESCRIPTION "Set of notifications implemented in this module." ::= { bfdGroups 5 } END 6. Security Considerations - BFD-STD-MIB June 14, 2012 As BFD may be tied into the stability of the network infrastructure + BFD-STD-MIB December 17, 2012 + (such as routing protocols), the effects of an attack on a BFD session may be very serious. This ultimately has denial-of-service effects, as links may be declared to be down (or falsely declared to be up.) As such, improper manipulation of the objects represented by this MIB may result in denial of service to a large number of end- users. There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network @@ -1704,23 +1704,23 @@ disruption of traffic on the network. This is especially true if an unauthorized user configures enough tables to invoke a denial of service attack on the device where they are configured, or on a remote device where the sessions terminate. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over - BFD-STD-MIB June 14, 2012 - the network via SNMP. These are the tables and objects and their + BFD-STD-MIB December 17, 2012 + sensitivity/vulnerability: o The bfdSessPerfTable both allows access to the performance characteristics of BFD sessions. Network administrators not wishing to show this information should consider this table sensitive. The bfdSessAuthenticationType, bfdSessAuthenticationKeyID, and bfdSessAuthenticationKey objects hold security methods and associated security keys of BFD sessions. These objects SHOULD be considered @@ -1753,23 +1753,23 @@ OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER value ---------- ----------------------- bfdMib { mib-2 XXX } [Editor's Note (to be removed prior to publication): the IANA is requested to assign a value for "XXX" under the 'mib-2' subtree and to record the assignment in the SMI Numbers registry. When the - BFD-STD-MIB June 14, 2012 - assignment has been made, the RFC Editor is asked to replace "XXX" + BFD-STD-MIB December 17, 2012 + (here and in the MIB module) with the assigned value and to remove this note.] This document also requests IANA to manage the registry for the BfdDiagTC object. 8. References 8.1. Normative References @@ -1802,23 +1802,23 @@ April 1999. 8.2. Informative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. - BFD-STD-MIB June 14, 2012 - [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, + BFD-STD-MIB December 17, 2012 + "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005. @@ -1838,17 +1838,16 @@ Zafar Ali Cisco Systems, Inc. 2000 Innovation Drive Kanata, Ontario K2K 3E8 Canada Email: zali@cisco.com Nobo Akiya - Cisco Systems G.K. - Shinjuku Mitsui Building - 2-1-1 Nishi-Shinjuku, Shinjuku-Ku - Tokyo 163-0409 - Japan + Cisco Systems, Inc. + 2000 Innovation Drive + Kanata, Ontario K2K 3E8 + Canada Email: nobo@cisco.com