draft-ietf-bfd-mib-12.txt   draft-ietf-bfd-mib-13.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: June 17, 2013 N. Akiya Expires: December 19, 2013 N. Akiya
Cisco Systems Cisco Systems
December 17, 2012 June 17, 2013
BFD Management Information Base BFD Management Information Base
draft-ietf-bfd-mib-12 draft-ietf-bfd-mib-13
Abstract Abstract
This draft defines a portion of the Management Information Base (MIB) This draft defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling In particular, it describes managed objects for modeling
Bidirectional Forwarding Detection (BFD) protocol. 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 This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on June 17, 2013. This Internet-Draft will expire on December 19, 2013.
Copyright Notice 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. 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. 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 Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . 2 1. The Internet-Standard Management Framework . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Brief Description of MIB Objects . . . . . . . . . . . . . . . 3 4. Brief Description of MIB Objects . . . . . . . . . . . . . . 3
4.1. General Variables . . . . . . . . . . . . . . . . . . . . 3 4.1. General Variables . . . . . . . . . . . . . . . . . . . . 3
4.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 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 4.4. BFD Session Discriminator Mapping Table
(bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 4 (bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 3
4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . . 4 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . 3
5. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . . 4 5. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 34 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.1. Normative References . . . . . . . . . . . . . . . . . . . 37 8.1. Normative References . . . . . . . . . . . . . . . . . . 36
8.2. Informative References . . . . . . . . . . . . . . . . . . 37 8.2. Informative References . . . . . . . . . . . . . . . . . 37
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 38 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current 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 Internet-Standard Management Framework, please refer to section 7 of
[RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 2. Introduction
This memo defines an portion of the Management Information Base (MIB) This memo defines an portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects to configure and/or In particular, it describes managed objects to configure and/or
monitor Bi-Directional Forwarding Detection for [BFD], [BFD-1HOP] and monitor Bi-Directional Forwarding Detection for [RFC5880], [RFC5881]
[BFD-MH], BFD versions 0 and/or 1, on devices supporting this and [RFC5883], BFD versions 0 and/or 1, on devices supporting this
feature. feature.
Comments should be made directly to the BFD mailing list at Comments should be made directly to the BFD mailing list at rtg-
rtg-bfd@ietf.org. bfd@ietf.org.
3. Terminology 3. Terminology
This document adopts the definitions, acronyms and mechanisms 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 stated, the mechanisms described therein will not be re-described
here. here.
4. Brief Description of MIB Objects 4. Brief Description of MIB Objects
This section describes objects pertaining to BFD. The MIB objects This section describes objects pertaining to BFD. The MIB objects
are derived from [BFD] and [BFD-MH], and also include textual are derived from [RFC5880], [RFC5881] and [RFC5883], and also include
conventions defined in [BFD-TC]. textual conventions defined in [I-D.ietf-bfd-tc-mib].
4.1. General Variables 4.1. General Variables
The General Variables are used to identify parameters that are global The General Variables are used to identify parameters that are global
to the BFD process. to the BFD process.
4.2. Session Table (bfdSessionTable) 4.2. Session Table (bfdSessionTable)
The session table is used to identify a BFD session between a pair of The session table is used to identify a BFD session between a pair of
nodes. nodes.
BFD-STD-MIB December 17, 2012
4.3. Session Performance Table (bfdSessionPerfTable) 4.3. Session Performance Table (bfdSessionPerfTable)
The session performance table is used for collecting BFD performance The session performance table is used for collecting BFD performance
counters on a per session basis. This table is an AUGMENT to the counters on a per session basis. This table is an AUGMENT to the
bfdSessionTable. bfdSessionTable.
4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) 4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable)
The BFD Session Discriminator Mapping Table maps a local The BFD Session Discriminator Mapping Table maps a local
discriminator value to associated BFD session's BfdSessIndexTC used discriminator value to associated BFD session's BfdSessIndexTC used
skipping to change at page 4, line 20 skipping to change at page 4, line 4
counters on a per session basis. This table is an AUGMENT to the counters on a per session basis. This table is an AUGMENT to the
bfdSessionTable. bfdSessionTable.
4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) 4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable)
The BFD Session Discriminator Mapping Table maps a local The BFD Session Discriminator Mapping Table maps a local
discriminator value to associated BFD session's BfdSessIndexTC used discriminator value to associated BFD session's BfdSessIndexTC used
in the bfdSessionTable. in the bfdSessionTable.
4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable)
The BFD Session IP Mapping Table maps, given bfdSessInterface, The BFD Session IP Mapping Table maps, given bfdSessInterface,
bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and
bfdSessDstAddr, to an associated BFD session's BfdSessIndexTC bfdSessDstAddr, to an associated BFD session's BfdSessIndexTC used in
used in the bfdSessionTable. This table SHOULD contains those the bfdSessionTable. This table SHOULD contains those BFD sessions
BFD sessions that are of IP type. that are of IP type.
5. BFD MIB Module Definitions 5. BFD MIB Module Definitions
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC3413]. [RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC3413].
BFD-STD-MIB DEFINITIONS ::= BEGIN BFD-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
skipping to change at page 5, line 4 skipping to change at page 4, line 33
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
InetAddress, InetAddressType, InetPortNumber InetAddress, InetAddressType, InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
BFD-STD-MIB December 17, 2012
BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, BfdDiagTC, BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, BfdDiagTC,
BfdSessTypeTC, BfdSessOperModeTC, BfdCtrlDestPortNumberTC, BfdSessTypeTC, BfdSessOperModeTC, BfdCtrlDestPortNumberTC,
BfdCtrlSourcePortNumberTC, BfdSessStateTC, BfdCtrlSourcePortNumberTC, BfdSessStateTC,
BfdSessAuthenticationTypeTC, BfdSessionAuthenticationKeyTC BfdSessAuthenticationTypeTC, BfdSessionAuthenticationKeyTC
FROM BFD-TC-STD-MIB; FROM BFD-TC-STD-MIB;
bfdMIB MODULE-IDENTITY 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 ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Thomas D. Nadeau
Juniper Networks Juniper Networks
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Email: zali@cisco.com Email: zali@cisco.com
skipping to change at page 5, line 24 skipping to change at page 5, line 4
ORGANIZATION "IETF Bidirectional Forwarding Detection ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Thomas D. Nadeau
Juniper Networks Juniper Networks
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Email: zali@cisco.com Email: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems, G.K. Cisco Systems, Inc.
Email: nobo@cisco.com" Email: nobo@cisco.com"
DESCRIPTION DESCRIPTION
"Bidirectional Forwarding Management Information Base." "Bidirectional Forwarding Management Information Base."
REVISION "201212171200Z" -- 17 December 2012 12:00:00 EST REVISION "201306171200Z" -- 17 June 2013 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." "Initial version. Published as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: assigned by IANA, see section 7.1 for details -- RFC Ed.: assigned by IANA, see section 7.1 for details
-- Top level components of this MIB module. -- Top level components of this MIB module.
bfdNotifications OBJECT IDENTIFIER ::= { bfdMIB 0 } bfdNotifications OBJECT IDENTIFIER ::= { bfdMIB 0 }
bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 } bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 }
bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 2 } bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 2 }
bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 }
-- BFD General Variables -- BFD General Variables
-- These parameters apply globally to the Systems' -- These parameters apply globally to the Systems'
-- BFD Process. -- BFD Process.
bfdAdminStatus OBJECT-TYPE bfdAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
BFD-STD-MIB December 17, 2012
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The global administrative status of BFD in this device. "The global administrative status of BFD in this device.
The value 'enabled' denotes that the BFD Process is The value 'enabled' denotes that the BFD Process is
active on at least one interface; 'disabled' disables active on at least one interface; 'disabled' disables
it on all interfaces." it on all interfaces."
skipping to change at page 6, line 35 skipping to change at page 6, line 14
the emission of bfdSessUp and bfdSessDown the emission of bfdSessUp and bfdSessDown
notifications; otherwise these notifications are not notifications; otherwise these notifications are not
emitted." emitted."
REFERENCE REFERENCE
"See also RFC3413 for explanation that "See also RFC3413 for explanation that
notifications are under the ultimate control of the notifications are under the ultimate control of the
MIB modules in this document." MIB modules in this document."
DEFVAL { false } DEFVAL { false }
::= { bfdScalarObjects 2 } ::= { bfdScalarObjects 2 }
-- BFD Session Table -- BFD Session Table
-- The BFD Session Table specifies BFD session specific -- The BFD Session Table specifies BFD session specific
-- information. -- information.
bfdSessTable OBJECT-TYPE bfdSessTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessEntry SYNTAX SEQUENCE OF BfdSessEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Table describes the BFD sessions." "The BFD Session Table describes the BFD sessions."
REFERENCE REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding "Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2012." Detection (BFD), RFC 5880, June 2012."
::= { bfdObjects 2 } ::= { bfdObjects 2 }
bfdSessEntry OBJECT-TYPE bfdSessEntry OBJECT-TYPE
SYNTAX BfdSessEntry SYNTAX BfdSessEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
BFD-STD-MIB December 17, 2012
DESCRIPTION DESCRIPTION
"The BFD Session Entry describes BFD session." "The BFD Session Entry describes BFD session."
INDEX { bfdSessIndex } INDEX { bfdSessIndex }
::= { bfdSessTable 1 } ::= { bfdSessTable 1 }
BfdSessEntry ::= SEQUENCE { BfdSessEntry ::= SEQUENCE {
bfdSessIndex BfdSessIndexTC, bfdSessIndex BfdSessIndexTC,
bfdSessVersionNumber Unsigned32, bfdSessVersionNumber Unsigned32,
bfdSessType BfdSessTypeTC, bfdSessType BfdSessTypeTC,
bfdSessDiscriminator Unsigned32, bfdSessDiscriminator Unsigned32,
skipping to change at page 8, line 4 skipping to change at page 7, line 33
bfdSessAuthenticationKeyID Integer32, bfdSessAuthenticationKeyID Integer32,
bfdSessAuthenticationKey BfdSessionAuthenticationKeyTC, bfdSessAuthenticationKey BfdSessionAuthenticationKeyTC,
bfdSessStorageType StorageType, bfdSessStorageType StorageType,
bfdSessRowStatus RowStatus bfdSessRowStatus RowStatus
} }
bfdSessIndex OBJECT-TYPE bfdSessIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
BFD-STD-MIB December 17, 2012
DESCRIPTION DESCRIPTION
"This object contains an index used to represent a "This object contains an index used to represent a
unique BFD session on this device." unique BFD session on this device."
::= { bfdSessEntry 1 } ::= { bfdSessEntry 1 }
bfdSessVersionNumber OBJECT-TYPE bfdSessVersionNumber OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 9, line 4 skipping to change at page 8, line 33
SYNTAX Unsigned32 (0 | 1..4294967295) SYNTAX Unsigned32 (0 | 1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the session discriminator chosen "This object specifies the session discriminator chosen
by the remote system for this BFD session. The value may by the remote system for this BFD session. The value may
be zero(0) if the remote discriminator is not yet known be zero(0) if the remote discriminator is not yet known
or if the session is in the down or adminDown(1) state." or if the session is in the down or adminDown(1) state."
REFERENCE REFERENCE
"Section 6.8.6, from Katz, D. and D. Ward, Bidirectional "Section 6.8.6, from Katz, D. and D. Ward, Bidirectional
BFD-STD-MIB December 17, 2012
Forwarding Detection (BFD), RFC 5880, June 2012." Forwarding Detection (BFD), RFC 5880, June 2012."
::= { bfdSessEntry 5 } ::= { bfdSessEntry 5 }
bfdSessDestinationUdpPort OBJECT-TYPE bfdSessDestinationUdpPort OBJECT-TYPE
SYNTAX BfdCtrlDestPortNumberTC SYNTAX BfdCtrlDestPortNumberTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the destination UDP port number "This object specifies the destination UDP port number
used for this BFD session's control packets. The value used for this BFD session's control packets. The value
skipping to change at page 9, line 30 skipping to change at page 9, line 8
bfdSessSourceUdpPort OBJECT-TYPE bfdSessSourceUdpPort OBJECT-TYPE
SYNTAX BfdCtrlSourcePortNumberTC SYNTAX BfdCtrlSourcePortNumberTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the source UDP port number used "This object specifies the source UDP port number used
for this BFD session's control packets. The value may be for this BFD session's control packets. The value may be
zero(0) if the session is in adminDown(1) state. Upon zero(0) if the session is in adminDown(1) state. Upon
creation of a new BFD session via this MIB, the value of creation of a new BFD session via this MIB, the value of
zero(0) specified would permit the implementation to zero(0) specified would permit the implementation to
chose its own source port number." choose its own source port number."
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 7 } ::= { bfdSessEntry 7 }
bfdSessEchoSourceUdpPort OBJECT-TYPE bfdSessEchoSourceUdpPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the source UDP port number used for "This object specifies the source UDP port number used for
this BFD session's echo packets. The value may be zero(0) this BFD session's echo packets. The value may be zero(0)
if the session is not running in the echo mode, or the if the session is not running in the echo mode, or the
session is in adminDown(1) state. Upon creation of a new session is in adminDown(1) state. Upon creation of a new
BFD session via this MIB, the value of zero(0) would 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." number."
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 8 } ::= { bfdSessEntry 8 }
bfdSessAdminStatus OBJECT-TYPE bfdSessAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stop(1), stop(1),
start(2) start(2)
} }
BFD-STD-MIB December 17, 2012
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A transition from 'stop' to 'start' will start "A transition from 'stop' to 'start' will start
the BFD state machine for the session. The state the BFD state machine for the session. The state
machine will have an initial state of down. machine will have an initial state of down.
A transition from 'start' to 'stop' will cause 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 adminDown(1). Care should be used in providing
write access to this object without adequate write access to this object without adequate
authentication." authentication."
DEFVAL { 2 } DEFVAL { 2 }
::= { bfdSessEntry 9 } ::= { bfdSessEntry 9 }
bfdSessState OBJECT-TYPE bfdSessState OBJECT-TYPE
SYNTAX BfdSessStateTC SYNTAX BfdSessStateTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 11, line 4 skipping to change at page 10, line 33
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 11 } ::= { bfdSessEntry 11 }
bfdSessDiag OBJECT-TYPE bfdSessDiag OBJECT-TYPE
SYNTAX BfdDiagTC SYNTAX BfdDiagTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A diagnostic code specifying the local system's reason "A diagnostic code specifying the local system's reason
for the last transition of the session from up(4) for the last transition of the session from up(4)
BFD-STD-MIB December 17, 2012
to some other state." to some other state."
::= { bfdSessEntry 12 } ::= { bfdSessEntry 12 }
bfdSessOperMode OBJECT-TYPE bfdSessOperMode OBJECT-TYPE
SYNTAX BfdSessOperModeTC SYNTAX BfdSessOperModeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies current operating mode that BFD "This object specifies current operating mode that BFD
session is operating in." session is operating in."
skipping to change at page 12, line 4 skipping to change at page 11, line 32
bfdSessMultipointFlag OBJECT-TYPE bfdSessMultipointFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Multipoint (M) bit for this "This object indicates the Multipoint (M) bit for this
session. It is set to true(1) if Multipoint (M) bit is session. It is set to true(1) if Multipoint (M) bit is
set to 1. Otherwise, the value is set to false(2)" set to 1. Otherwise, the value is set to false(2)"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 16 } ::= { bfdSessEntry 16 }
BFD-STD-MIB December 17, 2012
bfdSessInterface OBJECT-TYPE bfdSessInterface OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an interface index used to indicate "This object contains an interface index used to indicate
the interface which this BFD session is running on. This the interface which this BFD session is running on. This
value can be zero if there is no interface associated value can be zero if there is no interface associated
with this BFD session." with this BFD session."
skipping to change at page 12, line 25 skipping to change at page 12, line 4
::= { bfdSessEntry 17 } ::= { bfdSessEntry 17 }
bfdSessSrcAddrType OBJECT-TYPE bfdSessSrcAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies IP address type of the source IP "This object specifies IP address type of the source IP
address of this BFD session. Only values unknown(0), address of this BFD session. Only values unknown(0),
ipv4(1), ipv6(2), or ipv6z(4) have to be supported. ipv4(1), ipv6(2), or ipv6z(4) have to be supported.
The value of unknown(0) is allowed only when the session The value of unknown(0) is allowed only when the session
is singleHop(1) and the source IP address of this BFD 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 the BFD session is not associated with a specific
interface. If any other unsupported values are attempted interface. If any other unsupported values are attempted
in a set operation, the agent MUST return an in a set operation, the agent MUST return an
inconsistentValue error." inconsistentValue error."
::= { bfdSessEntry 18 } ::= { bfdSessEntry 18 }
bfdSessSrcAddr OBJECT-TYPE bfdSessSrcAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 13, line 4 skipping to change at page 12, line 33
bfdSessDstAddrType OBJECT-TYPE bfdSessDstAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies IP address type of the neighboring IP "This object specifies IP address type of the neighboring IP
address which is being monitored with this BFD session. address which is being monitored with this BFD session.
Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4) Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4)
have to be supported. The value of unknown(0) is allowed have to be supported. The value of unknown(0) is allowed
only when the session is singleHop(1) and the outgoing 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 interface is of type point-to-point, or when the BFD
session is not associated with a specific interface. If any session is not associated with a specific interface. If any
other unsupported values are attempted in a set operation, other unsupported values are attempted in a set operation,
the agent MUST return an inconsistentValue error." the agent MUST return an inconsistentValue error."
::= { bfdSessEntry 20 } ::= { bfdSessEntry 20 }
bfdSessDstAddr OBJECT-TYPE bfdSessDstAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 14, line 4 skipping to change at page 13, line 32
this object SHOULD be set to maximum TTL allowed for this object SHOULD be set to maximum TTL allowed for
single hop. The value of zero(0) indicates that single hop. The value of zero(0) indicates that
bfdSessGTSM is disabled." bfdSessGTSM is disabled."
REFERENCE REFERENCE
"RFC5082, The Generalized TTL Security Mechanism (GTSM). "RFC5082, The Generalized TTL Security Mechanism (GTSM).
RFC5881, Section 5" RFC5881, Section 5"
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 23 } ::= { bfdSessEntry 23 }
bfdSessDesiredMinTxInterval OBJECT-TYPE bfdSessDesiredMinTxInterval OBJECT-TYPE
BFD-STD-MIB December 17, 2012
SYNTAX BfdIntervalTC SYNTAX BfdIntervalTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum interval, in "This object specifies the minimum interval, in
microseconds, that the local system would like to use microseconds, that the local system would like to use
when transmitting BFD Control packets. The value of when transmitting BFD Control packets. The value of
zero(0) is reserved, and should not be used." zero(0) is reserved, and should not be used."
REFERENCE REFERENCE
"Section 4.1 from Katz, D. and D. Ward, Bidirectional "Section 4.1 from Katz, D. and D. Ward, Bidirectional
skipping to change at page 15, line 4 skipping to change at page 14, line 31
this is a multihop BFD session." this is a multihop BFD session."
::= { bfdSessEntry 26 } ::= { bfdSessEntry 26 }
bfdSessDetectMult OBJECT-TYPE bfdSessDetectMult OBJECT-TYPE
SYNTAX BfdMultiplierTC SYNTAX BfdMultiplierTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the Detect time multiplier." "This object specifies the Detect time multiplier."
::= { bfdSessEntry 27 } ::= { bfdSessEntry 27 }
BFD-STD-MIB December 17, 2012
bfdSessNegotiatedInterval OBJECT-TYPE bfdSessNegotiatedInterval OBJECT-TYPE
SYNTAX BfdIntervalTC SYNTAX BfdIntervalTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the negotiated interval, in "This object specifies the negotiated interval, in
microseconds, that the local system is transmitting microseconds, that the local system is transmitting
BFD Control packets." BFD Control packets."
::= { bfdSessEntry 28 } ::= { bfdSessEntry 28 }
skipping to change at page 16, line 4 skipping to change at page 15, line 32
REFERENCE REFERENCE
"Sections 4.2 - 4.4 from Katz, D. and D. Ward, "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), RFC 5880, Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012." June 2012."
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 31 } ::= { bfdSessEntry 31 }
bfdSessAuthenticationType OBJECT-TYPE bfdSessAuthenticationType OBJECT-TYPE
SYNTAX BfdSessAuthenticationTypeTC SYNTAX BfdSessAuthenticationTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
BFD-STD-MIB December 17, 2012
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Authentication Type used for this BFD session. "The Authentication Type used for this BFD session.
This field is valid only when the Authentication This field is valid only when the Authentication
Present bit is set. Max-access to this object as well as Present bit is set. Max-access to this object as well as
other authentication related objects are set to other authentication related objects are set to
read-create in order to support management of a single read-create in order to support management of a single
key ID at a time, key rotation is not handled. Key update key ID at a time, key rotation is not handled. Key update
in practice must be done by atomic update using a set in practice must be done by atomic update using a set
containing all affected objects in the same varBindList containing all affected objects in the same varBindList
skipping to change at page 17, line 4 skipping to change at page 16, line 31
bfdSessAuthenticationKey OBJECT-TYPE bfdSessAuthenticationKey OBJECT-TYPE
SYNTAX BfdSessionAuthenticationKeyTC SYNTAX BfdSessionAuthenticationKeyTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authentication key. When the "The authentication key. When the
bfdSessAuthenticationType is simplePassword(1), the value bfdSessAuthenticationType is simplePassword(1), the value
of this object is the password present in the BFD packets. of this object is the password present in the BFD packets.
When the bfdSessAuthentication type is one of the keyed When the bfdSessAuthentication type is one of the keyed
BFD-STD-MIB December 17, 2012
authentication types, this value is used in the authentication types, this value is used in the
computation of the key present in the BFD authentication computation of the key present in the BFD authentication
packet." packet."
REFERENCE 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, Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012." June 2012."
::= { bfdSessEntry 34 } ::= { bfdSessEntry 34 }
bfdSessStorageType OBJECT-TYPE bfdSessStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
skipping to change at page 17, line 38 skipping to change at page 17, line 15
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. When a row in this delete a row in this table. When a row in this
table has a row in the active(1) state, no table has a row in the active(1) state, no
objects in this row can be modified except the objects in this row can be modified except the
bfdSessRowStatus and bfdSessStorageType." bfdSessRowStatus and bfdSessStorageType."
::= { bfdSessEntry 36 } ::= { bfdSessEntry 36 }
-- BFD Session Performance Table -- BFD Session Performance Table
bfdSessPerfTable OBJECT-TYPE bfdSessPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessPerfEntry SYNTAX SEQUENCE OF BfdSessPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies BFD Session performance counters." "This table specifies BFD Session performance counters."
::= { bfdObjects 3 } ::= { bfdObjects 3 }
bfdSessPerfEntry OBJECT-TYPE bfdSessPerfEntry OBJECT-TYPE
SYNTAX BfdSessPerfEntry SYNTAX BfdSessPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a BFD-enabled node "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 for every BFD Session. bfdSessPerfDiscTime is used to
indicate potential discontinuity for all counter objects indicate potential discontinuity for all counter objects
in this table." in this table."
AUGMENTS { bfdSessEntry } AUGMENTS { bfdSessEntry }
::= { bfdSessPerfTable 1 } ::= { bfdSessPerfTable 1 }
BfdSessPerfEntry ::= SEQUENCE { BfdSessPerfEntry ::= SEQUENCE {
bfdSessPerfCtrlPktIn Counter32, bfdSessPerfCtrlPktIn Counter32,
bfdSessPerfCtrlPktOut Counter32, bfdSessPerfCtrlPktOut Counter32,
bfdSessPerfCtrlPktDrop Counter32, bfdSessPerfCtrlPktDrop Counter32,
skipping to change at page 18, line 26 skipping to change at page 18, line 4
bfdSessPerfCtrlPktDropLastTime TimeStamp, bfdSessPerfCtrlPktDropLastTime TimeStamp,
bfdSessPerfEchoPktIn Counter32, bfdSessPerfEchoPktIn Counter32,
bfdSessPerfEchoPktOut Counter32, bfdSessPerfEchoPktOut Counter32,
bfdSessPerfEchoPktDrop Counter32, bfdSessPerfEchoPktDrop Counter32,
bfdSessPerfEchoPktDropLastTime TimeStamp, bfdSessPerfEchoPktDropLastTime TimeStamp,
bfdSessUpTime TimeStamp, bfdSessUpTime TimeStamp,
bfdSessPerfLastSessDownTime TimeStamp, bfdSessPerfLastSessDownTime TimeStamp,
bfdSessPerfLastCommLostDiag BfdDiagTC, bfdSessPerfLastCommLostDiag BfdDiagTC,
bfdSessPerfSessUpCount Counter32, bfdSessPerfSessUpCount Counter32,
bfdSessPerfDiscTime TimeStamp, bfdSessPerfDiscTime TimeStamp,
-- High Capacity Counters -- High Capacity Counters
bfdSessPerfCtrlPktInHC Counter64, bfdSessPerfCtrlPktInHC Counter64,
bfdSessPerfCtrlPktOutHC Counter64, bfdSessPerfCtrlPktOutHC Counter64,
bfdSessPerfCtrlPktDropHC Counter64, bfdSessPerfCtrlPktDropHC Counter64,
bfdSessPerfEchoPktInHC Counter64, bfdSessPerfEchoPktInHC Counter64,
bfdSessPerfEchoPktOutHC Counter64, bfdSessPerfEchoPktOutHC Counter64,
bfdSessPerfEchoPktDropHC Counter64 bfdSessPerfEchoPktDropHC Counter64
} }
-- Ed Note: should we add per-diag code counts here, -- Ed Note: should we add per-diag code counts here,
bfdSessPerfCtrlPktIn OBJECT-TYPE bfdSessPerfCtrlPktIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD control messages received for this "The total number of BFD control messages received for this
BFD session. BFD session.
It MUST be equal to the least significant 32 bits of It MUST be equal to the least significant 32 bits of
bfdSessPerfCtrlPktInHC if supported, and MUST do so bfdSessPerfCtrlPktInHC if supported, and MUST do so
with the rules spelled out in RFC 2863." with the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 1 } ::= { bfdSessPerfEntry 1 }
bfdSessPerfCtrlPktOut OBJECT-TYPE bfdSessPerfCtrlPktOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
BFD-STD-MIB December 17, 2012
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD control messages sent for this BFD "The total number of BFD control messages sent for this BFD
session. session.
It MUST be equal to the least significant 32 bits of It MUST be equal to the least significant 32 bits of
bfdSessPerfCtrlPktOutHC if supported, and MUST do so bfdSessPerfCtrlPktOutHC if supported, and MUST do so
with the rules spelled out in RFC 2863." with the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 2 } ::= { bfdSessPerfEntry 2 }
skipping to change at page 20, line 4 skipping to change at page 19, line 32
DESCRIPTION DESCRIPTION
"The total number of BFD echo messages received for this "The total number of BFD echo messages received for this
BFD session. BFD session.
It MUST be equal to the least significant 32 bits of It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktInHC if supported, and MUST do so bfdSessPerfEchoPktInHC if supported, and MUST do so
with the rules spelled out in RFC 2863." with the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 5 } ::= { bfdSessPerfEntry 5 }
bfdSessPerfEchoPktOut OBJECT-TYPE bfdSessPerfEchoPktOut OBJECT-TYPE
BFD-STD-MIB December 17, 2012
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD echo messages sent for this BFD "The total number of BFD echo messages sent for this BFD
session. session.
It MUST be equal to the least significant 32 bits of It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktOutHC if supported, and MUST do so bfdSessPerfEchoPktOutHC if supported, and MUST do so
with the rules spelled out in RFC 2863." with the rules spelled out in RFC 2863."
skipping to change at page 21, line 4 skipping to change at page 20, line 31
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
the session came up. If no such up event exists this object the session came up. If no such up event exists this object
contains a zero value." contains a zero value."
::= { bfdSessPerfEntry 9 } ::= { bfdSessPerfEntry 9 }
bfdSessPerfLastSessDownTime OBJECT-TYPE bfdSessPerfLastSessDownTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
BFD-STD-MIB December 17, 2012
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at "The value of sysUpTime on the most recent occasion at
which the last time communication was lost with the which the last time communication was lost with the
neighbor. If no such down event exist this object neighbor. If no such down event exist this object
contains a zero value." contains a zero value."
::= { bfdSessPerfEntry 10 } ::= { bfdSessPerfEntry 10 }
bfdSessPerfLastCommLostDiag OBJECT-TYPE bfdSessPerfLastCommLostDiag OBJECT-TYPE
skipping to change at page 22, line 4 skipping to change at page 21, line 31
with this BFD session of any Counter32 object contained in with this BFD session of any Counter32 object contained in
the BfdSessPerfTable. If no such discontinuities have the BfdSessPerfTable. If no such discontinuities have
occurred since the last re-initialization of the local occurred since the last re-initialization of the local
management subsystem, then this object contains a zero management subsystem, then this object contains a zero
value." value."
::= { bfdSessPerfEntry 13 } ::= { bfdSessPerfEntry 13 }
bfdSessPerfCtrlPktInHC OBJECT-TYPE bfdSessPerfCtrlPktInHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
BFD-STD-MIB December 17, 2012
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD control "This value represents the total number of BFD control
messages received for this BFD session. messages received for this BFD session.
The least significant 32 bits MUST equal to The least significant 32 bits MUST equal to
bfdSessPerfCtrlPktIn, and MUST do so with bfdSessPerfCtrlPktIn, and MUST do so with
the rules spelled out in RFC 2863." the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 14 } ::= { bfdSessPerfEntry 14 }
skipping to change at page 23, line 4 skipping to change at page 22, line 32
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD echo "This value represents the total number of BFD echo
messages received for this BFD session. messages received for this BFD session.
The least significant 32 bits MUST equal to The least significant 32 bits MUST equal to
bfdSessPerfEchoPktIn, and MUST do so with bfdSessPerfEchoPktIn, and MUST do so with
the rules spelled out in RFC 2863." the rules spelled out in RFC 2863."
BFD-STD-MIB December 17, 2012
::= { bfdSessPerfEntry 17 } ::= { bfdSessPerfEntry 17 }
bfdSessPerfEchoPktOutHC OBJECT-TYPE bfdSessPerfEchoPktOutHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD echo "This value represents the total number of BFD echo
messages transmitted for this BFD session. messages transmitted for this BFD session.
skipping to change at page 23, line 35 skipping to change at page 23, line 12
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD echo "This value represents the total number of BFD echo
messages received for this BFD session yet dropped messages received for this BFD session yet dropped
for being invalid. for being invalid.
The least significant 32 bits MUST equal to The least significant 32 bits MUST equal to
bfdSessPerfEchoPktDrop, and MUST do so with bfdSessPerfEchoPktDrop, and MUST do so with
the rules spelled out in RFC 2863." the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 19 } ::= { bfdSessPerfEntry 19 }
-- BFD Session Discriminator Mapping Table -- BFD Session Discriminator Mapping Table
bfdSessDiscMapTable OBJECT-TYPE bfdSessDiscMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessDiscMapEntry SYNTAX SEQUENCE OF BfdSessDiscMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Discriminator Mapping Table maps a "The BFD Session Discriminator Mapping Table maps a
local discriminator value to associated BFD session's local discriminator value to associated BFD session's
BfdSessIndexTC used in the bfdSessionTable." BfdSessIndexTC used in the bfdSessionTable."
::= { bfdObjects 4 } ::= { bfdObjects 4 }
bfdSessDiscMapEntry OBJECT-TYPE bfdSessDiscMapEntry OBJECT-TYPE
SYNTAX BfdSessDiscMapEntry SYNTAX BfdSessDiscMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Discriminator Map Entry describes "The BFD Session Discriminator Map Entry describes
BFD session that is mapped to this BfdSessIndexTC." BFD session that is mapped to this BfdSessIndexTC."
BFD-STD-MIB December 17, 2012
INDEX { bfdSessDiscriminator } INDEX { bfdSessDiscriminator }
::= { bfdSessDiscMapTable 1 } ::= { bfdSessDiscMapTable 1 }
BfdSessDiscMapEntry ::= SEQUENCE { BfdSessDiscMapEntry ::= SEQUENCE {
bfdSessDiscMapIndex BfdSessIndexTC, bfdSessDiscMapIndex BfdSessIndexTC,
bfdSessDiscMapStorageType StorageType, bfdSessDiscMapStorageType StorageType,
bfdSessDiscMapRowStatus RowStatus bfdSessDiscMapRowStatus RowStatus
} }
bfdSessDiscMapIndex OBJECT-TYPE bfdSessDiscMapIndex OBJECT-TYPE
skipping to change at page 24, line 48 skipping to change at page 24, line 25
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. When a row in this delete a row in this table. When a row in this
table has a row in the active(1) state, no table has a row in the active(1) state, no
objects in this row can be modified except the objects in this row can be modified except the
bfdSessDiscMapRowStatus and bfdSessDiscMapStorageType." bfdSessDiscMapRowStatus and bfdSessDiscMapStorageType."
::= { bfdSessDiscMapEntry 3 } ::= { bfdSessDiscMapEntry 3 }
-- BFD Session IP Mapping Table -- BFD Session IP Mapping Table
bfdSessIpMapTable OBJECT-TYPE bfdSessIpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessIpMapEntry SYNTAX SEQUENCE OF BfdSessIpMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
BFD-STD-MIB December 17, 2012
DESCRIPTION DESCRIPTION
"The BFD Session IP Mapping Table maps given "The BFD Session IP Mapping Table maps given
bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr,
bfdSessDstAddrType and bfdSessDstAddr bfdSessDstAddrType and bfdSessDstAddr
to an associated BFD session's BfdSessIndexTC used in to an associated BFD session's BfdSessIndexTC used in
the bfdSessionTable." the bfdSessionTable."
::= { bfdObjects 5 } ::= { bfdObjects 5 }
bfdSessIpMapEntry OBJECT-TYPE bfdSessIpMapEntry OBJECT-TYPE
SYNTAX BfdSessIpMapEntry SYNTAX BfdSessIpMapEntry
skipping to change at page 26, line 4 skipping to change at page 25, line 32
::= { bfdSessIpMapEntry 1 } ::= { bfdSessIpMapEntry 1 }
bfdSessIpMapStorageType OBJECT-TYPE bfdSessIpMapStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
object. Conceptual rows having the value object. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
BFD-STD-MIB December 17, 2012
columnar objects in the row." columnar objects in the row."
::= { bfdSessIpMapEntry 2 } ::= { bfdSessIpMapEntry 2 }
bfdSessIpMapRowStatus OBJECT-TYPE bfdSessIpMapRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. When a row in this delete a row in this table. When a row in this
table has a row in the active(1) state, no table has a row in the active(1) state, no
objects in this row can be modified except the objects in this row can be modified except the
bfdSessIpMapRowStatus and bfdSessIpMapStorageType." bfdSessIpMapRowStatus and bfdSessIpMapStorageType."
::= { bfdSessIpMapEntry 3 } ::= { bfdSessIpMapEntry 3 }
-- Notification Configuration -- Notification Configuration
bfdSessUp NOTIFICATION-TYPE bfdSessUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
bfdSessDiag, -- low range value bfdSessDiag, -- low range value
bfdSessDiag -- high range value bfdSessDiag -- high range value
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the "This notification is generated when the
bfdSessState object for one or more contiguous bfdSessState object for one or more contiguous
entries in bfdSessTable are about to enter the up(4) entries in bfdSessTable are about to enter the up(4)
state from some other state. The included values of state from some other state. The included values of
bfdSessDiag MUST both be set equal to this bfdSessDiag MUST both be set equal to this
new state (i.e: up(4)). The two instances of new state (i.e: up(4)). The two instances of
bfdSessDiag in this notification indicate the range bfdSessDiag in this notification indicate the range
skipping to change at page 27, line 4 skipping to change at page 26, line 32
an effort to minimize the emission of a large number an effort to minimize the emission of a large number
of notifications. If a notification has to be of notifications. If a notification has to be
issued for just a single bfdSessEntry, then issued for just a single bfdSessEntry, then
the instance identifier (and values) of the two the instance identifier (and values) of the two
bfdSessDiag objects MUST be the identical." bfdSessDiag objects MUST be the identical."
::= { bfdNotifications 1 } ::= { bfdNotifications 1 }
bfdSessDown NOTIFICATION-TYPE bfdSessDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
bfdSessDiag, -- low range value bfdSessDiag, -- low range value
BFD-STD-MIB December 17, 2012
bfdSessDiag -- high range value bfdSessDiag -- high range value
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the "This notification is generated when the
bfdSessState object for one or more contiguous bfdSessState object for one or more contiguous
entries in bfdSessTable are about to enter the down(2) entries in bfdSessTable are about to enter the down(2)
or adminDown(1) states from some other state. The included or adminDown(1) states from some other state. The included
values of bfdSessDiag MUST both be set equal to this new values of bfdSessDiag MUST both be set equal to this new
state (i.e: down(2) or adminDown(1)). The two instances state (i.e: down(2) or adminDown(1)). The two instances
skipping to change at page 27, line 31 skipping to change at page 27, line 8
have transitioned into the down(2) or adminDown(1) states have transitioned into the down(2) or adminDown(1) states
at roughly the same time, the device SHOULD issue a single at roughly the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in notification for each range of contiguous indexes in
an effort to minimize the emission of a large number an effort to minimize the emission of a large number
of notifications. If a notification has to be of notifications. If a notification has to be
issued for just a single bfdSessEntry, then issued for just a single bfdSessEntry, then
the instance identifier (and values) of the two the instance identifier (and values) of the two
bfdSessDiag objects MUST be the identical." bfdSessDiag objects MUST be the identical."
::= { bfdNotifications 2 } ::= { bfdNotifications 2 }
-- Ed Note: We need to add notification for changes -- Ed Note: We need to add notification for changes
-- when the two ends automatically negotiate to a new detection time -- when the two ends automatically negotiate to a new detection time
-- value or when detection multiplier changes. -- value or when detection multiplier changes.
-- Module compliance. -- Module compliance.
bfdGroups bfdGroups
OBJECT IDENTIFIER ::= { bfdConformance 1 } OBJECT IDENTIFIER ::= { bfdConformance 1 }
bfdCompliances bfdCompliances
OBJECT IDENTIFIER ::= { bfdConformance 2 } OBJECT IDENTIFIER ::= { bfdConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
bfdModuleFullCompliance MODULE-COMPLIANCE bfdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "Compliance statement for agents that provide full
support for the BFD-MIB module. Such devices can support for the BFD-MIB module. Such devices can
then be monitored and also be configured using then be monitored and also be configured using
this MIB module." this MIB module."
BFD-STD-MIB December 17, 2012
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
bfdSessionGroup, bfdSessionGroup,
bfdSessionReadOnlyGroup, bfdSessionReadOnlyGroup,
bfdSessionPerfGroup, bfdSessionPerfGroup,
bfdNotificationGroup bfdNotificationGroup
} }
skipping to change at page 29, line 4 skipping to change at page 28, line 31
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notReady is not DESCRIPTION "Support for createAndWait and notReady is not
required." required."
OBJECT bfdSessDiscMapRowStatus OBJECT bfdSessDiscMapRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notReady is not DESCRIPTION "Support for createAndWait and notReady is not
required." required."
BFD-STD-MIB December 17, 2012
OBJECT bfdSessIpMapRowStatus OBJECT bfdSessIpMapRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notReady is not DESCRIPTION "Support for createAndWait and notReady is not
required." required."
::= { bfdCompliances 1 } ::= { bfdCompliances 1 }
skipping to change at page 30, line 4 skipping to change at page 29, line 29
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessDestinationUdpPort OBJECT bfdSessDestinationUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessSourceUdpPort OBJECT bfdSessSourceUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
BFD-STD-MIB December 17, 2012
OBJECT bfdSessEchoSourceUdpPort OBJECT bfdSessEchoSourceUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessAdminStatus OBJECT bfdSessAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessOperMode OBJECT bfdSessOperMode
skipping to change at page 31, line 4 skipping to change at page 30, line 29
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
OBJECT bfdSessDstAddrType OBJECT bfdSessDstAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), SYNTAX InetAddressType { unknown(0), ipv4(1),
ipv6(2), ipv6z(4) } ipv6(2), ipv6z(4) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4)
support are required." support are required."
BFD-STD-MIB December 17, 2012
OBJECT bfdSessDstAddr OBJECT bfdSessDstAddr
SYNTAX InetAddress (SIZE (0|4|16|20)) SYNTAX InetAddress (SIZE (0|4|16|20))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
OBJECT bfdSessGTSM OBJECT bfdSessGTSM
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
skipping to change at page 32, line 4 skipping to change at page 31, line 30
OBJECT bfdSessAuthenticationKeyID OBJECT bfdSessAuthenticationKeyID
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessAuthenticationKey OBJECT bfdSessAuthenticationKey
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessStorageType OBJECT bfdSessStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
BFD-STD-MIB December 17, 2012
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessRowStatus OBJECT bfdSessRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessDiscMapStorageType OBJECT bfdSessDiscMapStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
skipping to change at page 32, line 33 skipping to change at page 32, line 9
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessIpMapRowStatus OBJECT bfdSessIpMapRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { bfdCompliances 2 } ::= { bfdCompliances 2 }
-- Units of conformance. -- Units of conformance.
bfdSessionGroup OBJECT-GROUP bfdSessionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdAdminStatus, bfdAdminStatus,
bfdSessNotificationsEnable, bfdSessNotificationsEnable,
bfdSessVersionNumber, bfdSessVersionNumber,
bfdSessType, bfdSessType,
bfdSessDestinationUdpPort, bfdSessDestinationUdpPort,
bfdSessSourceUdpPort, bfdSessSourceUdpPort,
bfdSessEchoSourceUdpPort, bfdSessEchoSourceUdpPort,
bfdSessAdminStatus, bfdSessAdminStatus,
bfdSessOperMode, bfdSessOperMode,
bfdSessDemandModeDesiredFlag, bfdSessDemandModeDesiredFlag,
bfdSessControlPlaneIndepFlag, bfdSessControlPlaneIndepFlag,
bfdSessMultipointFlag, bfdSessMultipointFlag,
bfdSessInterface, bfdSessInterface,
bfdSessSrcAddrType, bfdSessSrcAddrType,
bfdSessSrcAddr, bfdSessSrcAddr,
bfdSessDstAddrType, bfdSessDstAddrType,
bfdSessDstAddr, bfdSessDstAddr,
BFD-STD-MIB December 17, 2012
bfdSessGTSM, bfdSessGTSM,
bfdSessGTSMTTL, bfdSessGTSMTTL,
bfdSessDesiredMinTxInterval, bfdSessDesiredMinTxInterval,
bfdSessReqMinRxInterval, bfdSessReqMinRxInterval,
bfdSessReqMinEchoRxInterval, bfdSessReqMinEchoRxInterval,
bfdSessDetectMult, bfdSessDetectMult,
bfdSessAuthPresFlag, bfdSessAuthPresFlag,
bfdSessAuthenticationType, bfdSessAuthenticationType,
bfdSessAuthenticationKeyID, bfdSessAuthenticationKeyID,
bfdSessAuthenticationKey, bfdSessAuthenticationKey,
skipping to change at page 34, line 4 skipping to change at page 33, line 31
::= { bfdGroups 2 } ::= { bfdGroups 2 }
bfdSessionPerfGroup OBJECT-GROUP bfdSessionPerfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfCtrlPktIn, bfdSessPerfCtrlPktIn,
bfdSessPerfCtrlPktOut, bfdSessPerfCtrlPktOut,
bfdSessPerfCtrlPktDrop, bfdSessPerfCtrlPktDrop,
bfdSessPerfCtrlPktDropLastTime, bfdSessPerfCtrlPktDropLastTime,
bfdSessPerfEchoPktIn, bfdSessPerfEchoPktIn,
bfdSessPerfEchoPktOut, bfdSessPerfEchoPktOut,
BFD-STD-MIB December 17, 2012
bfdSessPerfEchoPktDrop, bfdSessPerfEchoPktDrop,
bfdSessPerfEchoPktDropLastTime, bfdSessPerfEchoPktDropLastTime,
bfdSessUpTime, bfdSessUpTime,
bfdSessPerfLastSessDownTime, bfdSessPerfLastSessDownTime,
bfdSessPerfLastCommLostDiag, bfdSessPerfLastCommLostDiag,
bfdSessPerfSessUpCount, bfdSessPerfSessUpCount,
bfdSessPerfDiscTime bfdSessPerfDiscTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 35, line 4 skipping to change at page 34, line 30
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this "Set of notifications implemented in this
module." module."
::= { bfdGroups 5 } ::= { bfdGroups 5 }
END END
6. Security Considerations 6. Security Considerations
As BFD may be tied into the stability of the network infrastructure 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 (such as routing protocols), the effects of an attack on a BFD
session may be very serious. This ultimately has denial-of-service session may be very serious. This ultimately has denial-of-service
effects, as links may be declared to be down (or falsely declared to effects, as links may be declared to be down (or falsely declared to
be up.) As such, improper manipulation of the objects represented by 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- this MIB may result in denial of service to a large number of end-
users. users.
There are a number of management objects defined in this MIB module 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 with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
skipping to change at page 36, line 4 skipping to change at page 35, line 29
an unauthorized user configures enough tables to invoke a denial an unauthorized user configures enough tables to invoke a denial
of service attack on the device where they are configured, or on a of service attack on the device where they are configured, or on a
remote device where the sessions terminate. remote device where the sessions terminate.
Some of the readable objects in this MIB module (i.e., objects with a 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 MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
BFD-STD-MIB December 17, 2012
sensitivity/vulnerability: sensitivity/vulnerability:
o The bfdSessPerfTable both allows access to the performance o The bfdSessPerfTable both allows access to the performance
characteristics of BFD sessions. Network administrators not characteristics of BFD sessions. Network administrators not
wishing to show this information should consider this table wishing to show this information should consider this table
sensitive. sensitive.
The bfdSessAuthenticationType, bfdSessAuthenticationKeyID, and The bfdSessAuthenticationType, bfdSessAuthenticationKeyID, and
bfdSessAuthenticationKey objects hold security methods and associated bfdSessAuthenticationKey objects hold security methods and associated
security keys of BFD sessions. These objects SHOULD be considered security keys of BFD sessions. These objects SHOULD be considered
highly sensitive objects. In order for these sensitive information 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. read and create access to these objects.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure "for example by using IPSec", 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 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 allowed to access and GET/SET "read/change/create/delete" the objects
in these MIB modules. in these MIB modules.
It is RECOMMENDED that implementers consider the security features as 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 including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy". authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET "change/create/delete" them.
7. IANA Considerations 7. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
bfdMib { mib-2 XXX } bfdMib { mib-2 XXX }
[Editor's Note (to be removed prior to publication): the IANA is [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 requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" 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 (here and in the MIB module) with the assigned value and to remove
this note.] this note.]
This document also requests IANA to manage the registry for the This document also requests IANA to manage the registry for the
BfdDiagTC object. BfdDiagTC object.
8. References 8. References
8.1. Normative References 8.1. Normative References
[BFD] Katz, D. and D. Ward, "Bidirectional Forwarding [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Detection (BFD)", RFC 5880, June 2012. Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
STD 58, RFC 2579, April 1999. 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. 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 [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
Requirement Levels", BCP 14, RFC 2119, March 1997. (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June
2010.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
MIB", RFC 2863, June 2000. (BFD) for Multihop Paths", RFC 5883, June 2010.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [I-D.ietf-bfd-tc-mib]
BFD-STD-MIB December 17, 2012 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- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. 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. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. 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 Appendix A. Acknowledgments
We would like to thank David Ward, Jeffrey Haas, Reshad Rahman, David Authors would like to thank David Ward, Jeffrey Haas, Reshad Rahman,
Toscano, Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara David Toscano, Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara
Sreenivasa for their comments and suggestions. Sreenivasa for their comments and suggestions.
Authors' Addresses Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Juniper Networks
Email: tnadeau@juniper.net EMail: tnadeau@juniper.net
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems
2000 Innovation Drive
Kanata, Ontario K2K 3E8
Canada
Email: zali@cisco.com EMail: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems, Inc. Cisco Systems
2000 Innovation Drive
Kanata, Ontario K2K 3E8
Canada
Email: nobo@cisco.com EMail: nobo@cisco.com
 End of changes. 103 change blocks. 
186 lines changed or deleted 113 lines changed or added

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