draft-ietf-mpls-tp-oam-id-mib-08.txt   draft-ietf-mpls-tp-oam-id-mib-09.txt 
Network Working Group Network Working Group
INTERNET-DRAFT Sam Aldrin INTERNET-DRAFT Sam Aldrin
Intended Status: Standards Track Google, Inc. Intended Status: Standards Track Google, Inc.
Expires: August 29, 2015 M.Venkatesan Expires: March 1, 2016 M.Venkatesan
Dell, Inc. Dell, Inc.
Kannan KV Sampath Kannan KV Sampath
Redeem Redeem
Thomas D. Nadeau Thomas D. Nadeau
Brocade Brocade
February 26, 2015 September 1, 2015
MPLS-TP Operations, Administration, and Management (OAM) Identifiers MPLS-TP Operations, Administration, and Management (OAM) Identifiers
Management Information Base (MIB) Management Information Base (MIB)
draft-ietf-mpls-tp-oam-id-mib-08 draft-ietf-mpls-tp-oam-id-mib-09
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 the Internet community. for use with network management protocols in the Internet community.
In particular, it describes Operations, Administration, and In particular, it describes managed objects to configure the
Management (OAM) identifiers related managed objects for Operations, Administration, and Management (OAM) identifiers for
Multiprotocol Label Switching (MPLS) and MPLS based Transport Profile Multiprotocol Label Switching (MPLS) and MPLS-based Transport Profile
(TP). (TP).
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 29, 2015. This Internet-Draft will expire on March 4, 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 3, line 10 skipping to change at page 3, line 10
10.1 Normative References . . . . . . . . . . . . . . . . . . . 28 10.1 Normative References . . . . . . . . . . . . . . . . . . . 28
10.2 Informative References . . . . . . . . . . . . . . . . . . 29 10.2 Informative References . . . . . . . . . . . . . . . . . . 29
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30
12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 30 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 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 the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling a In particular, it describes managed objects for modeling a
Multiprotocol Label Switching (MPLS) [RFC3031] based transport Multiprotocol Label Switching- (MPLS) [RFC3031] based transport
profile. profile.
This MIB module should be used for performing the OAM (Operations, This MIB module should be used for performing the OAM (Operations,
Administration, and Maintenance) operations for MPLS LSP(Label Administration, and Maintenance) operations for MPLS Tunnel LSP
Switched Path), Pseudowires and Sections. (Label Switched Path), Pseudowires, and Sections.
At the time of writing, SNMP SET is no longer recommended as a way to At the time of writing, SNMP SET is no longer recommended as a way to
configure MPLS networks as was described in [RFC3812]. However, configure MPLS networks as was described in [RFC3812]. However,
since the MIB modules specified in this document are intended to work since the MIB modules specified in this document are intended to work
in parallel with the MIB modules for MPLS specified in [RFC3812], in parallel with the MIB modules for MPLS specified in [RFC3812],
certain objects defined here are specified with MAX-ACCESS of read- certain objects defined here are specified with MAX-ACCESS of read-
write or read-create so that specifications of the base tables in write or read-create so that specifications of the base tables in
[RFC3812] and the new MIB modules in this document are consistent. [RFC3812] and the new MIB modules in this document are consistent.
Although the examples described in Section 6 specify means to Although the examples described in Section 6 specify means to
configure OAM identifiers for MPLS-TP tunnels, this should be seen as configure OAM identifiers for MPLS-TP tunnels, this should be seen as
skipping to change at page 3, line 40 skipping to change at page 3, line 40
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC3410 [RFC3410]. RFC3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant with the SMIv2, which is described in STD
RFC2578, STD 58, RFC2579 and STD58, RFC2580. 58(RFC2578, RFC2579, RFC2580).
3. Overview 3. Overview
3.1 Conventions used in this document 3.1 Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in RFC
RFC-2119 [RFC2119]. 2119 [RFC2119].
3.2 Terminology 3.2 Terminology
This document uses terminology from the Multiprotocol Label Switching This document uses terminology from the Multiprotocol Label Switching
Architecture [RFC3031], MPLS Traffic Engineering (TE) MIB [RFC3812], Architecture [RFC3031], MPLS Traffic Engineering (TE) MIB [RFC3812],
MPLS Label Switching Router (LSR) MIB [RFC3813], OAM Framework for MPLS Label Switching Router (LSR) MIB [RFC3813], OAM Framework for
MPLS-Based Transport Networks [RFC6371], MPLS Transport Profile MPLS-Based Transport Networks [RFC6371], MPLS Transport Profile
(MPLS-TP) Identifiers [RFC6370], MPLS-TP Identifiers Following ITU-T (MPLS-TP) Identifiers [RFC6370], MPLS-TP Identifiers Following ITU-T
Conventions [RFC6923], and OAM in MPLS Transport Networks [RFC5860]. Conventions [RFC6923], and OAM in MPLS Transport Networks [RFC5860].
3.3 Acronyms 3.3 Acronyms
BFD: Bidirectional Forwarding Detection
ICC: ITU Carrier Code ICC: ITU Carrier Code
IP: Internet Protocol IP: Internet Protocol
LSP: Label Switched Path LSP: Label Switched Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base MIB: Management Information Base
ME: Maintenance Entity ME: Maintenance Entity
MEG: Maintenance Entity Group MEG: Maintenance Entity Group
MEP: Maintenance Entity Group End Point MEP: Maintenance Entity Group End Point
MIP: Maintenance Entity Group Intermediate Point MIP: Maintenance Entity Group Intermediate Point
MPLS: Multi-Protocol Label Switching MPLS: Multi-Protocol Label Switching
MPLS-TP: MPLS Transport Profile MPLS-TP: MPLS Transport Profile
PW: Pseudowire PW: Pseudowire
skipping to change at page 4, line 36 skipping to change at page 4, line 36
TE: Traffic Engineering TE: Traffic Engineering
TP: Transport Profile TP: Transport Profile
4. Feature List 4. Feature List
The MPLS transport profile OAM identifiers MIB module is designed The MPLS transport profile OAM identifiers MIB module is designed
to satisfy the following requirements and constraints: to satisfy the following requirements and constraints:
- The MIB module supports configuration of OAM identifiers for - The MIB module supports configuration of OAM identifiers for
MPLS point-to-point Tunnels, point-to-multipoint LSPs, co- MPLS point-to-point Tunnels, point-to-multipoint LSPs, co-
routed bidirectional LSPs, associated bidirectional LSPs and routed bidirectional LSPs, associated bidirectional LSPs, and
Pseudowires. Pseudowires.
5. Brief description of MIB Objects 5. Brief description of MIB Objects
The objects described in this section support the functionality The objects described in this section support the functionality
described in documents [RFC5654] and [RFC6370]. The tables support described in documents [RFC5654] and [RFC6370]. The tables support
both IP compatible and ICC based OAM identifiers configurations both IP-compatible and ICC-based OAM identifiers configurations
for MPLS Tunnels, LSPs and Pseudowires. for MPLS Tunnels, LSPs, and Pseudowires.
5.1. mplsOamIdMegTable 5.1. mplsOamIdMegTable
The mplsOamIdMegTable is used to manage one or more The mplsOamIdMegTable is used to manage one or more
Maintenance Entities (MEs) that belongs to the same transport path. Maintenance Entities (MEs) that belong to the same transport path.
When a new entry is created with mplsOamIdMegOperatorType set to When a new entry is created with mplsOamIdMegOperatorType set to
ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP
is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be
automatically formed. automatically formed.
For ICC based transport path, the user is expected to configure For ICC-based transport path, the user is expected to configure
the ICC identifier explicitly in this table for MPLS Tunnels, LSPs the ICC identifier explicitly in this table for MPLS Tunnels, LSPs,
and pseudowires. and Pseudowires.
5.2. mplsOamIdMeTable 5.2. mplsOamIdMeTable
The mplsOamIdMeTable defines a relationship between two points The mplsOamIdMeTable defines a relationship between two points
(source and sink) of a transport path to which maintenance and (source and sink) of a transport path to which maintenance and
monitoring operations apply. The two points that define monitoring operations apply. The two points that define
a maintenance entity are called Maintenance Entity Group a maintenance entity are called Maintenance Entity Group
End Points (MEPs). End Points (MEPs).
In between MEPs, there are zero or more intermediate points, In between MEPs, there are zero or more intermediate points,
called Maintenance Entity Group Intermediate Points (MIPs). called Maintenance Entity Group Intermediate Points (MIPs).
MEPs and MIPs are associated with the MEG and can be shared by MEPs and MIPs are associated with the MEG and can be shared by
more than one ME in a MEG. more than one ME in a MEG.
6. MPLS OAM identifier configuration for MPLS LSP example 6. MPLS OAM identifier configuration for MPLS LSP example
In this section, we provide an example of the OAM identifier In this section, we provide an example of the OAM identifier
configuration for an MPLS co-routed bidirectional LSP. configuration for an MPLS co-routed bidirectional LSP.
This example provides usage of a MEG and ME tables for management and This example provides usage of MEG and ME tables for management and
monitoring operations of an MPLS LSP. monitoring operations of an MPLS LSP.
This example considers the OAM identifiers configuration on a This example considers the OAM identifiers configuration on a
head-end LSR to manage and monitor a MPLS LSP. head-end LSR to manage and monitor an MPLS LSP.
Only relevant objects which are applicable for IP based OAM Only relevant objects which are applicable for IP-based OAM
identifiers of MPLS co-routed bidirectional LSP are illustrated here. identifiers of MPLS co-routed bidirectional LSP are illustrated here.
In mplsOamIdMegTable: In mplsOamIdMegTable:
{ {
-- MEG index (Index to the table) -- MEG index (Index to the table)
mplsOamIdMegIndex = 1, mplsOamIdMegIndex = 1,
mplsOamIdMegName = "MEG1", mplsOamIdMegName = "MEG1",
mplsOamIdMegOperatorType = ipCompatible (1), mplsOamIdMegOperatorType = ipCompatible (1),
mplsOamIdMegServicePointerType = lsp (1), mplsOamIdMegServicePointerType = lsp (1),
skipping to change at page 6, line 25 skipping to change at page 6, line 25
In mplsOamIdMeTable: In mplsOamIdMeTable:
{ {
-- ME index (Index to the table) -- ME index (Index to the table)
mplsOamIdMeIndex = 1, mplsOamIdMeIndex = 1,
-- MP index (Index to the table) -- MP index (Index to the table)
mplsOamIdMeMpIndex = 1, mplsOamIdMeMpIndex = 1,
mplsOamIdMeName = "ME1", mplsOamIdMeName = "ME1",
mplsOamIdMeMpIfIndex = 0, mplsOamIdMeMpIfIndex = 0,
-- Source MEP id is derived from the IP compatible MPLS LSP -- Source MEP id is derived from the IP-compatible MPLS LSP
mplsOamIdMeSourceMepIndex = 0, mplsOamIdMeSourceMepIndex = 0,
-- Source MEP id is derived from the IP compatible MPLS LSP -- Sink MEP id is derived from the IP-compatible MPLS LSP
mplsOamIdMeSinkMepIndex = 0, mplsOamIdMeSinkMepIndex = 0,
mplsOamIdMeMpType = mep (1), mplsOamIdMeMpType = mep (1),
mplsOamIdMeMepDirection = down (2), mplsOamIdMeMepDirection = down (2),
-- RowPointer MUST point to the first accessible column of an -- RowPointer MUST point to the first accessible column of an
-- MPLS LSP -- MPLS LSP
mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20, mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsOamIdMeRowStatus = createAndGo (4) mplsOamIdMeRowStatus = createAndGo (4)
} }
skipping to change at page 7, line 15 skipping to change at page 7, line 15
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB -- [RFC3289] FROM DIFFSERV-MIB -- [RFC3289]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
InterfaceIndexOrZero, ifGeneralInformationGroup, InterfaceIndexOrZero, ifGeneralInformationGroup,
ifCounterDiscontinuityGroup ifCounterDiscontinuityGroup
FROM IF-MIB; -- [RFC2863] FROM IF-MIB; -- [RFC2863]
mplsOamIdStdMIB MODULE-IDENTITY mplsOamIdStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201502260000Z" -- February 26, 2015 "201508290000Z" -- August 29, 2015
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Sam Aldrin Sam Aldrin
Google, Inc. Google, Inc.
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, CA Mountain View, CA 94043
USA USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Venkatesan Mahalingam Venkatesan Mahalingam
Dell, Inc. Dell, Inc.
5450 Great America Parkway, 5450 Great America Parkway,
Santa Clara, CA 95054, USA Santa Clara, CA 95054, USA
skipping to change at page 8, line 16 skipping to change at page 8, line 16
DESCRIPTION DESCRIPTION
"Copyright (c) 2015 IETF Trust and the persons identified "Copyright (c) 2015 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS OAM maintenance identifiers." MPLS OAM maintenance identifiers."
-- Revision history. -- Revision history.
REVISION REVISION
"201502260000Z" -- February 26, 2015 "201508290000Z" -- August 29, 2015
DESCRIPTION DESCRIPTION
"MPLS OAM Identifiers MIB objects for Tunnels, LSPs, "MPLS OAM Identifiers MIB objects for Tunnels, LSPs,
Pseudowires and Sections" Pseudowires, and Sections"
::= { mplsStdMIB xxx } -- xxx to be replaced with the correct ::= { mplsStdMIB xxx } -- xxx to be replaced with the correct
-- OID value assigned by -- OID value assigned by
-- IANA (see section 9). -- IANA (see section 9).
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- notifications -- notifications
mplsOamIdNotifications mplsOamIdNotifications
OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 }
skipping to change at page 9, line 38 skipping to change at page 9, line 38
mplsOamIdMegOperatorType set to ipCompatible (1), mplsOamIdMegOperatorType set to ipCompatible (1),
then as per [RFC6370] (MEG_ID for LSP is LSP_ID and then as per [RFC6370] (MEG_ID for LSP is LSP_ID and
MEG_ID for PW is PW_Path_ID), MEP_ID can be MEG_ID for PW is PW_Path_ID), MEP_ID can be
automatically formed. automatically formed.
For co-routed bidirectional LSP, MEG_ID is For co-routed bidirectional LSP, MEG_ID is
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num. Node_ID::Tunnel_Num}::LSP_Num.
For associated bidirectional LSP, MEG_ID is A1- For associated bidirectional LSP, MEG_ID is A1-
{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- {Global_ID::Node_ID::Tunnel_Num::LSP_Num}::Z9-
{Global_ID::Node_ID::Tunnel_Num::LSP_Num} {Global_ID::Node_ID::Tunnel_Num::LSP_Num}
For LSP, MEP_ID is formed using, For LSP, MEP_ID is formed using,
Global_ID::Node_ID::Tunnel_Num::LSP_Num Global_ID::Node_ID::Tunnel_Num::LSP_Num
For PW, MEG_ID is formed using AGI::A1- For PW, MEG_ID is formed using AGI::A1-
{Global_ID::Node_ID::AC_ID}:: Z9- {Global_ID::Node_ID::AC_ID}::Z9-
{Global_ID::Node_ID::AC_ID}. {Global_ID::Node_ID::AC_ID}.
For PW, MEP_ID is formed using For PW, MEP_ID is formed using
AGI::Global_ID::Node_ID::AC_ID AGI::Global_ID::Node_ID::AC_ID
MEP_ID is retrieved from the mplsOamIdMegServicePointer MEP_ID is retrieved from the mplsOamIdMegServicePointer
object based on the mplsOamIdMegServicePointerType value. object based on the mplsOamIdMegServicePointerType value.
ICC MEG_ID for LSP and PW is formed using the objects ICC MEG_ID for LSP and PW is formed using the objects
mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. mplsOamIdMegIdIcc and mplsOamIdMegIdUmc.
MEP_ID can be formed using MEG_ID::MEP_Index." MEP_ID can be formed using MEG_ID::MEP_Index."
REFERENCE REFERENCE
"1. RFC5860, Requirements for OAM in MPLS Transport "1. RFC 5860, Requirements for OAM in MPLS Transport
Networks, May 2010. Networks, May 2010.
2. RFC6371, Operations, Administration, and Maintenance 2. RFC 6371, Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks, Framework for MPLS-Based Transport Networks,
September 2011 Section 3. September 2011 Section 3.
3. RFC6370, MPLS Transport Profile (MPLS-TP) Identifiers. 3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers.
4. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 4. RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions." Following ITU-T Conventions."
INDEX { mplsOamIdMegIndex } INDEX { mplsOamIdMegIndex }
::= { mplsOamIdMegTable 1 } ::= { mplsOamIdMegTable 1 }
MplsOamIdMegEntry ::= SEQUENCE { MplsOamIdMegEntry ::= SEQUENCE {
mplsOamIdMegIndex Unsigned32, mplsOamIdMegIndex Unsigned32,
mplsOamIdMegName SnmpAdminString, mplsOamIdMegName SnmpAdminString,
mplsOamIdMegOperatorType INTEGER, mplsOamIdMegOperatorType INTEGER,
mplsOamIdMegIdCc SnmpAdminString, mplsOamIdMegIdCc SnmpAdminString,
mplsOamIdMegIdIcc SnmpAdminString, mplsOamIdMegIdIcc SnmpAdminString,
skipping to change at page 11, line 5 skipping to change at page 11, line 5
this MEG table. Managers should obtain new values for row this MEG table. Managers should obtain new values for row
creation in this table by reading creation in this table by reading
mplsOamIdMegIndexNext." mplsOamIdMegIndexNext."
::= { mplsOamIdMegEntry 1 } ::= { mplsOamIdMegEntry 1 }
mplsOamIdMegName OBJECT-TYPE mplsOamIdMegName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..48)) SYNTAX SnmpAdminString (SIZE(0..48))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each Maintenance Entity Group has unique name amongst "Each Maintenance Entity Group has a unique name amongst
all those used or available to a service provider or all those used or available to a service provider or
operator. It facilitates easy identification of operator. It facilitates easy identification of
administrative responsibility for each MEG." administrative responsibility for each MEG."
::= { mplsOamIdMegEntry 2 } ::= { mplsOamIdMegEntry 2 }
mplsOamIdMegOperatorType OBJECT-TYPE mplsOamIdMegOperatorType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ipCompatible (1), ipCompatible (1),
iccBased (2) iccBased (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the operator type for MEG. Conceptual rows "Indicates the operator type for MEG. Conceptual rows
having 'iccBased' as operator type, MUST have valid having 'iccBased' as operator type, MUST have valid
values for the objects mplsOamIdMegIdIcc and values for the objects mplsOamIdMegIdIcc and
mplsOamIdMegIdUmc when the row status is active." mplsOamIdMegIdUmc when the row status is active."
REFERENCE REFERENCE
skipping to change at page 11, line 25 skipping to change at page 11, line 24
iccBased (2) iccBased (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the operator type for MEG. Conceptual rows "Indicates the operator type for MEG. Conceptual rows
having 'iccBased' as operator type, MUST have valid having 'iccBased' as operator type, MUST have valid
values for the objects mplsOamIdMegIdIcc and values for the objects mplsOamIdMegIdIcc and
mplsOamIdMegIdUmc when the row status is active." mplsOamIdMegIdUmc when the row status is active."
REFERENCE REFERENCE
"1. RFC6370, MPLS Transport Profile (MPLS-TP) "1. RFC 6370, MPLS Transport Profile (MPLS-TP)
Identifiers. Identifiers.
2. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 2. RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions. Section 3.1" Following ITU-T Conventions. Section 3.1"
DEFVAL { ipCompatible } DEFVAL { ipCompatible }
::= { mplsOamIdMegEntry 3 } ::= { mplsOamIdMegEntry 3 }
mplsOamIdMegIdCc OBJECT-TYPE mplsOamIdMegIdCc OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..2)) SYNTAX SnmpAdminString (SIZE(0..2))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Global uniqueness is assured by concatenating the ICC "Global uniqueness is assured by concatenating the ICC
with a Country Code (CC). The Country Code (alpha-2) with a Country Code (CC). The Country Code (alpha-2)
is a string of two alphabetic characters represented is a string of two alphabetic characters represented
with upper case letters (i.e., A-Z). with upper case letters (i.e., A-Z).
This object MUST contain a non-null ICC value if This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased(2), the MplsOamIdMegOperatorType value is iccBased(2),
otherwise a null ICC value with octet size 0 otherwise a null value with octet size 0
should be assigned." should be assigned."
REFERENCE REFERENCE
"RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions. Section 3." Following ITU-T Conventions. Section 3."
DEFVAL {""} DEFVAL {""}
::= { mplsOamIdMegEntry 4 } ::= { mplsOamIdMegEntry 4 }
mplsOamIdMegIdIcc OBJECT-TYPE mplsOamIdMegIdIcc OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..6)) SYNTAX SnmpAdminString (SIZE(0..6))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Unique code assigned to Network Operator or Service "Unique code assigned to Network Operator or Service
Provider maintained by ITU-T. The ITU Carrier Code Provider maintained by ITU-T. The ITU Carrier Code
used to form MEGID. used to form MEGID.
This object MUST contain a non-null ICC value if This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased(2), the MplsOamIdMegOperatorType value is iccBased(2),
otherwise a null ICC value with octet size 0 otherwise a null value with octet size 0
should be assigned." should be assigned."
REFERENCE REFERENCE
"RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions. Section 3.1." Following ITU-T Conventions. Section 3.1."
DEFVAL {""} DEFVAL {""}
::= { mplsOamIdMegEntry 5 } ::= { mplsOamIdMegEntry 5 }
mplsOamIdMegIdUmc OBJECT-TYPE mplsOamIdMegIdUmc OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..7)) SYNTAX SnmpAdminString (SIZE(0..7))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Unique code assigned by Network Operator or Service "Unique code assigned by Network Operator or Service
Provider and is appended to mplsOamIdMegIdIcc to form Provider, which is appended to mplsOamIdMegIdIcc to form
the MEGID. the MEGID.
This object MUST contain a non-null ICC value if This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased(2), the MplsOamIdMegOperatorType value is iccBased(2),
otherwise a null ICC value with octet size 0 otherwise a null value with octet size 0
should be assigned." should be assigned."
REFERENCE REFERENCE
"RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions. Section 7.1." Following ITU-T Conventions. Section 7.1."
DEFVAL {""} DEFVAL {""}
::= { mplsOamIdMegEntry 6 } ::= { mplsOamIdMegEntry 6 }
mplsOamIdMegServicePointerType OBJECT-TYPE mplsOamIdMegServicePointerType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
tunnel (1), tunnel (1),
lsp (2), lsp (2),
pseudowire (3), pseudowire (3),
skipping to change at page 13, line 13 skipping to change at page 13, line 13
DESCRIPTION DESCRIPTION
"Indicates the service type for the MEG. "Indicates the service type for the MEG.
If the service type indicates tunnel, the service pointer If the service type indicates tunnel, the service pointer
in mplsOamIdMeTable points to an entry in in mplsOamIdMeTable points to an entry in
the point-to-point mplsTunnelTable [RFC3812]. the point-to-point mplsTunnelTable [RFC3812].
If the service type indicates lsp, the service pointer If the service type indicates lsp, the service pointer
in mplsOamIdMeTable points to an entry in in mplsOamIdMeTable points to an entry in
the co-routed or associated bidirectional mplsTunnelTable. the co-routed or associated bidirectional mplsTunnelTable.
If the value is pseudowire service type, the service If the value is pseudowire (3) service type, the service
pointer in mplsOamIdMeTable points to an entry in pointer in mplsOamIdMeTable points to an entry in
the pwTable [RFC5601]. the pwTable [RFC5601].
If the value is section service type, the service If the value is section service type, the service
pointer in mplsOamIdMeTable points to an entry in pointer in mplsOamIdMeTable points to an entry in
the mplsTunnelTable [RFC3812]." the mplsTunnelTable [RFC3812]."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic "1. RFC 3812, Multiprotocol Label Switching (MPLS)
Engineering (TE) Management Information Traffic Engineering (TE) Management Information
Base (MIB), Srinivasan, et al, RFC 3812, June 2004 Base (MIB), June 2004.
2. Pseudowire (PW) Management Information Base (MIB), 2. RFC 5601, Pseudowire (PW) Management Information
Nadeau & Zelig, RFC 5601, July 2009." Base (MIB), July 2009."
DEFVAL { lsp } DEFVAL { lsp }
::= { mplsOamIdMegEntry 7 } ::= { mplsOamIdMegEntry 7 }
mplsOamIdMegMpLocation OBJECT-TYPE mplsOamIdMegMpLocation OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
perNode (1), perNode (1),
perInterface (2) perInterface (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 14, line 52 skipping to change at page 14, line 52
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the operational status of the "This object specifies the operational status of the
Maintenance Entity Group (MEG). This object is used to Maintenance Entity Group (MEG). This object is used to
send the notification to the SNMP manager about the MEG. send the notification to the SNMP manager about the MEG.
The value up (1) indicates that the MEG and its monitored The value up (1) indicates that the MEG and its monitored
path are operationally up. The value down (2) indicates path are operationally up. The value down (2) indicates
that the MEG is operationally down. that the MEG is operationally down.
When the value of mplsOamIdMegOperStatus is up(1), all When the value of mplsOamIdMegOperStatus is up (1), all
the bits of mplsOamIdMegSubOperStatus must be cleared. the bits of mplsOamIdMegSubOperStatus must be cleared.
When the value of mplsOamIdMegOperStatus is down(2), When the value of mplsOamIdMegOperStatus is down (2),
at least one bit of mplsOamIdMegSubOperStatus must be at least one bit of mplsOamIdMegSubOperStatus must be
set." set."
::= { mplsOamIdMegEntry 10 } ::= { mplsOamIdMegEntry 10 }
mplsOamIdMegSubOperStatus OBJECT-TYPE mplsOamIdMegSubOperStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
megDown (0), megDown (0),
meDown (1), meDown (1),
oamAppDown (2), oamAppDown (2),
pathDown (3) pathDown (3)
skipping to change at page 15, line 44 skipping to change at page 15, line 44
::= { mplsOamIdMegEntry 11 } ::= { mplsOamIdMegEntry 11 }
mplsOamIdMegRowStatus OBJECT-TYPE mplsOamIdMegRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete "This variable is used to create, modify, and/or delete
a row in this table. When a row in this table is in a row in this table. When a row in this table is in
active(1) state, no objects in that row can be modified active (1) state, no objects in that row can be modified
by the agent except mplsOamIdMegRowStatus." by the agent except mplsOamIdMegRowStatus."
::= { mplsOamIdMegEntry 12 } ::= { mplsOamIdMegEntry 12 }
mplsOamIdMegStorageType OBJECT-TYPE mplsOamIdMegStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
object. object.
skipping to change at page 17, line 19 skipping to change at page 17, line 19
::= { mplsOamIdObjects 5 } ::= { mplsOamIdObjects 5 }
mplsOamIdMeEntry OBJECT-TYPE mplsOamIdMeEntry OBJECT-TYPE
SYNTAX MplsOamIdMeEntry SYNTAX MplsOamIdMeEntry
MAX-ACCESS not-accessible STATUS current MAX-ACCESS not-accessible STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents MPLS-TP maintenance "An entry in this table represents MPLS-TP maintenance
entity. This entry represents the ME if the source and entity. This entry represents the ME if the source and
sink MEPs are defined. sink MEPs are defined.
A ME is a p2p entity. One ME has two such MEPs. A ME is a point-to-point entity. One ME has two such MEPs.
A MEG is a group of one or more MEs. One MEG can have A MEG is a group of one or more MEs. One MEG can have
two or more MEPs. two or more MEPs.
For P2P LSP, one MEG has one ME and this ME is associated For point-to-point LSP, one MEG has one ME and this ME
two MEPs (source and sink MEPs) within a MEG. is associated two MEPs (source and sink MEPs) within
Each mplsOamIdMeIndex value denotes the ME within a MEG. a MEG. Each mplsOamIdMeIndex value denotes the ME within
a MEG.
In case of unidirectional point-to-point transport paths, In case of unidirectional point-to-point transport paths,
a single unidirectional Maintenance Entity is defined to a single unidirectional Maintenance Entity is defined to
monitor it and mplsOamIdMeServicePointer points to monitor it and mplsOamIdMeServicePointer points to
unidirectional point-to-point path. unidirectional point-to-point path.
In case of associated bidirectional point-to-point In case of associated bidirectional point-to-point
transport paths, two independent unidirectional transport paths, two independent unidirectional
Maintenance Entities are defined to independently monitor Maintenance Entities are defined to independently monitor
each direction and each mplsOamIdMeServicePointer MIB each direction and each mplsOamIdMeServicePointer MIB
skipping to change at page 19, line 27 skipping to change at page 19, line 28
If the mplsOamIdMegMpLocation object value If the mplsOamIdMegMpLocation object value
is perNode (1), the MP interface index should point is perNode (1), the MP interface index should point
to incoming interface or outgoing interface or to incoming interface or outgoing interface or
zero (indicates the MP OAM packets are initiated zero (indicates the MP OAM packets are initiated
from forwarding engine). from forwarding engine).
If the mplsOamIdMegMpLocation object value is If the mplsOamIdMegMpLocation object value is
perInterface (2), the MP interface index should point to perInterface (2), the MP interface index should point to
incoming interface or outgoing interface." incoming interface or outgoing interface."
REFERENCE REFERENCE
"RFC 6371, Operations, Administration, and Maintenance "1. RFC 6371, Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks, Framework for MPLS-Based Transport Networks,
September 2011. September 2011.
RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 2. RFC 2863 - The Interfaces Group MIB, McCloghrie, K.,
and F. Kastenholtz, June 2000." and F. Kastenholtz, June 2000."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsOamIdMeEntry 4 } ::= { mplsOamIdMeEntry 4 }
mplsOamIdMeSourceMepIndex OBJECT-TYPE mplsOamIdMeSourceMepIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the source MEP Index of the ME. This object "Indicates the source MEP Index of the ME. This object
should be configured if mplsOamIdMegOperatorType object should be configured if mplsOamIdMegOperatorType object
in the mplsOamIdMegEntry is configured as iccBased (2). in the mplsOamIdMegEntry is configured as iccBased (2).
If the MEG is configured for IP based operator, If the MEG is configured for IP-based operator,
the value of this object should be set zero and the MEP the value of this object should be set zero and the MEP
ID will be automatically derived from the service ID will be automatically derived from the service
Identifiers(MPLS-TP LSP/PW Identifier)." Identifiers(MPLS-TP LSP/PW Identifier)."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsOamIdMeEntry 5 } ::= { mplsOamIdMeEntry 5 }
mplsOamIdMeSinkMepIndex OBJECT-TYPE mplsOamIdMeSinkMepIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the sink MEP Index of the ME. This object "Indicates the sink MEP Index of the ME. This object
should be configured if mplsOamIdMegOperatorType object should be configured if mplsOamIdMegOperatorType object
in the mplsOamIdMegEntry is configured as iccBased (2). in the mplsOamIdMegEntry is configured as iccBased (2).
If the MEG is configured for IP based operator, If the MEG is configured for IP-based operator,
the value of this object should be set zero and the MEP the value of this object should be set to zero and the MEP
ID will be automatically derived from the service ID will be automatically derived from the service
Identifiers(MPLS-TP LSP/PW Identifier)." Identifiers (MPLS-TP LSP/PW Identifier)."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsOamIdMeEntry 6 } ::= { mplsOamIdMeEntry 6 }
mplsOamIdMeMpType OBJECT-TYPE mplsOamIdMeMpType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
mep (1), mep (1),
mip (2) mip (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the maintenance point type within the MEG. "Indicates the maintenance point type within the MEG.
The object should have the value mep (1), only in the The object should have the value mep (1), only in the
Ingress or Egress nodes of the transport path. Ingress or Egress nodes of the transport path.
The object can have the value mip (2), The object can have the value mip (2), in
in the intermediate nodes and possibly in the end nodes the Intermediate nodes and possibly in the Egress
of the transport path." nodes of the transport path."
DEFVAL { mep } DEFVAL { mep }
::= { mplsOamIdMeEntry 7 } ::= { mplsOamIdMeEntry 7 }
mplsOamIdMeMepDirection OBJECT-TYPE mplsOamIdMeMepDirection OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up (1), up (1),
down (2), down (2),
notApplicable (3) notApplicable (3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 21, line 19 skipping to change at page 21, line 19
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable represents a pointer to the MPLS-TP "This variable represents a pointer to the MPLS-TP
transport path. This value MUST point at an entry in the transport path. This value MUST point at an entry in the
mplsTunnelEntry if mplsOamIdMegServicePointerType mplsTunnelEntry if mplsOamIdMegServicePointerType
is configured as tunnel (1) or lsp (2) or section (4) or is configured as tunnel (1) or lsp (2) or section (4) or
at an entry in the pwEntry if at an entry in the pwEntry if
mplsOamIdMegServicePointerType is configured mplsOamIdMegServicePointerType is configured
as pseudowire (3). as pseudowire (3).
Note: This service pointer object, is placed in ME table Note: This service pointer object is placed in the ME table
instead of MEG table, since it will be useful in case of instead of the MEG table since it will be useful in case of
point-to-multipoint, where each ME will point to different point-to-multipoint, where each ME will point to different
branches of a P2MP tree." branches of a P2MP tree."
::= { mplsOamIdMeEntry 9 } ::= { mplsOamIdMeEntry 9 }
mplsOamIdMeRowStatus OBJECT-TYPE mplsOamIdMeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. When a row in this delete a row in this table. When a row in this
table is in active(1) state, no objects in that row table is in active (1) state, no objects in that row
can be modified by the agent except can be modified by the agent except
mplsOamIdMeRowStatus." mplsOamIdMeRowStatus."
::= { mplsOamIdMeEntry 10 } ::= { mplsOamIdMeEntry 10 }
mplsOamIdMeStorageType OBJECT-TYPE mplsOamIdMeStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
skipping to change at page 27, line 32 skipping to change at page 27, line 32
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module." "Set of notifications implemented in this module."
::= { mplsOamIdGroups 4 } ::= { mplsOamIdGroups 4 }
END END
8. Security Consideration 8. Security Consideration
There is a number of management objects defined in this MIB module This MIB relates to a system that will provide network connectivity
that has a MAX-ACCESS clause of read-create. Such objects may be and packet forwarding services. As such, improper manipulation of the
objects represented by this MIB may result in denial of service to a
large number of end-users.
There are number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-create. Such objects may be
considered sensitive or vulnerable in some network environments. considered sensitive or vulnerable in some network environments.
The support for SET operations in a non-secure environment The support for SET operations in a non-secure environment
without proper protection can have a negative effect on network without proper protection can have negative effect on network
operations. operations.
Some of the readable objects in this MIB module (i.e., objects Some of the readable objects in this MIB module (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. sensitive or vulnerable in some network environments.
It is thus important to control even GET and/or NOTIFY access It is thus important to control even GET and/or NOTIFY access
to these objects and possibly to even encrypt the values of these to these objects and possibly to even encrypt the values of these
objects when sending them over the network via SNMP. These are objects when sending them over the network via SNMP. These are
the tables and objects and their sensitivity/vulnerability: the tables and objects and their sensitivity/vulnerability:
skipping to change at page 30, line 37 skipping to change at page 30, line 42
[RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. [RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M.
Betts, "MPLS-TP Identifiers Following ITU-T Betts, "MPLS-TP Identifiers Following ITU-T
Conventions", RFC 6923, May 2013. Conventions", RFC 6923, May 2013.
[RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS [RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS
Transport Networks", RFC 5860, May 2010. Transport Networks", RFC 5860, May 2010.
11. Acknowledgments 11. Acknowledgments
We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara, We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara,
Weiying Cheng and Mach Chen for their valuable comments on this Weiying Cheng, Mach Chen, Peter Yee, and Tina TSOU for their
document. valuable comments on this document.
12. Authors' Addresses 12. Authors' Addresses
Venkatesan Mahalingam Venkatesan Mahalingam
Dell, Inc. Dell, Inc.
5450 Great America Parkway, 5450 Great America Parkway,
Santa Clara, CA 95054, USA Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Sam Aldrin Sam Aldrin
Google, Inc. Google, Inc.
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, CA Mountain View, CA 94043
USA USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Brocade Brocade
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Kannan KV Sampath Kannan KV Sampath
Redeem, Redeem,
India India
 End of changes. 62 change blocks. 
87 lines changed or deleted 91 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/