draft-ietf-bfd-mib-20.txt   draft-ietf-bfd-mib-21.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet-Draft Brocade Internet-Draft Brocade
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: November 10, 2014 N. Akiya Expires: November 10, 2014 N. Akiya
Cisco Systems Cisco Systems
May 9, 2014 May 30, 2014
BFD Management Information Base BFD Management Information Base
draft-ietf-bfd-mib-20 draft-ietf-bfd-mib-21
Abstract Abstract
This draft defines a portion of the Management Information Base (MIB) This draft defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling In particular, it describes managed objects for modeling
Bidirectional Forwarding Detection (BFD) protocol. Bidirectional Forwarding Detection (BFD) protocol.
Requirements Language Requirements Language
skipping to change at page 2, line 5 skipping to change at page 2, line 5
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 10, 2014. This Internet-Draft will expire on November 10, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
BFD-STD-MIB May 30, 2014
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
skipping to change at page 3, line 8 skipping to change at page 3, line 4
This memo does not define a compliance requirement for a system that This memo does not define a compliance requirement for a system that
only implements BFD version 0. This is a reflection of a considered only implements BFD version 0. This is a reflection of a considered
and deliberate decision by the BFD WG, because the BFD version 0 and deliberate decision by the BFD WG, because the BFD version 0
protocol is primarily of historical interest by comparison to the protocol is primarily of historical interest by comparison to the
widespread deployment of the BFD version 1 protocol. widespread deployment of the BFD version 1 protocol.
2. 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
BFD-STD-MIB May 30, 2014
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
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].
As with all MIB modules, an attempt to SET or CREATE an object to a
value that is not supported by the implementation will result in a
failure using a return code that indicates that the value is not
supported.
3. Terminology 3. Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [RFC5880], [RFC5881], [RFC5883] and [RFC7130]. Unless described in [RFC5880], [RFC5881], [RFC5883] and [RFC7130]. Unless
otherwise stated, the mechanisms described therein will not be re- otherwise stated, the mechanisms described therein will not be re-
described here. described here.
4. Brief Description of MIB Objects 4. Brief Description of MIB Objects
This section describes objects pertaining to BFD. The MIB objects This section describes objects pertaining to BFD. The MIB objects
skipping to change at page 4, line 6 skipping to change at page 4, line 4
The session table is used to identify a BFD session between a pair of The session table is used to identify a BFD session between a pair of
nodes. nodes.
4.3. Session Performance Table (bfdSessionPerfTable) 4.3. Session Performance Table (bfdSessionPerfTable)
The session performance table is used for collecting BFD performance The session performance table is used for collecting BFD performance
counters on a per session basis. This table is an AUGMENT to the counters on a per session basis. This table is an AUGMENT to the
bfdSessionTable. bfdSessionTable.
4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) 4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable)
BFD-STD-MIB May 30, 2014
The BFD Session Discriminator Mapping Table provides a mapping The BFD Session Discriminator Mapping Table provides a mapping
between a local discriminator value to the associated BFD session between a local discriminator value to the associated BFD session
found in the bfdSessionTable. found in the bfdSessionTable.
4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable)
The BFD Session IP Mapping Table maps, given bfdSessInterface, The BFD Session IP Mapping Table maps, given bfdSessInterface,
bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and
bfdSessDstAddr, to an associated BFD session found in the bfdSessDstAddr, to an associated BFD session found in the
skipping to change at page 5, line 6 skipping to change at page 5, line 4
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB -- [RFC3289] FROM DIFFSERV-MIB -- [RFC3289]
BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC,
BfdCtrlDestPortNumberTC, BfdCtrlSourcePortNumberTC BfdCtrlDestPortNumberTC, BfdCtrlSourcePortNumberTC
FROM BFD-TC-STD-MIB FROM BFD-TC-STD-MIB
IANAbfdDiagTC, IANAbfdSessTypeTC, IANAbfdSessOperModeTC, IANAbfdDiagTC, IANAbfdSessTypeTC, IANAbfdSessOperModeTC,
IANAbfdSessStateTC, IANAbfdSessAuthenticationTypeTC, IANAbfdSessStateTC, IANAbfdSessAuthenticationTypeTC,
IANAbfdSessAuthenticationKeyTC IANAbfdSessAuthenticationKeyTC
BFD-STD-MIB May 30, 2014
FROM IANA-BFD-TC-STD-MIB; FROM IANA-BFD-TC-STD-MIB;
bfdMIB MODULE-IDENTITY bfdMIB MODULE-IDENTITY
LAST-UPDATED "201405091200Z" -- 9 May 2014 12:00:00 EST LAST-UPDATED "201405091200Z" -- 9 May 2014 12:00:00 EST
ORGANIZATION "IETF Bidirectional Forwarding Detection ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Thomas D. Nadeau
Brocade Brocade
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
skipping to change at page 6, line 7 skipping to change at page 6, line 4
bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 }
-- BFD General Variables -- BFD General Variables
-- These parameters apply globally to the Systems' -- These parameters apply globally to the Systems'
-- BFD Process. -- BFD Process.
bfdAdminStatus OBJECT-TYPE bfdAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
BFD-STD-MIB May 30, 2014
enabled(1), enabled(1),
disabled(2), disabled(2),
adminDown(3), adminDown(3),
down(4) down(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired global administrative status of the BFD "The desired global administrative status of the BFD
system in this device." system in this device."
skipping to change at page 7, line 7 skipping to change at page 7, line 4
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 3 } ::= { bfdScalarObjects 3 }
bfdSessIndexNext OBJECT-TYPE bfdSessIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295) SYNTAX IndexIntegerNextFree (0..4294967295)
BFD-STD-MIB May 30, 2014
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an unused value for "This object contains an unused value for
bfdSessIndex that can be used when creating bfdSessIndex that can be used when creating
entries in the table. A zero indicates that entries in the table. A zero indicates that
no entries are available, but MUST NOT be used no entries are available, but MUST NOT be used
as a valid index. " as a valid index. "
::= { bfdScalarObjects 4 } ::= { bfdScalarObjects 4 }
skipping to change at page 8, line 6 skipping to change at page 8, line 4
bfdSessDiscriminator Unsigned32, bfdSessDiscriminator Unsigned32,
bfdSessRemoteDiscr Unsigned32, bfdSessRemoteDiscr Unsigned32,
bfdSessDestinationUdpPort BfdCtrlDestPortNumberTC, bfdSessDestinationUdpPort BfdCtrlDestPortNumberTC,
bfdSessSourceUdpPort BfdCtrlSourcePortNumberTC, bfdSessSourceUdpPort BfdCtrlSourcePortNumberTC,
bfdSessEchoSourceUdpPort InetPortNumber, bfdSessEchoSourceUdpPort InetPortNumber,
bfdSessAdminStatus INTEGER, bfdSessAdminStatus INTEGER,
bfdSessOperStatus INTEGER, bfdSessOperStatus INTEGER,
bfdSessState IANAbfdSessStateTC, bfdSessState IANAbfdSessStateTC,
bfdSessRemoteHeardFlag TruthValue, bfdSessRemoteHeardFlag TruthValue,
bfdSessDiag IANAbfdDiagTC, bfdSessDiag IANAbfdDiagTC,
BFD-STD-MIB May 30, 2014
bfdSessOperMode IANAbfdSessOperModeTC, bfdSessOperMode IANAbfdSessOperModeTC,
bfdSessDemandModeDesiredFlag TruthValue, bfdSessDemandModeDesiredFlag TruthValue,
bfdSessControlPlaneIndepFlag TruthValue, bfdSessControlPlaneIndepFlag TruthValue,
bfdSessMultipointFlag TruthValue, bfdSessMultipointFlag TruthValue,
bfdSessInterface InterfaceIndexOrZero, bfdSessInterface InterfaceIndexOrZero,
bfdSessSrcAddrType InetAddressType, bfdSessSrcAddrType InetAddressType,
bfdSessSrcAddr InetAddress, bfdSessSrcAddr InetAddress,
bfdSessDstAddrType InetAddressType, bfdSessDstAddrType InetAddressType,
bfdSessDstAddr InetAddress, bfdSessDstAddr InetAddress,
bfdSessGTSM TruthValue, bfdSessGTSM TruthValue,
skipping to change at page 9, line 6 skipping to change at page 9, line 4
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-create 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. Write access is available for this object is running in. Write access is available for this object
to provide ability to set desired version for this to provide ability to set desired version for this
BFD session." BFD session."
REFERENCE REFERENCE
BFD-STD-MIB May 30, 2014
"Katz, D. and D. Ward, Bidirectional Forwarding "Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2012." Detection (BFD), RFC 5880, June 2012."
DEFVAL { 1 } DEFVAL { 1 }
::= { bfdSessEntry 2 } ::= { bfdSessEntry 2 }
bfdSessType OBJECT-TYPE bfdSessType OBJECT-TYPE
SYNTAX IANAbfdSessTypeTC SYNTAX IANAbfdSessTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 10, line 6 skipping to change at page 10, line 4
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the destination UDP port number "This object specifies the destination UDP port number
used for this BFD session's control packets. The value used for this BFD session's control packets. The value
may be zero(0) if the session is in adminDown(1) state." may be zero(0) if the session is in adminDown(1) state."
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 6 } ::= { bfdSessEntry 6 }
bfdSessSourceUdpPort OBJECT-TYPE bfdSessSourceUdpPort OBJECT-TYPE
BFD-STD-MIB May 30, 2014
SYNTAX BfdCtrlSourcePortNumberTC SYNTAX BfdCtrlSourcePortNumberTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the source UDP port number used "This object specifies the source UDP port number used
for this BFD session's control packets. The value may be for this BFD session's control packets. The value may be
zero(0) if the session is in adminDown(1) state. Upon zero(0) if the session is in adminDown(1) state. Upon
creation of a new BFD session via this MIB, the value of creation of a new BFD session via this MIB, the value of
zero(0) specified would permit the implementation to zero(0) specified would permit the implementation to
choose its own source port number." choose its own source port number."
skipping to change at page 11, line 5 skipping to change at page 11, line 5
"Denotes the desired operational status of the BFD Session. "Denotes the desired operational status of the BFD Session.
A transition to enabled(1) will start the BFD state machine A transition to enabled(1) will start the BFD state machine
for the session. The state machine will have an initial for the session. The state machine will have an initial
state of down(2). state of down(2).
A transition to disabled(2) will stop the BFD state machine A transition to disabled(2) will stop the BFD state machine
for the session. The state machine may first transition to for the session. The state machine may first transition to
adminDown(1) prior to stopping. adminDown(1) prior to stopping.
BFD-STD-MIB May 30, 2014
A transition to adminDown(3) will cause the BFD state A transition to adminDown(3) will cause the BFD state
machine to transition to adminDown(1), and will cause the machine to transition to adminDown(1), and will cause the
session to remain in this state. session to remain in this state.
A transition to down(4) will cause the BFD state machine A transition to down(4) will cause the BFD state machine
to transition to down(2), and will cause the session to to transition to down(2), and will cause the session to
remain in this state. remain in this state.
Care should be used in providing write access to this Care should be used in providing write access to this
object without adequate authentication." object without adequate authentication."
skipping to change at page 12, line 4 skipping to change at page 12, line 4
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(2) 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." the BFD session."
BFD-STD-MIB May 30, 2014
REFERENCE REFERENCE
"Katz, D. and D. Ward, Bidirectional "Katz, D. and D. Ward, Bidirectional
Forwarding Detection (BFD), RFC 5880, June 2012." Forwarding Detection (BFD), RFC 5880, June 2012."
::= { bfdSessEntry 12 } ::= { bfdSessEntry 12 }
bfdSessDiag OBJECT-TYPE bfdSessDiag OBJECT-TYPE
SYNTAX IANAbfdDiagTC SYNTAX IANAbfdDiagTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 12, line 52 skipping to change at page 13, line 4
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
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(2)" value is set to false(2)"
BFD-STD-MIB May 30, 2014
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 16 } ::= { bfdSessEntry 16 }
bfdSessMultipointFlag OBJECT-TYPE bfdSessMultipointFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Multipoint (M) bit for this "This object indicates the Multipoint (M) bit for this
session. It is set to true(1) if Multipoint (M) bit is session. It is set to true(1) if Multipoint (M) bit is
skipping to change at page 13, line 51 skipping to change at page 14, line 4
::= { bfdSessEntry 19 } ::= { bfdSessEntry 19 }
bfdSessSrcAddr OBJECT-TYPE bfdSessSrcAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the source IP address of this BFD "This object specifies the source IP address of this BFD
session. The format of this object is controlled by the session. The format of this object is controlled by the
bfdSessSrcAddrType object." bfdSessSrcAddrType object."
BFD-STD-MIB May 30, 2014
::= { bfdSessEntry 20 } ::= { bfdSessEntry 20 }
bfdSessDstAddrType OBJECT-TYPE bfdSessDstAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies IP address type of the neighboring IP "This object specifies IP address type of the neighboring IP
address which is being monitored with this BFD session. address which is being monitored with this BFD session.
The value of unknown(0) is allowed only when the session is The value of unknown(0) is allowed only when the session is
skipping to change at page 14, line 51 skipping to change at page 15, line 4
DEFVAL { true } DEFVAL { true }
::= { bfdSessEntry 23 } ::= { bfdSessEntry 23 }
bfdSessGTSMTTL OBJECT-TYPE bfdSessGTSMTTL OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is valid only when bfdSessGTSM protection is "This object is valid only when bfdSessGTSM protection is
enabled on the system. This object indicates the minimum enabled on the system. This object indicates the minimum
BFD-STD-MIB May 30, 2014
allowed TTL for received BFD control packets. For a allowed TTL for received BFD control packets. For a
singleHop(1) session, if GTSM protection is enabled, singleHop(1) session, if GTSM protection is enabled,
this object SHOULD be set to maximum TTL value allowed this object SHOULD be set to maximum TTL value allowed
for single hop. for single hop.
By default, GTSM is enabled and TTL value is 255. For a By default, GTSM is enabled and TTL value is 255. For a
multihop session, updating of maximum TTL value allowed multihop session, updating of maximum TTL value allowed
is likely required." is likely required."
REFERENCE REFERENCE
"RFC5082, The Generalized TTL Security Mechanism (GTSM). "RFC5082, The Generalized TTL Security Mechanism (GTSM).
skipping to change at page 15, line 50 skipping to change at page 16, line 4
does not want the remote system to send any periodic BFD does not want the remote system to send any periodic BFD
control packets." control packets."
REFERENCE REFERENCE
"Section 4.1 from Katz, D. and D. Ward, Bidirectional "Section 4.1 from Katz, D. and D. Ward, Bidirectional
Forwarding Detection (BFD), RFC 5880, June 2012." Forwarding Detection (BFD), RFC 5880, June 2012."
::= { bfdSessEntry 26 } ::= { bfdSessEntry 26 }
bfdSessReqMinEchoRxInterval OBJECT-TYPE bfdSessReqMinEchoRxInterval OBJECT-TYPE
SYNTAX BfdIntervalTC SYNTAX BfdIntervalTC
MAX-ACCESS read-create MAX-ACCESS read-create
BFD-STD-MIB May 30, 2014
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. Value must be zero(0) if system is capable of supporting. Value must be zero(0) if
this is a multihop BFD session." this is a multihop BFD session."
::= { bfdSessEntry 27 } ::= { bfdSessEntry 27 }
bfdSessDetectMult OBJECT-TYPE bfdSessDetectMult OBJECT-TYPE
SYNTAX BfdMultiplierTC SYNTAX BfdMultiplierTC
skipping to change at page 16, line 50 skipping to change at page 17, line 4
SYNTAX BfdMultiplierTC SYNTAX BfdMultiplierTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the Detect time multiplier." "This object specifies the Detect time multiplier."
::= { bfdSessEntry 31 } ::= { bfdSessEntry 31 }
bfdSessAuthPresFlag OBJECT-TYPE bfdSessAuthPresFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
BFD-STD-MIB May 30, 2014
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(2) if not." to be authenticated or false(2) if not."
REFERENCE REFERENCE
"Sections 4.2 - 4.4 from Katz, D. and D. Ward, "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), RFC 5880, Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012." June 2012."
skipping to change at page 17, line 50 skipping to change at page 18, line 4
DESCRIPTION DESCRIPTION
"The authentication key ID in use for this session. This "The authentication key ID in use for this session. This
object permits multiple keys to be active simultaneously. object permits multiple keys to be active simultaneously.
The value -1 indicates that no Authentication Key ID will The value -1 indicates that no Authentication Key ID will
be present in the optional BFD Authentication Section." be present in the optional BFD Authentication Section."
REFERENCE REFERENCE
"Sections 4.2 - 4.4 from Katz, D. and D. Ward, "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), RFC 5880, Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012." June 2012."
DEFVAL { -1 } DEFVAL { -1 }
BFD-STD-MIB May 30, 2014
::= { bfdSessEntry 34 } ::= { bfdSessEntry 34 }
bfdSessAuthenticationKey OBJECT-TYPE bfdSessAuthenticationKey OBJECT-TYPE
SYNTAX IANAbfdSessAuthenticationKeyTC SYNTAX IANAbfdSessAuthenticationKeyTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authentication key. When the "The authentication key. When the
bfdSessAuthenticationType is simplePassword(1), the value bfdSessAuthenticationType is simplePassword(1), the value
of this object is the password present in the BFD packets. of this object is the password present in the BFD packets.
skipping to change at page 18, line 51 skipping to change at page 19, line 4
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 37 } ::= { bfdSessEntry 37 }
-- BFD Session Performance Table -- BFD Session Performance Table
bfdSessPerfTable OBJECT-TYPE bfdSessPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessPerfEntry SYNTAX SEQUENCE OF BfdSessPerfEntry
BFD-STD-MIB May 30, 2014
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies BFD Session performance counters." "This table specifies BFD Session performance counters."
::= { bfdObjects 3 } ::= { bfdObjects 3 }
bfdSessPerfEntry OBJECT-TYPE bfdSessPerfEntry OBJECT-TYPE
SYNTAX BfdSessPerfEntry SYNTAX BfdSessPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 19, line 50 skipping to change at page 20, line 4
bfdSessPerfEchoPktOutHC Counter64, bfdSessPerfEchoPktOutHC Counter64,
bfdSessPerfEchoPktDropHC Counter64 bfdSessPerfEchoPktDropHC Counter64
} }
bfdSessPerfCtrlPktIn OBJECT-TYPE bfdSessPerfCtrlPktIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD control messages received for this "The total number of BFD control messages received for this
BFD-STD-MIB May 30, 2014
BFD session. BFD session.
It MUST be equal to the least significant 32 bits of It MUST be equal to the least significant 32 bits of
bfdSessPerfCtrlPktInHC if supported, and MUST do so bfdSessPerfCtrlPktInHC if supported, and MUST do so
with the rules spelled out in RFC 2863." with the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 1 } ::= { bfdSessPerfEntry 1 }
bfdSessPerfCtrlPktOut OBJECT-TYPE bfdSessPerfCtrlPktOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 20, line 51 skipping to change at page 21, line 4
"The value of sysUpTime on the most recent occasion at "The value of sysUpTime on the most recent occasion at
which received BFD control message for this session was which received BFD control message for this session was
dropped. If no such up event exists, this object contains dropped. If no such up event exists, this object contains
a zero value." a zero value."
::= { bfdSessPerfEntry 4 } ::= { bfdSessPerfEntry 4 }
bfdSessPerfEchoPktIn OBJECT-TYPE bfdSessPerfEchoPktIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
BFD-STD-MIB May 30, 2014
DESCRIPTION DESCRIPTION
"The total number of BFD echo messages received for this "The total number of BFD echo messages received for this
BFD session. BFD session.
It MUST be equal to the least significant 32 bits of It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktInHC if supported, and MUST do so bfdSessPerfEchoPktInHC if supported, and MUST do so
with the rules spelled out in RFC 2863." with the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 5 } ::= { bfdSessPerfEntry 5 }
bfdSessPerfEchoPktOut OBJECT-TYPE bfdSessPerfEchoPktOut OBJECT-TYPE
skipping to change at page 21, line 50 skipping to change at page 22, 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 received BFD echo message for this session was which received BFD echo message for this session was
dropped. If no such up event has been issued, this dropped. If no such up event has been issued, this
object contains a zero value." object contains a zero value."
::= { bfdSessPerfEntry 8 } ::= { bfdSessPerfEntry 8 }
bfdSessUpTime OBJECT-TYPE bfdSessUpTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
BFD-STD-MIB May 30, 2014
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 event has been issued, the session came up. If no such event has been issued,
this object contains a zero value." this object contains a zero value."
::= { bfdSessPerfEntry 9 } ::= { bfdSessPerfEntry 9 }
bfdSessPerfLastSessDownTime OBJECT-TYPE bfdSessPerfLastSessDownTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
skipping to change at page 22, line 50 skipping to change at page 23, line 4
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.
The relevant counters are the specific instances associated The relevant counters are the specific instances associated
BFD-STD-MIB May 30, 2014
with this BFD session of any Counter32 object contained in with this BFD session of any Counter32 object contained in
the BfdSessPerfTable. If no such discontinuities have the BfdSessPerfTable. If no such discontinuities have
occurred since the last re-initialization of the local occurred since the last re-initialization of the local
management subsystem, then this object contains a zero management subsystem, then this object contains a zero
value." value."
::= { bfdSessPerfEntry 13 } ::= { bfdSessPerfEntry 13 }
bfdSessPerfCtrlPktInHC OBJECT-TYPE bfdSessPerfCtrlPktInHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 23, line 50 skipping to change at page 24, line 4
"This value represents the total number of BFD control "This value represents the total number of BFD control
messages received for this BFD session yet dropped for messages received for this BFD session yet dropped for
being invalid. being invalid.
The least significant 32 bits MUST equal to The least significant 32 bits MUST equal to
bfdSessPerfCtrlPktDrop, and MUST do so with bfdSessPerfCtrlPktDrop, and MUST do so with
the rules spelled out in RFC 2863." the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 16 } ::= { bfdSessPerfEntry 16 }
bfdSessPerfEchoPktInHC OBJECT-TYPE bfdSessPerfEchoPktInHC OBJECT-TYPE
BFD-STD-MIB May 30, 2014
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD echo "This value represents the total number of BFD echo
messages received for this BFD session. messages received for this BFD session.
The least significant 32 bits MUST equal to The least significant 32 bits MUST equal to
bfdSessPerfEchoPktIn, and MUST do so with bfdSessPerfEchoPktIn, and MUST do so with
the rules spelled out in RFC 2863." the rules spelled out in RFC 2863."
skipping to change at page 24, line 50 skipping to change at page 25, line 4
-- BFD Session Discriminator Mapping Table -- BFD Session Discriminator Mapping Table
bfdSessDiscMapTable OBJECT-TYPE bfdSessDiscMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessDiscMapEntry SYNTAX SEQUENCE OF BfdSessDiscMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Discriminator Mapping Table maps a "The BFD Session Discriminator Mapping Table maps a
local discriminator value to associated BFD session's local discriminator value to associated BFD session's
BFD-STD-MIB May 30, 2014
bfdSessIndex found in the bfdSessionTable." bfdSessIndex found in the bfdSessionTable."
::= { bfdObjects 4 } ::= { bfdObjects 4 }
bfdSessDiscMapEntry OBJECT-TYPE bfdSessDiscMapEntry OBJECT-TYPE
SYNTAX BfdSessDiscMapEntry SYNTAX BfdSessDiscMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Discriminator Mapping Entry "The BFD Session Discriminator Mapping Entry
specifies a mapping between a local discriminator specifies a mapping between a local discriminator
skipping to change at page 25, line 49 skipping to change at page 26, line 4
bfdSessDstAddrType and bfdSessDstAddr bfdSessDstAddrType and bfdSessDstAddr
to an associated BFD session found in the to an associated BFD session found in the
bfdSessionTable." bfdSessionTable."
::= { 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
BFD-STD-MIB May 30, 2014
"The BFD Session IP Map Entry contains a mapping "The BFD Session IP Map Entry contains a mapping
from the IP information for a session, to the session from the IP information for a session, to the session
in the bfdSessionTable." in the bfdSessionTable."
INDEX { INDEX {
bfdSessInterface, bfdSessInterface,
bfdSessSrcAddrType, bfdSessSrcAddrType,
bfdSessSrcAddr, bfdSessSrcAddr,
bfdSessDstAddrType, bfdSessDstAddrType,
bfdSessDstAddr bfdSessDstAddr
} }
skipping to change at page 26, line 48 skipping to change at page 27, line 4
state from some other state. The included values of state from some other state. The included values of
bfdSessDiag MUST both be set equal to this bfdSessDiag MUST both be set equal to this
new state (i.e: up(4)). The two instances of new state (i.e: up(4)). The two instances of
bfdSessDiag in this notification indicate the range bfdSessDiag in this notification indicate the range
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
BFD-STD-MIB May 30, 2014
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 { OBJECTS {
skipping to change at page 27, line 48 skipping to change at page 28, line 4
bfdGroups bfdGroups
OBJECT IDENTIFIER ::= { bfdConformance 1 } OBJECT IDENTIFIER ::= { bfdConformance 1 }
bfdCompliances bfdCompliances
OBJECT IDENTIFIER ::= { bfdConformance 2 } OBJECT IDENTIFIER ::= { bfdConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
bfdModuleFullCompliance MODULE-COMPLIANCE bfdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
BFD-STD-MIB May 30, 2014
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "Compliance statement for agents that provide full
support for the BFD-MIB module. Such devices can support for the BFD-MIB module. Such devices can
then be monitored and also be configured using then be monitored and also be configured using
this MIB module." this MIB module."
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
bfdSessionGroup, bfdSessionGroup,
skipping to change at page 28, line 48 skipping to change at page 29, line 4
OBJECT bfdSessDstAddr OBJECT bfdSessDstAddr
SYNTAX InetAddress (SIZE (0|4|16|20)) 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), ipv6(2) and ipv6z(4) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
OBJECT bfdSessRowStatus OBJECT bfdSessRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notReady is not DESCRIPTION "Support for createAndWait and notReady is not
BFD-STD-MIB May 30, 2014
required." required."
::= { bfdCompliances 1 } ::= { bfdCompliances 1 }
bfdModuleReadOnlyCompliance MODULE-COMPLIANCE bfdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only "Compliance requirement for implementations that only
provide read-only support for BFD-MIB. Such devices provide read-only support for BFD-MIB. Such devices
can then be monitored but cannot be configured using can then be monitored but cannot be configured using
skipping to change at page 29, line 49 skipping to change at page 30, line 4
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessSourceUdpPort OBJECT bfdSessSourceUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessEchoSourceUdpPort OBJECT bfdSessEchoSourceUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
BFD-STD-MIB May 30, 2014
OBJECT bfdSessAdminStatus OBJECT bfdSessAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessOperMode OBJECT bfdSessOperMode
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessDemandModeDesiredFlag OBJECT bfdSessDemandModeDesiredFlag
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessControlPlaneIndepFlag OBJECT bfdSessControlPlaneIndepFlag
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 30, line 47 skipping to change at page 31, line 4
OBJECT bfdSessDstAddrType OBJECT bfdSessDstAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), SYNTAX InetAddressType { unknown(0), ipv4(1),
ipv6(2), ipv6z(4) } ipv6(2), ipv6z(4) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4)
support are required. ipv4z(3) is not required support are required. ipv4z(3) is not required
and dns(16) is not allowed." and dns(16) is not allowed."
OBJECT bfdSessDstAddr OBJECT bfdSessDstAddr
BFD-STD-MIB May 30, 2014
SYNTAX InetAddress (SIZE (0|4|16|20)) SYNTAX InetAddress (SIZE (0|4|16|20))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
OBJECT bfdSessGTSM OBJECT bfdSessGTSM
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessGTSMTTL OBJECT bfdSessGTSMTTL
skipping to change at page 31, line 48 skipping to change at page 32, line 4
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessAuthenticationKey OBJECT bfdSessAuthenticationKey
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessStorageType OBJECT bfdSessStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
BFD-STD-MIB May 30, 2014
OBJECT bfdSessRowStatus OBJECT bfdSessRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { bfdCompliances 2 } ::= { bfdCompliances 2 }
-- Units of conformance. -- Units of conformance.
bfdSessionGroup OBJECT-GROUP bfdSessionGroup OBJECT-GROUP
skipping to change at page 32, line 47 skipping to change at page 33, line 4
bfdSessAuthPresFlag, bfdSessAuthPresFlag,
bfdSessAuthenticationType, bfdSessAuthenticationType,
bfdSessAuthenticationKeyID, bfdSessAuthenticationKeyID,
bfdSessAuthenticationKey, bfdSessAuthenticationKey,
bfdSessStorageType, bfdSessStorageType,
bfdSessRowStatus bfdSessRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for BFD sessions." "Collection of objects needed for BFD sessions."
BFD-STD-MIB May 30, 2014
::= { bfdGroups 1 } ::= { bfdGroups 1 }
bfdSessionReadOnlyGroup OBJECT-GROUP bfdSessionReadOnlyGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessRemoteDiscr, bfdSessRemoteDiscr,
bfdSessState, bfdSessState,
bfdSessRemoteHeardFlag, bfdSessRemoteHeardFlag,
bfdSessDiag, bfdSessDiag,
bfdSessNegotiatedInterval, bfdSessNegotiatedInterval,
bfdSessNegotiatedEchoInterval, bfdSessNegotiatedEchoInterval,
skipping to change at page 33, line 47 skipping to change at page 34, line 4
performance of BFD sessions." performance of BFD sessions."
::= { bfdGroups 3 } ::= { bfdGroups 3 }
bfdSessionPerfHCGroup OBJECT-GROUP bfdSessionPerfHCGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfCtrlPktInHC, bfdSessPerfCtrlPktInHC,
bfdSessPerfCtrlPktOutHC, bfdSessPerfCtrlPktOutHC,
bfdSessPerfCtrlPktDropHC, bfdSessPerfCtrlPktDropHC,
bfdSessPerfEchoPktInHC, bfdSessPerfEchoPktInHC,
bfdSessPerfEchoPktOutHC, bfdSessPerfEchoPktOutHC,
BFD-STD-MIB May 30, 2014
bfdSessPerfEchoPktDropHC bfdSessPerfEchoPktDropHC
} }
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 4 } ::= { bfdGroups 4 }
skipping to change at page 34, line 47 skipping to change at page 35, line 4
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o bfdAdminStatus - Improper change of bfdAdminStatus, to o bfdAdminStatus - Improper change of bfdAdminStatus, to
disabled(2), adminDown(3) or down(4), can cause significant disabled(2), adminDown(3) or down(4), can cause significant
disruption of the connectivity to those portions of the Internet disruption of the connectivity to those portions of the Internet
reached via all the applicable remote BFD peers. reached via all the applicable remote BFD peers.
o bfdSessAdminStatus - Improper change of bfdSessAdminStatus, to o bfdSessAdminStatus - Improper change of bfdSessAdminStatus, to
BFD-STD-MIB May 30, 2014
disabled(2), adminDown(3) or down(4), can cause significant disabled(2), adminDown(3) or down(4), can cause significant
disruption of the connectivity to those portions of the Internet disruption of the connectivity to those portions of the Internet
reached via all the applicable remote BFD peers. reached via all the applicable remote BFD peers.
o bfdSessDesiredMinTxInterval, bfdSessReqMinRxInterval, o bfdSessDesiredMinTxInterval, bfdSessReqMinRxInterval,
bfdSessReqMinEchoRxInterval, bfdSessDetectMult - Improper change bfdSessReqMinEchoRxInterval, bfdSessDetectMult - Improper change
of this object can cause connections to be disrupted for extremely of this object can cause connections to be disrupted for extremely
long time periods when otherwise they would be restored in a long time periods when otherwise they would be restored in a
relatively short period of time. relatively short period of time.
skipping to change at page 35, line 49 skipping to change at page 36, line 4
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. It is thus important to control even GET and/or NOTIFY environments. It is thus important to control even GET and/or NOTIFY
access to these objects and possibly to even encrypt the values of access to these objects and possibly to even encrypt the values of
these objects when sending them over the network via SNMP. these objects when sending them over the network via SNMP.
o The bfdSessTable may be used to directly configure BFD sessions. o The bfdSessTable may be used to directly configure BFD sessions.
The bfdSessMapTable can be used indirectly in the same way. The bfdSessMapTable can be used indirectly in the same way.
Unauthorized access to objects in this table could result in Unauthorized access to objects in this table could result in
disruption of traffic on the network. This is especially true if disruption of traffic on the network. This is especially true if
an unauthorized user configures enough tables to invoke a denial an unauthorized user configures enough tables to invoke a denial
BFD-STD-MIB May 30, 2014
of service attack on the device where they are configured, or on a of service attack on the device where they are configured, or on a
remote device where the sessions terminate. remote device where the sessions terminate.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
skipping to change at page 36, line 50 skipping to change at page 37, line 4
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET "change/create/delete" them.
7. IANA Considerations 7. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
BFD-STD-MIB May 30, 2014
---------- ----------------------- ---------- -----------------------
bfdMib { mib-2 XXX } bfdMib { mib-2 XXX }
[RFC-Editor's Note (to be removed prior to publication): the IANA is [RFC-Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note.] this note.]
skipping to change at page 37, line 49 skipping to change at page 38, line 4
[RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., and C. [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., and C.
Pignataro, "The Generalized TTL Security Mechanism Pignataro, "The Generalized TTL Security Mechanism
(GTSM)", RFC 5082, October 2007. (GTSM)", RFC 5082, October 2007.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010. (BFD)", RFC 5880, June 2010.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June
BFD-STD-MIB May 30, 2014
2010. 2010.
[RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for Multihop Paths", RFC 5883, June 2010. (BFD) for Multihop Paths", RFC 5883, June 2010.
[RFC7130] Bhatia, M., Chen, M., Boutros, S., Binderberger, M., and [RFC7130] Bhatia, M., Chen, M., Boutros, S., Binderberger, M., and
J. Haas, "Bidirectional Forwarding Detection (BFD) on Link J. Haas, "Bidirectional Forwarding Detection (BFD) on Link
Aggregation Group (LAG) Interfaces", RFC 7130, February Aggregation Group (LAG) Interfaces", RFC 7130, February
2014. 2014.
[I-D.ietf-bfd-tc-mib] [I-D.ietf-bfd-tc-mib]
Nadeau, T., Ali, Z., and N. Akiya, "Definitions of Textual Nadeau, T., Ali, Z., and N. Akiya, "Definitions of Textual
Conventions (TCs) for Bidirectional Forwarding Detection Conventions (TCs) for Bidirectional Forwarding Detection
(BFD) Management", draft-ietf-bfd-tc-mib-07 (work in (BFD) Management", draft-ietf-bfd-tc-mib-08 (work in
progress), April 2014. progress), April 2014.
9.2. Informative References 9.2. Informative References
[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 Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
skipping to change at page 38, line 46 skipping to change at page 39, line 4
Brocade Brocade
EMail: tnadeau@lucidvision.com EMail: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems Cisco Systems
EMail: zali@cisco.com EMail: zali@cisco.com
Nobo Akiya Nobo Akiya
BFD-STD-MIB May 30, 2014
Cisco Systems Cisco Systems
EMail: nobo@cisco.com EMail: nobo@cisco.com
 End of changes. 43 change blocks. 
3 lines changed or deleted 81 lines changed or added

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