--- 1/draft-ietf-mpls-tp-oam-id-mib-05.txt 2014-12-03 17:15:00.258932039 -0800 +++ 2/draft-ietf-mpls-tp-oam-id-mib-06.txt 2014-12-03 17:15:00.314933418 -0800 @@ -1,34 +1,35 @@ Network Working Group INTERNET-DRAFT Sam Aldrin Intended Status: Standards Track Huawei Technologies -Expires: December 17, 2014 M.Venkatesan +Expires: June 06, 2015 M.Venkatesan Dell Inc. Kannan KV Sampath Redeem Thomas D. Nadeau Brocade - June 15, 2014 + December 03, 2014 MPLS-TP Operations, Administration, and Management (OAM) Identifiers Management Information Base (MIB) - draft-ietf-mpls-tp-oam-id-mib-05 + draft-ietf-mpls-tp-oam-id-mib-06 Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes Operations, Administration, and Management (OAM) identifiers related managed objects for - Multiprotocol Label Switching (MPLS) based Transport Profile (TP). + Multiprotocol Label Switching (MPLS) and MPLS based Transport Profile + (TP). Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -37,21 +38,21 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on December 17, 2014. + This Internet-Draft will expire on June 06, 2015. Copyright and License Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -65,41 +66,42 @@ 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1 Conventions used in this document . . . . . . . . . . . . . 3 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 5.1. mplsOamIdMegTable . . . . . . . . . . . . . . . . . . . . 4 - 5.2. mplsOamIdMeTable . . . . . . . . . . . . . . . . . . . . . 5 - 6. MPLS OAM identifier configuration for MPLS tunnel example . . . 5 + 5.2. mplsOamIdMeTable . . . . . . . . . . . . . . . . . . . . . 4 + 6. MPLS OAM identifier configuration for MPLS LSP example . . . . 5 7. MPLS OAM Identifiers MIB definitions . . . . . . . . . . . . . 6 - 8. Security Consideration . . . . . . . . . . . . . . . . . . . . 25 + 8. Security Consideration . . . . . . . . . . . . . . . . . . . . 24 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 25 - 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 - 10.1 Normative References . . . . . . . . . . . . . . . . . . . 26 + 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 + 10.1 Normative References . . . . . . . . . . . . . . . . . . . 25 10.2 Informative References . . . . . . . . . . . . . . . . . . 26 - 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 - 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 27 + 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 26 + 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 26 1 Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling a Multiprotocol Label Switching (MPLS) [RFC3031] based transport profile. - This MIB module should be used for performing the OAM operations for - MPLS LSPs, Pseudowires and Sections. + This MIB module should be used for performing the OAM (Operations, + Administration, and Maintenance) operations for MPLS LSP(Label + Switching Path), Pseudowires and Sections. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). @@ -113,33 +115,30 @@ 3.1 Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119]. 3.2 Terminology This document uses terminology from the Multiprotocol Label Switching - Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic - Engineering (TE)Management Information Base (MIB)[RFC3812], - Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) - Management Information Base (MIB)[RFC3813], Operations, - Administration, and Maintenance Framework for MPLS-Based Transport - Networks [RFC6371], MPLS Transport Profile (MPLS-TP) Identifiers - [RFC6370], MPLS-TP Identifiers Following ITU-T Conventions [RFC6923], - and OAM in MPLS Transport Networks [RFC5860]. + Architecture [RFC3031], MPLS Traffic Engineering (TE) MIB [RFC3812], + MPLS Label Switching Router (LSR) MIB [RFC3813], OAM Framework for + MPLS-Based Transport Networks [RFC6371], MPLS Transport Profile + (MPLS-TP) Identifiers [RFC6370], MPLS-TP Identifiers Following ITU-T + Conventions [RFC6923], and OAM in MPLS Transport Networks [RFC5860]. 3.3 Acronyms + ICC: ITU Carrier Code IP: Internet Protocol - LSP: Label Switching Path LSR: Label Switching Router MIB: Management Information Base ME: Maintenance Entity MEG: Maintenance Entity Group MEP: Maintenance Entity Group End Point MIP: Maintenance Entity Group Intermediate Point MPLS: Multi-Protocol Label Switching MPLS-TP: MPLS Transport Profile PW: Pseudowire @@ -145,46 +144,46 @@ PW: Pseudowire TE: Traffic Engineering TP: Transport Profile 4. Feature List The MPLS transport profile OAM identifiers MIB module is designed to satisfy the following requirements and constraints: - The MIB module supports configuration of OAM identifiers for - point-to-point, co-routed bidirectional, associated - bidirectional MPLS tunnels and MPLS Pseudowires. + MPLS point-to-point Tunnels, point-to-multipoint LSPs, co- + routed bidirectional LSPs, associated bidirectional LSPs and + Pseudowires. 5. Brief description of MIB Objects The objects described in this section support the functionality described in documents [RFC5654] and [RFC6370]. The tables support both IP compatible and ICC based OAM identifiers configurations - for MPLS Tunnels and Pseudowires. + for MPLS Tunnels, LSPs and Pseudowires. 5.1. mplsOamIdMegTable The mplsOamIdMegTable is used to manage one or more Maintenance Entities (MEs) that belongs to the same transport path. When a new entry is created with mplsOamIdMegOperatorType set to 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 automatically formed. For ICC based transport path, the user is expected to configure - the ICC identifier explicitly in this table for MPLS tunnels + the ICC identifier explicitly in this table for MPLS Tunnels, LSPs and pseudowires. 5.2. mplsOamIdMeTable - The mplsOamIdMeTable defines a relationship between two points (source and sink) of a transport path to which maintenance and monitoring operations apply. The two points that define a maintenance entity are called Maintenance Entity Group End Points (MEPs). In between MEPs, there are zero or more intermediate points, called Maintenance Entity Group Intermediate Points (MIPs). MEPs and MIPs are associated with the MEG and can be shared by more than one ME in a MEG. @@ -182,32 +181,32 @@ (source and sink) of a transport path to which maintenance and monitoring operations apply. The two points that define a maintenance entity are called Maintenance Entity Group End Points (MEPs). In between MEPs, there are zero or more intermediate points, called Maintenance Entity Group Intermediate Points (MIPs). MEPs and MIPs are associated with the MEG and can be shared by more than one ME in a MEG. -6. MPLS OAM identifier configuration for MPLS tunnel example +6. MPLS OAM identifier configuration for MPLS LSP example In this section, we provide an example of the OAM identifier - configuration for an MPLS co-routed bidirectional tunnel. + configuration for an MPLS co-routed bidirectional LSP. This example provides usage of a MEG and ME tables for management and - monitoring operations of an MPLS tunnel. + monitoring operations of an MPLS LSP. This example considers the OAM identifiers configuration on a - head-end LSR to manage and monitor a MPLS tunnel. + head-end LSR to manage and monitor a MPLS LSP. Only relevant objects which are applicable for IP based OAM - identifiers of co-routed MPLS tunnel are illustrated here. + identifiers of MPLS co-routed bidirectional LSP are illustrated here. In mplsOamIdMegTable: { -- MEG index (Index to the table) mplsOamIdMegIndex = 1, mplsOamIdMegName = "MEG1", mplsOamIdMegOperatorType = ipCompatible (1), mplsOamIdMegServicePointerType = lsp (1), mplsOamIdMegMpLocation = perNode(1), @@ -226,30 +225,28 @@ In mplsOamIdMeTable: { -- ME index (Index to the table) mplsOamIdMeIndex = 1, -- MP index (Index to the table) mplsOamIdMeMpIndex = 1, mplsOamIdMeName = "ME1", mplsOamIdMeMpIfIndex = 0, - -- Source MEP id is derived from the IP compatible MPLS tunnel + -- Source MEP id is derived from the IP compatible MPLS LSP mplsOamIdMeSourceMepIndex = 0, - -- Source MEP id is derived from the IP compatible MPLS tunnel + -- Source MEP id is derived from the IP compatible MPLS LSP mplsOamIdMeSinkMepIndex = 0, mplsOamIdMeMpType = mep (1), mplsOamIdMeMepDirection = down (2), - mplsOamIdMeProactiveOamPhbTCValue = 0, - mplsOamIdMeOnDemandOamPhbTCValue = 0, -- RowPointer MUST point to the first accessible column of an - -- MPLS tunnel + -- MPLS LSP mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20, -- Mandatory parameters needed to activate the row go here mplsOamIdMeRowStatus = createAndGo (4) } 7. MPLS OAM Identifiers MIB definitions MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN IMPORTS @@ -266,23 +263,24 @@ IndexIntegerNextFree FROM DIFFSERV-MIB -- [RFC3289] mplsStdMIB FROM MPLS-TC-STD-MIB -- [RFC3811] InterfaceIndexOrZero, ifGeneralInformationGroup, ifCounterDiscontinuityGroup FROM IF-MIB; -- [RFC2863] mplsOamIdStdMIB MODULE-IDENTITY LAST-UPDATED - "201406150000Z" -- June 15, 2014 + "201410280000Z" -- October 28, 2014 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" + CONTACT-INFO " Sam Aldrin Huawei Technologies, co. 2330 Central Express Way, Santa Clara, CA 95051, USA Email: aldrin.ietf@gmail.com Thomas D. Nadeau @@ -314,47 +312,29 @@ DESCRIPTION "Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This MIB module contains generic object definitions for MPLS OAM maintenance identifiers." -- Revision history. REVISION - "201406150000Z" -- June 15, 2014 + "201410280000Z" -- October 28, 2014 DESCRIPTION - "MPLS OAM Identifiers MIB objects for LSPs and - Pseudowires" + "MPLS OAM Identifiers MIB objects for Tunnels, LSPs, + Pseudowires and Sections" ::= { mplsStdMIB xxx } -- xxx to be replaced with the correct -- OID value assigned by -- IANA (see section 9). - -- TEXTUAL-CONVENTIONs - - MplsOamPhbTCValue ::= TEXTUAL-CONVENTION - STATUS current - DESCRIPTION - "This is the Per-hop Behavior (PHB) traffic class values - for the MPLS OAM operations." - SYNTAX INTEGER { - be (1), - af1 (2), - af2 (3), - af3 (4), - af4 (5), - ef (6), - cs6 (7), - cs7 (8) - } - -- Top level components of this MIB module. -- notifications mplsOamIdNotifications OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } -- tables, scalars mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 } -- conformance mplsOamIdConformance OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 } @@ -548,32 +529,38 @@ the MplsOamIdMegOperatorType value is iccBased(2), otherwise a null ICC value with octet size 0 should be assigned." REFERENCE "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T Conventions. Section 7.1." DEFVAL {""} ::= { mplsOamIdMegEntry 6 } mplsOamIdMegServicePointerType OBJECT-TYPE + SYNTAX INTEGER { - lsp (1), - pseudowire (2), - section (3) + tunnel (1), + lsp (2), + pseudowire (3), + section (4) } MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the service type for the MEG. + If the service type indicates tunnel, the service pointer + in mplsOamIdMeTable points to an entry in + the point-to-point mplsTunnelTable [RFC3812]. + If the service type indicates lsp, the service pointer in mplsOamIdMeTable points to an entry in - the mplsTunnelTable [RFC3812]. + the co-routed or associated bidirectional mplsTunnelTable. If the value is pseudowire service type, the service pointer in mplsOamIdMeTable points to an entry in the pwTable [RFC5601]. If the value is section service type, the service pointer in mplsOamIdMeTable points to an entry in the mplsTunnelTable [RFC3812]." REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic @@ -809,22 +796,20 @@ MplsOamIdMeEntry ::= SEQUENCE { mplsOamIdMeIndex Unsigned32, mplsOamIdMeMpIndex Unsigned32, mplsOamIdMeName SnmpAdminString, mplsOamIdMeMpIfIndex InterfaceIndexOrZero, mplsOamIdMeSourceMepIndex Unsigned32, mplsOamIdMeSinkMepIndex Unsigned32, mplsOamIdMeMpType INTEGER, mplsOamIdMeMepDirection INTEGER, - mplsOamIdMeProactiveOamPhbTCValue MplsOamPhbTCValue, - mplsOamIdMeOnDemandOamPhbTCValue MplsOamPhbTCValue, mplsOamIdMeServicePointer RowPointer, mplsOamIdMeRowStatus RowStatus, mplsOamIdMeStorageType StorageType } mplsOamIdMeIndex OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -938,84 +923,64 @@ MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the direction of the MEP. This object should be configured if mplsOamIdMeMpType is configured as mep (1) else notApplicable (3) is set." DEFVAL { down } ::= { mplsOamIdMeEntry 8 } - mplsOamIdMeProactiveOamPhbTCValue OBJECT-TYPE - SYNTAX MplsOamPhbTCValue - MAX-ACCESS read-create - STATUS current - DESCRIPTION - "Indicates the Per-hop Behavior (PHB) value for this source - MEP generated proactive traffic." - DEFVAL { ef } - ::= { mplsOamIdMeEntry 9 } - - mplsOamIdMeOnDemandOamPhbTCValue OBJECT-TYPE - SYNTAX MplsOamPhbTCValue - MAX-ACCESS read-create - STATUS current - DESCRIPTION - "Indicates the Per-hop Behavior (PHB) value for this - source MEP generated on-demand traffic." - DEFVAL { ef } - - ::= { mplsOamIdMeEntry 10 } - mplsOamIdMeServicePointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This variable represents a pointer to the MPLS-TP transport path. This value MUST point at an entry in the mplsTunnelEntry if mplsOamIdMegServicePointerType - is configured as lsp (1) or at an entry in the pwEntry if + is configured as tunnel (1) or lsp (2) or section (4) or + at an entry in the pwEntry if mplsOamIdMegServicePointerType is configured - as pseudowire (2). + as pseudowire (3). Note: This service pointer object, is placed in ME table instead of MEG table, since it will be useful in case of point-to-multipoint, where each ME will point to different branches of a P2MP tree." - ::= { mplsOamIdMeEntry 11 } + ::= { mplsOamIdMeEntry 9 } mplsOamIdMeRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified by the agent except mplsOamIdMeRowStatus." - ::= { mplsOamIdMeEntry 12 } + ::= { mplsOamIdMeEntry 10 } mplsOamIdMeStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row." DEFVAL { volatile } - ::= { mplsOamIdMeEntry 13 } + ::= { mplsOamIdMeEntry 11 } -- End of MPLS Transport Profile ME table -- End of MPLS-TP OAM Tables -- Notification Definitions of MPLS-TP identifiers mplsOamIdDefectCondition NOTIFICATION-TYPE OBJECTS { mplsOamIdMegName, @@ -1099,22 +1065,20 @@ mplsOamIdMeGroup OBJECT-GROUP OBJECTS { mplsOamIdMeIndexNext, mplsOamIdMeMpIndexNext, mplsOamIdMeName, mplsOamIdMeMpIfIndex, mplsOamIdMeSourceMepIndex, mplsOamIdMeSinkMepIndex, mplsOamIdMeMpType, mplsOamIdMeMepDirection, - mplsOamIdMeProactiveOamPhbTCValue, - mplsOamIdMeOnDemandOamPhbTCValue, mplsOamIdMeServicePointer, mplsOamIdMeRowStatus, mplsOamIdMeStorageType } STATUS current DESCRIPTION "Collection of objects needed for MPLS ME information." ::= { mplsOamIdGroups 2 } mplsOamIdNotificationObjectsGroup OBJECT-GROUP @@ -1252,22 +1217,23 @@ [RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. Betts, "MPLS-TP Identifiers Following ITU-T Conventions", RFC 6923, May 2013. [RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS Transport Networks", RFC 5860, May 2010. 11. Acknowledgments - We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara and - Weiying Cheng for their valuable comments on this document. + We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara, + Weiying Cheng and Mach Chen for their valuable comments on this + document. 12. Authors' Addresses Venkatesan Mahalingam Dell Inc. 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com Sam Aldrin