draft-ietf-mpls-tp-linear-protection-mib-12.txt   rfc8150.txt 
MPLS Working Group Kingston Smiler Selvaraj Internet Engineering Task Force (IETF) S. Kingston Smiler
Internet-Draft IpInfusion Request for Comments: 8150 IP Infusion
Intended status: Standards Track Venkatesan Mahalingam Category: Standards Track M. Venkatesan
Expires: August 21, 2017 Dell Inc. ISSN: 2070-1721 Dell Technologies
Daniel King D. King
Old Dog Consulting Old Dog Consulting
Sam Aldrin S. Aldrin
Google, Inc. Google, Inc.
Jeong-dong Ryoo J. Ryoo
ETRI ETRI
February 17, 2017 April 2017
MPLS Transport Profile Linear Protection MIB MPLS Transport Profile Linear Protection MIB
draft-ietf-mpls-tp-linear-protection-mib-12
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines for use with network management protocols. In particular, it defines
objects for managing Multiprotocol Label Switching-Transport Profile objects for managing Multiprotocol Label Switching - Transport
(MPLS-TP) Linear Protection. Profile (MPLS-TP) linear protection.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on August 21, 2017. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8150.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction ....................................................3
2. The Internet-Standard Management Framework . . . . . . . . . 3 2. The Internet-Standard Management Framework ......................3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions .....................................................3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview ........................................................4
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module .....................................4
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 5.1. Textual Conventions ........................................4
5.2. The MPLS-TP Linear Protection Subtree . . . . . . . . . . 4 5.2. The MPLS-TP Linear Protection Switching Subtree ............4
5.3. The Notifications Subtree . . . . . . . . . . . . . . . . 4 5.3. The Notifications Subtree ..................................5
5.4. The Table Structures . . . . . . . . . . . . . . . . . . 5 5.4. The Table Structures .......................................5
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 6. Relationship to Other MIB Modules ...............................7
6.1. Relationship to the MPLS OAM Identifiers MIB Module . . . 6 6.1. Relationship to the MPLS OAM Identifiers MIB Module ........7
7. Example of Protection Switching Configuration . . . . . . . . 6 7. Example of Protection Switching Configuration ...................7
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Definitions .....................................................9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 38 9. Security Considerations ........................................43
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 10. IANA Considerations ...........................................44
11. Contributing Authors . . . . . . . . . . . . . . . . . . . . 40 11. References ....................................................45
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 40 11.1. Normative References .....................................45
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 11.2. Informative References ...................................47
13.1. Normative References . . . . . . . . . . . . . . . . . . 40 Acknowledgments ...................................................47
13.2. Informative References . . . . . . . . . . . . . . . . . 42 Contributors ......................................................47
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses ................................................48
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines for use with network management protocols. In particular, it defines
objects for managing Multiprotocol Label Switching-Transport Profile objects for managing Multiprotocol Label Switching - Transport
(MPLS-TP) Linear Protection. Profile (MPLS-TP) linear protection.
This MIB module should be used for configuring and managing the MPLS- This MIB module should be used for configuring and managing MPLS-TP
TP linear protection for MPLS-TP Label Switched Paths (LSPs). linear protection for MPLS-TP Label Switched Paths (LSPs).
At the time of writing, Simple Network Management Protocol (SNMP) SET At the time of this writing, Simple Network Management Protocol
is no longer recommended as a way to configure Multiprotocol Label (SNMP) SET is no longer recommended as a way to configure MPLS
Switching (MPLS) networks as was described in RFC 3812 [RFC3812]. networks as described in RFC 3812 [RFC3812]. However, since the MIB
However, since the MIB module specified in this document is intended module specified in this document is intended to work in parallel
to work in parallel with the MIB module for MPLS specified in with the MIB module for MPLS specified in [RFC3812] and the MIB
[RFC3812] and the MIB module for MPLS-TP Operations, Administration, module for MPLS-TP Operations, Administration, and Maintenance (OAM)
and Maintenance (OAM) identifiers in RFC 7697 [RFC7697], certain identifiers in RFC 7697 [RFC7697], certain objects defined here are
objects defined here are specified with MAX-ACCESS of read-write or specified with a MAX-ACCESS clause of read-write or read-create so
read-create so that specifications of the base tables in [RFC3812] that specifications of the base tables in [RFC3812] and [RFC7697] and
and [RFC7697] and the new MIB module in this document are consistent. the new MIB module in this document are consistent.
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
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 MIB. MIB objects are generally accessed through the SNMP. the Management Information Base or MIB. MIB objects are generally
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].
3. Conventions 3. Conventions
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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in BCP 14, RFC 2119 "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. BCP 14, RFC 2119 [RFC2119].
4. Overview 4. Overview
RFC 6378 [RFC6378] defines the protocol to provide a linear RFC 6378 [RFC6378] defines the protocol to provide a linear
protection switching mechanism for MPLS-TP for a point-to-point LSP protection switching mechanism for MPLS-TP for a point-to-point LSP
within the protection domain bounded by the end points of the LSP. within the protection domain bounded by the endpoints of the LSP.
RFC 7271 [RFC7271] describes alternative mechanisms to perform some RFC 7271 [RFC7271] describes alternative mechanisms to perform some
of the functions defined in [RFC6378], and also defines additional of the functions defined in [RFC6378] and also defines additional
mechanisms, in order to provide operator control and experience that mechanisms to provide operator control and experience that more
more closely models the behavior of linear protection seen in other closely model the behavior of linear protection seen in other
transport networks. Two modes are defined for MPLS-TP linear transport networks. Two modes are defined for MPLS-TP linear
protection switching: Protection State Coordination (PSC) mode and protection switching: the Protection State Coordination (PSC) mode
Automatic Protection Switching (APS) mode as specified in [RFC6378] and the Automatic Protection Switching (APS) mode, as specified in
and [RFC7271], respectively. The detailed protocol specification of [RFC6378] and [RFC7271], respectively. The detailed protocol
MPLS transport profile linear protection is described in [RFC6378] specification of MPLS-TP linear protection is described in [RFC6378]
and [RFC7271]. and [RFC7271].
This document specifies a MIB module for the Label Edge Router (LER) This document specifies a MIB module for Label Edge Routers (LERs)
that supports MPLS-TP linear protection as described in [RFC6378] and that support MPLS-TP linear protection as described in [RFC6378] and
[RFC7271]. Objects defined in the document are generally applied to [RFC7271]. Objects defined in this document are generally applied to
both PSC and APS modes. If an object is valid for a particular mode both the PSC mode and the APS mode. If an object is valid for a
only, it is noted in the description for the object. particular mode only, it is noted in the description for the object.
5. Structure of the MIB Module 5. Structure of the MIB Module
5.1. Textual Conventions 5.1. Textual Conventions
The following new textual conventions are defined in this document: The following new textual conventions are defined in this document:
o MplsLpsReq: This textual convention describes an object that o MplsLpsReq: This textual convention describes an object that
stores the PSC Request field of the PSC control packet. stores the PSC Request field of the PSC control packet.
o MplsLpsFpathPath: This textual convention describes an object that o MplsLpsFpathPath: This textual convention describes an object that
stores the Fault Path (FPath) field and Data Path (Path) field of stores the Fault Path (FPath) field and Data Path (Path) field of
the PSC control packet. the PSC control packet.
o MplsLpsCommand: This textual convention describes an object that o MplsLpsCommand: This textual convention describes an object that
allows a user to perform any action over a protection domain. allows a user to perform any action over a protection domain.
o MplsLpsState: This textual convention describes an object that o MplsLpsState: This textual convention describes an object that
stores the current state of the PSC state machine. stores the current state of the PSC state machine.
5.2. The MPLS-TP Linear Protection Subtree 5.2. The MPLS-TP Linear Protection Switching Subtree
MPLS-LPS-MIB is the MIB module defined in this document, and it is MPLS-LPS-MIB is the MIB module defined in this document. It is
put under mplsStdMIB [RFC3811]. rooted under the mplsStdMIB subtree per [RFC3811]. "LPS" as used in
this document means "Linear Protection Switching".
5.3. The Notifications Subtree 5.3. The Notifications Subtree
Notifications are defined to inform the management station about Notifications are defined to inform the management station about
switchover, provisioning mismatches, and protocol failures of the switchovers, provisioning mismatches, and protocol failures of the
linear protection domain. The following notifications are defined linear protection domain. The following notifications are defined
for this purpose: for this purpose:
o The notification, mplsLpsEventSwitchover is to inform the o The notification mplsLpsEventSwitchover informs the management
management station about the switchover of the active path. station about the switchover of the active path.
o The notification, mplsLpsEventRevertiveMismatch is to inform the o The notification mplsLpsEventRevertiveMismatch informs the
management station about the provisioning mismatch in the management station about a provisioning mismatch in the revertive
revertive mode across the end point of the protection domain. mode across the endpoint of the protection domain.
o The notification, mplsLpsEventProtecTypeMismatch is to inform the o The notification mplsLpsEventProtecTypeMismatch informs the
management station about the provisioning mismatch in protection management station about a provisioning mismatch in the protection
type, representing both bridge and switching types, across the end type, representing both the bridge type and the switching type,
point of the protection domain. across the endpoint of the protection domain.
o The notification, mplsLpsEventCapabilitiesMismatch is to inform o The notification mplsLpsEventCapabilitiesMismatch informs the
the management station about the provisioning mismatch in management station about a provisioning mismatch in Capabilities
Capabilities TLVs across the end point of the protection domain. TLVs across the endpoint of the protection domain.
o The notification, mplsLpsEventPathConfigMismatch is to inform the o The notification mplsLpsEventPathConfigMismatch informs the
management station about the provisioning mismatch in the management station about a provisioning mismatch in the protection
protection path configuration for PSC communication. path configuration for PSC communication.
o The notification, mplsLpsEventFopNoResponse is to inform the o The notification mplsLpsEventFopNoResponse informs the management
management station about the failure of protocol due to a lack of station that protocol failure has occurred due to a lack of
response to a traffic switchover request in 50 ms. response to a traffic switchover request in 50 ms.
o The notification, mplsLpsEventFopTimeout is to inform the o The notification mplsLpsEventFopTimeout informs the management
management station about the failure of protocol due to no station that protocol failure has occurred because no protocol
protocol message received during at least 3.5 times the long PSC message was received during at least 3.5 times the long PSC
message interval. message interval [RFC7271].
5.4. The Table Structures 5.4. The Table Structures
The MPLS-TP linear protection MIB module has four tables. The tables The MPLS-TP linear protection MIB module has four tables. The tables
are as follows are as follows:
o mplsLpsConfigTable o mplsLpsConfigTable
This table is used to configure MPLS-TP linear protection domains. This table is used to configure MPLS-TP linear protection domains.
An MPLS-TP linear protection domain (or a protection domain) is An MPLS-TP linear protection domain (or a protection domain) is
identified by mplsLpsConfigDomainIndex. A protection domain identified by mplsLpsConfigDomainIndex. A protection domain
consists of two LERs and the working and protection paths that consists of two LERs, as well as the working path and protection
connect the two LERs. The objects in this table are used to path that connect the two LERs. The objects in this table are
configure properties that are specific to the protection domain. used to configure properties that are specific to the protection
Two Maintenance Entities (MEs) MUST be defined for each protection domain. Two Maintenance Entities (MEs) MUST be defined for each
domain: one for the working path and the other for the protection protection domain: one for the working path and the other for the
path. Therefore, two entries of the mplsLpsMeConfigTable, which protection path. Therefore, two entries in the
is for configuring the MEs used in protection switching, are mplsLpsMeConfigTable, which is for configuring the MEs used in
associated to one entry in this table. protection switching, are associated to one entry in this table.
o mplsLpsStatusTable o mplsLpsStatusTable
This table provides the current status information of MPLS-TP This table provides the current status information of MPLS-TP
linear protection domains that have been configured on the system. linear protection domains that have been configured on the system.
The entries of mplsLpsStatusTable have an AUGMENTS relationship The entries in the mplsLpsStatusTable have an AUGMENTS
with the entries of mplsLpsConfigTable. When a protection domain relationship with the entries in the mplsLpsConfigTable. When a
is configured or deleted in the mplsLpsConfigTable, then the protection domain is configured or deleted in the
corresponding row of that session in the mplsLpsStatusTable is, mplsLpsConfigTable, then the corresponding row of that session in
respectively, automatically created or deleted. the mplsLpsStatusTable is automatically created or deleted,
respectively.
o mplsLpsMeConfigTable o mplsLpsMeConfigTable
This table is used to associate MEs to the protection domain. This table is used to associate MEs to the protection domain.
Each protection domain requires two MEs. One entry in the Each protection domain requires two MEs. One entry in the
mplsLpsConfigTable is associated with two entries in this table: mplsLpsConfigTable is associated with two entries in this table:
one for the working path and the other for the protection path of one for the working path and the other for the protection path of
the protection domain. The mplsLpsMeConfigPath object in this the protection domain. The mplsLpsMeConfigPath object in this
table indicates that the path is either working or protection. table indicates that the path is either the working path or the
The ME is identified by mplsOamIdMegIndex, mplsOamIdMeIndex and protection path. The ME is identified by mplsOamIdMegIndex,
mplsOamIdMeMpIndex, which are the same index values as the entry mplsOamIdMeIndex, and mplsOamIdMeMpIndex, which are the same index
in the mplsOamIdMeTable defined in [RFC7697]. The relationship values as the entry in the mplsOamIdMeTable defined in [RFC7697].
with the mplsOamIdMeTable is described in Section 6.1. The relationship to the mplsOamIdMeTable is described in
Section 6.1.
o mplsLpsMeStatusTable o mplsLpsMeStatusTable
This table provides the current information about protection This table provides current information about the protection
status of MEs that have been configured on the system. When an ME status of MEs that have been configured on the system. When an ME
configured or deleted in the mplsLpsMeConfigTable, then the is configured or deleted in the mplsLpsMeConfigTable, then the
corresponding row of that session in the mplsLpsMeStatusTable is, corresponding row of that session in the mplsLpsMeStatusTable is
respectively, automatically created or deleted. automatically created or deleted, respectively.
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
6.1. Relationship to the MPLS OAM Identifiers MIB Module 6.1. Relationship to the MPLS OAM Identifiers MIB Module
Entries in the mplsOamIdMeTable [RFC7697] are extended by entries in Entries in the mplsOamIdMeTable [RFC7697] are extended by entries in
the mplsLpsMeConfigTable. Note that the nature of the 'extends' the mplsLpsMeConfigTable. Note that the nature of the "extends"
relationship is a sparse augmentation so that the entry in the relationship is a sparse augmentation so that the entry in the
mplsLpsMeConfigTable has the same index values as the entry in the mplsLpsMeConfigTable has the same index values as the entry in the
mplsOamIdMeTable. Each time that an entry is created in the mplsOamIdMeTable. Each time that an entry is created in the
mplsOamIdMeTable for which the LER supports MPLS-TP linear mplsOamIdMeTable for which the LER supports MPLS-TP linear
protection, a row is created automatically in the protection, a row is created automatically in the
mplsLpsMeConfigTable. mplsLpsMeConfigTable.
When a point-to-point transport path needs to be monitored, one ME is When a point-to-point transport path needs to be monitored, one ME is
needed for the path and one entry in the mplsOamIdMeTable will be needed for the path and one entry in the mplsOamIdMeTable will be
created. But, the ME entry in the mplsOamIdMeTable may or may not created. But the ME entry in the mplsOamIdMeTable may or may not
participate in protection switching. If an ME participates in participate in protection switching. If an ME participates in
protection switching, an entry in mplsLpsMeConfigTable MUST be protection switching, an entry in the mplsLpsMeConfigTable MUST be
created, and the objects in the entry indicates which protection created, and the objects in the entry indicate which protection
domain this ME belongs to and whether this ME is for either working domain this ME belongs to and whether this ME is for the working path
path or protection path. If the ME does not participate in or the protection path. If the ME does not participate in protection
protection switching, an entry in mplsLpsMeConfigTable does not need switching, an entry in the mplsLpsMeConfigTable does not need to be
to be created. created.
7. Example of Protection Switching Configuration 7. Example of Protection Switching Configuration
This example considers the protection domain configuration on an LER This example considers the protection domain configuration on an LER
to provide protection for a co-routed bidirectional MPLS tunnel. For to provide protection for a co-routed bidirectional MPLS tunnel. For
the working and protection paths of the protection domain, two the working path and protection path of the protection domain, two
Maintenance Entity Groups (MEGs) need to be configured and each MEG Maintenance Entity Groups (MEGs) need to be configured, and each MEG
contains one ME for a point-to-point transport path. For more contains one ME for a point-to-point transport path. For more
information on mplsOamIdMegTable and mplsOamIdMeTable, see [RFC7697]. information on the mplsOamIdMegTable and the mplsOamIdMeTable, see
[RFC7697].
Although the example described in this section shows a way to Although the example described in this section shows a way to
configure linear protection for MPLS-TP tunnels, this also indicates configure linear protection for MPLS-TP tunnels, this also indicates
how the MIB values would be returned if they had been configured by how the MIB values would be returned if they had been configured by
alternative means. alternative means.
The following table configures a protection domain. The following table configures a protection domain.
In mplsLpsConfigTable: In the mplsLpsConfigTable:
mplsLpsConfigEntry ::= SEQUENCE mplsLpsConfigEntry ::= SEQUENCE
{ {
-- Protection Domain index (Index to the table) -- Protection domain index (index to the table)
mplsLpsConfigDomainIndex = 3, mplsLpsConfigDomainIndex = 3,
-- Protection Domain name -- Protection domain name
mplsLpsConfigDomainName = "LPDomain3", mplsLpsConfigDomainName = "LPDomain3",
mplsLpsConfigMode = psc (1), mplsLpsConfigMode = psc(1),
mplsLpsConfigProtectionType = oneColonOneBidirectional (2), mplsLpsConfigProtectionType = oneColonOneBidirectional(2),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsLpsConfigRowStatus = createAndGo (4) mplsLpsConfigRowStatus = createAndGo(4)
} }
The following table associates the MEs with the protection domain. The following table associates the MEs with the protection domain.
In mplsLpsMeConfigTable: In the mplsLpsMeConfigTable:
MplsLpsMeConfigEntry ::= SEQUENCE MplsLpsMeConfigEntry ::= SEQUENCE
{ {
-- MEG index (Index to the table) -- MEG index (index to the table)
mplsOamIdMegIndex = 1, mplsOamIdMegIndex = 1,
-- ME index (Index to the table) -- ME index (index to the table)
mplsOamIdMeIndex = 1, mplsOamIdMeIndex = 1,
-- MP index (Index to the table) -- Maintenance Point (MP) index (index to the table)
mplsOamIdMeMpIndex = 1, mplsOamIdMeMpIndex = 1,
-- Protection Domain this ME belongs to -- Protection domain this ME belongs to
mplsLpsMeConfigDomain = 3, mplsLpsMeConfigDomain = 3,
-- Configuration state -- Configuration state
mplsLpsMeConfigPath = working(1) mplsLpsMeConfigPath = working(1)
} }
{ {
-- MEG index (Index to the table) -- MEG index (index to the table)
mplsOamIdMegIndex = 2, mplsOamIdMegIndex = 2,
-- ME index (Index to the table) -- ME index (index to the table)
mplsOamIdMeIndex = 2, mplsOamIdMeIndex = 2,
-- MP index (Index to the table) -- MP index (index to the table)
mplsOamIdMeMpIndex = 2, mplsOamIdMeMpIndex = 2,
-- Protection Domain this ME belongs to -- Protection domain this ME belongs to
mplsLpsMeConfigDomain = 3, mplsLpsMeConfigDomain = 3,
-- Configuration state -- Configuration state
mplsLpsMeConfigPath = protection(2) mplsLpsMeConfigPath = protection(2)
} }
8. Definitions 8. Definitions
This MIB module makes reference to the following documents: This MIB module makes reference to the following documents:
[RFC2578], [RFC2579], [RFC2580], [RFC3289], [RFC3411], [RFC3811], [RFC2578], [RFC2579], [RFC2580], [RFC3289], [RFC3411], [RFC3811],
[RFC6378], [RFC7271], [RFC7697], [G8121], and [G8151]. [RFC6378], [RFC7271], [RFC7697], [G8121], and [G8151].
skipping to change at page 8, line 37 skipping to change at page 9, line 37
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB -- RFC 3289 FROM DIFFSERV-MIB -- RFC 3289
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC 3811 FROM MPLS-TC-STD-MIB -- RFC 3811
mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex
FROM MPLS-OAM-ID-STD-MIB; -- RFC 7697 FROM MPLS-OAM-ID-STD-MIB; -- RFC 7697
mplsLpsMIB MODULE-IDENTITY mplsLpsMIB MODULE-IDENTITY
LAST-UPDATED "201702170000Z" -- February 17, 2017 LAST-UPDATED "201704040000Z" -- April 4, 2017
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Kingston Smiler Selvaraj Kingston Smiler Selvaraj
IP Infusion IP Infusion
RMZ Centennial RMZ Centennial
Mahadevapura Post Mahadevapura Post
Bangalore - 560048 India Bangalore 560048
EMail: kingstonsmiler@gmail.com India
Email: kingstonsmiler@gmail.com
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc. Dell Technologies
5450 Great America Parkway, 5450 Great America Parkway
Santa Clara, CA 95054, USA Santa Clara, CA 95054
United States of America
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK United Kingdom
Email:daniel@olddog.co.uk Email: daniel@olddog.co.uk
Sam Aldrin Sam Aldrin
Google, Inc. Google, Inc.
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, CA Mountain View, CA 94043
USA United States of America
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Jeong-dong Ryoo Jeong-dong Ryoo
ETRI ETRI
218 Gajeong-ro 218 Gajeong-ro
Yuseong-gu, Daejeon 34129 Yuseong-gu, Daejeon 34129
South Korea South Korea
Email:ryoo@etri.re.kr Email: ryoo@etri.re.kr
" "
DESCRIPTION DESCRIPTION
"This management information module supports the "This MIB module supports the configuration and management of
configuration and management of MPLS-TP linear MPLS-TP linear protection domains.
protection domains. "
Copyright (c) 2017 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION REVISION
"201702170000Z" -- February 17, 2017 "201704040000Z" -- April 4, 2017
DESCRIPTION DESCRIPTION
"MPLS-TP Protection Switching Domain objects for LSP "MPLS-TP protection domain objects for
MEPs" LSP MEG End Points (MEPs)."
::= { mplsStdMIB xxx } -- xxx to be replaced with
-- correct value
-- Top level components of this MIB module. ::= { mplsStdMIB 22 }
-- Top-level components of this MIB module.
-- Notifications -- Notifications
mplsLpsNotifications mplsLpsNotifications
OBJECT IDENTIFIER ::= { mplsLpsMIB 0 } OBJECT IDENTIFIER ::= { mplsLpsMIB 0 }
-- tables, scalars -- Tables, scalars
mplsLpsObjects mplsLpsObjects
OBJECT IDENTIFIER ::= { mplsLpsMIB 1 } OBJECT IDENTIFIER ::= { mplsLpsMIB 1 }
-- conformance -- Conformance
mplsLpsConformance mplsLpsConformance
OBJECT IDENTIFIER ::= { mplsLpsMIB 2 } OBJECT IDENTIFIER ::= { mplsLpsMIB 2 }
MplsLpsReq ::= TEXTUAL-CONVENTION MplsLpsReq ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Textual Convention describes an object that stores "This textual convention describes an object that stores
the PSC Request field of the PSC control packet. The values the PSC Request field of the PSC control packet. The values
are as follows: are as follows:
noRequest noRequest
No Request No Request
doNotRevert doNotRevert
Do Not Revert Do-not-Revert
reverseRequest reverseRequest
Reverse Request Reverse Request
exercise exercise
Exercise Exercise
waitToRestore waitToRestore
Wait-to-Restore Wait-to-Restore
skipping to change at page 10, line 31 skipping to change at page 12, line 4
Wait-to-Restore Wait-to-Restore
manualSwitch manualSwitch
Manual Switch Manual Switch
signalDegrade signalDegrade
Signal Degrade (SD) Signal Degrade (SD)
signalFail signalFail
Signal Fail (SF) Signal Fail (SF)
forcedSwitch forcedSwitch
Forced Switch Forced Switch
lockoutOfProtection lockoutOfProtection
Lockout of Protection" Lockout of Protection."
REFERENCE REFERENCE
"Section 4.2.2 of RFC6378 and Section 8 of RFC7271" "Section 4.2.2 of RFC 6378 and Section 8 of RFC 7271"
SYNTAX INTEGER { SYNTAX INTEGER {
noRequest (0), noRequest(0),
doNotRevert (1), doNotRevert(1),
reverseRequest (2), reverseRequest(2),
exercise (3), exercise(3),
waitToRestore (4), waitToRestore(4),
manualSwitch (5), manualSwitch(5),
signalDegrade (7), signalDegrade(7),
signalFail (10), signalFail(10),
forcedSwitch (12), forcedSwitch(12),
lockoutOfProtection (14) lockoutOfProtection(14)
} }
MplsLpsFpathPath ::= TEXTUAL-CONVENTION MplsLpsFpathPath ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Textual Convention describes an object that stores "This textual convention describes an object that stores
the Fault Path (FPath) field and Data Path (Path) field of the Fault Path (FPath) field and Data Path (Path) field of
the PSC control packet. the PSC control packet.
FPath is located in the first octet and Path is FPath is located in the first octet, and Path is
located in the second octet. located in the second octet.
The value and the interpretation of FPath field is as follows: The value and the interpretation of the FPath field are
as follows:
2-255 2-255
for future extensions for future extensions
1 1
the anomaly condition is on the working path the anomaly condition is on the working path
0 0
the anomaly condition is on the protection path the anomaly condition is on the protection path
The value and the interpretation of the Path field are
The value and the interpretation of Path field is as follows: as follows:
2-255 2-255
for future extensions for future extensions
1 1
protection path is transporting user data traffic protection path is transporting user data traffic
0 0
protection path is not transporting user data traffic " protection path is not transporting user data traffic."
REFERENCE REFERENCE
"Section 4.2.5 and 4.2.6 of RFC6378" "Sections 4.2.5 and 4.2.6 of RFC 6378"
SYNTAX OCTET STRING (SIZE (2)) SYNTAX OCTET STRING (SIZE (2))
MplsLpsCommand ::= TEXTUAL-CONVENTION MplsLpsCommand ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This command allows a user to perform any action over a "This command allows a user to perform any action over a
protection domain. If the protection command cannot be protection domain. If the protection command cannot be
executed because an equal or higher priority request is executed because a request of equal or higher priority is
in effect, an inconsistentValue error is returned. in effect, an inconsistentValue error is returned.
The command values are: The command values are as follows:
noCmd noCmd
This value should be returned by a read request when no This value should be returned by a read request when no
command has been written to the object in question since command has been written to the object in question since
initialization. This value may not be used in a write initialization. This value may not be used in a write
operation. If noCmd is used in a write operation a operation. If noCmd is used in a write operation, a
wrongValue error is returned. wrongValue error is returned.
clear clear
Clears all of the commands listed below for the protection Clears all of the commands listed below for the protection
domain. domain.
lockoutOfProtection lockoutOfProtection
Prevents switching traffic to the protection path. Prevents switching traffic to the protection path.
forcedSwitch forcedSwitch
Switches traffic from the working path to the protection path. Switches traffic from the working path to the protection path.
manualSwitchToWork manualSwitchToWork
Switches traffic from the protection path to the working path. Switches traffic from the protection path to the working path.
manualSwitchToProtect manualSwitchToProtect
Switches traffic from the working path to the protection path. Switches traffic from the working path to the protection path.
exercise exercise
Used to verify the correct operation of the PSC communication Used to verify the correct operation of the PSC communication
and the integrity of the protection path. This command is not and the integrity of the protection path. This command is not
applicable to the PSC mode. applicable to the PSC mode.
freeze freeze
This command freezes the protection state and is a local This command freezes the protection state and is a local
command that is not signaled to the remote node. command that is not signaled to the remote node.
This command is not applicable to the PSC mode. This command is not applicable to the PSC mode.
clearfreeze clearfreeze
Clears the local freeze. This command is not applicable to Clears the local freeze. This command is not applicable to
the PSC mode. " the PSC mode."
REFERENCE REFERENCE
"Sections 3.1 and 3.2 of RFC6378 and Sections 4.3 and 6 of "Sections 3.1 and 3.2 of RFC 6378 and Sections 4.3 and 6 of
RFC7271" RFC 7271"
SYNTAX INTEGER { SYNTAX INTEGER {
noCmd(1), noCmd(1),
clear(2), clear(2),
lockoutOfProtection(3), lockoutOfProtection(3),
forcedSwitch(4), forcedSwitch(4),
manualSwitchToWork(5), manualSwitchToWork(5),
manualSwitchToProtect(6), manualSwitchToProtect(6),
exercise(7), exercise(7),
freeze(8), freeze(8),
clearfreeze(9) clearfreeze(9)
} }
MplsLpsState ::= TEXTUAL-CONVENTION MplsLpsState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Textual Convention describes an object that stores "This textual convention describes an object that stores
the current state of the PSC state machine. The values the current state of the PSC state machine. The values
are as follows: are as follows:
normal normal
normal state Normal state.
unavLOlocal unavLOlocal
Unavailable state due to local LO command. Unavailable state due to local LO command.
unavSFPlocal unavSFPlocal
Unavailable state due to local SF-P. Unavailable state due to local SF-P.
unavSDPlocal unavSDPlocal
Unavailable state due to local SD-P. Unavailable state due to local SD-P.
skipping to change at page 13, line 47 skipping to change at page 15, line 28
Protecting Failure state due to local SD-W. Protecting Failure state due to local SD-W.
protfailSFWremote protfailSFWremote
Protecting Failure state due to remote SF-W message. Protecting Failure state due to remote SF-W message.
protfailSDWremote protfailSDWremote
Protecting Failure state due to remote SD-W message. Protecting Failure state due to remote SD-W message.
switadmFSlocal switadmFSlocal
Switching Administrative state due to local FS command. Switching Administrative state due to local FS command.
Same as Protecting administrative state due to local FS Same as Protecting Administrative state due to local FS
command in the PSC mode. command in the PSC mode.
switadmMSWlocal switadmMSWlocal
Switching Administrative state due to local MS-W command Switching Administrative state due to local MS-W command.
switadmMSPlocal switadmMSPlocal
Switching Administrative state due to local MS-P command. Switching Administrative state due to local MS-P command.
Same as Protecting administrative state due to local MS Same as Protecting Administrative state due to local MS
command in the PSC mode command in the PSC mode.
switadmFSremote switadmFSremote
Switching Administrative state due to remote FS message. Switching Administrative state due to remote FS message.
Same as Protecting administrative state due to remote FS Same as Protecting Administrative state due to remote FS
message in the PSC mode. message in the PSC mode.
switadmMSWremote switadmMSWremote
Switching Administrative state due to remote MS-W message Switching Administrative state due to remote MS-W message.
switadmMSPremote switadmMSPremote
Switching Administrative state due to remote MS-P message. Switching Administrative state due to remote MS-P message.
Same as Protecting administrative state due to remote MS Same as Protecting Administrative state due to remote MS
message in the PSC mode. message in the PSC mode.
wtr wtr
Wait-to-Restore state Wait-to-Restore state.
dnr dnr
Do-not-Revert state Do-not-Revert state.
exerLocal exerLocal
Exercise state due to local EXER command. Exercise state due to local EXER command.
exerRemote exerRemote
Exercise state due to remote EXER message." Exercise state due to remote EXER message."
REFERENCE REFERENCE
"Section 11 of RFC7271" "Sections 3 and 11 of RFC 7271"
SYNTAX INTEGER { SYNTAX INTEGER {
normal (1), normal(1),
unavLOlocal (2), unavLOlocal(2),
unavSFPlocal (3), unavSFPlocal(3),
unavSDPlocal (4), unavSDPlocal(4),
unavLOremote (5), unavLOremote(5),
unavSFPremote (6), unavSFPremote(6),
unavSDPremote (7), unavSDPremote(7),
protfailSFWlocal (8), protfailSFWlocal(8),
protfailSDWlocal (9), protfailSDWlocal(9),
protfailSFWremote (10), protfailSFWremote(10),
protfailSDWremote (11), protfailSDWremote(11),
switadmFSlocal (12), switadmFSlocal(12),
switadmMSWlocal (13), switadmMSWlocal(13),
switadmMSPlocal (14), switadmMSPlocal(14),
switadmFSremote (15), switadmFSremote(15),
switadmMSWremote (16), switadmMSWremote(16),
switadmMSPremote (17), switadmMSPremote(17),
wtr (18), wtr(18),
dnr (19), dnr(19),
exerLocal (20), exerLocal(20),
exerRemote (21) exerRemote(21)
} }
-- Start of -- Start of
-- MPLS-TP Linear Protection Switching Configuration Table. -- MPLS-TP Linear Protection Switching Configuration Table.
-- This table supports the addition, configuration and deletion -- This table supports the addition, configuration, and deletion
-- of MPLS-TP linear protection domains. -- of MPLS-TP linear protection domains.
mplsLpsConfigDomainIndexNext OBJECT-TYPE mplsLpsConfigDomainIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295) SYNTAX IndexIntegerNextFree (0..4294967295)
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
mplsLpsConfigDomainIndex, or a zero to indicate mplsLpsConfigDomainIndex, or a zero to indicate that
that none exist. Negative values are not allowed, the number of unassigned entries has been exhausted.
as they do not correspond to valid values of Negative values are not allowed, as they do not correspond
mplsLpsConfigDomainIndex." to valid values of mplsLpsConfigDomainIndex."
::= { mplsLpsObjects 1 } ::= { mplsLpsObjects 1 }
mplsLpsConfigTable OBJECT-TYPE mplsLpsConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLpsConfigEntry SYNTAX SEQUENCE OF MplsLpsConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists the MPLS-TP linear protection domains that "This table lists the MPLS-TP linear protection domains that
have been configured on the system. have been configured on the system.
An entry is created by a network operator who wants to run An entry is created by a network operator who wants to run
skipping to change at page 15, line 48 skipping to change at page 17, line 41
domain." domain."
::= { mplsLpsObjects 2 } ::= { mplsLpsObjects 2 }
mplsLpsConfigEntry OBJECT-TYPE mplsLpsConfigEntry OBJECT-TYPE
SYNTAX MplsLpsConfigEntry SYNTAX MplsLpsConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the mplsLpsConfigTable." "A conceptual row in the mplsLpsConfigTable."
INDEX { mplsLpsConfigDomainIndex } INDEX { mplsLpsConfigDomainIndex }
::= { mplsLpsConfigTable 1 } ::= { mplsLpsConfigTable 1 }
MplsLpsConfigEntry ::= SEQUENCE { MplsLpsConfigEntry ::= SEQUENCE {
mplsLpsConfigDomainIndex Unsigned32, mplsLpsConfigDomainIndex Unsigned32,
mplsLpsConfigDomainName SnmpAdminString, mplsLpsConfigDomainName SnmpAdminString,
mplsLpsConfigMode INTEGER, mplsLpsConfigMode INTEGER,
mplsLpsConfigProtectionType INTEGER, mplsLpsConfigProtectionType INTEGER,
mplsLpsConfigRevertive INTEGER, mplsLpsConfigRevertive INTEGER,
mplsLpsConfigSdThreshold Unsigned32, mplsLpsConfigSdThreshold Unsigned32,
mplsLpsConfigSdBadSeconds Unsigned32, mplsLpsConfigSdBadSeconds Unsigned32,
mplsLpsConfigSdGoodSeconds Unsigned32, mplsLpsConfigSdGoodSeconds Unsigned32,
skipping to change at page 16, line 22 skipping to change at page 18, line 14
mplsLpsConfigHoldOff Unsigned32, mplsLpsConfigHoldOff Unsigned32,
mplsLpsConfigContinualTxInterval Unsigned32, mplsLpsConfigContinualTxInterval Unsigned32,
mplsLpsConfigRapidTxInterval Unsigned32, mplsLpsConfigRapidTxInterval Unsigned32,
mplsLpsConfigCommand MplsLpsCommand, mplsLpsConfigCommand MplsLpsCommand,
mplsLpsConfigCreationTime TimeStamp, mplsLpsConfigCreationTime TimeStamp,
mplsLpsConfigRowStatus RowStatus, mplsLpsConfigRowStatus RowStatus,
mplsLpsConfigStorageType StorageType mplsLpsConfigStorageType StorageType
} }
mplsLpsConfigDomainIndex OBJECT-TYPE mplsLpsConfigDomainIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index for the conceptual row identifying a protection domain. "Index for the conceptual row identifying a protection domain.
Operators should obtain new values for row creation in this Operators should obtain new values for row creation in this
table by reading mplsLpsConfigDomainIndexNext. table by reading mplsLpsConfigDomainIndexNext.
When the value of this object is the same as the value of When the value of this object is the same as the value of
mplsLpsMeConfigDomain, that means that the mplsLpsMeConfigDomain, the mplsLpsMeConfigDomain is defined
mplsLpsMeConfigDomain is defined as either the working path as either the working path or the protection path for this
or the protection path for this protection domain." protection domain."
::= { mplsLpsConfigEntry 1 } ::= { mplsLpsConfigEntry 1 }
mplsLpsConfigDomainName OBJECT-TYPE mplsLpsConfigDomainName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Textual name represents the MPLS-TP linear protection domain. "Textual name that represents the MPLS-TP linear protection
It facilitates easy administrative identification of domain. It facilitates easy administrative identification of
each protection domain." each protection domain."
DEFVAL {""} DEFVAL {""}
::= { mplsLpsConfigEntry 2 } ::= { mplsLpsConfigEntry 2 }
mplsLpsConfigMode OBJECT-TYPE mplsLpsConfigMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
psc(1), psc(1),
aps(2) aps(2)
} }
MAX-ACCESS read-create
MAX-ACCESS read-create STATUS current
STATUS current
DESCRIPTION DESCRIPTION
"The mode of MPLS-TP linear protection mechanism. This can "The mode of the MPLS-TP linear protection mechanism. This can
either be PSC or APS as follows: be either PSC or APS, as follows:
PSC PSC
The Protection State Coordination mode as described in The Protection State Coordination mode as described in
RFC 6378. RFC 6378.
APS APS
The Automatic Protection Switching mode as described in The Automatic Protection Switching mode as described in
RFC 7271. RFC 7271.
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). mplsLpsConfigRowStatus object is equal to active(1).
The value of this object is not supposed to be changed The value of this object is not supposed to be changed
during operation. When the value should be changed, during operation. When the value should be changed,
the protection processes in both LERs MUST be the protection processes in both LERs MUST be
restarted with the same new value. restarted with the same new value.
In case that this value is changed at one LER during If this value is changed at one LER during operation,
operation, the LER will generate PSC packets with a new the LER will generate PSC packets with a new
Capabilities TLV value. As a consequence, this will Capabilities TLV value. This will result in
result in mplsLpsEventCapabilitiesMismatch notification mplsLpsEventCapabilitiesMismatch notifications at both LERs."
at both LERs. "
REFERENCE REFERENCE
"Sections 9.2 and 10 of RFC7271" "Sections 9.2 and 10 of RFC 7271"
DEFVAL {psc} DEFVAL {psc}
::= { mplsLpsConfigEntry 3 } ::= { mplsLpsConfigEntry 3 }
mplsLpsConfigProtectionType OBJECT-TYPE mplsLpsConfigProtectionType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
onePlusOneUnidirectional (1), onePlusOneUnidirectional(1),
oneColonOneBidirectional (2), oneColonOneBidirectional(2),
onePlusOneBidirectional (3) onePlusOneBidirectional(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The protection architecture type of the Protection domain. "The protection architecture type of the protection domain.
This represents both bridge type, which can be This object represents both the bridge type, which can be
either permanent bridge (1+1) or selector bridge (1:1), either a permanent bridge (1+1) or a selector bridge (1:1);
and switching scheme, which can be and the switching scheme, which can be either unidirectional
either unidirectional or bidirectional. or bidirectional.
1+1 1+1
In the 1+1 protection scheme, a fully dedicated protection In the 1+1 protection scheme, a fully dedicated protection
path is allocated. Data traffic is copied and fed path is allocated. Data traffic is copied and fed at the
at the source to both the working and the protection path. source to both the working path and the protection path.
The traffic on the working and the protection paths is The traffic on the working path and protection path is
transmitted simultaneously to the sink of the protection transmitted simultaneously to the sink of the protection
domain, where selection between the working and protection domain, where selection between the working path and the
paths is performed protection path is performed.
1:1 1:1
In the 1:1 scheme, a protection path is allocated to In the 1:1 protection scheme, a protection path is allocated
protect against a defect, failure, or a degradation in the to protect against a defect, failure, or degradation on the
working path. In normal conditions, data traffic is working path. In normal conditions, data traffic is
transmitted over the working path, while the protection path transmitted over the working path, while the protection path
functions in the idle state. If there is a defect on the functions in the idle state. If there is a defect on the
working path or a specific administrative request, working path or a specific administrative request,
traffic is switched to the protection path. traffic is switched to the protection path.
bidirectional bidirectional
In bidirectional protection scheme, both the directions In the bidirectional protection scheme, both directions
will be switched simultaneously even if the fault applies will be switched simultaneously even if the fault applies
to only one direction of the path. to only one direction of the path.
unidirectional unidirectional
In unidirectional protection scheme protection switching In the unidirectional protection scheme, protection switching
will be performed independently for each direction of a will be performed independently for each direction of a
bidirectional transport path. bidirectional transport path.
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 4.2.3 of RFC6378" "Section 4.2.3 of RFC 6378"
DEFVAL {oneColonOneBidirectional} DEFVAL {oneColonOneBidirectional}
::= { mplsLpsConfigEntry 4 } ::= { mplsLpsConfigEntry 4 }
mplsLpsConfigRevertive OBJECT-TYPE mplsLpsConfigRevertive OBJECT-TYPE
SYNTAX INTEGER { nonrevertive(1), revertive(2) } SYNTAX INTEGER { nonrevertive(1), revertive(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the reversion mode of the linear "This object represents the reversion mode of the linear
protection domain. The reversion mode of protection protection domain. The reversion mode of the protection
mechanism may be either revertive or non-revertive. mechanism may be either revertive or non-revertive.
nonrevertive nonrevertive
In non-revertive mode, after a service has been recovered, In the non-revertive mode, after a service has been recovered,
traffic will be forwarded on the protection path. traffic will be forwarded on the protection path.
revertive revertive
In revertive mode, after a service has been recovered, In the revertive mode, after a service has been recovered,
traffic will be redirected back onto the original working traffic will be redirected back onto the original working
path. path.
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 4.2.4 of RFC6378" "Section 4.2.4 of RFC 6378"
DEFVAL { revertive } DEFVAL { revertive }
::= { mplsLpsConfigEntry 5 } ::= { mplsLpsConfigEntry 5 }
mplsLpsConfigSdThreshold OBJECT-TYPE mplsLpsConfigSdThreshold OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..100)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the threshold value of the Signal Degrade "This object holds the threshold value of the Signal Degrade
(SD) defect in percent. In order to detect the SD defect, (SD) defect in percent. In order to detect the SD defect,
the MPLS-TP packet loss measurement (LM) is performed the MPLS-TP packet loss measurement (LM) is performed
every second. every second.
If either the packet loss is negative (i.e., there are more If either the packet loss is negative (i.e., there are more
packets received than transmitted) or the packet loss ratio packets received than transmitted) or the packet loss ratio
(lost packets/transmitted packets) in percent is greater than (lost packets/transmitted packets) in percent is greater than
this threshold value, a Bad Second is declared. this threshold value, a Bad Second is declared.
Otherwise, a Good Second is declared. Otherwise, a Good Second is declared.
The SD defect is detected if there are The SD defect is detected if there are
mplsLpsConfigSdBadSeconds consecutive Bad Seconds mplsLpsConfigSdBadSeconds consecutive Bad Seconds
and cleared if there are and cleared if there are
mplsLpsConfigSdGoodSeconds consecutive Good Seconds. mplsLpsConfigSdGoodSeconds consecutive Good Seconds.
This object may be modified if the associated This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)." mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]" "Clause 6.1.3.3 of ITU-T Recommendation G.8121/Y.1381 and
Table 8-1 of ITU-T Recommendation G.8151/Y.1374"
DEFVAL { 30 } DEFVAL { 30 }
::= { mplsLpsConfigEntry 6 } ::= { mplsLpsConfigEntry 6 }
mplsLpsConfigSdBadSeconds OBJECT-TYPE mplsLpsConfigSdBadSeconds OBJECT-TYPE
SYNTAX Unsigned32 (2..10) SYNTAX Unsigned32 (2..10)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the number of Bad Seconds to detect the SD. "This object holds the number of Bad Seconds to detect the SD.
If the number of consecutive Bad Seconds reaches this value, If the number of consecutive Bad Seconds reaches this value,
the SD defect is detected and used as an input to the SD defect is detected and used as an input to
the protection switching process. the protection switching process.
This object may be modified if the associated This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]" "Clause 6.1.3.3 of ITU-T Recommendation G.8121/Y.1381 and
Table 8-1 of ITU-T Recommendation G.8151/Y.1374"
DEFVAL { 10 } DEFVAL { 10 }
::= { mplsLpsConfigEntry 7 } ::= { mplsLpsConfigEntry 7 }
mplsLpsConfigSdGoodSeconds OBJECT-TYPE mplsLpsConfigSdGoodSeconds OBJECT-TYPE
SYNTAX Unsigned32 (2..10) SYNTAX Unsigned32 (2..10)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the number of Good Seconds to declare "This object holds the number of Good Seconds to declare
the clearance of SD defect. the clearance of an SD defect.
After an SD defect occurs at a path, if the number of After an SD defect occurs on a path, if the number of
consecutive Good Seconds reaches this value for the consecutive Good Seconds reaches this value for the
degraded path, the clearance of SD defect is declared and degraded path, the clearance of the SD defect is declared
used as an input to the protection switching process. and used as an input to the protection switching process.
This object may be modified if the associated This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)." mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]" "Clause 6.1.3.3 of ITU-T Recommendation G.8121/Y.1381 and
Table 8-1 of ITU-T Recommendation G.8151/Y.1374"
DEFVAL { 10 } DEFVAL { 10 }
::= { mplsLpsConfigEntry 8 } ::= { mplsLpsConfigEntry 8 }
mplsLpsConfigWaitToRestore OBJECT-TYPE mplsLpsConfigWaitToRestore OBJECT-TYPE
SYNTAX Unsigned32 (5..12) SYNTAX Unsigned32 (5..12)
UNITS "minutes" UNITS "minutes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the Wait To Restore timer value in minutes, "This object holds the Wait-to-Restore timer value in minutes
and can be configured in 1 minute steps between 5 and and can be configured in 1-minute intervals between 5 and
12 minutes. 12 minutes.
The WTR timer is used to delay reversion of PSC state The WTR timer is used to delay the reversion of the PSC state
to Normal state when recovering from a failure to the Normal state when recovering from a failure condition
condition on the working path when the protection on the working path when the protection domain is configured
domain is configured for revertive behavior for revertive behavior.
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)." mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 3.5 of RFC6378" "Section 3.5 of RFC 6378"
DEFVAL { 5 } DEFVAL { 5 }
::= { mplsLpsConfigEntry 9 } ::= { mplsLpsConfigEntry 9 }
mplsLpsConfigHoldOff OBJECT-TYPE mplsLpsConfigHoldOff OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..100)
UNITS "deciseconds" UNITS "deciseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The hold-off time in deciseconds. Represents the time "The hold-off time in deciseconds. Represents the time
between SF/SD condition detection and declaration of between SF/SD condition detection and declaration of
an SF/SD request to the protection switching logic. an SF/SD request to the protection switching logic.
It is intended to avoid unnecessary switching when a lower- It is intended to avoid unnecessary switching when a
layer protection mechanism is in place. lower-layer protection mechanism is in place.
Can be configured in steps of 100 milli-seconds. Can be configured in intervals of 100 milliseconds.
When a new defect or more severe defect occurs at When a new defect or a more severe defect occurs on
the active path (the path from which the selector selects the active path (the path from which the selector selects
the user data traffic) and this value is non-zero, the user data traffic) and this value is non-zero,
the hold-off timer will be started. A defect on the standby the hold-off timer will be started. A defect on the standby
path (the path from which the selector does not select the path (the path from which the selector does not select the
user data traffic) does not trigger the start of the hold-off user data traffic) does not trigger the start of the hold-off
timer as there is no need for a traffic switchover. timer, as there is no need for a traffic switchover.
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 3.1 of RFC6378" "Section 3.1 of RFC 6378"
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsLpsConfigEntry 10 } ::= { mplsLpsConfigEntry 10 }
mplsLpsConfigContinualTxInterval OBJECT-TYPE mplsLpsConfigContinualTxInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..20) SYNTAX Unsigned32 (1..20)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Continual Tx Time in Seconds. Represents the time "The Continual Tx Time in seconds. Represents the time
interval to send the continual LPS packet to the other interval to send the continual PSC packet to the other
end based on the current state. end, based on the current state.
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 4.1 of RFC6378" "Section 4.1 of RFC 6378"
DEFVAL { 5 } DEFVAL { 5 }
::= { mplsLpsConfigEntry 11 } ::= { mplsLpsConfigEntry 11 }
mplsLpsConfigRapidTxInterval OBJECT-TYPE mplsLpsConfigRapidTxInterval OBJECT-TYPE
SYNTAX Unsigned32 (1000..20000) SYNTAX Unsigned32 (1000..20000)
UNITS "micro-seconds" UNITS "microseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Rapid Tx interval in micro-Seconds. Represents the time "The Rapid Tx interval in microseconds. Represents the time
interval to send the LPS packet to the other end, when interval to send the PSC packet to the other end, when
there is a change in state of linear protection domain due there is a change in the state of the linear protection domain
to local input. The default value is 3.3 milli-seconds due to local input. The default value is 3.3 milliseconds
which is 3300 micro-seconds (3300 microseconds).
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 4.1 of RFC6378" "Section 4.1 of RFC 6378"
DEFVAL { 3300 } DEFVAL { 3300 }
::= { mplsLpsConfigEntry 12 } ::= { mplsLpsConfigEntry 12 }
mplsLpsConfigCommand OBJECT-TYPE mplsLpsConfigCommand OBJECT-TYPE
SYNTAX MplsLpsCommand SYNTAX MplsLpsCommand
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Allows the initiation of an operator command on "Allows the initiation of an operator command on
the protection domain. the protection domain.
When read this object returns the last command written When read, this object returns the last command written
or noCmd if no command has been written or noCmd if no command has been written since initialization.
since initialization. The return of the last command The return of the last command written does not imply that
written does not imply that this command is currently in this command is currently in effect. This request may have
effect. This request may have been preempted by a higher been preempted by a higher-priority local or remote request.
priority local or remote request.
This object may be modified if the associated This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Sections 3.1 and 3.2 of RFC6378 and Sections 4.3 and 6 of "Sections 3.1 and 3.2 of RFC 6378 and Sections 4.3 and 6 of
RFC7271" RFC 7271"
DEFVAL { noCmd } DEFVAL { noCmd }
::= { mplsLpsConfigEntry 13 } ::= { mplsLpsConfigEntry 13 }
mplsLpsConfigCreationTime OBJECT-TYPE mplsLpsConfigCreationTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the row was created." "The value of sysUpTime at the time the row was created."
::= { mplsLpsConfigEntry 14 } ::= { mplsLpsConfigEntry 14 }
mplsLpsConfigRowStatus OBJECT-TYPE mplsLpsConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This represents the status of the MPLS-TP linear "This object represents the status of the MPLS-TP linear
protection domain entry. This variable is used to protection domain entry. This variable is used to
create, modify, and/or delete a row in this table." create, modify, and/or delete a row in this table."
::= { mplsLpsConfigEntry 15 } ::= { mplsLpsConfigEntry 15 }
mplsLpsConfigStorageType OBJECT-TYPE mplsLpsConfigStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row." allow write access to any columnar objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLpsConfigEntry 16 } ::= { mplsLpsConfigEntry 16 }
-- --
-- MPLS-TP Linear Protection Switching Status Table -- MPLS-TP Linear Protection Switching Status Table.
-- This table provides Protection Switching domain statistics. -- This table provides protection domain statistics.
-- --
mplsLpsStatusTable OBJECT-TYPE mplsLpsStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLpsStatusEntry SYNTAX SEQUENCE OF MplsLpsStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides status information about MPLS-TP "This table provides status information about MPLS-TP
linear protection domains that have been configured linear protection domains that have been configured
on the system." on the system."
::= { mplsLpsObjects 3 } ::= { mplsLpsObjects 3 }
mplsLpsStatusEntry OBJECT-TYPE mplsLpsStatusEntry OBJECT-TYPE
SYNTAX MplsLpsStatusEntry SYNTAX MplsLpsStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the mplsLpsStatusTable." "A conceptual row in the mplsLpsStatusTable."
AUGMENTS { mplsLpsConfigEntry } AUGMENTS { mplsLpsConfigEntry }
::= { mplsLpsStatusTable 1 } ::= { mplsLpsStatusTable 1 }
MplsLpsStatusEntry ::= SEQUENCE { MplsLpsStatusEntry ::= SEQUENCE {
mplsLpsStatusState MplsLpsState, mplsLpsStatusState MplsLpsState,
mplsLpsStatusReqRcv MplsLpsReq, mplsLpsStatusReqRcv MplsLpsReq,
mplsLpsStatusReqSent MplsLpsReq, mplsLpsStatusReqSent MplsLpsReq,
mplsLpsStatusFpathPathRcv MplsLpsFpathPath, mplsLpsStatusFpathPathRcv MplsLpsFpathPath,
mplsLpsStatusFpathPathSent MplsLpsFpathPath, mplsLpsStatusFpathPathSent MplsLpsFpathPath,
mplsLpsStatusRevertiveMismatch TruthValue, mplsLpsStatusRevertiveMismatch TruthValue,
mplsLpsStatusProtecTypeMismatch TruthValue, mplsLpsStatusProtecTypeMismatch TruthValue,
mplsLpsStatusCapabilitiesMismatch TruthValue, mplsLpsStatusCapabilitiesMismatch TruthValue,
skipping to change at page 24, line 18 skipping to change at page 27, line 4
mplsLpsStatusReqSent MplsLpsReq, mplsLpsStatusReqSent MplsLpsReq,
mplsLpsStatusFpathPathRcv MplsLpsFpathPath, mplsLpsStatusFpathPathRcv MplsLpsFpathPath,
mplsLpsStatusFpathPathSent MplsLpsFpathPath, mplsLpsStatusFpathPathSent MplsLpsFpathPath,
mplsLpsStatusRevertiveMismatch TruthValue, mplsLpsStatusRevertiveMismatch TruthValue,
mplsLpsStatusProtecTypeMismatch TruthValue, mplsLpsStatusProtecTypeMismatch TruthValue,
mplsLpsStatusCapabilitiesMismatch TruthValue, mplsLpsStatusCapabilitiesMismatch TruthValue,
mplsLpsStatusPathConfigMismatch TruthValue, mplsLpsStatusPathConfigMismatch TruthValue,
mplsLpsStatusFopNoResponses Counter32, mplsLpsStatusFopNoResponses Counter32,
mplsLpsStatusFopTimeouts Counter32 mplsLpsStatusFopTimeouts Counter32
} }
mplsLpsStatusState OBJECT-TYPE mplsLpsStatusState OBJECT-TYPE
SYNTAX MplsLpsState SYNTAX MplsLpsState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state of the PSC state machine." "The current state of the PSC state machine."
REFERENCE REFERENCE
"Section 11 of RFC7271" "Section 11 of RFC 7271"
::= { mplsLpsStatusEntry 1 } ::= { mplsLpsStatusEntry 1 }
mplsLpsStatusReqRcv OBJECT-TYPE mplsLpsStatusReqRcv OBJECT-TYPE
SYNTAX MplsLpsReq SYNTAX MplsLpsReq
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current value of the PSC Request field received on "The current value of the PSC Request field received on
the most recent PSC packet." the most recent PSC packet."
REFERENCE REFERENCE
"Section 4.2 of RFC6378" "Section 4.2 of RFC 6378"
::= { mplsLpsStatusEntry 2 } ::= { mplsLpsStatusEntry 2 }
mplsLpsStatusReqSent OBJECT-TYPE mplsLpsStatusReqSent OBJECT-TYPE
SYNTAX MplsLpsReq SYNTAX MplsLpsReq
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current value of the PSC Request field sent on the "The current value of the PSC Request field sent on the
most recent PSC packet." most recent PSC packet."
REFERENCE REFERENCE
"Section 4.2 of RFC6378" "Section 4.2 of RFC 6378"
::= { mplsLpsStatusEntry 3 } ::= { mplsLpsStatusEntry 3 }
mplsLpsStatusFpathPathRcv OBJECT-TYPE mplsLpsStatusFpathPathRcv OBJECT-TYPE
SYNTAX MplsLpsFpathPath SYNTAX MplsLpsFpathPath
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current value of the FPath and Path fields received "The current value of the FPath and Path fields received
on the most recent PSC packet." on the most recent PSC packet."
REFERENCE REFERENCE
"Section 4.2 of RFC6378" "Section 4.2 of RFC 6378"
::= { mplsLpsStatusEntry 4 } ::= { mplsLpsStatusEntry 4 }
mplsLpsStatusFpathPathSent OBJECT-TYPE mplsLpsStatusFpathPathSent OBJECT-TYPE
SYNTAX MplsLpsFpathPath SYNTAX MplsLpsFpathPath
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current value of the FPath and Path fields sent "The current value of the FPath and Path fields sent
on the most recent PSC packet." on the most recent PSC packet."
REFERENCE REFERENCE
"Section 4.2 of RFC6378" "Section 4.2 of RFC 6378"
::= { mplsLpsStatusEntry 5 } ::= { mplsLpsStatusEntry 5 }
mplsLpsStatusRevertiveMismatch OBJECT-TYPE mplsLpsStatusRevertiveMismatch OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the provisioning mismatch in "This object indicates a provisioning mismatch in the
revertive mode across the protection domain end points. revertive mode across the protection domain endpoints.
The value of this object becomes true when a PSC message with The value of this object becomes true when a PSC message with
incompatible Revertive field is received, or false an incompatible Revertive field is received or false when a
when a PSC message with compatible Revertive field is PSC message with a compatible Revertive field is received."
received. "
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC 7271"
::= { mplsLpsStatusEntry 6 } ::= { mplsLpsStatusEntry 6 }
mplsLpsStatusProtecTypeMismatch OBJECT-TYPE mplsLpsStatusProtecTypeMismatch OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the provisioning mismatch in "This object indicates a provisioning mismatch in the
protection type, representing both bridge and switching types, protection type, representing both the bridge type and the
across the protection domain end points. switching type, across the protection domain endpoints.
The value of this object becomes true when a PSC message with The value of this object becomes true when a PSC message with
incompatible PT field is received, or false an incompatible Protection Type (PT) field is received or
when a PSC message with compatible PT field is received. " false when a PSC message with a compatible PT field is
received."
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC 7271"
::= { mplsLpsStatusEntry 7 } ::= { mplsLpsStatusEntry 7 }
mplsLpsStatusCapabilitiesMismatch OBJECT-TYPE mplsLpsStatusCapabilitiesMismatch OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the provisioning mismatch in "This object indicates a provisioning mismatch in
Capabilities TLVs across the protection domain end points. Capabilities TLVs across the protection domain endpoints.
The value of this object becomes true when a PSC message with The value of this object becomes true when a PSC message with
incompatible Capabilities TLV field is received, or false an incompatible Capabilities TLV field is received or false
when a PSC message with compatible Capabilities TLV field is when a PSC message with a compatible Capabilities TLV field is
received. received.
The Capabilities TLV with 0xF8000000 indicates that the APS The Capabilities TLV with 0xF8000000 indicates that the APS
mode is used for MPLS-TP linear protection mechanism, mode is used for the MPLS-TP linear protection mechanism,
whereas PSC mode uses either the Capabilities TLV with Ox0 whereas the PSC mode either (1) uses the Capabilities TLV
or no existence of the Capabilities TLV." with a value of 0x0 or (2) does not use the Capabilities TLV
because the TLV does not exist."
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC 7271"
::= { mplsLpsStatusEntry 8 } ::= { mplsLpsStatusEntry 8 }
mplsLpsStatusPathConfigMismatch OBJECT-TYPE mplsLpsStatusPathConfigMismatch OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the provisioning mismatch in the "This object indicates a provisioning mismatch in the
protection path configuration for PSC communication across protection path configuration for PSC communication across
the protection domain end points. the protection domain endpoints.
The value of this object becomes true when a PSC message is The value of this object becomes true when a PSC message is
received from the working path, or false when a PSC message received from the working path or false when a PSC message
is received from the protection path." is received from the protection path."
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC 7271"
::= { mplsLpsStatusEntry 9 } ::= { mplsLpsStatusEntry 9 }
mplsLpsStatusFopNoResponses OBJECT-TYPE mplsLpsStatusFopNoResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the number of occurrences of the failure "This object holds the number of occurrences of protocol
of protocol due to a lack of response to a traffic switchover failure due to a lack of response to a traffic
request within in 50 ms. switchover request within 50 ms.
When there is a traffic switchover due to a local request, When there is a traffic switchover due to a local request,
a 50 ms timer is started to detect the failure of protocol a 50 ms timer is started to detect protocol failure due to
due to no response. If there is no PSC message is received no response. If there is no PSC message received with the
with the same Path value as in the transmitted PSC message same Path value as the Path value in the transmitted
until the 50 ms timer expires, the failure of protocol due to PSC message until the 50 ms timer expires, protocol failure
no response occurs." due to no response occurs."
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC 7271"
::= { mplsLpsStatusEntry 10 } ::= { mplsLpsStatusEntry 10 }
mplsLpsStatusFopTimeouts OBJECT-TYPE mplsLpsStatusFopTimeouts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the number of occurrences of the failure "This object holds the number of occurrences of protocol
of protocol due to no PSC message received during at least failure due to no PSC message being received during
3.5 times the long PSC message interval. at least 3.5 times the long PSC message interval.
When no PSC message is received on the protection path during When no PSC message is received on the protection path during
at least 3.5 times the long PSC message interval and there at least 3.5 times the long PSC message interval and there
is no defect on the protection path, the failure of protocol is no defect on the protection path, protocol failure due to
due to no PSC message occurs." no PSC message occurs."
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC 7271"
::= { mplsLpsStatusEntry 11 } ::= { mplsLpsStatusEntry 11 }
-- MPLS-TP Linear Protection ME Association Configuration Table -- MPLS-TP Linear Protection ME Association Configuration Table.
-- This table supports the addition, configuration and deletion -- This table supports the addition, configuration, and deletion
-- of MPLS-TP Linear Protection Maintenance Entities in protection -- of MPLS-TP linear protection MEs in protection domains.
-- domains.
mplsLpsMeConfigTable OBJECT-TYPE mplsLpsMeConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLpsMeConfigEntry SYNTAX SEQUENCE OF MplsLpsMeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Maintenance Association that have been "This table lists ME associations that have been configured
configured in Protection domains." in protection domains."
::= { mplsLpsObjects 4 } ::= { mplsLpsObjects 4 }
mplsLpsMeConfigEntry OBJECT-TYPE mplsLpsMeConfigEntry OBJECT-TYPE
SYNTAX MplsLpsMeConfigEntry SYNTAX MplsLpsMeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the mplsLpsMeConfigTable. There is "A conceptual row in the mplsLpsMeConfigTable. There is
a sparse relationship between the conceptual rows of a sparse relationship between the conceptual rows of
this table and mplsOamIdMeTable. this table and the mplsOamIdMeTable.
Each time that an entry is created in the mplsOamIdMeTable Each time that an entry is created in the mplsOamIdMeTable
for which the LER supports MPLS-TP linear protection, for which the LER supports MPLS-TP linear protection,
a row is created automatically in the mplsLpsMeConfigTable. a row is created automatically in the mplsLpsMeConfigTable.
An entry of this table is related to a single entry in An entry in this table is related to a single entry in
mplsOamIdMeTable. When a point-to-point transport path the mplsOamIdMeTable. When a point-to-point transport path
needs to be monitored, one ME is needed for the path needs to be monitored, one ME is needed for the path,
and one entry in the mplsOamIdMeTable will be created. and one entry in the mplsOamIdMeTable will be created.
But, the ME entry in the mplsOamIdMeTable may or may not But the ME entry in the mplsOamIdMeTable may or may not
participate in protection switching. participate in protection switching.
If an ME participates in protection switching, If an ME participates in protection switching, an entry in
an entry in mplsLpsMeConfigTable MUST be created, the mplsLpsMeConfigTable MUST be created, and the objects
and the objects in the entry indicates in the entry indicate which protection domain this ME
which protection domain this ME belongs to and belongs to and whether this ME is for the working path or
whether this ME is for either working path or protection path. the protection path.
If the ME does not participate in protection switching, If the ME does not participate in protection switching,
an entry in mplsLpsMeConfigTable does not need to be created. " an entry in the mplsLpsMeConfigTable does not need
to be created."
INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex} INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex}
::= { mplsLpsMeConfigTable 1 } ::= { mplsLpsMeConfigTable 1 }
MplsLpsMeConfigEntry ::= SEQUENCE { MplsLpsMeConfigEntry ::= SEQUENCE {
mplsLpsMeConfigDomain Unsigned32, mplsLpsMeConfigDomain Unsigned32,
mplsLpsMeConfigPath INTEGER mplsLpsMeConfigPath INTEGER
} }
mplsLpsMeConfigDomain OBJECT-TYPE
mplsLpsMeConfigDomain OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295)
SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS read-create
MAX-ACCESS read-create STATUS current
STATUS current
DESCRIPTION DESCRIPTION
"This object holds the value of protection domain index wherein "This object holds the mplsLpsConfigDomainIndex value for
this ME is included. If this ME is not part of any the protection domain in which this ME is included.
protection domain then this object contains value 0. If this ME is not part of any protection domain, then
this object contains the value 0.
When the value of this object is the same as the value of When the value of this object is the same as the value of
mplsLpsConfigDomainIndex, that means that the object is mplsLpsConfigDomainIndex, the object is defined as either
defined as either the working path or the protection path the working path or the protection path of the
of the protection domain corresponding to protection domain corresponding to mplsLpsConfigDomainIndex."
mplsLpsConfigDomainIndex."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsLpsMeConfigEntry 1 } ::= { mplsLpsMeConfigEntry 1 }
mplsLpsMeConfigPath OBJECT-TYPE mplsLpsMeConfigPath OBJECT-TYPE
SYNTAX INTEGER { working(1), protection(2) } SYNTAX INTEGER { working(1), protection(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents whether the ME is configured "This object represents whether the ME is configured
as either the working path or the protection path" as the working path or the protection path."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC 6378"
::= { mplsLpsMeConfigEntry 2 } ::= { mplsLpsMeConfigEntry 2 }
-- --
-- MPLS Linear Protection ME Status Table -- MPLS Linear Protection ME Status Table.
-- This table provides Protection Switching ME statistics. -- This table provides protection switching ME statistics.
-- --
mplsLpsMeStatusTable OBJECT-TYPE mplsLpsMeStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLpsMeStatusEntry SYNTAX SEQUENCE OF MplsLpsMeStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains status information of all the MEs "This table contains status information of all the MEs
that are included in MPLS-TP linear protection domains." that are included in MPLS-TP linear protection domains."
::= { mplsLpsObjects 5 } ::= { mplsLpsObjects 5 }
mplsLpsMeStatusEntry OBJECT-TYPE mplsLpsMeStatusEntry OBJECT-TYPE
SYNTAX MplsLpsMeStatusEntry SYNTAX MplsLpsMeStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the mplsLpsMeStatusTable." "A conceptual row in the mplsLpsMeStatusTable."
AUGMENTS { mplsLpsMeConfigEntry } AUGMENTS { mplsLpsMeConfigEntry }
::= { mplsLpsMeStatusTable 1 } ::= { mplsLpsMeStatusTable 1 }
MplsLpsMeStatusEntry ::= SEQUENCE { MplsLpsMeStatusEntry ::= SEQUENCE {
mplsLpsMeStatusCurrent BITS, mplsLpsMeStatusCurrent BITS,
mplsLpsMeStatusSignalDegrades Counter32, mplsLpsMeStatusSignalDegrades Counter32,
mplsLpsMeStatusSignalFailures Counter32, mplsLpsMeStatusSignalFailures Counter32,
mplsLpsMeStatusSwitchovers Counter32, mplsLpsMeStatusSwitchovers Counter32,
mplsLpsMeStatusLastSwitchover TimeStamp, mplsLpsMeStatusLastSwitchover TimeStamp,
mplsLpsMeStatusSwitchoverSeconds Counter32 mplsLpsMeStatusSwitchoverSeconds Counter32
} }
mplsLpsMeStatusCurrent OBJECT-TYPE mplsLpsMeStatusCurrent OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
localSelectTraffic(0), localSelectTraffic(0),
localSD(1), localSD(1),
localSF(2) localSF(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the current state of the ME. "Indicates the current state of the ME.
localSelectTraffic localSelectTraffic
This bit indicates that traffic is being selected from This bit indicates that traffic is being selected from
this ME. this ME.
localSD localSD
This bit implies that local signal degrade condition is This bit implies that a local Signal Degrade condition is
in effect on this ME / path. in effect on this ME/path.
localSF localSF
This bit implies that local signal failure condition is This bit implies that a local Signal Fail condition is
in effect on this ME / path." in effect on this ME/path."
REFERENCE REFERENCE
"Section 4.3 of RFC6378 and Section 7 of RFC7271" "Section 4.3 of RFC 6378 and Section 7 of RFC 7271"
::= { mplsLpsMeStatusEntry 1 } ::= { mplsLpsMeStatusEntry 1 }
mplsLpsMeStatusSignalDegrades OBJECT-TYPE mplsLpsMeStatusSignalDegrades OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the count of Signal Degrade conditions. "Represents the count of Signal Degrade conditions.
For the detection and clearance of Signal Degrade, For the detection and clearance of Signal Degrade,
see the description of mplsLpsConfigSdThreshold." see the description of mplsLpsConfigSdThreshold."
REFERENCE REFERENCE
"Section 7 of RFC7271" "Section 7 of RFC 7271"
::= { mplsLpsMeStatusEntry 2 } ::= { mplsLpsMeStatusEntry 2 }
mplsLpsMeStatusSignalFailures OBJECT-TYPE mplsLpsMeStatusSignalFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the count of Signal failure conditions. "Represents the count of Signal Fail conditions.
This condition occurs when the OAM running on this ME This condition occurs when the OAM running on this ME
detects the Signal Fail event." detects the Signal Fail event."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC 6378"
::= { mplsLpsMeStatusEntry 3 } ::= { mplsLpsMeStatusEntry 3 }
mplsLpsMeStatusSwitchovers OBJECT-TYPE mplsLpsMeStatusSwitchovers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the count of SwitchOvers happened in this ME. "Represents the count of switchovers that happened in this ME.
When the mplsLpsMeConfigPath is working, this object will
return the number of times that traffic has been switched
from this working path to the protection path.
When the mplsLpsMeConfigPath is protection, this object When the mplsLpsMeConfigPath value is 'working', this object
will return the number of times that traffic has been will return the number of times that traffic has been
switched from this working path to the protection path.
When the mplsLpsMeConfigPath value is 'protection', this
object will return the number of times that traffic has been
switched back to the working path from this protection path." switched back to the working path from this protection path."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC 6378"
::= { mplsLpsMeStatusEntry 4 } ::= { mplsLpsMeStatusEntry 4 }
mplsLpsMeStatusLastSwitchover OBJECT-TYPE mplsLpsMeStatusLastSwitchover OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the value of sysUpTime wherein the "This object holds the value of sysUpTime at the time that
last switchover happened. the last switchover happened.
When the mplsLpsMeConfigPath is working, this object When the mplsLpsMeConfigPath value is 'working', this object
will return the value of sysUpTime when traffic was switched will return the value of sysUpTime when traffic was switched
from this path to the protection path. from this path to the protection path.
If traffic has never switched to the protection path, the If traffic has never switched to the protection path, the
value 0 will be returned. value 0 will be returned.
When the mplsLpsMeConfigPath is protection, this object When the mplsLpsMeConfigPath value is 'protection', this
will return the value of sysUpTime the last time that object will return the value of sysUpTime the last time that
traffic was switched back to the working path from this path. traffic was switched back to the working path from this path.
If no traffic has ever switched back to the working path from If no traffic has ever switched back to the working path from
this protection path, the value 0 will be returned." this protection path, the value 0 will be returned."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC 6378"
::= { mplsLpsMeStatusEntry 5 } ::= { mplsLpsMeStatusEntry 5 }
mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The cumulative Protection Switching Duration (PSD) time "The cumulative Protection Switching Duration (PSD) time
in seconds. in seconds.
For the working path, this is the cumulative number of For the working path, this is the cumulative number of
seconds that traffic was selected from the protection path. seconds that traffic was selected from the protection path.
For the protection path, this is the cumulative number For the protection path, this is the cumulative number
of seconds that the working path has been used to of seconds that the working path has been used to
select traffic." select traffic."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC 6378"
::= { mplsLpsMeStatusEntry 6 } ::= { mplsLpsMeStatusEntry 6 }
mplsLpsNotificationEnable OBJECT-TYPE mplsLpsNotificationEnable OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
switchover(0), switchover(0),
revertiveMismatch(1), revertiveMismatch(1),
protecTypeMismatch(2), protecTypeMismatch(2),
capabilitiesMismatch(3), capabilitiesMismatch(3),
pathConfigMismatch(4), pathConfigMismatch(4),
fopNoResponse(5), fopNoResponse(5),
fopTimeout(6) fopTimeout(6)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Provides the ability to enable and disable notifications "Provides the ability to enable and disable notifications
defined in this MIB module. defined in this MIB module.
switchover switchover
Indicates mplsLpsEventSwitchover notifications should be Indicates that mplsLpsEventSwitchover notifications should be
generated. generated.
revertiveMismatch revertiveMismatch
Indicates mplsLpsEventRevertiveMismatch notifications Indicates that mplsLpsEventRevertiveMismatch notifications
should be generated. should be generated.
protecTypeMismatch protecTypeMismatch
Indicates mplsLpsEventProtecTypeMismatch notifications Indicates that mplsLpsEventProtecTypeMismatch notifications
should be generated. should be generated.
capabilitiesMismatch capabilitiesMismatch
Indicates mplsLpsEventCapabilitiesMismatch notifications Indicates that mplsLpsEventCapabilitiesMismatch notifications
should be generated. should be generated.
pathConfigMismatch pathConfigMismatch
Indicates mplsLpsEventPathConfigMismatch notifications Indicates that mplsLpsEventPathConfigMismatch notifications
should be generated. should be generated.
fopNoResponse fopNoResponse
Indicates mplsLpsEventFopNoResponse notifications Indicates that mplsLpsEventFopNoResponse notifications should
should be generated. be generated.
fopTimeout fopTimeout
Indicates mplsLpsEventFopTimeout notifications Indicates that mplsLpsEventFopTimeout notifications should be
should be generated." generated."
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC 7271"
DEFVAL { { } } DEFVAL { { } }
::= { mplsLpsObjects 6 } ::= { mplsLpsObjects 6 }
-- MPLS Linear Protection EVENTS -- MPLS Linear Protection EVENTS.
mplsLpsEventSwitchover NOTIFICATION-TYPE mplsLpsEventSwitchover NOTIFICATION-TYPE
OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent } OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An mplsLpsEventSwitchover notification is sent when the "An mplsLpsEventSwitchover notification is sent when the
value of an instance of mplsLpsMeStatusSwitchovers value of an instance of mplsLpsMeStatusSwitchovers
increments." increments."
::= { mplsLpsNotifications 1 } ::= { mplsLpsNotifications 1 }
skipping to change at page 34, line 36 skipping to change at page 38, line 34
mplsLpsCompliances mplsLpsCompliances
OBJECT IDENTIFIER ::= { mplsLpsConformance 1 } OBJECT IDENTIFIER ::= { mplsLpsConformance 1 }
mplsLpsGroups mplsLpsGroups
OBJECT IDENTIFIER ::= { mplsLpsConformance 2 } OBJECT IDENTIFIER ::= { mplsLpsConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
mplsLpsModuleFullCompliance MODULE-COMPLIANCE mplsLpsModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "Compliance statement for agents that provide full support for
support for MPLS-LPS-MIB. Such devices can the MPLS-LPS-MIB module. Such devices can provide linear
provide linear protection and also be configured using protection and also be configured using this MIB module."
this MIB module." MODULE -- this module
MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLpsScalarGroup, mplsLpsScalarGroup,
mplsLpsTableGroup, mplsLpsTableGroup,
mplsLpsMeTableGroup mplsLpsMeTableGroup
} }
GROUP mplsLpsNotificationGroup GROUP mplsLpsNotificationGroup
DESCRIPTION DESCRIPTION
"This group is only mandatory for those "This group is only mandatory for those
implementations which can efficiently implement implementations that can efficiently implement
the notifications contained in this group." the notifications contained in this group."
::= { mplsLpsCompliances 1 } ::= { mplsLpsCompliances 1 }
-- Compliance requirement for read-only implementations -- Compliance requirement for read-only implementations.
mplsLpsModuleReadOnlyCompliance MODULE-COMPLIANCE mplsLpsModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that only provide "Compliance statement for agents that only provide
read-only support for the MPLS-LPS-MIB module." read-only support for the MPLS-LPS-MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {
MANDATORY-GROUPS {
mplsLpsScalarGroup, mplsLpsScalarGroup,
mplsLpsTableGroup, mplsLpsTableGroup,
mplsLpsMeTableGroup mplsLpsMeTableGroup
} }
GROUP mplsLpsNotificationGroup GROUP mplsLpsNotificationGroup
DESCRIPTION DESCRIPTION
"This group is only mandatory for those "This group is only mandatory for those
implementations which can efficiently implement implementations that can efficiently implement
the notifications contained in this group." the notifications contained in this group."
-- mplsLpsConfigTable -- mplsLpsConfigTable
OBJECT mplsLpsConfigMode OBJECT mplsLpsConfigMode
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigProtectionType OBJECT mplsLpsConfigProtectionType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigRevertive OBJECT mplsLpsConfigRevertive
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigSdThreshold OBJECT mplsLpsConfigSdThreshold
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigSdBadSeconds OBJECT mplsLpsConfigSdBadSeconds
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigSdGoodSeconds OBJECT mplsLpsConfigSdGoodSeconds
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigWaitToRestore OBJECT mplsLpsConfigWaitToRestore
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigContinualTxInterval OBJECT mplsLpsConfigContinualTxInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigRapidTxInterval OBJECT mplsLpsConfigRapidTxInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigCommand OBJECT mplsLpsConfigCommand
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigRowStatus OBJECT mplsLpsConfigRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigStorageType OBJECT mplsLpsConfigStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- mplsLpsMeConfigTable -- mplsLpsMeConfigTable
OBJECT mplsLpsMeConfigDomain OBJECT mplsLpsMeConfigDomain
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsMeConfigPath OBJECT mplsLpsMeConfigPath
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLpsCompliances 2 } ::= { mplsLpsCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLpsScalarGroup OBJECT-GROUP mplsLpsScalarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLpsConfigDomainIndexNext, mplsLpsConfigDomainIndexNext,
mplsLpsNotificationEnable mplsLpsNotificationEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS Linear Protection." "Collection of objects needed for MPLS linear protection."
::= { mplsLpsGroups 1 } ::= { mplsLpsGroups 1 }
mplsLpsTableGroup OBJECT-GROUP mplsLpsTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLpsConfigDomainName, mplsLpsConfigDomainName,
mplsLpsConfigRowStatus, mplsLpsConfigRowStatus,
mplsLpsConfigMode, mplsLpsConfigMode,
mplsLpsConfigProtectionType, mplsLpsConfigProtectionType,
mplsLpsConfigRevertive, mplsLpsConfigRevertive,
mplsLpsConfigSdThreshold, mplsLpsConfigSdThreshold,
skipping to change at page 37, line 51 skipping to change at page 42, line 13
mplsLpsStatusFpathPathSent, mplsLpsStatusFpathPathSent,
mplsLpsStatusRevertiveMismatch, mplsLpsStatusRevertiveMismatch,
mplsLpsStatusProtecTypeMismatch, mplsLpsStatusProtecTypeMismatch,
mplsLpsStatusCapabilitiesMismatch, mplsLpsStatusCapabilitiesMismatch,
mplsLpsStatusPathConfigMismatch, mplsLpsStatusPathConfigMismatch,
mplsLpsStatusFopNoResponses, mplsLpsStatusFopNoResponses,
mplsLpsStatusFopTimeouts mplsLpsStatusFopTimeouts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS Linear Protection "Collection of objects needed for MPLS linear protection
configuration and statistics." configuration and statistics."
::= { mplsLpsGroups 2 } ::= { mplsLpsGroups 2 }
mplsLpsMeTableGroup OBJECT-GROUP mplsLpsMeTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLpsMeConfigDomain, mplsLpsMeConfigDomain,
mplsLpsMeConfigPath, mplsLpsMeConfigPath,
mplsLpsMeStatusCurrent, mplsLpsMeStatusCurrent,
mplsLpsMeStatusSignalDegrades, mplsLpsMeStatusSignalDegrades,
mplsLpsMeStatusSignalFailures, mplsLpsMeStatusSignalFailures,
mplsLpsMeStatusSwitchovers, mplsLpsMeStatusSwitchovers,
mplsLpsMeStatusLastSwitchover, mplsLpsMeStatusLastSwitchover,
mplsLpsMeStatusSwitchoverSeconds mplsLpsMeStatusSwitchoverSeconds
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS Linear Protection "Collection of objects needed for MPLS linear protection
ME configuration and statistics." ME configuration and statistics."
::= { mplsLpsGroups 3 } ::= { mplsLpsGroups 3 }
mplsLpsNotificationGroup NOTIFICATION-GROUP mplsLpsNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
mplsLpsEventSwitchover, mplsLpsEventSwitchover,
mplsLpsEventRevertiveMismatch, mplsLpsEventRevertiveMismatch,
mplsLpsEventProtecTypeMismatch, mplsLpsEventProtecTypeMismatch,
mplsLpsEventCapabilitiesMismatch, mplsLpsEventCapabilitiesMismatch,
mplsLpsEventPathConfigMismatch, mplsLpsEventPathConfigMismatch,
mplsLpsEventFopNoResponse, mplsLpsEventFopNoResponse,
mplsLpsEventFopTimeout mplsLpsEventFopTimeout
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement notifications." "Collection of objects needed to implement notifications."
::= { mplsLpsGroups 4 } ::= { mplsLpsGroups 4 }
-- MPLS-LPS-MIB module ends -- MPLS-LPS-MIB module ends
END END
9. Security Considerations 9. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some networks in objects may be considered sensitive or vulnerable in some network
a non-secure environment without proper protection can have a environments. The support for SET operations in a non-secure
negative effect on network operations. These are the tables and environment without proper protection opens devices to attack. These
objects and their sensitivity/vulnerability: are the tables and objects and their sensitivity/vulnerability:
o mplsLpsConfigTable is used to configure MPLS-TP linear protection o The mplsLpsConfigTable is used to configure MPLS-TP linear
domains. Improper manipulation of the objects in this table may protection domains. Improper manipulation of the objects in this
result in different behaviors than network operators have table may result in different behaviors than what network
originally intended, such as delaying traffic switching or causing operators originally intended, such as delaying traffic switching
a race condition with server layer protection after network or causing a race condition with server-layer protection after
failure (mplsLpsConfigHoldOff), delaying or speeding up reversion network failure (mplsLpsConfigHoldOff), delaying or speeding up
after recovering network failure (mplsLpsConfigWaitToRestore), reversion after recovering from network failure
unexpected traffic switching (mplsLpsConfigCommand), or (mplsLpsConfigWaitToRestore), unexpected traffic switching
discontinuance of operation of a protection switching control (mplsLpsConfigCommand), or the discontinuance of the operation of
process (mplsLpsConfigMode, mplsLpsConfigProtectionType). a protection switching control process (mplsLpsConfigMode,
mplsLpsConfigProtectionType).
o mplsLpsMeConfigTable is used to assign each ME either working or o The mplsLpsMeConfigTable is used to assign each ME to either the
protection path. Improper manipulation of this object may result working path or the protection path. Improper manipulation of
in discontinuance of operation of a protection switching control this object may result in the discontinuance of the operation of a
process. protection switching control process.
o The notification is controlled by mplsLpsNotificationEnable o The notification is controlled by the mplsLpsNotificationEnable
object. In the case of the discontinuance of a protection object. In the case of the discontinuance of a protection
switching control process, network operators may not be notified switching control process, network operators may not be notified
if the mplsLpsNotificationEnable object is compromised. if the mplsLpsNotificationEnable object is compromised.
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:
o mplsLpsStatusTable and mplsLpsMeStatusTable collectively show the o The mplsLpsStatusTable and the mplsLpsMeStatusTable collectively
history and current status of the MPLS-TP linear protection show the history and current status of the MPLS-TP linear
domains. They can be used to estimate the performances and protection domains. They can be used to estimate the performance
qualities of the network being operated with the MPLS-TP linear and qualities of networks configured to use MPLS-TP linear
protection. If an administrator does not want to reveal this protection. If an administrator does not want to reveal this
information, then these tables should be considered sensitive/ information, then these tables should be considered
vulnerable. sensitive/vulnerable.
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),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
Implementations SHOULD provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM) authentication and privacy via the User-based Security Model (USM)
RFC 3414 [RFC3414] with the AES cipher algorithm RFC 3826 [RFC3826]. [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
Implementations MAY also provide support for the Transport Security [RFC5591] in combination with a secure transport such as SSH
Model (TSM) RFC 5591 [RFC5591] in combination with a secure transport [RFC5592] or TLS/DTLS [RFC6353].
such as SSH RFC 5592 [RFC5592] or TLS/DTLS RFC 6353 [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is not Further, deployment of SNMP versions prior to SNMPv3 is
recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to NOT 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.
10. IANA Considerations 10. IANA Considerations
IANA is requested to assign an OID for the MIB module from the "MIB IANA has assigned an OID of decimal 22 for the MPLS Linear Protection
Transmission Group - MPLS STD" sub-registry of the "Internet-standard MIB module (MPLS-LPS-MIB) specified in this document in the "MIB
MIB - Transmission Group" registry for the MPLS Linear Protection MIB Transmission Group - MPLS STD MIB" subregistry of the
module specified in this document. "Internet-standard MIB - Transmission Group" registry.
11. Contributing Authors
Vishwas Manral
Nano Sec
599 Fairchild Drive
Mountain View, CA
USA
EMail: vishwas@nanosec.io
12. Acknowledgments
The authors wish to thank Joan Cucchiara for her review as MIB
Doctor. Joan's detailed comments were of great help for improving
the quality of this document.
The authors would also like to thank Loa Andersson and Adrian Farrel
for their valuable comments and suggestion on this document.
13. References 11. References
13.1. Normative References 11.1. Normative 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", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, Version 2 (SMIv2)", STD 58, RFC 2578,
DOI 10.17487/RFC2578, April 1999, DOI 10.17487/RFC2578, April 1999,
skipping to change at page 41, line 38 skipping to change at page 45, line 47
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
DOI 10.17487/RFC3411, December 2002, DOI 10.17487/RFC3411, December 2002,
<http://www.rfc-editor.org/info/rfc3411>. <http://www.rfc-editor.org/info/rfc3411>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, Protocol (SNMPv3)", STD 62, RFC 3414,
DOI 10.17487/RFC3414, December 2002, DOI 10.17487/RFC3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>. <http://www.rfc-editor.org/info/rfc3414>.
[RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of
Textual Conventions (TCs) for Multiprotocol Label Textual Conventions (TCs) for Multiprotocol Label
Switching (MPLS) Management", RFC 3811, Switching (MPLS) Management", RFC 3811,
DOI 10.17487/RFC3811, June 2004, DOI 10.17487/RFC3811, June 2004,
<http://www.rfc-editor.org/info/rfc3811>. <http://www.rfc-editor.org/info/rfc3811>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, SNMP User-based Security Model", RFC 3826,
DOI 10.17487/RFC3826, June 2004, DOI 10.17487/RFC3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>. <http://www.rfc-editor.org/info/rfc3826>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>. <http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592,
2009, <http://www.rfc-editor.org/info/rfc5592>. June 2009, <http://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
<http://www.rfc-editor.org/info/rfc6353>. <http://www.rfc-editor.org/info/rfc6353>.
[RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher, [RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher,
N., and A. Fulignoli, Ed., "MPLS Transport Profile (MPLS- N., and A. Fulignoli, Ed., "MPLS Transport Profile
TP) Linear Protection", RFC 6378, DOI 10.17487/RFC6378, (MPLS-TP) Linear Protection", RFC 6378,
October 2011, <http://www.rfc-editor.org/info/rfc6378>. DOI 10.17487/RFC6378, October 2011,
<http://www.rfc-editor.org/info/rfc6378>.
[RFC7271] Ryoo, J., Ed., Gray, E., Ed., van Helvoort, H., [RFC7271] Ryoo, J., Ed., Gray, E., Ed., van Helvoort, H.,
D'Alessandro, A., Cheung, T., and E. Osborne, "MPLS D'Alessandro, A., Cheung, T., and E. Osborne, "MPLS
Transport Profile (MPLS-TP) Linear Protection to Match the Transport Profile (MPLS-TP) Linear Protection to Match the
Operational Expectations of Synchronous Digital Hierarchy, Operational Expectations of Synchronous Digital Hierarchy,
Optical Transport Network, and Ethernet Transport Network Optical Transport Network, and Ethernet Transport Network
Operators", RFC 7271, DOI 10.17487/RFC7271, June 2014, Operators", RFC 7271, DOI 10.17487/RFC7271, June 2014,
<http://www.rfc-editor.org/info/rfc7271>. <http://www.rfc-editor.org/info/rfc7271>.
[RFC7697] Pan, P., Aldrin, S., Venkatesan, M., Sampath, K., Nadeau, [RFC7697] Pan, P., Aldrin, S., Venkatesan, M., Sampath, K., Nadeau,
T., and S. Boutros, "MPLS Transport Profile (MPLS-TP) T., and S. Boutros, "MPLS Transport Profile (MPLS-TP)
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Identifiers Management Information Base (MIB)", RFC 7697, Identifiers Management Information Base (MIB)", RFC 7697,
DOI 10.17487/RFC7697, January 2016, DOI 10.17487/RFC7697, January 2016,
<http://www.rfc-editor.org/info/rfc7697>. <http://www.rfc-editor.org/info/rfc7697>.
13.2. Informative References 11.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
Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
DOI 10.17487/RFC3410, December 2002, DOI 10.17487/RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>. <http://www.rfc-editor.org/info/rfc3410>.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic Engineering "Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB)", RFC 3812, (TE) Management Information Base (MIB)", RFC 3812,
DOI 10.17487/RFC3812, June 2004, DOI 10.17487/RFC3812, June 2004,
<http://www.rfc-editor.org/info/rfc3812>. <http://www.rfc-editor.org/info/rfc3812>.
[G8121] International Telecommunication Union, "Characteristics of [G8121] International Telecommunication Union, "Characteristics of
MPLS-TP equipment functional blocks", ITU-T Recommendation MPLS-TP equipment functional blocks", ITU-T Recommendation
G.8121/Y.1381, April 2016. G.8121/Y.1381, April 2016,
<https://www.itu.int/rec/T-REC-G.8121/en>.
[G8151] International Telecommunication Union, "Management aspects [G8151] International Telecommunication Union, "Management aspects
of the MPLS-TP network element", ITU-T Recommendation of the MPLS-TP network element", ITU-T Recommendation
G.8151/Y.1374, January 2015. G.8151/Y.1374, January 2015,
<https://www.itu.int/rec/T-REC-G.8151/en>.
Acknowledgments
The authors wish to thank Joan Cucchiara for her review as MIB
Doctor. Joan's detailed comments were of great help for improving
the quality of this document.
The authors would also like to thank Loa Andersson and Adrian Farrel
for their valuable comments and suggestions on this document.
Contributors
Vishwas Manral
Nano Sec
599 Fairchild Drive
Mountain View, CA
United States of America
Email: vishwas@nanosec.io
Authors' Addresses Authors' Addresses
Kingston Smiler Selvaraj Kingston Selvaraj
IpInfusion IP Infusion
RMZ Centennial RMZ Centennial
Mahadevapura Post Mahadevapura Post
Bangalore - 560048 Bangalore 560048
India India
EMail: kingstonsmiler@gmail.com Email: kingstonsmiler@gmail.com
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc. Dell Technologies
5450 Great America Parkway 5450 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA United States of America
EMail: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK United Kingdom
EMail: daniel@olddog.co.uk Email: daniel@olddog.co.uk
Sam Aldrin Sam Aldrin
Google, Inc. Google, Inc.
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, CA Mountain View, CA 94043
USA United States of America
Email: aldrin.ietf@gmail.com
EMail: aldrin.ietf@gmail.com
Jeong-dong Ryoo Jeong-dong Ryoo
ETRI ETRI
218 Gajeong-ro 218 Gajeong-ro
Yuseong-gu, Daejeon 34129 Yuseong-gu, Daejeon 34129
South Korea South Korea
EMail: ryoo@etri.re.kr Email: ryoo@etri.re.kr
 End of changes. 298 change blocks. 
649 lines changed or deleted 659 lines changed or added

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