--- 1/draft-ietf-mpls-tp-linear-protection-mib-01.txt 2014-02-04 19:14:31.781692319 -0800 +++ 2/draft-ietf-mpls-tp-linear-protection-mib-02.txt 2014-02-04 19:14:31.833693577 -0800 @@ -1,25 +1,25 @@ Internet Engineering Task Force Kingston Smiler Selvaraj Internet-Draft IpInfusion Intended status: Standards Track M.Venkatesan -Expires: February 8, 2014 Dell Inc. +Expires: August 8, 2014 Dell Inc. V. Manral Hewlett-Packard Corp Daniel King Old Dog Consulting Sam Aldrin Huawei Technologies - August 7, 2013 + February 4, 2014 MPLS Transport Profile Linear Protection MIB - draft-ietf-mpls-tp-linear-protection-mib-01 + draft-ietf-mpls-tp-linear-protection-mib-02 Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing MPLS Transport Profile (MPLS-TP) Linear Protection. Status of This Memo This Internet-Draft is submitted to IETF in full conformance with the @@ -33,25 +33,25 @@ 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 February 8, 2014. +This Internet-Draft will expire on August 8, 2014. Copyright and License Notice -Copyright (c) 2013 IETF Trust and the persons identified as the document +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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. @@ -64,28 +64,30 @@ 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 3 5.2. The MPLS TP Linear Protection Subtree . . . . . . . . . . . 4 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . . 4 5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 6.1. Relationship to the MPLS OAM maintenance identifiers MIB module . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 5 - 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 - 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 - 10.1. Normative References . . . . . . . . . . . . . . . . . . 27 - 10.2. Informative References . . . . . . . . . . . . . . . . . 28 - 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28 - 12. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 28 + 7. Example of Protection switching groups configuration for + MPLS-TP TE tunnel . . . . . . . . . . . . . . . . . . . . . . . 5 + 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 27 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 + 11.1. Normative References . . . . . . . . . . . . . . . . . . 28 + 11.2. Informative References . . . . . . . . . . . . . . . . . 29 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29 + 13. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 29 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing MPLS Transport Profile (MPLS-TP) Linear Protection. This MIB module should be used for configuring and managing the MPLS TP linear protection for MPLS TP LSPs. @@ -199,21 +201,98 @@ The MPLS-LPS-MIB module requires following MIB modules for IMPORTS: o SNMPv2-SMI defined in [RFC2578] o SNMPv2-CONF defined in [RFC2580] o SNMPv2-TC defined in [RFC2579] o MPLS-OAM-ID-STD-MIB defined in [draft-ietf-mpls-tp-oam-id-mib] -7. Definitions +7. Example of Protection switching groups configuration for MPLS-TP TE + tunnel + + This example considers the protection group configuration on a + head-end LSR to provide protection for a co-routed bidirectional + MPLS tunnel. + Only relevant objects which are applicable for protection group + identifiers of co-routed MPLS tunnel are illustrated here. + + In mplsOamIdMegTable: + { + -- MEG index (Index to the table) + mplsOamIdMegIndex = 1, + mplsOamIdMegName = "MEG1", + mplsOamIdMegOperatorType = ipCompatible (1), + mplsOamIdMegServiceType = lsp (1), + mplsOamIdMegMpLocation = perNode(1), + -- Mandatory parameters needed to activate the row go here + mplsOamIdMegRowStatus = createAndGo (4) + } + + This will create an entry in the mplsOamIdMegTable to protect + the MPLS tunnel. + + The following ME table is used to associate the path information + to a MEG. + + 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 + mplsOamIdMeSourceMepIndex = 0, + -- Source MEP id is derived from the IP compatible MPLS + -- tunnel + mplsOamIdMeSinkMepIndex = 0, + mplsOamIdMeMpType = mep (1), + mplsOamIdMeMepDirection = down (2), + mplsOamIdMeProactiveOamPhbTCValue = 0, + mplsOamIdMeOnDemandOamPhbTCValue = 0, + -- RowPointer MUST point to the first accessible column + -- of an MPLS tunnel + mplsOamIdMeServicePointer = mplsTunnelName.1.1.1.2, + -- Mandatory parameters needed to activate the row go here + mplsOamIdMeRowStatus = createAndGo (4) + } + + The below table associates the MEs with protection switching + groups. + In mplsLpsConfigTable: + mplsLpsConfigEntry ::= SEQUENCE { + -- Group index + mplsLpsConfigGroupIndex = 1, + mplsLpsConfigGroupName = "PGGroup1", + mplsLpsConfigMode = onePlusOne (1), + -- Mandatory parameters needed to activate the row go here + mplsLpsConfigRowStatus = createAndGo (4) + } + In mplsLpsMeConfigTable: + MplsLpsMeConfigEntry ::= SEQUENCE { + -- MEG index (Index to the table) + mplsOamIdMegIndex = 1, + -- ME index + mplsOamIdMeIndex = 1, + -- MP index (Index to the table) + mplsOamIdMeMpIndex = 1, + -- Group index + mplsLpsMeConfigGroupIndex = 1, + -- Configuration state + mplsLpsMeConfigState = primary(1) + } + +8. Definitions MPLS-LPS-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, Gauge32, Counter32, Integer32, Unsigned32 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] TEXTUAL-CONVENTION, RowStatus, TimeStamp, StorageType @@ -1141,21 +1222,21 @@ mplsLpsEventModeMismatch } STATUS current DESCRIPTION "Collection of objects needed to implement notifications." ::= { mplsLpsGroups 4 } -- MPLS-LPS-MIB module ends END -8. Security Considerations +9. Security Considerations 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 objects may be considered sensitive or vulnerable in some networks in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: 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 @@ -1177,71 +1258,74 @@ authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is not recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. -9. IANA Considerations +10. IANA Considerations - To be added in a later version of this document. + IANA is requested to assign an OID for the MIB module from the "MIB + Transmission Group - MPLS STD" sub-registry of the "Internet-standard + MIB - Transmission Group" registry for the MPLS Linear Protection MIB + module specified in this document. -10. References +11. References -10.1. Normative References +11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. -10.2. Informative References +11.2. Informative References [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction and Applicability Statement for Internet Standard Management Framework", RFC 3410, December 2002. [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004. [RFC6378] Weingarten, Y., Osborne, E., Sprecher, N., Fulignoli, A., Ed., and Y. Weingarten, Ed., "MPLS-TP Linear Protection", October 2011. [MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath, Thomas D. Nadeau, Sami Boutros, Ping Pan, "MPLS-TP Operations, Administration, and Management (OAM) Identifiers Management Information Base (MIB)", ID draft-ietf-mpls-tp-oam-id-mib-01, October 2012. -11. Acknowledgments +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. -12. Author's Address +13. Author's Address Kingston Smiler Selvaraj IpInfusion India Email: kingstons@ipinfusion.com Venkatesan Mahalingam Dell Inc. 350 Holger way, San Jose, CA, USA Email: venkat.mahalingams@gmail.com