draft-ietf-mpls-tp-linear-protection-mib-04.txt   draft-ietf-mpls-tp-linear-protection-mib-05.txt 
Internet Engineering Task Force Kingston Smiler Selvaraj Internet Engineering Task Force Kingston Smiler Selvaraj
Internet-Draft IpInfusion Internet-Draft IpInfusion
Intended status: Standards Track M.Venkatesan Intended status: Standards Track M.Venkatesan
Expires: August 06, 2015 Dell Inc. Expires: February 04, 2016 Dell Inc.
V. Manral V. Manral
Hewlett-Packard Corp Ionos Corp.
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
Sam Aldrin Sam Aldrin
Huawei Technologies Google, Inc.
February 02, 2015 August 03, 2015
MPLS Transport Profile Linear Protection MIB MPLS Transport Profile Linear Protection MIB
draft-ietf-mpls-tp-linear-protection-mib-04 draft-ietf-mpls-tp-linear-protection-mib-05
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 MPLS Transport Profile (MPLS-TP) Linear objects for managing MPLS Transport Profile (MPLS-TP) Linear
Protection. Protection.
Status of This Memo Status of This Memo
skipping to change at page 1, line 46 skipping to change at page 1, line 46
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 06, 2015. This Internet-Draft will expire on February 04, 2016.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 33 skipping to change at page 2, line 33
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 Subtree . . . . . . . . . . . 4
5.3. The Notifications Subtree . . . . . . . . . . . . . . . . . 4 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . . 4
5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4 5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5
6.1. Relationship to the MPLS OAM maintenance identifiers MIB 6.1. Relationship to the MPLS OAM maintenance identifiers MIB
module . . . . . . . . . . . . . . . . . . . . . . . . . . 5 module . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Example of Protection switching configuration for MPLS-TP TE 7. Example of Protection switching configuration for MPLS-TP TE
tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7
9. Security Considerations . . . . . . . . . . . . . . . . . . . 27 9. Security Considerations . . . . . . . . . . . . . . . . . . . 26
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
11.1. Normative References . . . . . . . . . . . . . . . . . . 28 11.1. Normative References . . . . . . . . . . . . . . . . . . 28
11.2. Informative References . . . . . . . . . . . . . . . . . 29 11.2. Informative References . . . . . . . . . . . . . . . . . 29
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30
13. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 30 13. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 30
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
skipping to change at page 4, line 7 skipping to change at page 4, line 7
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview 4. Overview
[RFC6378] defines the protocol to provide a linear protection [RFC6378] defines the protocol to provide a linear protection
switching mechanism for MPLS transport profile with protection switching mechanism for MPLS transport profile with protection
domain as point-to-point LSP. The detailed protocol specification of domain as point-to-point LSP. The detailed protocol specification of
MPLS transport profile linear protection is described in [RFC6378]. MPLS transport profile linear protection is described in [RFC6378].
This document specifies a MIB module for the LER that supports MPLS This document specifies a MIB module for the LER that supports MPLS
TP Linear protection (which includes 1:n protection architecture) TP Linear protection and a MIB module that defines textual
and a MIB module that defines textual conventions. conventions.
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 a separate MIB The following new textual conventions are defined in a separate MIB
module in this document module in this document
MplsLpsReq MplsLpsReq
MplsLpsFpathPath MplsLpsFpathPath
skipping to change at page 7, line 40 skipping to change at page 7, line 40
FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex
FROM MPLS-OAM-ID-STD-MIB; FROM MPLS-OAM-ID-STD-MIB;
mplsLpsMIB MODULE-IDENTITY mplsLpsMIB MODULE-IDENTITY
LAST-UPDATED "201301210000Z" -- January 21, 2013 LAST-UPDATED "201508030000Z" -- August 03, 2015
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Kingston Smiler Selvaraj Kingston Smiler
Ipinfusion IP Infusion
Email:kingstons@ipinfusion.com RMZ Centennial
Mahadevapura Post
Venkatesan Mahalingam Bangalore - 560048 India
Dell Inc. EMail: kingstonsmiler@gmail.com
350 Holger way, San Jose, CA, USA Venkatesan Mahalingam
Email: venkat.mahalingams@gmail.com Dell Inc.
5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
Vishwas Manral Vishwas Manral
Hewlet-Packard, Inc. Ionos Corp,
19111 Pruneridge Ave., Cupertino, CA, 95014 4100 Moorpark Ave,
Phone: 408-447-1497 San Jose, CA
Email: vishwas.manral@hp.com Email: vishwas@ionosnetworks.com
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK UK
Email:daniel@olddog.co.uk Email:daniel@olddog.co.uk
Sam Aldrin Sam Aldrin
Huawei Technologies, co. Google, Inc.
2330 Central Express Way, 1600 Amphitheatre Parkway
Santa Clara, CA 95051, USA Mountain View, CA
Email: aldrin.ietf@gmail.com" USA
Email: aldrin.ietf@gmail.com"
DESCRIPTION DESCRIPTION
"This management information module supports the "This management information module supports the
configuration and management of MPLS TP linear configuration and management of MPLS TP linear
protection groups. " protection groups. "
REVISION REVISION
"201301210000Z" -- January 21, 2013 "201508030000Z" -- August 03, 2015
DESCRIPTION DESCRIPTION
"MPLS Protection Switching Group objects for LSP "MPLS Protection Switching Group objects for LSP
MEPs" MEPs"
::= { mplsStdMIB xxx } -- xxx to be replaced with ::= { mplsStdMIB xxx } -- xxx to be replaced with
-- correct value -- correct value
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Notifications -- Notifications
mplsLpsNotifications mplsLpsNotifications
skipping to change at page 12, line 28 skipping to change at page 12, line 28
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Textual name represents the mpls tp protection group. "Textual name represents the mpls tp protection group.
Each Protection Group is identified by a unique Each Protection Group is identified by a unique
protection group name. " protection group name. "
::= { mplsLpsConfigEntry 2 } ::= { mplsLpsConfigEntry 2 }
mplsLpsConfigMode OBJECT-TYPE mplsLpsConfigMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
onePlusOne(1), onePlusOne(1),
oneColonOne(2), oneColonOne(2)
oneColonN(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The architectural mode of the Protection group. This can "The architectural mode of the Protection group. This can
either be 1+1, 1:1, 1:n. either be 1+1, 1:1.
1+1 1+1
In the 1+1 protection scheme, a fully dedicated In the 1+1 protection scheme, a fully dedicated
protection entity is allocated. Data traffic is copied protection entity is allocated. Data traffic is copied
and fed at the source to both the working and the and fed at the source to both the working and the
protection entities. The traffic on the working and the protection entities. The traffic on the working and the
protection entities is transmitted simultaneously to protection entities is transmitted simultaneously to
the sink of the protection domain, where selection the sink of the protection domain, where selection
between the working and protection entities is performed between the working and protection entities is performed
1:1 1:1
In the 1:1 scheme, a protection path is allocated to In the 1:1 scheme, a protection path is allocated to
protect against a defect, failure, or a degradation in a protect against a defect, failure, or a degradation in a
skipping to change at page 13, line 8 skipping to change at page 13, line 6
1:1 1:1
In the 1:1 scheme, a protection path is allocated to In the 1:1 scheme, a protection path is allocated to
protect against a defect, failure, or a degradation in a protect against a defect, failure, or a degradation in a
working path. In normal conditions, data traffic is working path. In normal conditions, data traffic is
transmitted over the working entity, while the transmitted over the working entity, while the
protection entity functions in the idle state. If there protection entity functions in the idle state. If there
is a defect on the working entity or a specific is a defect on the working entity or a specific
administrative request, traffic is switched to the administrative request, traffic is switched to the
protection entity. protection entity."
1:n
In case of 1:n linear protection, one protection entity
is allocated to protect n working entities. The protection
entity might not have sufficient resources to protect all the
working entities that may be affected by fault conditions at a
specific time. In this case, in order to guaranteed
protection, the protection entity should support enough
capacity and bandwidth to protect any of the n working
entities."
DEFVAL {onePlusOne} DEFVAL {onePlusOne}
::= { mplsLpsConfigEntry 3 } ::= { mplsLpsConfigEntry 3 }
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
skipping to change at page 13, line 31 skipping to change at page 13, line 18
DEFVAL {onePlusOne} DEFVAL {onePlusOne}
::= { mplsLpsConfigEntry 3 } ::= { mplsLpsConfigEntry 3 }
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 Switching group. The reversion mode of Protection Switching group. The reversion mode of
protection mechanism may be either revertive or protection mechanism may be either revertive or
non-revertive. non-revertive.
nonrevertive nonrevertive
In non-revertive mode, after a service has been In non-revertive mode, after a service has been
recovered, traffic will be forwarded on the recovery recovered, traffic will be forwarded on the recovery
path.
path
revertive revertive
In revertive mode, after a service has been In revertive mode, after a service has been
recovered, traffic will be redirected back onto the recovered, traffic will be redirected back onto the
original working path." original working path."
DEFVAL { nonrevertive } DEFVAL { nonrevertive }
::= { mplsLpsConfigEntry 4 } ::= { mplsLpsConfigEntry 4 }
skipping to change at page 15, line 41 skipping to change at page 15, line 24
SYNTAX Integer32 (1000..20000) SYNTAX Integer32 (1000..20000)
UNITS "micro-seconds" UNITS "micro-seconds"
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 micro-Seconds. Represents the time
interval to send the LPS packet to the other end, when interval to send the LPS packet to the other end, when
there is a change in state of Linear Protection domain due there is a change in state of Linear Protection domain due
to local input. The default value is 3.3 milli-seconds to local input. The default value is 3.3 milli-seconds
which is 3300 micro-seconds" which is 3300 micro-seconds"
DEFVAL { 3300 } DEFVAL { 3300 }
::= { mplsLpsConfigEntry 9 } ::= { mplsLpsConfigEntry 9 }
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 "The value of sysUpTime at the time the row was
created" created."
::= { mplsLpsConfigEntry 10 } ::= { mplsLpsConfigEntry 10 }
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 represents the status of the MPLS TP Linear
Protection group Entry. This variable is used to Protection group 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.
skipping to change at page 17, line 22 skipping to change at page 17, line 4
mplsLpsStatusFpathPathSent MplsLpsFpathPath, mplsLpsStatusFpathPathSent MplsLpsFpathPath,
mplsLpsStatusModeMismatches Counter32 mplsLpsStatusModeMismatches Counter32
} }
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
more recent PSC packet" more recent PSC packet."
::= { mplsLpsStatusEntry 1 } ::= { mplsLpsStatusEntry 1 }
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
more recent PSC packet" more recent PSC packet."
::= { mplsLpsStatusEntry 2 } ::= { mplsLpsStatusEntry 2 }
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 more recent PSC packet" on more recent PSC packet."
::= { mplsLpsStatusEntry 3 } ::= { mplsLpsStatusEntry 3 }
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 more recent PSC packet" on more recent PSC packet."
::= { mplsLpsStatusEntry 4 } ::= { mplsLpsStatusEntry 4 }
mplsLpsStatusModeMismatches OBJECT-TYPE mplsLpsStatusModeMismatches OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds number of occurrences of mismatch in "This object holds number of occurrences of mismatch in
revertive mode across the protection domain end points." revertive mode across the protection domain end points."
::= { mplsLpsStatusEntry 5 } ::= { mplsLpsStatusEntry 5 }
skipping to change at page 20, line 49 skipping to change at page 20, line 30
mplsLpsMeStatusSwitchoverSeconds Counter32 mplsLpsMeStatusSwitchoverSeconds Counter32
} }
mplsLpsMeStatusCurrent OBJECT-TYPE mplsLpsMeStatusCurrent OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
localLockedOut(0), localLockedOut(0),
localSd(1), localSd(1),
localSf(2), localSf(2),
localSwitched(3), localSwitched(3),
localWtr(4), localWtr(4),
remoteLockedout(5) remoteLockedout(5),
remoteSd(6), remoteSd(6),
remoteSf(7), remoteSf(7),
remoteSwitched(8), remoteSwitched(8),
remoteWtr(9) remoteWtr(9)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the current state of the MA. "Indicates the current state of the MA.
localLockedOut localLockedOut
This bit, when it is set on a working ME or working path This bit, when it is set on a working ME or working path
indicates that the working path is prevented from indicates that the working path is prevented from
switching to the protection path because of local request. switching to the protection path because of local request.
When it is set on protection / backup path, this bit When it is set on protection / backup path, this bit
indicates that none of the working path (in case of indicates that none of the working path can switch
1:n) can switch to the protection path. to the protection path.
localSd localSd
This bit implies that local signal degrade condition is This bit implies that 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 local signal failure condition is
in effect on this ME / path. in effect on this ME / path.
localSwitched localSwitched
This bit is only applicable to the working ME / path. This bit is only applicable to the working ME / path.
It implies that the working path is currently switched It implies that the working path is currently switched
to the protection path because of local request. to the protection path because of local request.
local wtr local wtr
This bit implies that local Wait-to-Restore state is This bit implies that local Wait-to-Restore state is
in effect." in effect.
remoteLockedOut remoteLockedOut
This bit, when it is set on a working ME or working path This bit, when it is set on a working ME or working path
indicates that the working path is prevented from indicates that the working path is prevented from
switching to the protection path because of remote request. switching to the protection path because of remote request.
When it is set on protection / backup path, this bit When it is set on protection / backup path, this bit
indicates that none of the working path (in case of indicates that none of the working path can switch
1:n) can switch to the protection path. to the protection path.
remoteSd remoteSd
This bit implies that remote signal degrade condition is This bit implies that remote signal degrade condition is
in effect on this ME / path. in effect on this ME / path.
remoteSf remoteSf
This bit implies that remote signal failure condition is This bit implies that remote signal failure condition is
in effect on this ME / path. in effect on this ME / path.
remoteSwitched remoteSwitched
skipping to change at page 26, line 14 skipping to change at page 25, line 40
mplsLpsConfigTableGroup OBJECT-GROUP mplsLpsConfigTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLpsConfigGroupName, mplsLpsConfigGroupName,
mplsLpsConfigRowStatus, mplsLpsConfigRowStatus,
mplsLpsConfigMode, mplsLpsConfigMode,
mplsLpsConfigRevertive, mplsLpsConfigRevertive,
mplsLpsConfigProtectionScheme, mplsLpsConfigProtectionScheme,
mplsLpsConfigSdThreshold, mplsLpsConfigSdThreshold,
mplsLpsConfigWaitToRestore, mplsLpsConfigWaitToRestore,
mplsLpsConfigHoldOff,
mplsLpsConfigContinualTxInterval, mplsLpsConfigContinualTxInterval,
mplsLpsConfigRapidTxInterval, mplsLpsConfigRapidTxInterval,
mplsLpsConfigCreationTime, mplsLpsConfigCreationTime,
mplsLpsConfigStorageType, mplsLpsConfigStorageType,
mplsLpsStatusReqRcv, mplsLpsStatusReqRcv,
mplsLpsStatusReqSent, mplsLpsStatusReqSent,
mplsLpsStatusFpathPathRcv, mplsLpsStatusFpathPathRcv,
mplsLpsStatusFpathPathSent, mplsLpsStatusFpathPathSent,
mplsLpsStatusModeMismatches mplsLpsStatusModeMismatches
skipping to change at page 26, line 36 skipping to change at page 26, line 13
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 {
mplsLpsMeConfigState, mplsLpsMeConfigState,
mplsLpsMeConfigCommand, mplsLpsMeConfigCommand,
mplsLpsMeConfigHoldOff,
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."
skipping to change at page 29, line 49 skipping to change at page 29, line 49
[RFC6378] Weingarten, Y., Osborne, E., Sprecher, N., Fulignoli, [RFC6378] Weingarten, Y., Osborne, E., Sprecher, N., Fulignoli,
A., Ed., and Y. Weingarten, Ed., "MPLS-TP Linear A., Ed., and Y. Weingarten, Ed., "MPLS-TP Linear
Protection", October 2011. Protection", October 2011.
[MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath, [MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath,
Thomas D. Nadeau, Sami Boutros, Ping Pan, Thomas D. Nadeau, Sami Boutros, Ping Pan,
"MPLS-TP Operations, Administration, and "MPLS-TP Operations, Administration, and
Management (OAM) Identifiers Management Management (OAM) Identifiers Management
Information Base (MIB)", ID Information Base (MIB)", ID
draft-ietf-mpls-tp-oam-id-mib-07, February 2015. draft-ietf-mpls-tp-oam-id-mib-08, February 2015.
12. Acknowledgments 12. Acknowledgments
The authors wish to thank Joan Cucchiara for her review as MIB The authors wish to thank Joan Cucchiara for her review as MIB
Doctor, Joan's detailed comments were of great help for improving the Doctor, Joan's detailed comments were of great help for improving the
quality of this document. quality of this document.
13. Author's Address 13. Author's Address
Kingston Smiler Selvaraj Kingston Smiler
IpInfusion IP Infusion
India RMZ Centennial
Email: kingstons@ipinfusion.com Mahadevapura Post
Bangalore - 560048 India
EMail: kingstonsmiler@gmail.com
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc. Dell Inc.
350 Holger way, San Jose, CA, USA 5450 Great America Parkway,
Email: venkat.mahalingams@gmail.com Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
Vishwas Manral Vishwas Manral
Hewlet-Packard, Inc. Ionos Corp,
19111 Pruneridge Ave., Cupertino, CA, 95014 4100 Moorpark Ave,
Phone: 408-447-1497 San Jose, CA
Email: vishwas.manral@hp.com Email: vishwas@ionosnetworks.com
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK UK
Email:daniel@olddog.co.uk Email:daniel@olddog.co.uk
Sam Aldrin Sam Aldrin
Huawei Technologies, co. Google, Inc.
2330 Central Express Way, 1600 Amphitheatre Parkway
Santa Clara, CA 95051, USA Mountain View, CA
Email: aldrin.ietf@gmail.com USA
Email: aldrin.ietf@gmail.com"
 End of changes. 41 change blocks. 
89 lines changed or deleted 76 lines changed or added

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