draft-ietf-bfd-mib-02.txt   draft-ietf-bfd-mib-03.txt 
BFD Working Group Thomas D. Nadeau BFD Working Group Thomas D. Nadeau
Standard Track Zafar Ali Standard Track Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Expires: April 2007 October 2006
Bidirectional Forwarding Detection Management Information Base Bidirectional Forwarding Detection Management Information Base
draft-ietf-bfd-mib-02.txt draft-ietf-bfd-mib-03.txt
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 other
skipping to change at page 1, line 40 skipping to change at page 1, line 42
Abstract Abstract
This draft defines a portion of the Management Information Base This draft defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects for modeling community. In particular, it describes managed objects for modeling
Bidirectional Forwarding Detection (BFD) protocol [BFD]. Bidirectional Forwarding Detection (BFD) protocol [BFD].
Contents Contents
1. Introduction...................................................2 1. Introduction..................................................2
2. Terminology....................................................3 2. Terminology...................................................3
3. The Internet-Standard Management Framework.....................3 3. The Internet-Standard Management Framework....................3
3. Brief Description of MIB Objects...............................3 3. Brief Description of MIB Objects..............................3
3.1 General Variables..........................................3 3.1 General Variables.............................................3
3.2 Session Table (bfdSessionTable)............................3 3.2 Session Table (bfdSessionTable)...............................3
3.3 Session Performance Table (bfdSessionPerfTable)............3 3.3 Session Performance Table (bfdSessionPerfTable)...............3
3.4 Session Mapping Table (bfdSessMapTable)....................3 3.4 Session Mapping Table (bfdSessMapTable).......................3
4. BFD MIB Module Definitions.....................................4 BFD MIB October 20, 2006
5. Security Considerations.......................................21
6. Acknowledgements..............................................22 5. BFD MIB Module Definitions....................................4
7. References....................................................23 6. Security Considerations......................................21
7.1 Normative References.........................................23 7. IANA Considerations..........................................41
7.2 Informative References.......................................23 7.1 IANA Considerations for BFD-STD-MIB..........................41
8. Author's Addresses............................................23 8. References...................................................23
9. Full Copyright Statement......................................24 8.1 Normative References.........................................23
10. IANA Considerations.........................................41 8.2 Informative References.......................................23
10.1. IANA Considerations for BFD-STD-MIB.......................41 9. Acknowledgements.............................................22
11. Intellectual Property Statement.............................41 10. Authors' Addresses...........................................23
11. Intellectual Property Statement..............................41
12. Full Copyright Statement.....................................24
1. Introduction 1. Introduction
This memo defines an portion of the Management This memo defines an portion of the Management
Information Base (MIB) for use with network management protocols Information Base (MIB) for use with network management protocols
in the Internet community. In particular, it describes managed in the Internet community. In particular, it describes managed
objects to configure and/or monitor Bi-Directional Forwarding objects to configure and/or monitor Bi-Directional Forwarding
Detection on devices supporting this feature. Detection on devices supporting this feature.
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
skipping to change at page 3, line 4 skipping to change at page 3, line 4
here. here.
3. The Internet-Standard Management Framework 3. 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]. 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
BFD MIB October 20, 2006
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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
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
skipping to change at page 3, line 39 skipping to change at page 3, line 41
performance counts on a per session basis. This table is an AUGMENT performance counts on a per session basis. This table is an AUGMENT
to the bfdSessionTable. to the bfdSessionTable.
3.4 Session Mapping Table (bfdSessMapTable) 3.4 Session Mapping Table (bfdSessMapTable)
The BFD Session Mapping Table maps the complex indexing of the BFD The BFD Session Mapping Table maps the complex indexing of the BFD
sessions to the flat BFDIndex used in the BfdSessionTable. sessions to the flat BFDIndex used in the BfdSessionTable.
5. BFD MIB Module Definitions 5. BFD MIB Module Definitions
This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC3291], and [RFC3413].
BFD-STD-MIB DEFINITIONS ::= BEGIN BFD-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, Counter32, Counter64, Unsigned32, Counter32, Counter64,
NOTIFICATION-TYPE, mib-2 NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
TEXTUAL-CONVENTION, TruthValue, TEXTUAL-CONVENTION, TruthValue,
RowStatus, StorageType, TimeStamp RowStatus, StorageType, TimeStamp
BFD MIB October 20, 2006
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
InetAddress, InetAddressType, InetPortNumber InetAddress, InetAddressType, InetPortNumber
FROM INET-ADDRESS-MIB -- [RFC3291] FROM INET-ADDRESS-MIB -- [RFC3291]
; ;
bfdMIB MODULE-IDENTITY bfdMIB MODULE-IDENTITY
LAST-UPDATED "200507221200Z" -- 04 July 2005 12:00:00 EST LAST-UPDATED "200507221200Z" -- 04 July 2005 12:00:00 EST
ORGANIZATION "IETF" ORGANIZATION "IETF"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
skipping to change at page 4, line 47 skipping to change at page 5, line 4
bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 } bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 }
bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 3 } bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 3 }
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"
BFD MIB October 20, 2006
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD interval delay in microseconds." "The BFD interval delay in microseconds."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
BfdDiag ::= TEXTUAL-CONVENTION BfdDiag ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A common BFD diagnostic code." "A common BFD diagnostic code."
skipping to change at page 5, line 47 skipping to change at page 6, line 4
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 }
bfdVersionNumber OBJECT-TYPE bfdVersionNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
BFD MIB October 20, 2006
DESCRIPTION DESCRIPTION
"The current version number of the BFD protocol." "The current version number of the BFD protocol."
REFERENCE REFERENCE
" BFD Version 0 (draft-katz-ward-bfd-02.txt)" " BFD Version 0 (draft-katz-ward-bfd-02.txt)"
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdScalarObjects 3 } ::= { bfdScalarObjects 3 }
-- BFD Session Table -- BFD Session Table
-- The BFD Session Table specifies BFD session specific -- The BFD Session Table specifies BFD session specific
-- information. -- information.
skipping to change at page 6, line 47 skipping to change at page 6, line 52
bfdSessState INTEGER, bfdSessState INTEGER,
bfdSessRemoteHeardFlag TruthValue, bfdSessRemoteHeardFlag TruthValue,
bfdSessDiag Unsigned32, bfdSessDiag Unsigned32,
bfdSessOperMode INTEGER, bfdSessOperMode INTEGER,
bfdSessDemandModeDesiredFlag TruthValue, bfdSessDemandModeDesiredFlag TruthValue,
bfdSessEchoFuncModeDesiredFlag TruthValue, bfdSessEchoFuncModeDesiredFlag TruthValue,
bfdSessControlPlanIndepFlag TruthValue, bfdSessControlPlanIndepFlag TruthValue,
bfdSessAddrType InetAddressType, bfdSessAddrType InetAddressType,
bfdSessAddr InetAddress, bfdSessAddr InetAddress,
bfdSessDesiredMinTxInterval BfdInterval, bfdSessDesiredMinTxInterval BfdInterval,
bfdSessDesiredMinRxInterval BfdInterval, bfdSessReqMinRxInterval BfdInterval,
bfdSessDesiredMinEchoRxInterval BfdInterval, BFD MIB October 20, 2006
bfdSessReqMinEchoRxInterval BfdInterval,
bfdSessDetectMult Unsigned32, bfdSessDetectMult Unsigned32,
bfdSessStorType StorageType, bfdSessStorType StorageType,
bfdSessRowStatus RowStatus, bfdSessRowStatus RowStatus,
bfdSessAuthPresFlag TruthValue, bfdSessAuthPresFlag TruthValue,
bfdSessAuthenticationType INTEGER bfdSessAuthenticationType INTEGER
} }
bfdSessIndex OBJECT-TYPE bfdSessIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 7, line 49 skipping to change at page 8, line 4
::= { bfdSessEntry 3 } ::= { bfdSessEntry 3 }
bfdSessRemoteDiscr OBJECT-TYPE bfdSessRemoteDiscr 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 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."
::= { bfdSessEntry 4 } ::= { bfdSessEntry 4 }
BFD MIB October 20, 2006
bfdSessUdpPort OBJECT-TYPE bfdSessUdpPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The UDP Port for BFD. The default value is the "The UDP Port for BFD. The default value is the
well-known value for this port." well-known value for this port."
REFERENCE REFERENCE
"draft-katz-ward-bfd-02.txt and "draft-katz-ward-bfd-02.txt and
skipping to change at page 8, line 49 skipping to change at page 9, line 4
the BFD session." the BFD session."
::= { bfdSessEntry 7 } ::= { bfdSessEntry 7 }
bfdSessDiag OBJECT-TYPE bfdSessDiag OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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(1) for the last transition of the session from up(1)
BFD MIB October 20, 2006
to some other state." to some other state."
::= { bfdSessEntry 8 } ::= { bfdSessEntry 8 }
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
skipping to change at page 9, line 49 skipping to change at page 10, line 4
DESCRIPTION DESCRIPTION
"This object indicates that the local system's "This object indicates that the local system's
desire to use Echo mode. Specifically, it is set desire to use Echo 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
Echo mode or false(0) if not" Echo mode or false(0) if not"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 11 } ::= { bfdSessEntry 11 }
bfdSessControlPlanIndepFlag OBJECT-TYPE bfdSessControlPlanIndepFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
BFD MIB October 20, 2006
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
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(0)"
DEFVAL { false } DEFVAL { false }
skipping to change at page 10, line 49 skipping to change at page 11, line 4
DESCRIPTION DESCRIPTION
"This object specifies IP address of the interface "This object specifies IP address of the interface
associated with this BFD session. associated 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 14 } ::= { bfdSessEntry 14 }
bfdSessDesiredMinTxInterval OBJECT-TYPE bfdSessDesiredMinTxInterval OBJECT-TYPE
SYNTAX BfdInterval SYNTAX BfdInterval
BFD MIB October 20, 2006
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 15 } ::= { bfdSessEntry 15 }
bfdSessDesiredMinRxInterval 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 16 } ::= { bfdSessEntry 16 }
bfdSessDesiredMinEchoRxInterval 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 17 } ::= { bfdSessEntry 17 }
bfdSessDetectMult OBJECT-TYPE bfdSessDetectMult OBJECT-TYPE
skipping to change at page 11, line 49 skipping to change at page 12, line 4
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
columnar objects in the row." columnar objects in the row."
::= { bfdSessEntry 19 } ::= { bfdSessEntry 19 }
bfdSessRowStatus OBJECT-TYPE bfdSessRowStatus OBJECT-TYPE
BFD MIB October 20, 2006
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
bfdSessRowStatus and bfdSessStorageType." bfdSessRowStatus and bfdSessStorageType."
::= { bfdSessEntry 20 } ::= { bfdSessEntry 20 }
skipping to change at page 12, line 49 skipping to change at page 13, line 4
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
BFD MIB October 20, 2006
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 }
::= { bfdSessPerfTable 1 } ::= { bfdSessPerfTable 1 }
skipping to change at page 13, line 49 skipping to change at page 14, line 4
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 }
bfdSessUpTime OBJECT-TYPE bfdSessUpTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
BFD MIB October 20, 2006
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
skipping to change at page 14, line 49 skipping to change at page 15, line 4
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.
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 occurred
since the last re-initialization of the local management since the last re-initialization of the local management
BFD MIB October 20, 2006
subsystem, then this object contains a zero value." 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
if bfdSessPerfPktInHC is supported according to if bfdSessPerfPktInHC is supported according to
the rules spelled out in RFC2863." the rules spelled out in RFC2863."
skipping to change at page 15, line 47 skipping to change at page 16, line 4
indexing of the BFD sessions to the flat indexing of the BFD sessions to the flat
BFDIndex used in the BfdSessionTable. BFDIndex used in the BfdSessionTable.
Implementors need to be aware that if the value of Implementors need to be aware that if the value of
the bfdSessAddr (an OID) has more the bfdSessAddr (an OID) has more
that 111 sub-identifiers, then OIDs of column that 111 sub-identifiers, then OIDs of column
instances in this table will have more than 128 instances in this table will have more than 128
sub-identifiers and cannot be accessed using SNMPv1, sub-identifiers and cannot be accessed using SNMPv1,
SNMPv2c, or SNMPv3. SNMPv2c, or SNMPv3.
" "
BFD MIB October 20, 2006
REFERENCE REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-02.txt)" "BFD Version 0 (draft-katz-ward-bfd-02.txt)"
::= { bfdObjects 4 } ::= { bfdObjects 4 }
bfdSessMapEntry OBJECT-TYPE bfdSessMapEntry OBJECT-TYPE
SYNTAX BfdSessMapEntry SYNTAX BfdSessMapEntry
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
that is mapped to this index. that is mapped to this index.
Implementors need to be aware that if the value of Implementors need to be aware that if the value of
the mplsInSegmentMapLabelPtrIndex (an OID) has more the mplsInSegmentMapLabelPtrIndex (an OID) has more
skipping to change at page 16, line 48 skipping to change at page 17, line 4
-- Notification Configuration -- Notification Configuration
bfdSessNotificationsEnable OBJECT-TYPE bfdSessNotificationsEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is set to true(1), then it enables "If this object is set to true(1), then it enables
the emission of bfdSessUp and bfdSessDown the emission of bfdSessUp and bfdSessDown
BFD MIB October 20, 2006
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 4 } ::= { bfdScalarObjects 4 }
bfdSessUp NOTIFICATION-TYPE bfdSessUp NOTIFICATION-TYPE
skipping to change at page 17, line 48 skipping to change at page 18, line 4
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(4) entries in bfdSessTable are about to enter the down(4)
or adminDown(5) states from some other state. The included or adminDown(5) 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 state (i.e: down(4) or adminDown(5)). The two instances new state (i.e: down(4) or adminDown(5)). The two instances
BFD MIB October 20, 2006
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(4) or adminDown(5) states have transitioned into the down(4) or adminDown(5) 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
skipping to change at page 18, line 48 skipping to change at page 19, line 4
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
bfdSessionGroup, bfdSessionGroup,
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
BFD MIB October 20, 2006
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."
skipping to change at page 19, line 46 skipping to change at page 19, line 52
bfdSessRemoteDiscr, bfdSessRemoteDiscr,
bfdSessUdpPort, bfdSessUdpPort,
bfdSessState, bfdSessState,
bfdSessRemoteHeardFlag, bfdSessRemoteHeardFlag,
bfdSessDiag, bfdSessDiag,
bfdSessOperMode, bfdSessOperMode,
bfdSessDemandModeDesiredFlag, bfdSessDemandModeDesiredFlag,
bfdSessEchoFuncModeDesiredFlag, bfdSessEchoFuncModeDesiredFlag,
bfdSessControlPlanIndepFlag, bfdSessControlPlanIndepFlag,
bfdSessDesiredMinTxInterval, bfdSessDesiredMinTxInterval,
bfdSessDesiredMinRxInterval, bfdSessReqMinRxInterval,
bfdSessDesiredMinEchoRxInterval, BFD MIB October 20, 2006
bfdSessReqMinEchoRxInterval,
bfdSessDetectMult, bfdSessDetectMult,
bfdSessStorType, bfdSessStorType,
bfdSessRowStatus, bfdSessRowStatus,
bfdSessMapBfdIndex, bfdSessMapBfdIndex,
bfdSessAuthPresFlag, bfdSessAuthPresFlag,
bfdSessAuthenticationType bfdSessAuthenticationType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for BFD sessions." "Collection of objects needed for BFD sessions."
skipping to change at page 20, line 47 skipping to change at page 21, line 4
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 3 }
bfdNotificationGroup NOTIFICATION-GROUP bfdNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
bfdSessUp, bfdSessUp,
bfdSessDown bfdSessDown
} }
BFD MIB October 20, 2006
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this "Set of notifications implemented in this
module." module."
::= { bfdGroups 4 } ::= { bfdGroups 4 }
END END
6. Security Considerations 6. Security Considerations
skipping to change at page 21, line 47 skipping to change at page 22, line 4
table sensative. table sensative.
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 provided by the SNMPv3 framework "see [RFC3410], section 8", as provided by the SNMPv3 framework "see [RFC3410], section 8",
BFD MIB October 20, 2006
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. Acknowledgements 7. IANA Considerations
We would like to thank David Ward for his comments and suggestions.
8. References There is one MIB module contained in this document. The following
"IANA Considerations" subsection requests IANA for a new
assignment under the mib-2 subtree. New assignments can only
be made via a Standards Action as specified in [RFC2434].
8.1 Normative References 7.1. IANA Considerations for BFD-STD-MIB
[BFD] Katz, D., and Ward, D., "Bidirectional Forwarding The IANA is requested to assign { mib-2 XXX } to the
Detection", draft-ietf-bfd-base-02.txt. MPLS-L3VPN-STD-MIB module specified in this document.
[BFD-MH] Katz, D., and Ward, D., "BFD for Multihop Paths", 8. References
draft-ietf-bfd-multihop-03.txt.
[BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow 8.1 Normative References
BFD For MPLS LSPs, draft-ietf-bfd-mpls-02.txt.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J. [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Schoenwaelder, "Textual Conventions for Internet
Network Addresses", RFC 3291, May 2002. Network Addresses", RFC 3291, May 2002.
[BFD] Katz, D., and Ward, D., "Bidirectional Forwarding
Detection", draft-ietf-bfd-base-05.txt.
BFD MIB October 20, 2006
[BFD-MH] Katz, D., and Ward, D., "BFD for Multihop Paths",
draft-ietf-bfd-multihop-04.txt.
[BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow
BFD For MPLS LSPs, draft-ietf-bfd-mpls-03.txt.
8.2 Informative References 8.2 Informative References
[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, April 1997.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3413] Levi, D., Meyer, P., Stewart, B., [RFC3413] Levi, D., Meyer, P., Stewart, B.,
"SNMP Applications", RFC 3413, December 2002. "SNMP Applications", RFC 3413, December 2002.
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing
an IANA Considerations Section in RFCs", BCP 26, RFC an IANA Considerations Section in RFCs", BCP 26, RFC
2434, October 1998. 2434, October 1998.
9. Authors' Addresses 9. Acknowledgements
We would like to thank David Ward for his comments and suggestions.
10. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road 300 Beaver Brook Road
Boxboro, MA 01719 Boxboro, MA 01719
Phone: +1-978-936-1470 Phone: 978-936-1470
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Zafar Ali Zafar Ali
Cisco Systems Inc. Cisco Systems Inc.
100 South Main St. #200 100 South Main St. #200
Ann Arbor, MI 48104, USA. Ann Arbor, MI 48104, USA.
Phone: +1-734-276-2459 Phone: 734-276-2459
Email: zali@cisco.com Email: zali@cisco.com
10. Full Copyright Statement 11. Intellectual Property Statement
BFD MIB October 20, 2006
Copyright (C) The Internet Society (2005). 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 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.
11. IANA Considerations
There is one MIB module contained in this document. The following
"IANA Considerations" subsection requests IANA for a new
assignment under the mib-2 subtree. New assignments can only
be made via a Standards Action as specified in [RFC2434].
11.1. IANA Considerations for BFD-STD-MIB
The IANA is requested to assign { mib-2 XXX } to the
MPLS-L3VPN-STD-MIB module specified in this document.
12. Intellectual Property Statement
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.
skipping to change at line 1119 skipping to change at page 24, line 27
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 ietf-
ipr@ietf.org. ipr@ietf.org.
12. Full Copyright Statement
Copyright (C) The Internet Society (2006). 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 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. 45 change blocks. 
71 lines changed or deleted 111 lines changed or added

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