draft-ietf-bfd-mib-04.txt   draft-ietf-bfd-mib-05.txt 
BFD Working Group Thomas D. Nadeau
INTERNET-DRAFT BT
Intended status: Standards Track Zafar Ali
Cisco Systems, Inc.
Nobo Akiya
Cisco Systems, G.K.
Expires: August 24, 2008 February 25, 2008 BFD Working Group T. Nadeau
Internet-Draft BT
Intended status: Standards Track Z. Ali
Expires: February 5, 2009 Cisco Systems, Inc.
N. Akiya
Cisco Systems G.K.
August 4, 2008
Bidirectional Forwarding Detection Management Information Base BFD Management Information Base
draft-ietf-bfd-mib-04.txt draft-ietf-bfd-mib-05
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract This Internet-Draft will expire on February 5, 2009.
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 [BFD].
Contents
1. Introduction..................................................2
2. Terminology...................................................2
3. The Internet-Standard Management Framework....................2
4. Brief Description of MIB Objects..............................3
4.1 General Variables.............................................3
4.2 Session Table (bfdSessionTable)...............................3
BFD MIB February 25, 2008
4.3 Session Performance Table (bfdSessionPerfTable)...............3
4.4 BFD Session Discriminator Mapping Table (bfdSessDiscMapTable).3
4.5 BFD Session IP Mapping Table (bfdSessIpMapTable)..............3
5. BFD MIB Module Definitions....................................4
6. Security Considerations......................................23
7. IANA Considerations..........................................24
7.1 IANA Considerations for BFD-STD-MIB..........................24
8. References...................................................24
8.1 Normative References.........................................24
8.2 Informative References.......................................25
9. Acknowledgements.............................................25
10. Authors' Addresses...........................................25
11. Intellectual Property Statement..............................26
12. Full Copyright Statement.....................................26
1. 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] and
[BFD-MH],BFD versions 0 and/or 1, on devices supporting this
feature.
-- Ed Note: TBA, support for [BFD-LSP].
This document adopts the definitions, acronyms and mechanisms Abstract
described in [BFD], [BFD-MH] and [BFD-LSP]. Unless otherwise
stated, the mechanisms described therein will not be re-described
here.
Comments should be made directly to the BFD mailing list at This draft defines a portion of the Management Information Base (MIB)
rtg-bfd@ietf.org. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling
Bidirectional Forwarding Detection (BFD) protocol.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL Table of Contents
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
2. Terminology 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Brief Description of MIB Objects . . . . . . . . . . . . . . . 3
5.1. General Variables . . . . . . . . . . . . . . . . . . . . 4
5.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 4
5.3. Session Performance Table (bfdSessionPerfTable) . . . . . 4
5.4. BFD Session Discriminator Mapping Table
(bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 4
5.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . . 4
6. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 26
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
9.1. Normative References . . . . . . . . . . . . . . . . . . . 29
9.2. Informative References . . . . . . . . . . . . . . . . . . 29
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
Intellectual Property and Copyright Statements . . . . . . . . . . 31
This document adopts the definitions, acronyms and mechanisms 1. Requirements notation
described in [BFD], [BFD-MH] and [BFD-LSP]. Unless otherwise
stated, the mechanisms described therein will not be re-described
here.
BFD MIB February 25, 2008 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 [RFC2119].
3. The Internet-Standard Management Framework 2. 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
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. [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,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580].
[RFC2580].
4. Brief Description of MIB Objects 3. 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] and [BFD-MH],
BFD versions 0 and/or 1, on devices supporting this feature.
-- Ed Note: TBA, support for [BFD-LSP].
Comments should be made directly to the BFD mailing list at
rtg-bfd@ietf.org.
4. Terminology
This document adopts the definitions, acronyms and mechanisms
described in [BFD], [BFD-MH] and [BFD-LSP]. Unless otherwise stated,
the mechanisms described therein will not be re-described here.
5. 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]. are derived from [BFD] and [BFD-MH].
4.1 General Variables 5.1. General Variables
The General Variables are used to identify parameters that are The General Variables are used to identify parameters that are global
global to the BFD process. to the BFD process.
4.2 Session Table (bfdSessionTable) 5.2. Session Table (bfdSessionTable)
The session table is used to identify a BFD session between a pair The session table is used to identify a BFD session between a pair of
of nodes. nodes.
4.3 Session Performance Table (bfdSessionPerfTable) 5.3. Session Performance Table (bfdSessionPerfTable)
The session performance table is used for collecting BFD The session performance table is used for collecting BFD performance
performance counts on a per session basis. This table is an AUGMENT counts on a per session basis. This table is an AUGMENT to the
to the bfdSessionTable. bfdSessionTable.
4.4 BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) 5.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 sessions' BfdSessIndexTC used discriminator value to associated BFD sessions' BfdSessIndexTC used
in the bfdSessionTable. in the bfdSessionTable.
4.5 BFD Session IP Mapping Table (bfdSessIpMapTable) 5.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,
bfdSessAddrType, and bfdSessAddr, to an associated BFD sessions' bfdSessAddrType, and bfdSessAddr, to an associated BFD sessions'
BfdSessIndexTC used in the bfdSessionTable. This table SHOULD BfdSessIndexTC used in the bfdSessionTable. This table SHOULD
contains those BFD sessions are of IP type. contains those BFD sessions are of IP type.
BFD MIB February 25, 2008 6. 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.
[RFC2578], [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, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, Counter64, mib-2, Integer32, Unsigned32, Counter32, Counter64
NOTIFICATION-TYPE, mib-2 FROM SNMPv2-SMI
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, TEXTUAL-CONVENTION, TruthValue, RowStatus,
RowStatus, StorageType, TimeStamp StorageType, TimeStamp
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
NOTIFICATION-GROUP FROM SNMPv2-CONF
FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndex InterfaceIndexOrZero
FROM IF-MIB -- [RFC2863] FROM IF-MIB
InetAddress, InetAddressType, InetPortNumber InetAddress, InetAddressType, InetPortNumber
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB;
;
bfdMIB MODULE-IDENTITY bfdMib MODULE-IDENTITY
LAST-UPDATED "200802231200Z" -- 23 February 2008 12:00:00 EST LAST-UPDATED "200808041200Z" -- 4 August 2008 12:00:00 EST
ORGANIZATION "IETF" ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
BT BT
Email: tom.nadeau@bt.com Email: tom.nadeau@bt.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, G.K.
Email: nobo@cisco.com Email: nobo@cisco.com"
"
DESCRIPTION DESCRIPTION
"Bidirectional Forwarding Management Information Base." "Bidirectional Forwarding Management Information Base."
REVISION "200808041200Z" -- 4 Auguest 2008 12:00:00 EST
BFD MIB February 25, 2008
-- Revision history.
REVISION
"200802231200Z" -- 23 February 2008 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." -- RFC-editor pls fill "Initial version. Published as RFC xxxx."
-- in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } -- assigned by IANA, see section 7.1 for details ::= { mib-2 XXX }
-- 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 3 } bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 2 }
bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 }
-- Textual Conventions -- Textual Conventions
BfdSessIndexTC ::= TEXTUAL-CONVENTION BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index used to uniquely identify BFD sessions." "An index used to uniquely identify BFD sessions."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
BfdInterval ::= TEXTUAL-CONVENTION BfdInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD interval delay in microseconds." "The BFD interval delay in microseconds."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (0..4294967295)
BfdDiag ::= TEXTUAL-CONVENTION BfdDiag ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A common BFD diagnostic code." "A common BFD diagnostic code."
SYNTAX INTEGER { noDiagnostic(1), SYNTAX INTEGER {
noDiagnostic(1),
controlDetectionTimeExpired(2), controlDetectionTimeExpired(2),
echoFunctionFailed(3), echoFunctionFailed(3),
neighborSignaledSessionDown(4), neighborSignaledSessionDown(4),
forwardingPlaneReset(5), forwardingPlaneReset(5),
pathDown(6), pathDown(6),
concatenatedPathDown(7), concatenatedPathDown(7),
administrativelyDown(8), administrativelyDown(8),
reverseConcatenatedPathDown (9) reverseConcatenatedPathDown (9)
} }
BFD MIB February 25, 2008
-- BFD General Variables -- BFD General Variables
-- These parameters apply globally to the Router's -- These parameters apply globally to the Systems'
-- BFD Process. -- BFD Process.
bfdAdminStatus OBJECT-TYPE bfdAdminStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The global administrative status of BFD in this router. "The global administrative status of BFD in this router.
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."
DEFVAL { enabled } DEFVAL { enabled }
::= { bfdScalarObjects 1 } ::= { bfdScalarObjects 1 }
bfdSessNotificationsEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is set to true(1), then it enables
the emission of bfdSessUp and bfdSessDown
notifications; otherwise these notifications are not
emitted."
REFERENCE
"See also RFC3413 for explanation that
notifications are under the ultimate control of the
MIB modules in this document."
DEFVAL { false }
::= { 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
"BFD Version 0 (draft-katz-ward-bfd-02.txt) and "BFD Version 0 (draft-katz-ward-bfd-02.txt) and
BFD Version 1 (draft-ietf-bfd-base-07.txt)" BFD Version 1 (draft-ietf-bfd-base-08.txt)"
::= { 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
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 INTEGER, bfdSessType INTEGER,
bfdSessDiscriminator Unsigned32, bfdSessDiscriminator Unsigned32,
bfdSessRemoteDiscr Unsigned32, bfdSessRemoteDiscr Unsigned32,
bfdSessDestinationUdpPort InetPortNumber,
BFD MIB February 25, 2008 bfdSessSourceUdpPort InetPortNumber,
bfdSessEchoSourceUdpPort InetPortNumber,
bfdSessUdpPort InetPortNumber, bfdSessAdminStatus INTEGER,
bfdSessState INTEGER, bfdSessState INTEGER,
bfdSessRemoteHeardFlag TruthValue, bfdSessRemoteHeardFlag TruthValue,
bfdSessDiag BfdDiag, bfdSessDiag BfdDiag,
bfdSessOperMode INTEGER, bfdSessOperMode INTEGER,
bfdSessDemandModeDesiredFlag TruthValue, bfdSessDemandModeDesiredFlag TruthValue,
bfdSessEchoFuncModeDesiredFlag TruthValue, bfdSessControlPlaneIndepFlag TruthValue,
bfdSessControlPlanIndepFlag TruthValue, bfdSessInterface InterfaceIndexOrZero,
bfdSessInterface InterfaceIndex,
bfdSessAddrType InetAddressType, bfdSessAddrType InetAddressType,
bfdSessAddr InetAddress, bfdSessAddr InetAddress,
bfdSessGTSM TruthValue,
bfdSessGTSMTTL Unsigned32,
bfdSessDesiredMinTxInterval BfdInterval, bfdSessDesiredMinTxInterval BfdInterval,
bfdSessReqMinRxInterval BfdInterval, bfdSessReqMinRxInterval BfdInterval,
bfdSessReqMinEchoRxInterval BfdInterval, bfdSessReqMinEchoRxInterval BfdInterval,
bfdSessDetectMult Unsigned32, bfdSessDetectMult Unsigned32,
bfdSessStorType StorageType, bfdSessNegotiatedInterval BfdInterval,
bfdSessRowStatus RowStatus, bfdSessNegotiatedEchoInterval BfdInterval,
bfdSessNegotiatedDetectMult Unsigned32,
bfdSessAuthPresFlag TruthValue, bfdSessAuthPresFlag TruthValue,
bfdSessAuthenticationType INTEGER bfdSessAuthenticationType INTEGER,
bfdSessAuthenticationKeyID Integer32,
bfdSessAuthenticationKey OCTET STRING,
bfdSessStorType StorageType,
bfdSessRowStatus RowStatus
} }
bfdSessIndex OBJECT-TYPE bfdSessIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
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 }
bfdVersionNumber OBJECT-TYPE bfdSessVersionNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version number of the BFD protocol that this session "The version number of the BFD protocol that this session
is running in." is running in. Write access is available for this object
to provide ability to set desired version for this
BFD session."
REFERENCE REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-02.txt) and "BFD Version 0 (draft-katz-ward-bfd-02.txt) and
BFD Version 1 (draft-ietf-bfd-base-07.txt)" BFD Version 1 (draft-ietf-bfd-base-08.txt)"
DEFVAL { 0 } DEFVAL { 1 }
::= { bfdSessEntry 2 } ::= { bfdSessEntry 2 }
bfdSessType OBJECT-TYPE bfdSessType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
singleHop(1), singleHop(1),
multiHop(2) multiHop(2)
} }
BFD MIB February 25, 2008
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of this BFD session." "The type of this BFD session."
::= { bfdSessEntry 3 } ::= { bfdSessEntry 3 }
bfdSessDiscriminator OBJECT-TYPE bfdSessDiscriminator OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the local discriminator for this BFD "This object specifies the local discriminator for this BFD
session, used to uniquely identify it." session, used to uniquely identify it."
::= { bfdSessEntry 4 } ::= { bfdSessEntry 4 }
bfdSessRemoteDiscr OBJECT-TYPE bfdSessRemoteDiscr OBJECT-TYPE
SYNTAX Unsigned32 (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." 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
"draft-ietf-bfd-base-08, Section 6.8.6."
::= { bfdSessEntry 5 } ::= { bfdSessEntry 5 }
bfdSessUdpPort OBJECT-TYPE bfdSessDestinationUdpPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination UDP Port for BFD. The default value is "This object specifies the destination UDP port used for
the well-known value for this port. BFD State failing(5) this BFD session. The value maybe zero(0) if the session
is only applicable if this BFD session is running is in adminDown(1) state."
version 0"
REFERENCE REFERENCE
"draft-katz-ward-bfd-02.txt and "Port 3784 (draft-ietf-bfd-v4v6-1hop-08),
draft-raggarwa-mpls-bfd-00.txt" Port 3785 (draft-ietf-bfd-v4v6-1hop-08), and
Port 4784 (draft-ietf-bfd-multihop-06)"
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 6 } ::= { bfdSessEntry 6 }
bfdSessSourceUdpPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the source UDP port of BFD control
packets for this BFD session. The value maybe zero(0) if
the session is in adminDown(1) state."
REFERENCE
"draft-ietf-bfd-v4v6-1hop-08 and
draft-ietf-bfd-multihop-06"
DEFVAL { 0 }
::= { bfdSessEntry 7 }
bfdSessEchoSourceUdpPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the source UDP port of BFD echo
packets for this BFD session. The value maybe zero(0) if
the session is not running in the echo mode, or the
session is in adminDown(1) state."
REFERENCE
"draft-ietf-bfd-v4v6-1hop-08 and
draft-ietf-bfd-multihop-06"
DEFVAL { 0 }
::= { bfdSessEntry 8 }
bfdSessAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
stop(1),
start(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A transition from 'stop' to 'start' will start
the BFD state machine for the session. The state
machine will have an initial state of down.
A transition from 'start' to 'stop' will cause
the BFD sesssion to be brought down to
adminDown(1). Care should be used in providing
write access to this object without adequate
authentication."
DEFVAL { 2 }
::= { bfdSessEntry 9 }
bfdSessState OBJECT-TYPE bfdSessState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
adminDown(1), adminDown(1),
down(2), down(2),
init(3), init(3),
up(4), up(4),
failing(5) failing(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
BFD MIB February 25, 2008
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The perceived state of the BFD session." "The perceived state of the BFD session.
::= { bfdSessEntry 7 } BFD State failing(5) is only applicable if this BFD
session is running version 0.
Upon creation of a new BFD session via this MIB, the
suggested initial state is down(2)."
DEFVAL { 2 }
::= { bfdSessEntry 10 }
bfdSessRemoteHeardFlag OBJECT-TYPE bfdSessRemoteHeardFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies status of BFD packet reception from "This object specifies status of BFD packet reception from
the remote system. Specifically, it is set to true(1) if the remote system. Specifically, it is set to true(1) if
the local system is actively receiving BFD packets from the the local system is actively receiving BFD packets from the
remote system, and is set to false(0) if the local system remote system, and is set to false(2) if the local system
has not received BFD packets recently (within the detection has not received BFD packets recently (within the detection
time) or if the local system is attempting to tear down time) or if the local system is attempting to tear down
the BFD session. Value placed in this object is valid only the BFD session."
if this session is running in BFD version 0."
REFERENCE REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-02.txt) and "BFD Version 0 (draft-katz-ward-bfd-02.txt) and
BFD Version 1 (draft-ietf-bfd-base-07.txt)" BFD Version 1 (draft-ietf-bfd-base-08.txt)"
DEFVAL { 0 } DEFVAL { false }
::= { bfdSessEntry 8 } ::= { bfdSessEntry 11 }
bfdSessDiag OBJECT-TYPE bfdSessDiag OBJECT-TYPE
SYNTAX BfdDiag SYNTAX BfdDiag
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
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)
to some other state." to some other state."
::= { bfdSessEntry 9 } ::= { bfdSessEntry 12 }
bfdSessOperMode OBJECT-TYPE bfdSessOperMode OBJECT-TYPE
SYNTAX INTEGER { asyncModeWEchoFun(1), SYNTAX INTEGER {
asyncModeWEchoFun(1),
asynchModeWOEchoFun(2), asynchModeWOEchoFun(2),
demandModeWEchoFunction(3), demandModeWEchoFunction(3),
demandModeWOEchoFunction(4) demandModeWOEchoFunction(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
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."
::= { bfdSessEntry 13 }
BFD MIB February 25, 2008
A value of AsyncModeWEchoFun(1) ...
A value of AsynchModeWOEchoFun(2) ...
A value of DemandModeWEchoFunction(3) ...
A value of DemandModeWOEchoFunction(4) ...
"
::= { bfdSessEntry 10 }
bfdSessDemandModeDesiredFlag OBJECT-TYPE bfdSessDemandModeDesiredFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates that the local system's "This object indicates that the local system's
desire to use Demand mode. Specifically, it is set desire to use Demand mode. Specifically, it is set
to true(1) if the local system wishes to use to true(1) if the local system wishes to use
Demand mode or false(0) if not" Demand mode or false(2) if not"
DEFVAL { false }
::= { bfdSessEntry 11 }
bfdSessEchoFuncModeDesiredFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates that the local system's
desire to use Echo mode. Specifically, it is set
to true(1) if the local system wishes to use
Echo mode or false(0) if not"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 12 } ::= { bfdSessEntry 14 }
bfdSessControlPlanIndepFlag OBJECT-TYPE bfdSessControlPlaneIndepFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates that the local system's "This object indicates that the local system's
ability to continue to function through a disruption of ability to continue to function through a disruption of
the control plane. Specifically, it is set the control plane. Specifically, it is set
to true(1) if the local system BFD implementation is to true(1) if the local system BFD implementation is
independent of the control plane. Otherwise, the independent of the control plane. Otherwise, the
value is set to false(0)" value is set to false(2)"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 13 } ::= { bfdSessEntry 15 }
BFD MIB February 25, 2008
bfdSessInterface OBJECT-TYPE bfdSessInterface OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only 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 are no interface associated value can be zero if there is no interface associated
with this BFD session" with this BFD session."
::= { bfdSessEntry 14 } ::= { bfdSessEntry 16 }
bfdSessAddrType OBJECT-TYPE bfdSessAddrType 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) or ipv6(2) Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4)
have to be supported. have to be supported.
A value of unknown(0) is allowed only when A value of unknown(0) is allowed only when
the outgoing interface is of type point-to-point, or the outgoing interface is of type point-to-point, or
when the BFD session is not associated with a specific when the BFD session is not associated with a specific
interface. interface.
If any other unsupported values are attempted in a set If any other unsupported values are attempted in a set
operation, the agent MUST return an inconsistentValue operation, the agent MUST return an inconsistentValue
error. error."
" ::= { bfdSessEntry 17 }
::= { bfdSessEntry 15 }
bfdSessAddr OBJECT-TYPE bfdSessAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the neighboring IP address which is "This object specifies the neighboring IP address which is
being monitored with this BFD session. being monitored with this BFD session.
It can also be used to enabled BFD on a specific It can also be used to enabled BFD on a specific
interface. The value is set to zero when BFD session is not interface. The value is set to zero when BFD session is not
associated with a specific interface. " associated with a specific interface. "
::= { bfdSessEntry 16 } ::= { bfdSessEntry 18 }
BFD MIB February 25, 2008 bfdSessGTSM OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Setting the value of this object to true(1) will enable GTSM
protection of the BFD session. GTSM MUST be enabled on a
singleHop(1) session if no authentication is in use."
REFERENCE
"RFC 5082 - The Generalized TTL Security Mechanism (GTSM).
draft-ietf-bfd-v4v6-1hop-08, Sec. 5"
DEFVAL { false }
::= { bfdSessEntry 19 }
bfdSessGTSMTTL OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is valid only when bfdSessGTSM protection is
enabled on the system. This object specifies the minimum
allowed TTL for received BFD control packets. For
singleHop(1) session, if GTSM protection is enabled,
this object SHOULD be set to maximum TTL allowed for
single hop."
REFERENCE
"RFC 5082 - The Generalized TTL Security Mechanism (GTSM).
draft-ietf-bfd-v4v6-1hop-08, Sec. 5"
DEFVAL { 0 }
::= { bfdSessEntry 20 }
bfdSessDesiredMinTxInterval OBJECT-TYPE bfdSessDesiredMinTxInterval OBJECT-TYPE
SYNTAX BfdInterval SYNTAX BfdInterval
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 when microseconds, that the local system would like to use when
transmitting BFD Control packets." transmitting BFD Control packets."
::= { bfdSessEntry 17 } ::= { bfdSessEntry 21 }
bfdSessReqMinRxInterval OBJECT-TYPE bfdSessReqMinRxInterval OBJECT-TYPE
SYNTAX BfdInterval SYNTAX BfdInterval
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, between received BFD Control packets the microseconds, between received BFD Control packets the
local system is capable of supporting." local system is capable of supporting."
::= { bfdSessEntry 18 } ::= { bfdSessEntry 22 }
bfdSessReqMinEchoRxInterval OBJECT-TYPE bfdSessReqMinEchoRxInterval OBJECT-TYPE
SYNTAX BfdInterval SYNTAX BfdInterval
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, between received BFD Echo packets that this microseconds, between received BFD Echo packets that this
system is capable of supporting." system is capable of supporting."
::= { bfdSessEntry 19 } ::= { bfdSessEntry 23 }
bfdSessDetectMult OBJECT-TYPE bfdSessDetectMult OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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 20 } ::= { bfdSessEntry 24 }
bfdSessStorType OBJECT-TYPE bfdSessNegotiatedInterval OBJECT-TYPE
SYNTAX StorageType SYNTAX BfdInterval
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This object specifies the negotiated interval, in
object. Conceptual rows having the value microseconds, that the local system is transmitting
'permanent' need not allow write-access to any BFD Control packets."
columnar objects in the row." ::= { bfdSessEntry 25 }
::= { bfdSessEntry 21 }
BFD MIB February 25, 2008 bfdSessNegotiatedEchoInterval OBJECT-TYPE
SYNTAX BfdInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the negotiated interval, in
microseconds, that the local system is transmitting
BFD echo packets. Value is expected to be zero if
the sessions is not running in echo mode."
::= { bfdSessEntry 26 }
bfdSessRowStatus OBJECT-TYPE bfdSessNegotiatedDetectMult OBJECT-TYPE
SYNTAX RowStatus SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This object specifies the Detect time multiplier."
delete a row in this table. When a row in this ::= { bfdSessEntry 27 }
table has a row in the active(1) state, no
objects in this row can be modified except the
bfdSessRowStatus and bfdSessStorageType."
::= { bfdSessEntry 22 }
bfdSessAuthPresFlag OBJECT-TYPE bfdSessAuthPresFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates that the local system's "This object indicates that the local system's
desire to use Authentication. Specifically, it is set desire to use Authentication. Specifically, it is set
to true(1) if the local system wishes the session to true(1) if the local system wishes the session
to be authenticated or false(0) if not" to be authenticated or false(2) if not."
REFERENCE
"draft-ietf-bfd-base-08, Sections 4.2 - 4.4"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 23 } ::= { bfdSessEntry 28 }
bfdSessAuthenticationType OBJECT-TYPE bfdSessAuthenticationType OBJECT-TYPE
SYNTAX INTEGER { simplePassword(1), SYNTAX INTEGER {
reserved(0),
simplePassword(1),
keyedMD5(2), keyedMD5(2),
meticulousKeyedMD5(3), meticulousKeyedMD5(3),
keyedSHA1(4), keyedSHA1(4),
meticulousKeyedSHA1(5) meticulousKeyedSHA1(5)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Authentication Type used for this BFD session. This "The Authentication Type used for this BFD session.
field is valid only when the Authentication Present bit is set" This field is valid only when the Authentication
::= { bfdSessEntry 24 } Present bit is set."
REFERENCE
"draft-ietf-bfd-base-08, Sections 4.2 - 4.4"
::= { bfdSessEntry 29 }
bfdSessAuthenticationKeyID OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The authentication key ID in use for this session. This
object permits multiple keys to be active simultaneously.
When bfdSessAuthPresFlag is false(2), then the value
of this object MUST be -1. The value -1 indicates that
no Authentication Key ID will be present in the optional
BFD Authentication Section."
REFERENCE
"draft-ietf-bfd-base-08, Sections 4.2 - 4.4"
DEFVAL { -1 }
::= { bfdSessEntry 30 }
bfdSessAuthenticationKey OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..252))
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
authentication types, this value is used in the
computation of the key present in the BFD authentication
packet.
Implementations may further restrict the length of this
key. When doing so, a SET of this object should return
tooBig.
Note that due to the highly sensitive nature of the data
managed by this object an implementation may choose to
implement this object as 'write-only'. SET operations
will succeed normally but GET and GET-BULK operations are
permitted to return noSuchName."
REFERENCE
"draft-ietf-bfd-base-08, Sections 4.2 - 4.4"
::= { bfdSessEntry 31 }
bfdSessStorType 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
columnar objects in the row."
::= { bfdSessEntry 32 }
bfdSessRowStatus 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
table has a row in the active(1) state, no
objects in this row can be modified except the
bfdSessRowStatus and bfdSessStorageType."
::= { bfdSessEntry 33 }
-- 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 }
BFD MIB February 25, 2008
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 for "An entry in this table is created by a BFD-enabled node for
every BFD Session. bfdCounterDiscontinuityTime is used to every BFD Session. bfdCounterDiscontinuityTime 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 }
skipping to change at page 14, line 49 skipping to change at page 19, line 4
DESCRIPTION DESCRIPTION
"The total number of BFD messages received for this BFD "The total number of BFD messages received for this BFD
session." session."
::= { bfdSessPerfEntry 1 } ::= { bfdSessPerfEntry 1 }
bfdSessPerfPktOut OBJECT-TYPE bfdSessPerfPktOut 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 messages sent for this BFD session." "The total number of BFD messages sent for this BFD
session."
::= { bfdSessPerfEntry 2 } ::= { bfdSessPerfEntry 2 }
BFD MIB February 25, 2008
bfdSessUpTime OBJECT-TYPE bfdSessUpTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
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 3 } ::= { bfdSessPerfEntry 3 }
bfdSessPerfLastSessDownTime OBJECT-TYPE bfdSessPerfLastSessDownTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
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
the last time communication was lost with the neighbor. If which the last time communication was lost with the
no such down event exist this object contains a zero value." neighbor. If no such down event exist this object
contains a zero value."
::= { bfdSessPerfEntry 4 } ::= { bfdSessPerfEntry 4 }
bfdSessPerfLastCommLostDiag OBJECT-TYPE bfdSessPerfLastCommLostDiag OBJECT-TYPE
SYNTAX BfdDiag SYNTAX BfdDiag
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD diag code for the last time communication was lost "The BFD diag code for the last time communication was lost
with the neighbor. If no such down event exists this object with the neighbor. If no such down event exists this object
contains a zero value." contains a zero value."
::= { bfdSessPerfEntry 5 } ::= { bfdSessPerfEntry 5 }
bfdSessPerfSessUpCount OBJECT-TYPE bfdSessPerfSessUpCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times this session has gone into the Up "The number of times this session has gone into the Up
state since the router last rebooted." state since the system last rebooted."
::= { bfdSessPerfEntry 6 } ::= { bfdSessPerfEntry 6 }
bfdSessPerfDiscTime OBJECT-TYPE bfdSessPerfDiscTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
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 any one or more of the session counters suffered which any one or more of the session counters suffered
a discontinuity. a discontinuity.
BFD MIB February 25, 2008
The relevant counters are the specific instances associated The relevant counters are the specific instances associated
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 occurred the BfdSessPerfTable. If no such discontinuities have
since the last re-initialization of the local management occurred since the last re-initialization of the local
subsystem, then this object contains a zero value." management subsystem, then this object contains a zero
value."
::= { bfdSessPerfEntry 7 } ::= { bfdSessPerfEntry 7 }
bfdSessPerfPktInHC OBJECT-TYPE bfdSessPerfPktInHC 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 messages "This value represents the total number of BFD messages
received for this BFD session. It MUST be equal to the received for this BFD session. It MUST be equal to the
least significant 32 bits of bfdSessPerfPktIn least significant 32 bits of bfdSessPerfPktIn
skipping to change at page 17, line 4 skipping to change at page 21, line 4
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 sessions' local discriminator value to associated BFD sessions'
BfdSessIndexTC used in the bfdSessionTable." BfdSessIndexTC used in the bfdSessionTable."
::= { bfdObjects 4 } ::= { bfdObjects 4 }
BFD MIB February 25, 2008
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."
INDEX { bfdSessDiscriminator } INDEX { bfdSessDiscriminator }
::= { bfdSessDiscMapTable 1 } ::= { bfdSessDiscMapTable 1 }
BfdSessDiscrMapEntry ::= SEQUENCE { BfdSessDiscMapEntry ::= SEQUENCE {
bfdSessDiscMapIndex BfdSessIndexTC bfdSessDiscMapIndex BfdSessIndexTC
} }
bfdSessDiscMapIndex OBJECT-TYPE bfdSessDiscMapIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the BfdIndex referred to by "This object specifies the BfdIndex referred to by
the indexes of this row. In essence, a mapping is the indexes of this row. In essence, a mapping is
skipping to change at page 18, line 4 skipping to change at page 21, line 50
MultiHop(2)." MultiHop(2)."
::= { bfdObjects 5 } ::= { bfdObjects 5 }
bfdSessIpMapEntry OBJECT-TYPE bfdSessIpMapEntry OBJECT-TYPE
SYNTAX BfdSessIpMapEntry SYNTAX BfdSessIpMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session IP Map Entry describes "The BFD Session IP Map Entry describes
BFD session that is mapped to this BfdSessIndexTC." BFD session that is mapped to this BfdSessIndexTC."
INDEX {
BFD MIB February 25, 2008 bfdSessInterface,
INDEX { bfdSessInterface,
bfdSessAddrType, bfdSessAddrType,
bfdSessAddr bfdSessAddr
} }
::= { bfdSessIpMapTable 1 } ::= { bfdSessIpMapTable 1 }
BfdSessIpMapEntry ::= SEQUENCE { BfdSessIpMapEntry ::= SEQUENCE {
bfdSessIpMapIndex BfdSessIndexTC bfdSessIpMapIndex BfdSessIndexTC
} }
bfdSessIpMapIndex OBJECT-TYPE bfdSessIpMapIndex OBJECT-TYPE
skipping to change at page 18, line 29 skipping to change at page 22, line 25
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the BfdIndex referred to by "This object specifies the BfdIndex referred to by
the indexes of this row. In essence, a mapping is the indexes of this row. In essence, a mapping is
provided between these indexes and the BfdSessTable." provided between these indexes and the BfdSessTable."
::= { bfdSessIpMapEntry 1 } ::= { bfdSessIpMapEntry 1 }
-- Notification Configuration -- Notification Configuration
bfdSessNotificationsEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is set to true(1), then it enables
the emission of bfdSessUp and bfdSessDown
notifications; otherwise these notifications are not
emitted."
REFERENCE
"See also RFC3413 for explanation that
notifications are under the ultimate control of the
MIB modules in this document."
DEFVAL { false }
::= { bfdScalarObjects 4 }
bfdSessUp NOTIFICATION-TYPE bfdSessUp NOTIFICATION-TYPE
OBJECTS { bfdSessDiag, -- low range value OBJECTS {
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
BFD MIB February 25, 2008
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
of indexes that are affected. Note that all the indexes of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the of the two ends of the range can be derived from the
instance identifiers of these two objects. For the instance identifiers of these two objects. For the
cases where a contiguous range of sessions cases where a contiguous range of sessions
have transitioned into the up(4) state at roughly have transitioned into the up(4) state at roughly
the same time, the device SHOULD issue a single 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
skipping to change at page 19, line 23 skipping to change at page 23, line 4
cases where a contiguous range of sessions cases where a contiguous range of sessions
have transitioned into the up(4) state at roughly have transitioned into the up(4) state at roughly
the same time, the device SHOULD issue a single 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 1 } ::= { bfdNotifications 1 }
bfdSessDown NOTIFICATION-TYPE bfdSessDown NOTIFICATION-TYPE
OBJECTS { bfdSessDiag, -- low range value OBJECTS {
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 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 values of bfdSessDiag MUST both be set equal to this new
new state (i.e: down(2) or adminDown(1)). The two instances state (i.e: down(2) or adminDown(1)). The two instances
of bfdSessDiag in this notification indicate the range of bfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the of the two ends of the range can be derived from the
instance identifiers of these two objects. For instance identifiers of these two objects. For
cases where a contiguous range of sessions cases where a contiguous range of sessions
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 }
BFD MIB February 25, 2008
-- 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.
-- Similarly, changes in the operating mode (bfdSessOperMode) -- Similarly, changes in the operating mode (bfdSessOperMode)
-- also need to be notified. -- also need to be notified.
-- Module compliance. -- Module compliance.
bfdGroups bfdGroups
OBJECT IDENTIFIER ::= { bfdConformance 1 } OBJECT IDENTIFIER ::= { bfdConformance 1 }
skipping to change at page 20, line 29 skipping to change at page 24, line 6
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 "Compliance statement for agents that provide full DESCRIPTION "Compliance statement for agents that provide full
support for BFD-MIB. Such devices can support for BFD-MIB. 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."
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
bfdSessionGroup, bfdSessionGroup,
bfdSessionReadOnlyGroup,
bfdSessionPerfGroup, bfdSessionPerfGroup,
bfdSessionPerfHCGroup, bfdSessionPerfHCGroup,
bfdNotificationGroup bfdNotificationGroup
} }
GROUP bfdSessionPerfHCGroup GROUP bfdSessionPerfHCGroup
DESCRIPTION "This group is mandatory for those bfdPerfTable DESCRIPTION "This group is mandatory for those bfdPerfTable
entries for which any of the objects entries for which any of the objects
bfdSessPerfPktInHC or bfdSessPerfPktOutHC bfdSessPerfPktInHC or bfdSessPerfPktOutHC
wraps around too quickly wraps around too quickly
based on the criteria specified in RFC 2863 for based on the criteria specified in RFC 2863 for
high-capacity counters." high-capacity counters."
GROUP bfdNotificationGroup GROUP bfdNotificationGroup
DESCRIPTION "This group is only mandatory for those DESCRIPTION "This group is only mandatory for those
implementations which can efficiently implement implementations which can efficiently implement
the notifications contained in this group." the notifications contained in this group."
OBJECT bfdSessAddrType OBJECT bfdSessAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType {
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support unknown(0),
is required." ipv4(1),
ipv6(2),
BFD MIB February 25, 2008 ipv6z(4)
}
DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4)
support are required."
OBJECT bfdSessAddr OBJECT bfdSessAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE (0|4|16|20))
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
::= { bfdCompliances 1 } ::= { bfdCompliances 1 }
-- Read-Only Conformance TBD...
-- Units of conformance. -- Units of conformance.
bfdSessionGroup OBJECT-GROUP bfdSessionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessNotificationsEnable, bfdSessNotificationsEnable,
bfdAdminStatus, bfdAdminStatus,
bfdSessVersionNumber, bfdSessVersionNumber,
bfdSessType, bfdSessSourceUdpPort,
bfdSessDiscriminator, bfdSessEchoSourceUdpPort,
bfdSessRemoteDiscr, bfdSessAdminStatus,
bfdSessUdpPort,
bfdSessState,
bfdSessRemoteHeardFlag,
bfdSessDiag, bfdSessDiag,
bfdSessOperMode,
bfdSessDemandModeDesiredFlag, bfdSessDemandModeDesiredFlag,
bfdSessEchoFuncModeDesiredFlag,
bfdSessControlPlanIndepFlag,
bfdSessInterface, bfdSessInterface,
bfdSessAddrType, bfdSessAddrType,
bfdSessAddr, bfdSessAddr,
bfdSessGTSM,
bfdSessGTSMTTL,
bfdSessDesiredMinTxInterval, bfdSessDesiredMinTxInterval,
bfdSessReqMinRxInterval, bfdSessReqMinRxInterval,
bfdSessReqMinEchoRxInterval, bfdSessReqMinEchoRxInterval,
bfdSessDetectMult, bfdSessDetectMult,
bfdSessStorType, bfdSessStorType,
bfdSessRowStatus, bfdSessRowStatus,
bfdSessAuthPresFlag, bfdSessAuthPresFlag,
bfdSessAuthenticationType, bfdSessAuthenticationType,
bfdSessDiscMapIndex, bfdSessAuthenticationKeyID,
bfdSessIpMapIndex bfdSessAuthenticationKey
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for BFD sessions." "Collection of objects needed for BFD sessions."
::= { bfdGroups 1 } ::= { bfdGroups 1 }
BFD MIB February 25, 2008 bfdSessionReadOnlyGroup OBJECT-GROUP
OBJECTS {
bfdSessType,
bfdSessDiscriminator,
bfdSessRemoteDiscr,
bfdSessDestinationUdpPort,
bfdSessState,
bfdSessRemoteHeardFlag,
bfdSessOperMode,
bfdSessControlPlaneIndepFlag,
bfdSessNegotiatedInterval,
bfdSessNegotiatedEchoInterval,
bfdSessNegotiatedDetectMult,
bfdSessDiscMapIndex,
bfdSessIpMapIndex
}
STATUS current
DESCRIPTION
"Collection of read-only objects needed for BFD sessions."
::= { bfdGroups 2 }
bfdSessionPerfGroup OBJECT-GROUP bfdSessionPerfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfPktIn, bfdSessPerfPktIn,
bfdSessPerfPktOut, bfdSessPerfPktOut,
bfdSessUpTime, bfdSessUpTime,
bfdSessPerfLastSessDownTime, bfdSessPerfLastSessDownTime,
bfdSessPerfLastCommLostDiag, bfdSessPerfLastCommLostDiag,
bfdSessPerfSessUpCount, bfdSessPerfSessUpCount,
bfdSessPerfDiscTime bfdSessPerfDiscTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to monitor the "Collection of objects needed to monitor the
performance of BFD sessions." performance of BFD sessions."
::= { bfdGroups 2 } ::= { bfdGroups 3 }
bfdSessionPerfHCGroup OBJECT-GROUP bfdSessionPerfHCGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfPktInHC, bfdSessPerfPktInHC,
bfdSessPerfPktOutHC bfdSessPerfPktOutHC
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to monitor the "Collection of objects needed to monitor the
performance of BFD sessions for which the performance of BFD sessions for which the
values of bfdSessPerfPktIn, bfdSessPerfPktOut values of bfdSessPerfPktIn, bfdSessPerfPktOut
wrap around too quickly." wrap around too quickly."
::= { bfdGroups 3 } ::= { bfdGroups 4 }
bfdNotificationGroup NOTIFICATION-GROUP bfdNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
bfdSessUp, bfdSessUp,
bfdSessDown bfdSessDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this "Set of notifications implemented in this
module." module."
::= { bfdGroups 4 } ::= { bfdGroups 5 }
END END
BFD MIB February 25, 2008 7. Security Considerations
6. Security Considerations As BFD may be tied into the stability of the network infrastructure
(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 There are a number of management objects defined in this MIB module
module with a MAX-ACCESS clause of read-write and/or read-create. with a MAX-ACCESS clause of read-write and/or read-create. Such
Such objects may be considered sensitive or vulnerable in some objects may be considered sensitive or vulnerable in some network
network environments. It is thus important to control even GET and/or environments. The support for SET operations in a non-secure
NOTIFY access to these objects and possibly to even encrypt the environment without proper protection can have a negative effect on
values of these objects when sending them over the network via SNMP. network operations. These are the tables and objects and their
sensitivity/vulnerability:
o The bfdSessTable may be used to directly configure BFD o bfdSessAdminStatus - Improper change of bfdSessAdminStatus, from
sessions. The bfdSessMapTable can be used indirectly start to stop, can cause significant disruption of the
in the same way. Unauthorized access to objects in connectivity to those portions of the Internet reached via the
this table could result in disruption of traffic on applicable remote BFD peer.
the network. This is especially true if an unauthorized
user configures enough tables to invoke a denial of
service attack on the device where they are configured,
or on a remote device where the sessions terminate.
Some of the readable objects in this MIB module (i.e., objects o bfdSessDesiredMinTxInterval, bfdSessReqMinRxInterval,
with a MAX-ACCESS other than not-accessible) may be considered bfdSessReqMinEchoRxInterval, bfdSessDetectMult - Improper change
sensitive or vulnerable in some network environments. It is thus of this object can cause connections to be disrupted for extremely
important to control even GET and/or NOTIFY access to these objects long time periods when otherwise they would be restored in a
and possibly to even encrypt the values of these objects when sending relatively short period of time.
them over the network via SNMP. These are the tables and objects and
their sensitivity/vulnerability: 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
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.
o The bfdSessTable may be used to directly configure BFD sessions.
The bfdSessMapTable can be used indirectly in the same way.
Unauthorized access to objects in this table could result in
disruption of traffic on the network. This is especially true if
an unauthorized user configures enough tables to invoke a denial
of service attack on the device where they are configured, or on a
remote device where the sessions terminate.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
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 wishing to show this information should consider this table
table sensative. 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 allow only
write-only access to these objects. Even in such case, SET
operations SHOULD be performed with security features.
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 It is RECOMMENDED that implementers consider the security features as
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".
BFD MIB February 25, 2008
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 8. IANA Considerations
There is one MIB module contained in this document. The following The MIB module in this document uses the following IANA-assigned
"IANA Considerations" subsection requests IANA for a new OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
assignment under the mib-2 subtree. New assignments can only
be made via a Standards Action as specified in [RFC2434].
7.1. IANA Considerations for BFD-STD-MIB Descriptor OBJECT IDENTIFIER value
---------- -----------------------
The IANA is requested to assign { mib-2 XXX } to the BFD-STD-MIB bfdMib { mib-2 XXX }
module specified in this document.
8. References [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"
(here and in the MIB module) with the assigned value and to remove
this note.]
8.1 Normative References This document also requests IANA to manage the registry for the
BfdDiag object.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 9. References
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 9.1. Normative References
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding
Rose, M. and S. Waldbusser, "Conformance Statements for Detection", ID Document: draft-ietf-bfd-base-08.txt,
SMIv2", STD 58, RFC 2580, April 1999. March 2008.
[BFD] Katz, D., and Ward, D., "Bidirectional Forwarding [BFD-LSP] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
Detection", draft-ietf-bfd-base-07.txt. "BFD For MPLS LSPs", ID Document:
draft-ietf-bfd-mpls-06.txt, June 2008.
BFD MIB February 25, 2008 [BFD-MH] Katz, D. and D. Ward, "BFD for Multihop Paths",
ID Document: draft-ietf-bfd-multihop-06.txt, January 2008.
[BFD-MH] Katz, D., and Ward, D., "BFD for Multihop Paths", [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
draft-ietf-bfd-multihop-06.txt. Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
BFD For MPLS LSPs, draft-ietf-bfd-mpls-05.txt. Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
8.2 Informative References [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", 9.2. Informative References
STD 58, RFC 2863, June 2000.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Schoenwaelder, "Textual Conventions for Internet Requirement Levels", BCP 14, RFC 2119, March 1997.
Network Addresses", RFC 4001, Feb. 2005.
[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Requirement Levels", RFC 2119, BCP 14, April 1997. IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
"Introduction and Applicability Statements for MIB", RFC 2863, June 2000.
Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3413] Levi, D., Meyer, P., Stewart, B., [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"SNMP Applications", RFC 3413, December 2002. "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
an IANA Considerations Section in RFCs", BCP 26, RFC Management Protocol (SNMP) Applications", STD 62,
2434, October 1998. RFC 3413, December 2002.
9. Acknowledgements [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
We would like to thank David Ward, Reshad Rahman, David Toscano, Appendix A. Acknowledgments
Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara Sreenivasa
for their comments and suggestions.
10. Authors' Addresses We 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 Thomas D. Nadeau
BT BT
BT Centre BT Centre
81 Newgate Street 81 Newgate Street
London, EC1A 7AJ London EC1A 7AJ
United Kingdom United Kingdom
Email: tom.nadeau@bt.com Email: tom.nadeau@bt.com
Zafar Ali Zafar Ali
Cisco Systems, Inc.
2000 Innovation Drive 2000 Innovation Drive
Kanata, Ontario, K2K 3E8, Canada. Kanata, Ontario K2K 3E8
Phone: 734-276-2459 Canada
Email: zali@cisco.com
BFD MIB February 25, 2008 Email: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems G.K. Cisco Systems G.K.
Shinjuku Mitsui Building, 2-1-1, Shinjuku Mitsui Building
Nishi-Shinjuku, Shinjuku-Ku, 2-1-1 Nishi-Shinjuku, Shinjuku-Ku
Tokyo 163-0409, Japan Tokyo 163-0409
Phone: +81 3 5324 4096 Japan
Email: nobo@cisco.com Email: nobo@cisco.com
11. Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
12. Full Copyright Statement
Copyright (C) The IETF Trust (2008). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 165 change blocks. 
402 lines changed or deleted 588 lines changed or added

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