--- 1/draft-ietf-bfd-mib-12.txt 2013-06-17 16:14:21.982733284 +0100 +++ 2/draft-ietf-bfd-mib-13.txt 2013-06-17 16:14:22.054735098 +0100 @@ -1,141 +1,136 @@ + Network Working Group T. Nadeau -Internet Draft Juniper Networks +Internet-Draft Juniper Networks Intended status: Standards Track Z. Ali -Expires: June 17, 2013 N. Akiya +Expires: December 19, 2013 N. Akiya Cisco Systems - December 17, 2012 + June 17, 2013 BFD Management Information Base - draft-ietf-bfd-mib-12 + draft-ietf-bfd-mib-13 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 +Requirements Language + + The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", + "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this + document are to be interpreted as described in BCP 14, RFC 2119 + [RFC2119]. + +Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 June 17, 2013. + This Internet-Draft will expire on December 19, 2013. Copyright Notice - BFD-STD-MIB December 17, 2012 - Copyright (c) 2012 IETF Trust and the persons identified as the + Copyright (c) 2013 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 include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. -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 . . . . . . . . . . 2 - 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 1. The Internet-Standard Management Framework . . . . . . . . . 2 + 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 4. Brief Description of MIB Objects . . . . . . . . . . . . . . . 3 + 4. Brief Description of MIB Objects . . . . . . . . . . . . . . 3 4.1. General Variables . . . . . . . . . . . . . . . . . . . . 3 4.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 3 - 4.3. Session Performance Table (bfdSessionPerfTable) . . . . . 4 + 4.3. Session Performance Table (bfdSessionPerfTable) . . . . . 3 4.4. BFD Session Discriminator Mapping Table - (bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 4 - 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . . 4 - 5. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . . 4 + (bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 3 + 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . 3 + 5. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . 4 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 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 36 + 8.2. Informative References . . . . . . . . . . . . . . . . . 37 + Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current - BFD-STD-MIB December 17, 2012 - Internet-Standard Management Framework, please refer to section 7 of - [RFC3410]. + RFC 3410 [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, - [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. + RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 + [RFC2580]. 2. Introduction - This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or - monitor Bi-Directional Forwarding Detection for [BFD], [BFD-1HOP] and - [BFD-MH], BFD versions 0 and/or 1, on devices supporting this + monitor Bi-Directional Forwarding Detection for [RFC5880], [RFC5881] + and [RFC5883], BFD versions 0 and/or 1, on devices supporting this feature. - Comments should be made directly to the BFD mailing list at - rtg-bfd@ietf.org. + Comments should be made directly to the BFD mailing list at rtg- + bfd@ietf.org. 3. Terminology This document adopts the definitions, acronyms and mechanisms - described in [BFD], [BFD-1HOP] and [BFD-MH]. Unless otherwise + described in [RFC5880], [RFC5881] and [RFC5883]. Unless otherwise stated, the mechanisms described therein will not be re-described here. 4. Brief Description of MIB Objects This section describes objects pertaining to BFD. The MIB objects - are derived from [BFD] and [BFD-MH], and also include textual - conventions defined in [BFD-TC]. + are derived from [RFC5880], [RFC5881] and [RFC5883], and also include + textual conventions defined in [I-D.ietf-bfd-tc-mib]. 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 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 discriminator value to associated BFD session's BfdSessIndexTC used @@ -135,26 +130,25 @@ 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 discriminator value to associated BFD session's BfdSessIndexTC used in the bfdSessionTable. 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) - 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. This table SHOULD contains those - BFD sessions that are of IP type. + bfdSessDstAddr, to an associated BFD session's BfdSessIndexTC used in + the bfdSessionTable. This table SHOULD contains those BFD sessions + that are of IP type. 5. BFD MIB Module Definitions This MIB module makes references to the following documents. [RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC3413]. BFD-STD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, @@ -165,30 +159,29 @@ 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 December 17, 2012 BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, BfdDiagTC, BfdSessTypeTC, BfdSessOperModeTC, BfdCtrlDestPortNumberTC, BfdCtrlSourcePortNumberTC, BfdSessStateTC, BfdSessAuthenticationTypeTC, BfdSessionAuthenticationKeyTC FROM BFD-TC-STD-MIB; bfdMIB MODULE-IDENTITY - LAST-UPDATED "201212171200Z" -- 17 December 2012 12:00:00 EST + LAST-UPDATED "201306171200Z" -- 17 June 2013 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 @@ -185,27 +178,26 @@ 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. + Cisco Systems, Inc. Email: nobo@cisco.com" DESCRIPTION "Bidirectional Forwarding Management Information Base." - REVISION "201212171200Z" -- 17 December 2012 12:00:00 EST + REVISION "201306171200Z" -- 17 June 2013 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,22 +207,20 @@ 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 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 it on all interfaces." @@ -265,22 +255,20 @@ "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 December 17, 2012 - DESCRIPTION "The BFD Session Entry describes BFD session." INDEX { bfdSessIndex } ::= { bfdSessTable 1 } BfdSessEntry ::= SEQUENCE { bfdSessIndex BfdSessIndexTC, bfdSessVersionNumber Unsigned32, bfdSessType BfdSessTypeTC, bfdSessDiscriminator Unsigned32, @@ -315,22 +303,20 @@ bfdSessAuthenticationKeyID Integer32, bfdSessAuthenticationKey BfdSessionAuthenticationKeyTC, bfdSessStorageType StorageType, bfdSessRowStatus RowStatus } bfdSessIndex OBJECT-TYPE SYNTAX BfdSessIndexTC MAX-ACCESS not-accessible STATUS current - 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 DESCRIPTION @@ -365,22 +351,20 @@ 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 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 used for this BFD session's control packets. The value @@ -391,54 +375,52 @@ bfdSessSourceUdpPort OBJECT-TYPE SYNTAX BfdCtrlSourcePortNumberTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the source UDP port number used for this BFD session's control packets. The value may be zero(0) if the session is in adminDown(1) state. Upon creation of a new BFD session via this MIB, the value of zero(0) specified would permit the implementation to - chose its own source port number." + choose its own source port number." DEFVAL { 0 } ::= { bfdSessEntry 7 } bfdSessEchoSourceUdpPort OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the source UDP port number used for this BFD session's echo packets. The value may be zero(0) if the session is not running in the echo mode, or the session is in adminDown(1) state. Upon creation of a new BFD session via this MIB, the value of zero(0) would - permit the implementation to chose its own source port + permit the implementation to choose its own source port number." DEFVAL { 0 } ::= { bfdSessEntry 8 } bfdSessAdminStatus OBJECT-TYPE SYNTAX INTEGER { stop(1), start(2) } - 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 + the BFD session to be brought down to adminDown(1). Care should be used in providing write access to this object without adequate authentication." DEFVAL { 2 } ::= { bfdSessEntry 9 } bfdSessState OBJECT-TYPE SYNTAX BfdSessStateTC MAX-ACCESS read-only STATUS current @@ -465,22 +448,20 @@ 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 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 session is operating in." @@ -515,21 +496,20 @@ 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 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." @@ -536,23 +516,24 @@ ::= { bfdSessEntry 17 } bfdSessSrcAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies IP address type of the source IP address of 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 source IP address of this BFD - session is drived from the outgoing interface, or when + session is derived from the outgoing interface, 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 18 } bfdSessSrcAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current @@ -564,22 +545,20 @@ 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 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 STATUS current @@ -614,22 +593,20 @@ 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 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 "Section 4.1 from Katz, D. and D. Ward, Bidirectional @@ -663,21 +640,20 @@ 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 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,22 +689,20 @@ 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 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 containing all affected objects in the same varBindList @@ -763,27 +737,25 @@ 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 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, + "Sections 4.2 - 4.4 from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2012." ::= { bfdSessEntry 34 } bfdSessStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this @@ -813,22 +785,20 @@ 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 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, bfdSessPerfCtrlPktDrop Counter32, @@ -863,22 +832,20 @@ 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 session. It MUST be equal to the least significant 32 bits of bfdSessPerfCtrlPktOutHC if supported, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 2 } @@ -913,22 +881,20 @@ DESCRIPTION "The total number of BFD echo messages received for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktInHC if supported, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 5 } 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 with the rules spelled out in RFC 2863." @@ -963,22 +929,20 @@ 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 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 @@ -1013,22 +977,20 @@ 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 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. The least significant 32 bits MUST equal to bfdSessPerfCtrlPktIn, and MUST do so with the rules spelled out in RFC 2863." ::= { bfdSessPerfEntry 14 } @@ -1063,22 +1026,20 @@ SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This value represents the total number of BFD echo messages received for this BFD session. 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. @@ -1113,22 +1074,20 @@ 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 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 @@ -1163,22 +1122,20 @@ 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 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 @@ -1213,22 +1171,20 @@ ::= { 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 '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 @@ -1263,22 +1220,20 @@ 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 { 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 +1266,20 @@ -- 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 December 17, 2012 MODULE -- This module. MANDATORY-GROUPS { bfdSessionGroup, bfdSessionReadOnlyGroup, bfdSessionPerfGroup, bfdNotificationGroup } @@ -1361,21 +1315,20 @@ 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 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 } @@ -1408,21 +1361,20 @@ 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 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 @@ -1457,21 +1409,20 @@ 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 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,22 +1457,20 @@ 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 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,22 +1505,20 @@ bfdSessAdminStatus, bfdSessOperMode, bfdSessDemandModeDesiredFlag, bfdSessControlPlaneIndepFlag, bfdSessMultipointFlag, bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, bfdSessDstAddr, - BFD-STD-MIB December 17, 2012 - bfdSessGTSM, bfdSessGTSMTTL, bfdSessDesiredMinTxInterval, bfdSessReqMinRxInterval, bfdSessReqMinEchoRxInterval, bfdSessDetectMult, bfdSessAuthPresFlag, bfdSessAuthenticationType, bfdSessAuthenticationKeyID, bfdSessAuthenticationKey, @@ -1607,22 +1553,20 @@ ::= { bfdGroups 2 } bfdSessionPerfGroup OBJECT-GROUP OBJECTS { bfdSessPerfCtrlPktIn, bfdSessPerfCtrlPktOut, bfdSessPerfCtrlPktDrop, bfdSessPerfCtrlPktDropLastTime, bfdSessPerfEchoPktIn, bfdSessPerfEchoPktOut, - BFD-STD-MIB December 17, 2012 - bfdSessPerfEchoPktDrop, bfdSessPerfEchoPktDropLastTime, bfdSessUpTime, bfdSessPerfLastSessDownTime, bfdSessPerfLastCommLostDiag, bfdSessPerfSessUpCount, bfdSessPerfDiscTime } STATUS current DESCRIPTION @@ -1656,22 +1601,20 @@ DESCRIPTION "Set of notifications implemented in this module." ::= { bfdGroups 5 } END 6. Security Considerations 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 @@ -1705,44 +1648,42 @@ 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 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 highly sensitive objects. In order for these sensitive information - from being improperly accessed, implementors MAY wish to disallow + from being improperly accessed, implementers MAY wish to disallow read and create access to these objects. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure "for example by using IPSec", even then, there is no control as to who on the secure network is allowed to access and GET/SET "read/change/create/delete" the objects in these MIB modules. It is RECOMMENDED that implementers consider the security features as - provided by the SNMPv3 framework "see [RFC3410], section 8", + provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms "for authentication and privacy". Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module, is properly configured to give access to the objects only to those principals "users" that have legitimate rights to indeed GET or SET "change/create/delete" them. @@ -1754,100 +1695,90 @@ 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 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 - [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding - Detection (BFD)", RFC 5880, June 2012. - - [BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding - Detection (BFD) for IPv4 and IPv6 (Single Hop)", - RFC 5881, June 2012. - - [BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding - Detection (BFD) for Multihop Paths", RFC 5883, - June 2012. - - [BFD-TC] Nadeau, T., Ali, Z. and N. Akiya, "Definitions of Textual - Conventions (TCs) for Bidirectional Forwarding Detection - (BFD) Management", - ID Document: draft-ietf-bfd-tc-mib-01.txt, June 2012. + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate + Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. - Schoenwaelder, Ed., "Textual Conventions for SMIv2", - STD 58, RFC 2579, April 1999. + Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD + 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. -8.2. Informative References + [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection + (BFD)", RFC 5880, June 2010. - [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. + [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection + (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June + 2010. - [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group - MIB", RFC 2863, June 2000. + [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection + (BFD) for Multihop Paths", RFC 5883, June 2010. - [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, - BFD-STD-MIB December 17, 2012 + [I-D.ietf-bfd-tc-mib] + Nadeau, T., Ali, Z., and N. Akiya, "Definitions of Textual + Conventions (TCs) for Bidirectional Forwarding Detection + (BFD) Management", draft-ietf-bfd-tc-mib-01 (work in + progress), June 2012. +8.2. Informative References + + [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "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. + [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group + MIB", RFC 2863, June 2000. + + [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network + Management Protocol (SNMP) Applications", STD 62, RFC + 3413, December 2002. + Appendix A. Acknowledgments - We would like to thank David Ward, Jeffrey Haas, Reshad Rahman, David - Toscano, Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara + Authors would like to thank David Ward, Jeffrey Haas, Reshad Rahman, + David Toscano, Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara Sreenivasa for their comments and suggestions. Authors' Addresses Thomas D. Nadeau Juniper Networks - Email: tnadeau@juniper.net + EMail: tnadeau@juniper.net Zafar Ali - Cisco Systems, Inc. - 2000 Innovation Drive - Kanata, Ontario K2K 3E8 - Canada + Cisco Systems - Email: zali@cisco.com + EMail: zali@cisco.com Nobo Akiya - Cisco Systems, Inc. - 2000 Innovation Drive - Kanata, Ontario K2K 3E8 - Canada + Cisco Systems - Email: nobo@cisco.com + EMail: nobo@cisco.com