--- 1/draft-ietf-l2vpn-vpls-mib-07.txt 2013-02-25 21:35:36.471874336 +0100 +++ 2/draft-ietf-l2vpn-vpls-mib-08.txt 2013-02-25 21:35:36.539874500 +0100 @@ -1,24 +1,24 @@ L2VPN Working Group Thomas D. Nadeau (Ed.) Internet Draft Juniper Networks Intended status: Standards Track -Expires: April 2013 A S Kiran Koushik (Ed.) +Expires: Aug 2013 A S Kiran Koushik (Ed.) Cisco Systems, Inc. Rohit Mediratta (Ed.) Alcatel-Lucent - September 29, 2012 + February 22, 2013 Virtual Private Lan Services (VPLS) Management Information Base - draft-ietf-l2vpn-vpls-mib-07.txt + draft-ietf-l2vpn-vpls-mib-08.txt Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow @@ -42,21 +42,21 @@ 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 April 2, 2013. Copyright Notice - Copyright (c) 2012 IETF Trust and the persons identified as the + Copyright (c) 2013 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 @@ -99,48 +99,47 @@ 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 defines a MIB module that can be used to manage VPLS (Virtual Private LAN Services) for transmission over a packet Switched Network (PSN) using LDP [RFC4762] or BGP [RFC4761] signalling. This MIB module provides generic management of VPLS services as defined by the IETF L2VPN Working Group. Additional MIB modules are also defined for management of LDP VPLS and BGP VPLS - services as defined by they IETF L2VPN Working Group. + services as defined by the IETF L2VPN Working Group. 2. Terminology This document adopts the definitions, acronyms and mechanisms described in [RFC3985]. Unless otherwise stated, the mechanisms of [RFC3985] apply and will not be re-described here. 2.1. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "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 [RFC2119]. 3. 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 RFC 3410 [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). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a set of MIB modules that are compliant to the SMIv2, - which is described in STD 58 [RFC2578], STD 58 [RFC2579] and STD 58 - [RFC2580]. + which is described in STD 58 [RFC2578][RFC2579][RFC2580]. 4. VPLS MIB Module Architecture The MIB structure for defining a VPLS service is composed from three MIB modules. The first is the VPLS-GENERIC-MIB module, which configures general parameters of the VPLS service that are common to all types of VPLS services. @@ -154,20 +153,23 @@ PW Mapping | | | | -----> | PW-MIB |-->|PW-ENET/MPLS-MIB | __________ / | | | | | | / -------- ----------------- | VPLS MIB | / ------------ | |----------------------> | | ---------- MAC addr. mapping using | BRIDGE-MIB | [SNMP-CONTEXT-MAP-MIB] | | ------------ + Figure A + -------- + Additionally service-specific modules may be defined in other documents. 4.1. VPLS-GENERIC-MIB Module Usage An entry in the vplsConfigTable MUST exist for a VPLS service. This table holds generic parameters which apply to a VPLS service which can be signaled via LDP or BGP. A conceptual row can be created in the vplsConfigTable in one of @@ -179,49 +181,49 @@ manually assigned VPLS service. 2) The agent MAY create a row in the vplsConfigTable automatically due to some auto discovery application, or based on configuration that is done through non-SNMP applications. This mode is OPTIONAL. An entry in the vplsPwBindTable MUST exist for a VPLS service. This binding table links one VPLS service with one or many pseudowires (defined in [RFC5601]). Each pseudowire may - be used as a spoke or a mesh based on the parameters defined - in this table. + be used as a spoke or as part of a mesh based on the parameters + defined in this table. An entry in the vplsBgpAdConfigTable MUST exist if Auto-discovery has been enabled on this service. This table stores the information required for auto-discovery. An entry in the vplsBgpRteTargetTable MUST exist if auto-discovery has been configured on this service. One service can import - and export multiple Route targets. + and export multiple Route Targets. The agent then creates the rows in the (locally supported) performance tables and reverse mapping tables in VPLS-GENERIC-MIB module. 4.2. VPLS-LDP-MIB Module Usage An entry in the vplsLdpConfigTable MUST be created by the agent for a VPLS service signaled using LDP. 4.3. VPLS-BGP-MIB Module Usage An entry in the vplsBgpConfigTable MUST be created by the agent for a VPLS service signaled using BGP. 4.4. Relations to other MIB modules - The vplsPwBindTable links the VPLS entry to the pwTable in - the [RFC5601] + [RFC5601] - The association of MAC addresses to VPLS entries is possible by adding a turnstile function to interpret the entries in [SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB] there is a mapping between the vacmContextName [RFC3415] to dot1dBasePort [RFC4188] and vplsConfigIndex. This mapping can be used to map the vplsConfigIndex to a dot1dBasePort in the BRIDGE-MIB. This resulting value of dot1dBasePort can be used to access corresponding MAC addresses that belong to a particular vplsConfigIndex. @@ -236,61 +238,61 @@ tables in [RFC5601] 5. Example of the VPLS MIB modules usage In this section we provide an example of using the MIB objects described in section 7 to set up a VPLS service over MPLS. While this example is not meant to illustrate every permutation of the MIB, it is intended as an aid to understanding some of the key concepts. It is meant to be read after going through the MIB itself. - In this example a vpls service (VPLS-A) is setup using Ldp for + In this example a vpls service (VPLS-A) is setup using LDP for signaling the pseudowire. The binding between the Vpls service and the pseudowire is reflected in the VplsPwBindTable. The pseudowire configuration is defined in RFC 5601. In the VPLS-GENERIC-MIB module: - In vplsConfigTable: + Row in vplsConfigTable: { vplsConfigIndex 10, vplsConfigName "VPLS-A" vplsConfigAdminStatus 1(up), vplsConfigMacLearning 1(true), vplsConfigDiscardUnknownDest 2(false), vplsConfigMacAging 1(true), vplsConfigVpnId "100:10" vplsConfigRowStatus 1(active) } - In vplsStatusTable: + Row in vplsStatusTable: { vplsStatusOperStatus 1(up), } - In VplsPwBindTable : + Row in VplsPwBindTable : { vplsPwBindConfigType manual, vplsPwBindType spoke, vplsPwBindRowStatus 1(active), vplsPwBindStorageType volatile } In the VPLS-LDP-MIB module: - In vplsLdpConfigTable: + Row in vplsLdpConfigTable: { vplsLdpConfigMacAddrWithdraw 1(true), } - In vplsLdpPwBindTable: + Row in vplsLdpPwBindTable: { vplsLdpPwBindType 1(mesh), vplsLdpPwBindMacAddressLimit 100 } 6. Object definitions 6.1. VPLS-GENERIC-MIB This MIB module makes references to the following documents. @@ -313,21 +315,21 @@ SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC3411 pwIndex FROM PW-TC-STD-MIB VPNIdOrZero FROM VPN-TC-STD-MIB -- RFC4265 - -- Vpls BGP Auto-Discovery specific Textual Convention + -- VPLS BGP Auto-Discovery specific Textual Convention VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Syntax for a route distinguisher. For a complete definition of a route distinguisher, see [RFC4364]. For more details on use of a route distinguisher for a VPLS service, see [RFC4761]" REFERENCE "[RFC4364]" SYNTAX OCTET STRING(SIZE (0..256)) @@ -347,51 +349,54 @@ "Used to define the type of a route target usage. Route targets can be specified to be imported, exported, or both. For a complete definition of a route target, see [RFC4364]." REFERENCE "[RFC4364]" SYNTAX INTEGER { import(1), export(2), both(3) } ; vplsGenericDraft01MIB MODULE-IDENTITY - LAST-UPDATED "201208261200Z" -- 26 Aug 2012 12:00:00 GMT + -- RFC Editor: Please replace vplsGenericDraft01MIB with + -- vplsGenericMIB throughout the MIB and remove + -- this note. + LAST-UPDATED "201302221200Z" -- 22 Feb 2013 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) Working Group" CONTACT-INFO " Thomas D. Nadeau Email: tnadeau@juniper.net The L2VPN Working Group (email distribution l2vpn@ietf.org, http://www.ietf.org/html.charters/l2vpn-charter.html) " DESCRIPTION - "Copyright (C) The IETF Trust (2012). The initial + "Copyright (C) The IETF Trust (2013). The initial version of this MIB module was published in RFC XXXX. -- RFC Editor: Please replace XXXX with RFC number & remove -- this note. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module contains generic managed object definitions for Virtual Private LAN Services as define in [RFC4762] and [RFC4761] This MIB module enables the use of any underlying Pseudowire network." -- Revision history. REVISION - "201209291200Z" -- 29 September 2012 12:00:00 GMT + "201302221200Z" -- 22 Feb 2013 12:00:00 GMT DESCRIPTION 1) Changed the OID for vplsBgpRteTargetTable from vplsObjects.6 to vplsObjects.5 2) Index to VplsPwBindTable is now pwIndex, not vplsPwBindIndex. 3) vplsConfigMtu increased to upto 9192 4) Default value for vplsConfigStorageType changed to nonvolatile. 5) vplsConfigServiceType should be a property of each PW. Deleting this object and adjusting the corresponding object indexes. @@ -1248,34 +1253,38 @@ TruthValue FROM SNMPv2-TC -- RFC2579 pwIndex FROM PW-TC-STD-MIB vplsConfigIndex FROM VPLS-GENERIC-MIB; vplsLdpDraft01MIB MODULE-IDENTITY - LAST-UPDATED "201208201200Z" -- 20 August 2012 12:00:00 GMT + -- RFC Editor: Please replace vplsLdpDraft01MIB with + -- vplsLdpMIB throughout the MIB and remove + -- this note. + + LAST-UPDATED "201302221200Z" -- 22 Feb 2013 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) Working Group" CONTACT-INFO " Rohit Mediratta Email: Rohit.mediratta@alcatel-lucent.com The L2VPN Working Group (email distribution l2vpn@ietf.org, http://www.ietf.org/html.charters/l2vpn-charter.html) " DESCRIPTION - "Copyright (C) The IETF Trust (2012). The initial + "Copyright (C) The IETF Trust (2013). The initial version of this MIB module was published in RFC XXXX. -- RFC Editor: Please replace XXXX with RFC number & remove -- this note. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module contains managed object definitions for LDP signaled Virtual Private LAN Services as in @@ -1529,52 +1538,55 @@ FROM SNMPv2-TC -- RFC2579 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC3411 vplsConfigIndex FROM VPLS-GENERIC-MIB ; vplsBgpDraft01MIB MODULE-IDENTITY - LAST-UPDATED "201208201200Z" -- 20 Aug 2012 12:00:00 GMT + -- RFC Editor: Please replace vplsBgpDraft01MIB with + -- vplsBgpMIB throughout the MIB and remove + -- this note. + LAST-UPDATED "201302221200Z" -- 22 Feb 2013 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) Working Group" CONTACT-INFO " V. J. Shah Email: vshah@juniper.net The L2VPN Working Group (email distribution l2vpn@ietf.org, http://www.ietf.org/html.charters/l2vpn-charter.html) " DESCRIPTION - "Copyright (C) The IETF Trust (2012). The initial + "Copyright (C) The IETF Trust (2013). The initial version of this MIB module was published in RFC XXXX. -- RFC Editor: Please replace XXXX with RFC number & remove -- this note. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module contains managed object definitions for BGP signaled Virtual Private LAN Services as in [RFC4761] This MIB module enables the use of any underlying pseudowire network. " -- Revision history. REVISION - "201208201200Z" -- 20 Aug 2012 12:00:00 GMT + "201302221200Z" -- 22 Feb 2013 12:00:00 GMT DESCRIPTION "Initial version published as part of RFC YYYY." -- RFC Editor: please replace YYYY with IANA assigned value, and -- delete this note. ::= { transmission XXXX } -- RFC Editor: please replace XXXX with IANA assigned value, and -- delete this note. -- VPLS BGP specific Textual Conventions. VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION STATUS current @@ -1994,25 +2006,28 @@ [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. + [SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik, + Nadeau, T, draft-kkoushik-snmp-context-map-mib. + [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- Edge (PWE3) Architecture", RFC 3985, March 2005. - [SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik, - Nadeau, T, draft-kkoushik-snmp-context-map-mib. + [RFC6074] E. Rosen et. al., "Provisioning, Autodiscovery, and + Signaling in L2VPNs", RFC 6074, January 2011. 10. Acknowledgments We wish to thank Marcelo Mourier and Reva Bailey for their valuable feedback. Some portion of the work has been referenced from their original Timetra Enterprise MIB work. We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo Jian, Feng Jun, Takeshi Usui for their feedback. @@ -2029,21 +2044,21 @@ Email: kkoushik@cisco.com Rohit Mediratta Alcatel-Lucent, 701 E Middlefield Rd. Mountain View, CA 94040 Email: rohit.mediratta@alcatel-lucent.com 12. Full Copyright Statement - Copyright (c) 2012 IETF Trust and the persons identified as the + Copyright (c) 2013 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