draft-ietf-bfd-mpls-mib-02.txt   draft-ietf-bfd-mpls-mib-03.txt 
Network Working Group Network Working Group
INTERNET-DRAFT Sam Aldrin INTERNET-DRAFT Sam Aldrin
Intended Status: Standards Track Huawei Technologies Intended Status: Standards Track Huawei Technologies
Expires: December 30, 2013 M.Venkatesan Expires: June 29, 2014 M.Venkatesan
Dell Inc. Dell Inc.
Kannan KV Sampath Kannan KV Sampath
Redeem Software Redeem Software
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks
June 28, 2013 December 26, 2013
BFD Management Information Base (MIB) extensions BFD Management Information Base (MIB) extensions
for MPLS and MPLS-TP Networks for MPLS and MPLS-TP Networks
draft-ietf-bfd-mpls-mib-02 draft-ietf-bfd-mpls-mib-03
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 extends the BFD Management Information Base BFD- In particular, it extends the BFD Management Information Base BFD-
STD-MIB and describes the managed objects for modeling Bidirectional STD-MIB and describes the managed objects for modeling Bidirectional
Forwarding Detection (BFD) protocol for MPLS and MPLS-TP networks. Forwarding Detection (BFD) protocol for MPLS and MPLS-TP networks.
Status of this Memo Status of this Memo
skipping to change at page 1, line 48 skipping to change at page 1, line 47
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 30, 2013. This Internet-Draft will expire on June 29, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 36 skipping to change at page 2, line 36
3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4
5.1. Extensions to the BFD session table (bfdSessionTable) . . . 4 5.1. Extensions to the BFD session table (bfdSessionTable) . . . 4
5.2. Example of BFD session configuration . . . . . . . . . . . 6 5.2. Example of BFD session configuration . . . . . . . . . . . 6
5.2.1 Example of BFD Session configuration for MPLS TE 5.2.1 Example of BFD Session configuration for MPLS TE
tunnel . . . . . . . . . . . . . . . . . . . . . . . . . 6 tunnel . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2.2 Example of BFD Session configuration for ME of MPLS-TP 5.2.2 Example of BFD Session configuration for ME of MPLS-TP
TE tunnel . . . . . . . . . . . . . . . . . . . . . . . 7 TE tunnel . . . . . . . . . . . . . . . . . . . . . . . 7
5.3. BFD objects for session performance counters . . . . . . . 9 5.3. BFD objects for session performance counters . . . . . . . 9
5.4. Notification Objects . . . . . . . . . . . . . . . . . . . 9 6. BFD-EXT-STD-MIB Module Definition . . . . . . . . . . . . . . . 10
6. BFD MPLS-MPLS-TP MIB Module Definition . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 18
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 20
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1 Normative References . . . . . . . . . . . . . . . . . . . . 20 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 20
9.2 Informative References . . . . . . . . . . . . . . . . . . . 21 9.2 Informative References . . . . . . . . . . . . . . . . . . . 21
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 21 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22
1 Introduction 1 Introduction
Current MIB for BFD as defined by BFD-STD-MIB is used for neighbor The current MIB for BFD as defined by BFD-STD-MIB is used for
monitoring in IP networks. The BFD session association to the neighbor monitoring in IP networks. The BFD session association to
neighbors being monitored is done using the source and destination IP the neighbors being monitored is done using the source and
addresses of the neighbors configured using the respective MIB destination IP addresses of the neighbors configured using the
objects. respective MIB objects.
To monitor MPLS/MPLS-TP paths like tunnels or Pseudowires, there is a To monitor MPLS/MPLS-TP paths like tunnels or Pseudowires, there is a
necessity to identify or associate the BFD session to those paths. necessity to identify or associate the BFD session to those paths.
This memo defines an portion of the Management Information Base (MIB) This memo defines an portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it extends the BFD Management Information Base BFD- In particular, it extends the BFD Management Information Base BFD-
STD-MIB and describes the managed objects to configure and/or monitor STD-MIB and describes the managed objects to configure and/or monitor
Bidirectional Forwarding Detection (BFD) protocol for MPLS [BFD-MPLS] Bidirectional Forwarding Detection (BFD) protocol for MPLS [RFC5884]
and MPLS-TP networks [RFC6428]. and MPLS-TP networks [RFC6428].
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
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC3410 [RFC3410]. RFC3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
skipping to change at page 3, line 48 skipping to change at page 3, line 48
3.1 Conventions used in this document 3.1 Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
3.2 Terminology 3.2 Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [BFD], [BFD-1HOP], [BFD-MH], [BFD-MPLS], [RFC6428]. described in [BFD], [BFD-1HOP], [BFD-MH], [RFC5884], [RFC6428].
Unless otherwise stated, the mechanisms described therein will not be Unless otherwise stated, the mechanisms described therein will not be
re-described here. re-described here.
4. Acronyms 4. Acronyms
BFD: Bidirectional Forwarding Detection BFD: Bidirectional Forwarding Detection
CC: Continuity Check
CV: Connectivity Verification
IP: Internet Protocol IP: Internet Protocol
LDP: Label Distribution Protocol
LOC: Loss Of Continuity
LSP: Label Switching Path LSP: Label Switching Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base
MPLS: Multi-Protocol Label Switching
MPLS-TP: MPLS Transport Profile
ME: Maintenance Entity ME: Maintenance Entity
MEG: Maintenance Entity Group MEG: Maintenance Entity Group
MEP: Maintenance Entity End-Point MEP: Maintenance Entity End-Point
PW: Pseudowire MIP: Maintenance Entity Group Intermediate Point
MIB: Management Information Base
MPLS: Multi-Protocol Label Switching
MPLS-TP: MPLS Transport Profile
OAM: Operations, Administration, and Maintenance
PW: Pseudo Wire
RDI: Remote Defect Indication
TE: Traffic Engineering
TP: Transport Profile TP: Transport Profile
LOC: Loss Of Continuity
5. Brief description of MIB Objects 5. Brief description of MIB Objects
The objects described in this section support the functionality The objects described in this section support the functionality
described in documents [BFD-MPLS] and [RFC6428]. The objects are described in documents [RFC5884] and [RFC6428]. The objects are
defined as an extension to the BFD base MIB defined by BFD-STD-MIB. defined as an extension to the BFD base MIB defined by BFD-STD-MIB.
5.1. Extensions to the BFD session table (bfdSessionTable) 5.1. Extensions to the BFD session table (bfdSessionTable)
The BFD session table used to identify a BFD session between a pair The BFD session table used to identify a BFD session between a pair
of nodes, as defined in BFD-STD-MIB, is extended with managed objects of nodes, as defined in BFD-STD-MIB, is extended with managed objects
to achieve the required functionality in MPLS and MPLS-TP networks as to achieve the required functionality in MPLS and MPLS-TP networks as
described below: described below:
1. SessionRole - Active/Passive role specification for the BFD 1. SessionRole - Active/Passive role specification for the BFD
session configured on the node. Either end of a BFD session session configured on the node. Either end of a BFD session
can be configured as Active/Passive to determine which can be configured as Active/Passive to determine which
end starts transmitting the BFD control packets. end starts transmitting the BFD control packets.
2. SessionMode - Defines the mode in which BFD 2. SessionMode - Defines the mode in which BFD
session is running, defined as below: session is running, defined as below:
i. CC - Only Continuity Check and RDI functionality is i. CC - Indicates Continuity Check and RDI operations.
performed.
ii. CV - Provides for Continuity Check, Connectivity ii. CV - Indicates Continuity Check, Connectivity
Verification and RDI functionalities to be Verification and RDI operations.
supported.
3. Timer Negotiation Flag - Provides for timer negotiation 3. Timer Negotiation Flag - Provides for timer negotiation
to be enabled or disabled. This object can be used to tune to be enabled or disabled. This object can be used to tune
the detection of period-misconfiguration. the detection of period mis-configuration.
4. Map Type - Indicates the type of the path being monitored by 4. Map Type - Indicates the type of the path being monitored by
the BFD session. the BFD session.
This object can take the following values: This object can take the following values:
For BFD session over MPLS based paths: For BFD session over MPLS based paths:
nonTeIpv4 (1) - BFD session configured for Non-TE nonTeIpv4 (1) - BFD session configured for Non-TE
Ipv4 path IPv4 path
nonTeIpv6 (2) - BFD session configured for Non-TE nonTeIpv6 (2) - BFD session configured for Non-TE
Ipv6 path IPv6 path
teIpv4 (3) - BFD session configured for a TE teIpv4 (3) - BFD session configured for a TE
Ipv4 path IPv4 path
teIpv6 (4) - BFD session configured for a TE teIpv6 (4) - BFD session configured for a TE
Ipv6 path IPv6 path
pw (5) - BFD session configured for a PW pw (5) - BFD session configured for a pseudowire
For MPLS-TP based paths: For MPLS-TP based paths:
mep (6) - BFD session configured for an MPLS-TP path mep (6) - BFD session configured for an MPLS-TP path
(Bidirectional tunnel, PW or Sections) will map to (Bidirectional tunnel, PW or Sections) will map to
the corresponding maintenance entity. the corresponding maintenance entity.
5. Map Pointer 5. Map Pointer
A Row Pointer object which can be used to point to the first A Row Pointer object which can be used to point to the first
accessible object in the respective instance of the table entry accessible object in the respective instance of the table entry
identifying the path being monitored (mplsXCEntry/mplsTunnelEntry/ identifying the path being monitored (mplsXCEntry[RFC3813]/
pwEntry respectively for LSP/Tunnel/PW). mplsTunnelEntry[RFC3812]/pwEntry[RFC5601] respectively for
LSP/Tunnel/PW).
For NON-TE LSP, the Map pointer points to the corresponding For NON-TE LSP, the map pointer points to the corresponding
mplsXCEntry. mplsXCEntry.
For TE based tunnel, the Map pointer points to the corresponding For TE based tunnel, the map pointer points to the corresponding
instance of the mplsTunnelEntry. instance of the mplsTunnelEntry.
For PW, this object points to the corresponding instance of For PW, this object points to the corresponding instance of
pwEntry. pwEntry.
For MPLS-TP paths, this object points to the corresponding For MPLS-TP paths, this object points to the corresponding
instance of mplsOamIdMeEntry configured to monitor the instance of mplsOamIdMeEntry[MPLS-OAM-ID-STD-MIB] configured to
MPLS-TP path associated with the BFD session. monitor the MPLS-TP path associated with the BFD session.
6. Usage of existing object bfdSessType: 6. Usage of existing object bfdSessType:
Additionally existing object "bfdSessType" in the base MIB can be Additionally existing object "bfdSessType" in the BFD base MIB
used with the already defined value multiHopOutOfBandSignaling(3) [BFD-STD-MIB] can be used with the already defined value
to specify an OOB (Out of band) mechanism [E.g. LSP Ping] for multiHopOutOfBandSignaling(3) to specify an OOB (Out of band)
bootstrapping the BFD session. mechanism [E.g. LSP Ping] for bootstrapping the BFD session.
5.2. Example of BFD session configuration 5.2. Example of BFD session configuration
This section provides an example of BFD session configuration This section provides an example of BFD session configuration
for an MPLS and MPLS-TP TE tunnel. This example is only meant for an MPLS and MPLS-TP TE tunnel. This example is only meant
to enable an understanding of the proposed extension and does not to enable an understanding of the proposed extension and does not
illustrate every permutation of the MIB. illustrate every permutation of the MIB.
5.2.1 Example of BFD Session configuration for MPLS TE tunnel 5.2.1 Example of BFD Session configuration for MPLS TE tunnel
This section provides an example BFD session configuration This section provides an example BFD session configuration
for an MPLS TE tunnel. This example is only meant to enable for an MPLS TE tunnel.
an understanding of the proposed extension and does not
illustrate every permutation of the MIB.
The following denotes the configured tunnel "head" entry: The following denotes the configured tunnel "head" entry:
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 100, mplsTunnelIndex = 100,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
mplsTunnelIngressLSRId = 192.0.2.1, mplsTunnelIngressLSRId = 192.0.2.1,
mplsTunnelEgressLSRId = 192.0.2.3, mplsTunnelEgressLSRId = 192.0.2.3,
mplsTunnelName = "Tunnel", mplsTunnelName = "Tunnel",
skipping to change at page 9, line 25 skipping to change at page 9, line 28
-- Indicates that the BFD session is to monitor -- Indicates that the BFD session is to monitor
-- a ME of an MPLS-TP TE tunnel -- a ME of an MPLS-TP TE tunnel
bfdMplsSessMapType = mep(6), bfdMplsSessMapType = mep(6),
bfdMplsSessMapPointer bfdMplsSessMapPointer
= mplsOamIdMeName.1.1.1, = mplsOamIdMeName.1.1.1,
bfdSessRowStatus = createAndGo bfdSessRowStatus = createAndGo
} }
Similarly BFD session would be configured on the tail-end of Similarly BFD session would be configured on the tail-end of
the tunnel. Creating the above row will trigger the bootstrapping the tunnel and creating the above row will trigger
of the session using LSP Ping and its subsequent establishment the bootstrapping of the session using LSP Ping and its subsequent
over the path by de-multiplexing of the control packets using establishment over the path by de-multiplexing of the control
the BFD session discriminators. packets using the BFD session discriminators.
5.3. BFD objects for session performance counters 5.3. BFD objects for session performance counters
BFD-STD-MIB defines BFD Session Performance Table BFD-STD-MIB defines BFD Session Performance Table
(bfdSessionPerfTable), for collecting per-session BFD performance (bfdSessionPerfTable), for collecting per-session BFD performance
counters, as an extension to the bfdSessionTable. counters, as an extension to the bfdSessionTable.
The bfdSessionPerfTable is extended with the performance counters The bfdSessionPerfTable is extended with the performance counters
to collect Mis-connectivity Defect, Loss of Continuity Defect to collect Mis-connectivity Defect, Loss of Continuity Defect
and RDI (Remote Defect Indication) counters. and RDI (Remote Defect Indication) counters.
1. bfdMplsSessPerfMisDefCount - Mis-connectivity defect count 1. bfdMplsSessPerfMisDefCount - Mis-connectivity defect count
for this BFD session. for this BFD session.
2. bfdMplsSessPerfLocDefCount - Loss of continuity defect count for 2. bfdMplsSessPerfLocDefCount - Loss of continuity defect count for
this BFD session. this BFD session.
3. bfdMplsSessPerfRdiInCount - Total number of RDI messages 3. bfdMplsSessPerfRdiInCount - Total number of RDI messages
received for this BFD session. received for this BFD session.
4. bfdMplsSessPerfRdiOutCount - Total number of RDI messages sent 4. bfdMplsSessPerfRdiOutCount - Total number of RDI messages sent
for this BFD session. for this BFD session.
5.4. Notification Objects
To be added in the next version of this document.
6. BFD MPLS-MPLS-TP MIB Module Definition 6. BFD-EXT-STD-MIB Module Definition
BFD-EXT-STD-MIB DEFINITIONS ::= BEGIN BFD-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, mib-2,
Counter32, zeroDotZero Counter32, zeroDotZero
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
RowPointer,TruthValue,TEXTUAL-CONVENTION RowPointer,TruthValue,TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
bfdSessIndex bfdSessIndex
FROM BFD-STD-MIB; FROM BFD-STD-MIB;
bfdMplsMib MODULE-IDENTITY bfdMplsMib MODULE-IDENTITY
LAST-UPDATED "201306260000Z" -- June 26 2013 LAST-UPDATED "201312260000Z" -- December 26 2013
ORGANIZATION "IETF Bidirectional Forwarding Detection ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" "
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
skipping to change at page 10, line 46 skipping to change at page 10, line 46
350 Holger Way, 350 Holger Way,
San Jose, CA 95134, USA San Jose, CA 95134, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Redeem Software Redeem Software
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Email: tnadeau@lucidvision.com"
10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net"
DESCRIPTION DESCRIPTION
" Copyright (c) 2013 IETF Trust and the persons identified " Copyright (c) 2013 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module is an initial version containing objects This MIB module is an initial version containing objects
to provide a proactive mechanism to detect faults using to provide a proactive mechanism to detect faults using
BFD for MPLS and MPLS-TP networks" BFD for MPLS and MPLS-TP networks."
REVISION "201306260000Z" -- June 26 2013 REVISION "201312260000Z" -- December 26 2013
DESCRIPTION DESCRIPTION
" Initial version published as RFC xxx " -- RFC Ed.: RFC-editor pls fill in xxxx
-- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } -- XXX to be replaced with correct value ::= { mib-2 XXX } -- XXX to be replaced with correct value
-- RFC Ed.: assigned by IANA -- RFC Ed.: assigned by IANA
-- ------------------------------------------------------------ -- ------------------------------------------------------------
-- groups in the MIB -- groups in the MIB
-- ------------------------------------------------------------ -- ------------------------------------------------------------
bfdMplsObjects OBJECT IDENTIFIER ::= { bfdMplsMib 0 } bfdMplsObjects OBJECT IDENTIFIER ::= { bfdMplsMib 0 }
bfdMplsConformance OBJECT IDENTIFIER ::= { bfdMplsMib 1 } bfdMplsConformance OBJECT IDENTIFIER ::= { bfdMplsMib 1 }
skipping to change at page 12, line 4 skipping to change at page 11, line 45
DefectActionTC ::= TEXTUAL-CONVENTION DefectActionTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The action to be taken when the mis-connectivity/loss of "The action to be taken when the mis-connectivity/loss of
connectivity defect occurs in the MPLS or MPLS-TP connectivity defect occurs in the MPLS or MPLS-TP
path associated to the session" path associated to the session"
SYNTAX INTEGER { SYNTAX INTEGER {
alarmOnly(1), -- Alarm only alarmOnly(1), -- Alarm only
alarmAndBlockData(2) -- Alarm and block the data alarmAndBlockData(2) -- Alarm and block the data
} }
-- ------------------------------------------------------------------ -- ------------------------------------------------------------------
-- BFD session table extensions for BFD on MPLS and MPLS-TP -- BFD session table extensions for MPLS and MPLS-TP BFD sessions
-- ------------------------------------------------------------------ -- ------------------------------------------------------------------
-- bfdMplsSessTable - bfdSessTable Extension -- bfdMplsSessTable - bfdSessTable Extension
bfdMplsSessTable OBJECT-TYPE bfdMplsSessTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdMplsSessEntry SYNTAX SEQUENCE OF BfdMplsSessEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is an extension to the bfdSessTable for "This table is an extension to the bfdSessTable for
configuring BFD sessions for MPLS or MPLS-TP paths." configuring BFD sessions for MPLS or MPLS-TP paths."
::= { bfdMplsObjects 1 } ::= { bfdMplsObjects 1 }
bfdMplsSessEntry OBJECT-TYPE bfdMplsSessEntry OBJECT-TYPE
SYNTAX BfdMplsSessEntry SYNTAX BfdMplsSessEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 13, line 37 skipping to change at page 13, line 26
DEFVAL { cc } DEFVAL { cc }
::= { bfdMplsSessEntry 2 } ::= { bfdMplsSessEntry 2 }
bfdMplsSessTmrNegotiate OBJECT-TYPE bfdMplsSessTmrNegotiate OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies if timer negotiation is required for "This object specifies if timer negotiation is required for
the BFD session. When set to false, timer negotiation is the BFD session. When set to false, timer negotiation is
disabled" disabled."
DEFVAL { true } DEFVAL { true }
::= { bfdMplsSessEntry 3 } ::= { bfdMplsSessEntry 3 }
bfdMplsSessMapType OBJECT-TYPE bfdMplsSessMapType OBJECT-TYPE
SYNTAX SessionMapTypeTC SYNTAX SessionMapTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the type of path being monitored "This object indicates the type of path being monitored
by this BFD session entry." by this BFD session entry."
skipping to change at page 14, line 43 skipping to change at page 14, line 26
If this object points to a conceptual row instance If this object points to a conceptual row instance
in a table consistent with bfdMplsSessMapType but this in a table consistent with bfdMplsSessMapType but this
instance does not currently exist then no valid instance does not currently exist then no valid
path is associated with this session entry. path is associated with this session entry.
If this object contains zeroDotZero then no valid path is If this object contains zeroDotZero then no valid path is
associated with this BFD session entry till it is associated with this BFD session entry till it is
populated with a valid pointer consistent with populated with a valid pointer consistent with
the value of bfdMplsSessMapType as explained above." the value of bfdMplsSessMapType as explained above."
DEFVAL { zeroDotZero } REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE)Management Information Base (MIB),
[RFC3812].
2. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB),
[RFC3813].
3. Pseudowire (PW) Management Information Base (MIB,
[RFC5601].
4. MPLS-TP Operations, Administration, and Management
(OAM) Identifiers Management Information Base (MIB), ID
draft-ietf-mpls-tp-oam-id-mib-04, December 2013."
DEFVAL { zeroDotZero }
::= { bfdMplsSessEntry 5 } ::= { bfdMplsSessEntry 5 }
bfdMplsSessMisConnectivityDefectAction OBJECT-TYPE bfdMplsSessMisConnectivityDefectAction OBJECT-TYPE
SYNTAX DefectActionTC SYNTAX DefectActionTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the action to be taken when "This object indicates the action to be taken when
the mis-connectivity defect is detected on the mis-connectivity defect is detected on
this BFD session." this BFD session."
skipping to change at page 17, line 26 skipping to change at page 17, line 11
support for the BFD-EXT-STD-MIB module. " support for the BFD-EXT-STD-MIB module. "
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
bfdSessionExtGroup, bfdSessionExtGroup,
bfdSessionExtPerfGroup bfdSessionExtPerfGroup
} }
::= { bfdMplsCompliances 1 } ::= { bfdMplsCompliances 1 }
-- Compliance requirement for read-only implementations.
bfdMplsModuleReadOnlyCompliance MODULE-COMPLIANCE bfdMplsModuleReadOnlyCompliance 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-EXT-STD-MIB. Such devices provide read-only support for BFD-EXT-STD-MIB. Such devices
can then be monitored but cannot be configured using can then be monitored but cannot be configured using
this MIB module." this MIB module."
MODULE -- This module. MODULE -- This module.
skipping to change at page 21, line 14 skipping to change at page 20, line 48
Detection (BFD)", RFC 5880, June 2010. Detection (BFD)", RFC 5880, June 2010.
[BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD) for IPv4 and IPv6 (Single Hop)", Detection (BFD) for IPv4 and IPv6 (Single Hop)",
RFC 5881, June 2010. RFC 5881, June 2010.
[BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD) for Multihop Paths", RFC 5883, Detection (BFD) for Multihop Paths", RFC 5883,
June 2010. June 2010.
[BFD-MPLS] Aggarwal, R. et.al., "Bidirectional Forwarding [RFC5884] Aggarwal, R. et.al., "Bidirectional Forwarding
Detection (BFD) for MPLS Label Switched Paths (LSPs)", Detection (BFD) for MPLS Label Switched Paths (LSPs)",
RFC 5884, June 2010 RFC 5884, June 2010
[RFC6428] Allan, D., Swallow, G., Drake, J., "Proactive [RFC6428] Allan, D., Swallow, G., Drake, J., "Proactive
Connectivity Verification, Continuity Check and Remote Connectivity Verification, Continuity Check and Remote
Defect indication for MPLS Transport Profile", RFC Defect indication for MPLS Transport Profile", RFC
6428, November 2011. 6428, November 2011.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
skipping to change at page 21, line 41 skipping to change at page 21, line 28
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
9.2 Informative References 9.2 Informative References
[RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction
and Applicability Statement for Internet Standard and Applicability Statement for Internet Standard
Management Framework", RFC 3410, December 2002. Management Framework", RFC 3410, December 2002.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB)", RFC 3812, June
2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching
(LSR) Router Management Information Base (MIB)",
RFC 3813, June 2004.
[RFC5601] T. Nadeau, Ed., D. Zelig, Ed., "Pseudowire (PW)
Management Information Base (MIB)", RFC 5601,
July 2009
[BFD-STD-MIB] T. Nadeau, Z. Ali, N. Akiya "BFD Management
Information Base", ID draft-ietf-bfd-mib-16,
November 2013.
[MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath,
Thomas D. Nadeau, Sami Boutros, Ping Pan,
"MPLS-TP Operations, Administration, and
Management (OAM) Identifiers Management
Information Base (MIB)", ID
draft-ietf-mpls-tp-oam-id-mib-04,
December 2013.
10. Acknowledgments 10. Acknowledgments
The authors would like to thank Jeffrey Haas, Mukund Mani, The authors would like to thank Jeffrey Haas, Mukund Mani,
Lavanya Srivatsa, Muly Ilan and John Salloway for their valuable Lavanya Srivatsa, Muly Ilan and John Salloway for their valuable
comments. comments.
11. Authors' Addresses 11. Authors' Addresses
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
skipping to change at page 22, line 20 skipping to change at page 22, line 31
350 Holger Way, 350 Holger Way,
San Jose, CA 95134, USA San Jose, CA 95134, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Redeem Software Redeem Software
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Email: tnadeau@lucidvision.com
10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net
 End of changes. 49 change blocks. 
74 lines changed or deleted 105 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/