--- 1/draft-ietf-l2vpn-vpls-mib-03.txt 2010-04-10 01:11:27.000000000 +0200 +++ 2/draft-ietf-l2vpn-vpls-mib-04.txt 2010-04-10 01:11:27.000000000 +0200 @@ -1,20 +1,22 @@ Internet Draft Thomas D. Nadeau (Ed.) -Intended status: Standards Track A S Kiran Koushik (Ed.) -Expires: Nov 2010 Cisco Systems, Inc. +Intended status: Standards Track BT +Expires: Dec 2010 + A S Kiran Koushik (Ed.) + Cisco Systems, Inc. Rohit Mediratta (Ed.) Alcatel-Lucent Virtual Private Lan Services (VPLS) Management Information Base - draft-ietf-l2vpn-vpls-mib-03.txt + draft-ietf-l2vpn-vpls-mib-04.txt 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. @@ -23,44 +25,37 @@ 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 November 07, 2010. + This Internet-Draft will expire on December 07, 2010. Abstract This memo defines an experimental portion of the Management Information Base for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Virtual Private LAN services. It needs to be used in conjunction with Pseudo Wire (PW) Management Information Base - [PWE3-PW-MIB]. + [RFC5601]. Table of Contents Abstract........................................................1 1 Introduction................................................2 -1.1 Changes from version 00 to 01 (individual submission)......2 -1.2 Changes from version 01 to 02 (individual submission)......3 -1.3 Changes from version 02 to 03 (individual submission)......3 -1.4 Changes from version 03 to 04 (individual submission)......3 - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 -1.5 Changes from version 00 to 01 (Standards track).............3 -1.6 Changes from version 01 to 02 (Standards track).............3 -1.7 Changes from version 02 to 03 (Standards track).............3 2 Terminology..................................................4 3 The Internet-Standard Management Framework...................4 4 VPLS MIB Module Architecture.................................4 4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage......................4 4.2 VPLS-LDP-DRAFT-01-MIB Module Usage..........................5 4.3 VPLS-BGP-DRAFT-01-MIB Module Usage..........................5 4.4 Relations to other MIB modules..............................5 5 Example of the VPLS MIB modules usage........................6 6 Object definitions...........................................6 6.1 VPLS-GENERIC-DRAFT-01-MIB...................................7 @@ -74,106 +69,43 @@ 10 Acknowledgement.............................................43 11 Authors' Addresses..........................................43 12 Full Copyright Statement....................................45 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 [L2VPN-VPLS-LDP] or - BGP[L2VPN-VPLS-BGP] signalling. This MIB module provides generic + 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. Comments should be made directly to the L2VPN mailing list at l2vpn@ietf.org. 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 [RFC2119]. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in - RFC-2119 [BCP14]. - -1.1 Changes from version 00 to 01 (individual submission) - - [NOTE to RFC Editor: this section is to be removed before - publication.] - - 1.1.1. Split the MIB modules into VPLS-GENERIC-DRAFT-01-MIB, - VPLS-LDP-DRAFT-01-MIB, VPLS-BGP-DRAFT-01-MIB. - The generic MIB Module will contain information common - to both LDP and BGP signalled VPLS. - 1.1.2. Moved certain objects from vplsConfigTable to - vplsStatusTable. - 1.1.3. Added new objects to the vplsLdpPwBindTable. - 1.1.4. Retained MAC related objects since there is specific - reference in [L2VPN-VPLS-LDP] and [L2VPN-VPLS-BGP]. - -1.2 Changes from version 01 to 02 (individual submission) - - [NOTE to RFC Editor: this section is to be removed before - publication.] - - 1.2.1. Added new objects to the vplsConfigTable. - 1.2.2. Editorial changes. - -1.3 Changes from version 02 to 03 (individual submission) - - [NOTE to RFC Editor: this section is to be removed before - publication.] - - 1.3.1. Added the VPLS-BGP-DRAFT-01-MIB module. - -1.4 Changes from version 03 to 04 (individual submission) - - [NOTE to RFC Editor: this section is to be removed before - publication.] - - 1.4 Published as a Standards Track document. - -1.5 Changes from version 00 to 01 (Standards track) - - [NOTE to RFC Editor: this section is to be removed before - publication.] - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 - - 1.5.1 Added the mechanism to associate VPLS MIB Mac address - entries into BRIDGE-MIB. - 1.5.2 Added Rohit Mediratta as a co-editor. - -1.6 Changes from version 01 to 02 (Standards track) - - [NOTE to RFC Editor: this section is to be removed before - publication.] - 1.6.1 Added support for BGP based Autodiscovery for Ldp and Bgp - flavours of Vpls. - 1.6.2 Created separate table for RouteTarget to allow representation - of hierarchical Vpls. - 1.6.3 Moved configuration of Route Distinguisher and Route Target - to the Vpls-MIB from the VPLS-BGP-MIB - 1.6.4 Removed extra defintion of pwIndex from vplsPwBindTable - 1.6.5 Index for vplsBgpObjects were incorrect, fixed. + RFC-2119 [RFC2119]. -1.7 Changes from version 02 to 03 (Standards track) - 1.7.1 Added Notification for vplsLdpPwBindMacTableFull. - 1.7.2 Attachment Circuit being a PW is now incorporated in the - [SNMP-CONTEXT-MAPPING-MIB] + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 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. 3 The Internet-Standard Management Framework For a detailed overview of the documents that describe the current @@ -187,32 +119,32 @@ defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58,[RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 4 VPLS MIB Module Architecture The MIB structure for defining a VPLS service is composed from four types of MIB modules. - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 The first type is the VPLS-GENERIC-DRAFT-01-MIB module, which configures general parameters of the VPLS service that are common to all types of emulated services. The second type is the VPLS-LDP-DRAFT-01-MIB module, which - configures VPLS-LDP[L2VPN-VPLS-LDP] specific parameters of the + configures VPLS-LDP[RFC4762] specific parameters of the VPLS service. The third type is the VPLS-BGP-DRAFT-01-MIB module, which configures - VPLS-BGP[L2VPN-VPLS-BGP] specific parameters of the + VPLS-BGP[RFC4761] specific parameters of the VPLS service. The fourth type of modules are service-specific modules, which are defined in other documents. -------- ----------------- PW Mapping | | | | -----> | PW-MIB |-->|PW-ENET/MPLS-MIB | __________ / | | | | | | / -------- ----------------- @@ -235,23 +167,23 @@ supported by the agent, and MUST be used when creating a 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 - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 - pseudo wires (defined in [PWE3-PW-MIB]). The pseudo wire may + pseudo wires (defined in [RFC5601]). The pseudo wire may be used as a spoke or 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. @@ -265,39 +197,39 @@ for a VPLS service signalled using LDP. 4.3 VPLS-BGP-DRAFT-01-MIB Module Usage An entry in the vplsBgpConfigTable MUST be created by the agent for a VPLS service signalled using BGP. 4.4 Relations to other MIB modules - The vplsPwBindTable links the VPLS entry to various entries in - the [PWE3-PW-MIB] + the [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. - Unless all the necessary entries in the applicable tables have been created and all the parameters have been consistently configured in those tables, signaling cannot be performed from the local node, and the ??? should report 'notPresent'. - - Statistics can be gathered from the [PWE3-PW-MIB] - TBD - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + - Statistics can be gathered from the [RFC5601] - TBD + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 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. @@ -333,21 +265,21 @@ vplsLdpPwBindType 1(mesh), vplsLdpPwBindMacAddressLimit 100 } 6 Object definitions 6.1 VPLS-GENERIC-DRAFT-01-MIB This MIB module makes references to the following documents. - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 [RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC2863], [RFC4001], [RFC4265] and [RFC3813]. VPLS-GENERIC-DRAFT-01-MIB DEFINITIONS ::= BEGIN IMPORTS NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, transmission FROM SNMPv2-SMI -- RFC2578 @@ -367,37 +299,37 @@ VPNIdOrZero FROM VPN-TC-STD-MIB -- RFC4265 -- Vpls BGP Autodiscovery 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 [L2VPN-VPLS-BGP]" + for a VPLS service, see [RFC4761]" REFERENCE "[RFC4364]" SYNTAX OCTET STRING(SIZE (0..256)) VplsBgpRouteTarget ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Syntax for a route target. For a complete definition of a route target, see [RFC4364]." REFERENCE "[RFC4364]" SYNTAX OCTET STRING(SIZE (0..256)) VplsBgpRouteTargetType ::= TEXTUAL-CONVENTION STATUS current - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 DESCRIPTION "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) } @@ -419,36 +351,36 @@ DESCRIPTION "Copyright (C) The IETF Trust (2010). 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 in [L2VPN-VPLS-LDP] and - [L2VPN-VPLS-BGP] + for Virtual Private LAN Services as in [RFC4762] and + [RFC4761] This MIB module enables the use of any underlying PseudoWire network." -- Revision history. REVISION "200608301200Z" -- 30 August 2006 12:00:00 GMT DESCRIPTION "Changes from previous version: 1) Moved LDP Specific information to VPLS-LDP-DRAFT-01-MIB 2) Created the vplsStatusTable to store status information. 3) - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 " REVISION "200606041200Z" -- 4 June 2006 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 } @@ -482,21 +414,21 @@ value of vplsConfigIndex for a new entry in the vplsConfigTable, the manager issues a management protocol retrieval operation to obtain the current value of vplsConfigIndex. After each retrieval operation, the agent should modify the value to reflect the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse." ::= { vplsObjects 1 } - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF VplsConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies information for configuring and monitoring Virtual Private Lan Services(VPLS). " ::= { vplsObjects 2 } @@ -532,21 +464,21 @@ SEQUENCE { vplsConfigIndex Unsigned32, vplsConfigName SnmpAdminString, vplsConfigDescr SnmpAdminString, vplsConfigAdminStatus INTEGER, vplsConfigMacLearning TruthValue, vplsConfigDiscardUnknownDest TruthValue, vplsConfigMacAging TruthValue, vplsConfigFwdFullHighWatermark Unsigned32, vplsConfigFwdFullLowWatermark Unsigned32, - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsConfigRowStatus RowStatus, vplsConfigMtu Unsigned32, vplsConfigVpnId VPNIdOrZero, vplsConfigServiceType INTEGER, vplsConfigStorageType StorageType } vplsConfigIndex OBJECT-TYPE SYNTAX Unsigned32 (1.. 2147483647) @@ -583,21 +515,21 @@ vplsConfigAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), testing(3) -- in some test mode } MAX-ACCESS read-create - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 STATUS current DESCRIPTION "The desired administrative state of the VPLS service. If the administrative status of the Vpls service is changed to enable then this service is able to utilize the pseudo wire to perform the tasks of a VPLS service. The testing(3) state indicates that no operational packets can be passed. " @@ -633,21 +565,21 @@ MAX-ACCESS read-create STATUS current DESCRIPTION "If the value of this object is 'true' then the MAC ageing process is enabled in this VPLS. If 'false', then the MAC ageing process is disabled" DEFVAL { true } ::= { vplsConfigEntry 8 } - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsConfigFwdFullHighWatermark OBJECT-TYPE SYNTAX Unsigned32 (0..100) UNITS "percentage" MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the utilization of the forwarding database for this VPLS instance at which the vplsFwdFullAlarmRaised notification @@ -683,21 +615,21 @@ SYNTAX Unsigned32 (64..1518) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object specifies the MTU of this vpls instance." DEFVAL { 1518 } ::= { vplsConfigEntry 13 } vplsConfigVpnId OBJECT-TYPE - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 SYNTAX VPNIdOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "This objects indicates the IEEE 802-1990 VPN ID of the associated VPLS service." -- Ed note: Should we import the VPNIdOrZero TC or -- define a new TC? ::= { vplsConfigEntry 14 } @@ -734,21 +666,21 @@ "This table provides information for monitoring Virtual Private Lan Services(VPLS). " ::= { vplsObjects 3 } vplsStatusEntry OBJECT-TYPE SYNTAX VplsStatusEntry MAX-ACCESS not-accessible STATUS current - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 DESCRIPTION "A row in this table represents a Virtual Private Lan Service(VPLS) in a packet network. It is indexed by vplsConfigIndex, which uniquely identifies a single VPLS. A row in this table is automatically created by the agent when a VPLS service is configured. " INDEX { vplsConfigIndex } @@ -784,21 +716,21 @@ -- VPLS PW Binding Table vplsPwBindTable OBJECT-TYPE SYNTAX SEQUENCE OF VplsPwBindEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides an association between a VPLS service and the corresponding Pseudo - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 Wires. A service can have more than one Pseudo Wire association. Pseudo Wires are defined in the pwTable" ::= { vplsObjects 4 } vplsPwBindEntry OBJECT-TYPE SYNTAX VplsPwBindEntry MAX-ACCESS not-accessible STATUS current @@ -835,21 +767,21 @@ The value of this object must be specifed when the row is created and cannot be changed while the row status is active(1)" ::= { vplsPwBindEntry 1 } vplsPwBindType OBJECT-TYPE SYNTAX INTEGER { mesh (1), - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 spoke (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object indicates whether the Pseudo Wire binding is of type mesh or spoke. @@ -886,21 +818,21 @@ STATUS current DESCRIPTION "This table specifies information for configuring BGP Auto-discovery parameters for a given Vpls service. " ::= { vplsObjects 5 } vplsBgpADConfigEntry OBJECT-TYPE SYNTAX VplsBgpADConfigEntry - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in this table represents BGP based autodiscovery is in use for this instance of Vpls. A row in this table is indexed by vplsConfigIndex, which uniquely identifies a single VPLS. None of the read-create objects can be changed when vplsBGPADConfigRowStatus is in active(1) state. Changes @@ -925,33 +857,33 @@ } vplsBgpADConfigRouteDistinguisher OBJECT-TYPE SYNTAX VplsBgpRouteDistinguisher MAX-ACCESS read-create STATUS current DESCRIPTION " The route distinguisher for this VPLS. See [RFC4364] for a complete definition of a route distinguisher. for more details on use of a route distinguisher - for a VPLS service, see [L2VPN-VPLS-BGP] + for a VPLS service, see [RFC4761] " ::= { vplsBgpADConfigEntry 1 } vplsBgpADConfigPrefix OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION " In case of auto-discovery the default prefix advertised is the ip address of the loopback. In case the user wants - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 to override the loopback address, vplsBgpADConfigPrefix should be set. When this value if non-zero it is used as the advertised IP address in the NLRI. " DEFVAL { 0 } ::= { vplsBgpADConfigEntry 2 } vplsBgpADConfigVplsId OBJECT-TYPE SYNTAX VplsBgpRouteDistinguisher @@ -987,21 +919,21 @@ " ::= { vplsObjects 5 } vplsBgpRteTargetEntry OBJECT-TYPE SYNTAX VplsBgpRteTargetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table specifies the value of the - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 Route Target being used by BGP. Depending on the value of vplsBgpRteTargetType an RT might be exported or imported or both. Every VPLS which uses auto-discovery for finding peer nodes can import and export multiple Route Targets. This representation allows support for hierarchical VPLS. " INDEX { vplsConfigIndex, vplsBgpRteTargetIndex } ::= { vpsBgpRteTargetTable 1 } @@ -1038,24 +970,24 @@ " ::= { vplsBgpADConfigEntry 2 } vplsBgpRteTargetRT OBJECT-TYPE SYNTAX VplsBgpRouteTarget MAX-ACCESS read-create STATUS current DESCRIPTION " The route target associated with the VPLS service. - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 For more details on use of route targets - for a VPLS service, see [L2VPN-VPLS-BGP] + for a VPLS service, see [RFC4761] " ::= { vplsBgpADConfigEntry 3 } vplsBgpRteTargetRowStatus 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 @@ -1088,21 +1020,21 @@ "This object indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period, or may queue them until an appropriate time. A value of 0 means no throttling is applied and events may be notified at the rate at which they occur." DEFVAL { 0 } ::= { vplsObjects 8 } - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 -- VPLS Service Notifications vplsStatusChanged NOTIFICATION-TYPE OBJECTS { vplsConfigVpnId, vplsConfigAdminStatus, vplsStatusOperStatus } STATUS current @@ -1137,21 +1069,21 @@ "The vplsFwdFullAlarmCleared notification is generated when the utilization of the Forwarding database is below the value specified by vplsConfigFwdFullLowWatermark." ::= { vplsNotifications 3 } -- Compliance requirement for read-only implementations. vplsCompliances OBJECT IDENTIFIER ::= { vplsConformance 1 } - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that provide full support for VPLS-GENERIC-DRAFT-01-MIB. Such devices can then be monitored and configured using this MIB module." MODULE -- this module @@ -1186,21 +1118,21 @@ OBJECT vplsConfigDescr MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT vplsConfigAdminStatus MIN-ACCESS read-only DESCRIPTION - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 "Write access is not required." OBJECT vplsConfigMacLearning MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT vplsConfigDiscardUnknownDest MIN-ACCESS read-only @@ -1236,21 +1168,21 @@ OBJECT vplsConfigServiceType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT vplsPwBindConfigType MIN-ACCESS read-only DESCRIPTION "Write access is not required." - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 OBJECT vplsPwBindType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT vplsPwBindRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." @@ -1285,21 +1217,21 @@ vplsStatusNotifEnable, vplsNotificationMaxRate } STATUS current DESCRIPTION "The group of objects supporting management of L2VPN VPLS services" ::= { vplsGroups 1 } vplsPwBindGroup OBJECT-GROUP - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 OBJECTS { vplsPwBindConfigType, vplsPwBindType, vplsPwBindRowStatus, vplsPwBindStorageType } STATUS current DESCRIPTION "The group of objects supporting @@ -1333,21 +1265,21 @@ IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission FROM SNMPv2-SMI -- RFC2578 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC2580 TruthValue FROM SNMPv2-TC -- RFC2579 - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsConfigIndex, vplsPwBindIndex FROM VPLS-GENERIC-DRAFT-01-MIB; vplsLdpDraft01MIB MODULE-IDENTITY LAST-UPDATED "200608301200Z" -- 20 August 2006 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) Working Group" CONTACT-INFO " @@ -1363,40 +1295,40 @@ 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 signalled Virtual Private LAN Services as in - [L2VPN-VPLS-LDP] + [RFC4762] This MIB module enables the use of any underlying PseudoWire network. " -- Revision history. REVISION "200608301200Z" -- 30 Aug 2006 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 assigne value, and -- delete this note. -- Top-level components of this MIB. - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 -- Notifications vplsLdpNotifications OBJECT IDENTIFIER ::= { vplsLdpDraft01MIB 0 } -- Tables, Scalars vplsLdpObjects OBJECT IDENTIFIER ::= { vplsLdpDraft01MIB 1 } -- Conformance vplsLdpConformance OBJECT IDENTIFIER @@ -1432,21 +1364,21 @@ If the operator need to change one of the values for an active row the vplsConfigRowStatus should be first changed to notInService(2), the objects may be changed now, and later to active(1) in order to re-initiate the signaling process with the new values in effect. " INDEX { vplsConfigIndex } ::= { vplsLdpConfigTable 1 } - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 VplsLdpConfigEntry ::= SEQUENCE { vplsLdpConfigMacAddrWithdraw TruthValue } vplsLdpConfigMacAddrWithdraw OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current @@ -1483,21 +1415,21 @@ in describing an entry in this table. However both indexes are required to define the one to many association of service to pseudowire. An entry in this table in instantiated only when LDP signalling is used to configure VPLS service. Each entry in this table provides LDP specific information for the VPlS represented by - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsConfigIndex." INDEX { vplsConfigIndex, vplsPwBindIndex } ::= { vplsLdpPwBindTable 1 } VplsLdpPwBindEntry ::= SEQUENCE { vplsLdpPwBindMacAddressLimit Unsigned32 } @@ -1532,21 +1464,21 @@ vplsLdpCompliances OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } vplsLdpModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that provide full support for VPLS-LDP-DRAFT-01-MIB. Such devices can then be monitored and configured using - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 this MIB module." MODULE -- this module MANDATORY-GROUPS { vplsLdpGroup, vplsLdpNotificationGroup } @@ -1582,21 +1514,21 @@ -- Units of conformance. vplsLdpGroups OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } vplsLdpGroup OBJECT-GROUP OBJECTS { vplsLdpConfigMacAddrWithdraw, vplsLdpPwBindMacAddressLimit - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 } STATUS current DESCRIPTION "The group of objects supporting management of L2VPN VPLS services using LDP." ::= { vplsLdpGroups 1 } vplsLdpNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { @@ -1631,41 +1563,41 @@ vplsConfigIndex, vplsPwBindIndex FROM VPLS-GENERIC-DRAFT-01-MIB ; vplsBgpDraft01MIB MODULE-IDENTITY LAST-UPDATED "200612061200Z" -- 06 Dec 2006 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) Working Group" CONTACT-INFO - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 " 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 (2010). 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 signalled Virtual Private LAN Services as in - [L2VPN-VPLS-BGP] + [RFC4761] This MIB module enables the use of any underlying PseudoWire network. " -- Revision history. REVISION "200612061200Z" -- 06 Dec 2006 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. @@ -1673,29 +1605,29 @@ -- RFC Editor: please replace XXXX with IANA assigne value, and -- delete this note. -- VPLS BGP specific Textual Conventions. 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 [L2VPN-VPLS-BGP]" + for a VPLS service, see [RFC4761]" REFERENCE "[RFC4364]" SYNTAX OCTET STRING(SIZE (0..256)) VplsBgpRouteTarget ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 "Syntax for a route target. For a complete definition of a route target, see [RFC4364]." REFERENCE "[RFC4364]" SYNTAX OCTET STRING(SIZE (0..256)) -- Top-level components of this MIB. -- Tables, Scalars @@ -1732,21 +1664,21 @@ None of the read-create objects values can be changed when vplsRowStatus is in the active(1) state. Changes are allowed when the vplsRowStatus is in notInService(2) or notReady(3) states only. If the operator need to change one of the values for an active row the vplsConfigRowStatus should be first changed to notInService(2), the objects may be changed now, and later to active(1) in order to - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 re-initiate the signaling process with the new values in effect. " INDEX { vplsConfigIndex } ::= { vplsBgpConfigTable 1 } VplsBgpConfigEntry ::= SEQUENCE { vplsBgpConfigVERangeSize Unsigned32 @@ -1783,21 +1715,21 @@ DESCRIPTION "An entry in this table is created for each VE Id configured on a PE for a particular VPLS service instance." INDEX { vplsConfigIndex, vplsBgpVEId } ::= { vplsBgpVETable 1 } VplsBgpVEEntry ::= SEQUENCE { vplsBgpVEId Unsigned32, - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsBgpVEName SnmpAdminString, vplsBgpVEPreference Unsigned32, vplsBgpVERowStatus RowStatus, vplsBgpVEStorageType StorageType } vplsBgpVEId OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS not-accessible @@ -1834,21 +1766,21 @@ 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 except vplsBgpSiteRowStatus." ::= { vplsBgpVEEntry 5 } vplsBgpVEStorageType OBJECT-TYPE SYNTAX StorageType - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this row." DEFVAL { volatile } ::= { vplsBgpVEEntry 6 } -- VPLS BGP PW Binding Table @@ -1884,21 +1816,21 @@ vplsConfigIndex." INDEX { vplsConfigIndex, vplsPwBindIndex } ::= { vplsBgpPwBindTable 1 } VplsBgpPwBindEntry ::= SEQUENCE { vplsBgpPwBindLocalVEId Unsigned32, vplsBgpPwBindRemoteVEId Unsigned32 } - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsBgpPwBindLocalVEId OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Identifies the local VE that this Pseudo Wire is associated with." ::= { vplsBgpPwBindEntry 1 } @@ -1934,21 +1866,21 @@ ::= { vplsBgpCompliances 1 } vplsBgpModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for VPLS-BGP-DRAFT-01-MIB. Such devices can then be monitored but cannot be configured using this MIB modules." - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 MODULE -- this module MANDATORY-GROUPS { vplsBgpConfigGroup, vplsBgpVEGroup, vplsBgpPwBindGroup } OBJECT vplsBgpConfigRouteDistinguisher @@ -1984,21 +1916,21 @@ ::= { vplsBgpCompliances 2 } -- Units of conformance. vplsBgpGroups OBJECT IDENTIFIER ::= { vplsBgpConformance 2 } vplsBgpConfigGroup OBJECT-GROUP OBJECTS { - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 vplsBgpConfigVERangeSize } STATUS current DESCRIPTION "The group of objects supporting configuration of L2VPN VPLS services using BGP" ::= { vplsBgpGroups 1 } vplsBgpVEGroup OBJECT-GROUP @@ -2023,59 +1955,98 @@ DESCRIPTION "The group of objects supporting management of Pseudo Wires for L2VPN VPLS services using BGP" ::= { vplsBgpGroups 3 } END 7. Security Considerations It is clear that the MIB modules described in this document in - association with the PW-STD-MIB [PW-STD-MIB] are potentially + association with the PW-STD-MIB [RFC5601] are potentially useful for monitoring of GMPLS LSRs. These MIB modules can also be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. There are a number of management objects defined in these MIB modules with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 network operations. These are the tables and objects and their sensitivity/vulnerability: 8. IANA Considerations -- (Note to RFC-Editor:) -- We request that you assign contiguous RFC numbers to the -- IANA is requested to root MIB objects in the MIB module -- contained in this document under the transmission subtree. -- 9. References 9.1 Normative References - [PWE3-PW-MIB] Pseudo Wire (PW) Management Information Base. - David Zelig, Thomas D. Nadeau. - [L2VPN-VPLS-LDP] Virtual Private LAN Services over MPLS, - Marc Lasserre, Vach Kompella. - [L2VPN-VPLS-BGP] Virtual Private LAN Service (VPLS) Using BGP - for Auto-discovery and Signaling, - K. Kompella, Y. Rekhter. + [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate + Requirement Levels", RFC 2119, BCP 14, March 1997. + + [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group + MIB", RFC 2863, June 2000. + + [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network + Management Protocol (SNMP) Applications", STD 62, RFC + 3413, December 2002. + + [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View- + based Access Control Model (VACM) for the Simple + Network Management Protocol (SNMP)", STD 62, RFC + 3415, December 2002. + + [RFC3813] Srinivasan, C., Viswanathan, A. and Nadeau, T., + "Multiprotocol Label Switching (MPLS) Label Switching + Router (LSR) Management Information Base", + RFC 3813, June 2004 + + [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- + Edge (PWE3) Architecture", RFC 3985, March 2005. + + [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. + Schoenwaelder, "Textual Conventions for Internet Network + Addresses", RFC 4001, Feb 2005. [RFC4188] Norseth, K., and Bell, E., "Definitions of Managed Objects for Bridges", RFC 4188, Sept 2006. + [RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual + Conventions for Virtual Private Network (VPN) Management", + RFC 4265, November 2005. + + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 + + [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private + Networks (VPNs)", RFC 4364, February 2006. + + [RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service + (VPLS) Using BGP for Auto-Discovery and Signaling",RFC + 4761, January 2007. + + [RFC4762] Lasserre, M. and Kompella, V. (Editors), "Virtual Private + LAN Service (VPLS) Using Label Distribution Protocol (LDP) + Signaling", RFC 4762, January 2007. + + [RFC5601] T. Nadeau, Ed., D. Zelig, Ed., "Pseudowire (PW) + Management Information Base (MIB)", RFC 5601, July 2009. + 9.2 Informative References [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. @@ -2072,40 +2043,39 @@ 9.2 Informative References [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. - [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 - [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. + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 + 10 Acknowledgement 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. 11 Authors' Addresses Thomas D. Nadeau Cisco Systems, Inc. @@ -2129,26 +2099,24 @@ Alcatel-Lucent Email: praveen.muley@alcatel-lucent.com Reva Bailey Alcatel-Lucent Email: reva.bailey@alcatel-lucent.com VJ Shah Juniper Networks Email: vshah@juniper.net + draft-ietf-l2vpn-vpls-mib-04 L2-VPN-MIB Apr 07, 2010 Li Wentao ZTE Inc. - - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 - CHINA Email: li.wentao@zte.com.cn Kong Yong ZTE Inc. CHINA Email: kong.yong@zte.com.cn Luo Jian ZTE Inc. @@ -2157,26 +2125,37 @@ Feng Jun ZTE Inc. CHINA Email: Feng.jun99@zte.com.cn Takeshi Usui KDDI Corpration Japan Email:ta-usui@kddi.com - draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 12 Full Copyright Statement Copyright (c) 2010 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. + + 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 + modifications of such material outside the IETF Standards Process. + Without obtaining an adequate license from the person(s) + controlling the copyright in such materials, this document may not + be modified outside the IETF Standards Process, and derivative + works of it may not be created outside the IETF Standards Process, + except to format it for publication as an RFC or to translate it + into languages other than English.