--- 1/draft-ietf-l2vpn-vpls-mib-12.txt 2014-01-17 07:14:32.220903670 -0800 +++ 2/draft-ietf-l2vpn-vpls-mib-13.txt 2014-01-17 07:14:32.304905860 -0800 @@ -1,24 +1,24 @@ L2VPN Working Group Thomas D. Nadeau (Ed.) -Internet Draft Juniper Networks +Internet Draft Lucid Vision Intended status: Standards Track -Expires: Apr 2014 A S Kiran Koushik (Ed.) +Expires: July 2014 A S Kiran Koushik (Ed.) Cisco Systems, Inc. Rohit Mediratta (Ed.) Alcatel-Lucent - Oct 03, 2013 + January 13, 2014 Virtual Private Lan Services (VPLS) Management Information Base - draft-ietf-l2vpn-vpls-mib-12.txt + draft-ietf-l2vpn-vpls-mib-13.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 @@ -38,21 +38,21 @@ Internet-Drafts are draft documents valid for a maximum of six months 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 - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 This Internet-Draft will expire on April 2, 2013. Copyright Notice 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 @@ -63,40 +63,39 @@ 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. 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 Pseudowire (PW) Management Information Base - [RFC5601]. + conjunction with The Pseudowire (PW) Management Information Base. Table of Contents 1. Introduction...................................................3 2. Terminology....................................................3 2.1. Conventions used in this document.........................3 3. The Internet-Standard Management Framework.....................4 4. VPLS MIB Module Architecture...................................4 4.1. VPLS-GENERIC-MIB Module Usage.............................5 4.2. VPLS-LDP-MIB Module Usage.................................5 4.3. VPLS-BGP-MIB Module Usage.................................5 4.4. Relations to other MIB modules............................6 5. Example of the VPLS MIB modules usage..........................6 6. Object definitions.............................................7 6.1. VPLS-GENERIC-MIB..........................................7 6.2. VPLS-LDP-MIB Object definitions..........................28 6.3. VPLS-BGP-MIB Object definitions..........................34 - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 7. Security Considerations.......................................42 8. IANA Considerations...........................................43 9. References....................................................43 9.1. Normative References.....................................43 9.2. Informative References...................................44 10. Acknowledgments..............................................45 11. Authors' Addresses...........................................45 12. Full Copyright Statement.....................................45 @@ -132,21 +131,21 @@ 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][RFC2579][RFC2580]. 4. VPLS MIB Module Architecture - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 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. The second is the VPLS-LDP-MIB module, which configures VPLS-LDP [RFC4762] specific parameters of the VPLS service. @@ -180,21 +179,21 @@ A conceptual row can be created in the vplsConfigTable in one of the following ways: 1) An NMS creates a row in the vplsConfigTable using SNMP Set requests which causes the node to create and start a new VPLS service. The agent MUST support the creation of VPLS services in this way. 2) The agent MAY create a row in the vplsConfigTable automatically due to some auto discovery application, or based on - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 configuration that is done through non-SNMP applications. This mode is OPTIONAL. At least one entry in the vplsPwBindTable MUST exist for each 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 as part of a mesh based on the parameters defined in this table. @@ -229,21 +228,21 @@ 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 - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 from the local node, and the vplsConfigRowStatus should report 'notReady'. - Statistics can be gathered from the Pseudowire performance tables in [RFC5601] 5. Example of the VPLS MIB modules usage In this section we provide an example of using the MIB objects @@ -277,21 +276,21 @@ vplsStatusPeerCount 1 } Row in VplsPwBindTable : { vplsPwBindConfigType manual, vplsPwBindType spoke, vplsPwBindRowStatus 1(active), vplsPwBindStorageType volatile } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 In the VPLS-LDP-MIB module: Row in vplsLdpConfigTable: { vplsLdpConfigMacAddrWithdraw 1(true), } Row in vplsLdpPwBindTable: @@ -323,21 +322,21 @@ SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC3411 pwIndex FROM PW-STD-MIB VPNIdOrZero FROM VPN-TC-STD-MIB -- RFC4265 - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 ; vplsGenericDraft01MIB MODULE-IDENTITY -- 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" @@ -372,21 +371,21 @@ 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 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." REVISION - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 "200608301200Z" -- 30 August 2006 12:00:00 GMT DESCRIPTION "Changes from previous version: 1) Moved LDP Specific information to VPLS-LDP-MIB 2) Created the vplsStatusTable to store status information. " REVISION "200606041200Z" -- 4 June 2006 12:00:00 GMT @@ -421,21 +420,21 @@ SYNTAX OCTET STRING(SIZE (0..256)) VplsBgpRouteTargetType ::= TEXTUAL-CONVENTION STATUS current 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 - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 "[RFC4364]" SYNTAX INTEGER { import(1), export(2), both(3) } -- Top-level components of this MIB. -- Notifications vplsNotifications OBJECT IDENTIFIER ::= { vplsGenericDraft01MIB 0 } -- Tables, Scalars @@ -469,21 +468,21 @@ 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 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 vplsConfigEntry OBJECT-TYPE SYNTAX VplsConfigEntry MAX-ACCESS not-accessible STATUS current 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. @@ -515,21 +514,21 @@ vplsConfigRowStatus RowStatus, vplsConfigMtu Unsigned32, vplsConfigVpnId VPNIdOrZero, vplsConfigStorageType StorageType, vplsConfigSignalingType INTEGER } vplsConfigIndex OBJECT-TYPE SYNTAX Unsigned32 (1..2147483647) MAX-ACCESS not-accessible - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 STATUS current DESCRIPTION "Unique index for the conceptual row identifying a VPLS service." ::= { vplsConfigEntry 1 } vplsConfigName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create @@ -565,21 +564,21 @@ STATUS current DESCRIPTION "The desired administrative state of the VPLS service. If the administrative status of the VPLS service is changed to enabled then this service is able to utilize pseudowires to perform the tasks of a VPLS service. The testing(3) state indicates that no operational packets can be passed. " DEFVAL { down } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 ::= { vplsConfigEntry 4 } vplsConfigMacLearning OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies if MAC Learning is enabled in this service. If this object is true then MAC @@ -616,21 +615,21 @@ 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 will be sent." - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 DEFVAL { 95 } ::= { vplsConfigEntry 10 } vplsConfigFwdFullLowWatermark OBJECT-TYPE SYNTAX Unsigned32 (0..100) UNITS "percentage" MAX-ACCESS read-create STATUS current DESCRIPTION @@ -665,21 +664,21 @@ SYNTAX Unsigned32 (64..9192) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object specifies the MTU of this vpls instance. This can be used to limit the MTU to a value lower than the MTU supported by the associated Pseudowires" DEFVAL { 1518 } ::= { vplsConfigEntry 13 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 vplsConfigVpnId OBJECT-TYPE SYNTAX VPNIdOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "This objects indicates the IEEE 802-1990 VPN ID of the associated VPLS service." ::= { vplsConfigEntry 14 } @@ -714,21 +713,21 @@ indicates a static configuration of PW labels." DEFVAL { none } ::= { vplsConfigEntry 16 } -- VPLS Status table vplsStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF VplsStatusEntry MAX-ACCESS not-accessible STATUS current - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 DESCRIPTION "This table provides information for monitoring Virtual Private Lan Services (VPLS). " ::= { vplsObjects 3 } vplsStatusEntry OBJECT-TYPE SYNTAX VplsStatusEntry MAX-ACCESS not-accessible @@ -763,21 +762,21 @@ ::= { vplsStatusEntry 1 } vplsStatusPeerCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This objects specifies the number of peers (pseudowires) present in this VPLS instance." ::= { vplsStatusEntry 2 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 -- 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 pseudowires. @@ -813,21 +812,21 @@ VplsPwBindEntry ::= SEQUENCE { vplsPwBindConfigType INTEGER, vplsPwBindType INTEGER, vplsPwBindRowStatus RowStatus, vplsPwBindStorageType StorageType } vplsPwBindConfigType OBJECT-TYPE SYNTAX INTEGER { - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 manual (1), autodiscovery (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object indicates whether the Pseudo Wire binding was created via SNMP/Console or via Auto-Discovery. @@ -864,21 +863,21 @@ All other objects in this row must be set to valid values before this object can be set to active(1). None of the read-create objects in the conceptual rows may be changed when this object is in the active(1) state. If autodiscovered entries are deleted they would likely re-appear in the next autodiscovery interval." - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 ::= { vplsPwBindEntry 3 } vplsPwBindStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this row." DEFVAL { volatile } @@ -906,21 +905,21 @@ A row in this table is indexed by vplsConfigIndex, which uniquely identifies a single VPLS. Entries in this table may be created or deleted through SNMP, as side-effects of console or other non-SNMP management commands, or upon learning via autodiscovery. All of the read-create objects can be changed when vplsBGPADConfigRowStatus is in active(1) state." - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 INDEX { vplsConfigIndex } ::= { vplsBgpADConfigTable 1 } VplsBgpADConfigEntry ::= SEQUENCE { vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher, vplsBgpADConfigPrefix Unsigned32, vplsBgpADConfigVplsId VplsBgpRouteDistinguisher, vplsBgpADConfigRowStatus RowStatus, @@ -955,21 +954,21 @@ " DEFVAL { 0 } ::= { vplsBgpADConfigEntry 2 } vplsBgpADConfigVplsId OBJECT-TYPE SYNTAX VplsBgpRouteDistinguisher MAX-ACCESS read-create STATUS current DESCRIPTION " VplsId is a unique identifier for all VSIs belonging to - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 the same VPLS. It is advertised as an extended community. " ::= { vplsBgpADConfigEntry 3 } vplsBgpADConfigRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION @@ -1005,21 +1004,21 @@ ::= { vplsObjects 6 } vplsBgpRteTargetEntry OBJECT-TYPE SYNTAX VplsBgpRteTargetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table specifies the value of the Route Target being used by BGP. Depending on the value of vplsBgpRteTargetType a Route Target might be exported or - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 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. Entries in this table may be created or deleted through SNMP, as side-effects of console or other non-SNMP management commands, or upon learning via autodiscovery. @@ -1055,21 +1054,21 @@ vplsBgpRteTargetRTType OBJECT-TYPE SYNTAX VplsBgpRouteTargetType MAX-ACCESS read-create STATUS current 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]." ::= { vplsBgpRteTargetEntry 2 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 vplsBgpRteTargetRT OBJECT-TYPE SYNTAX VplsBgpRouteTarget MAX-ACCESS read-create STATUS current DESCRIPTION " The route target associated with the VPLS service. For more details on use of route targets for a VPLS service, see [RFC4761] " @@ -1103,21 +1102,21 @@ ::= { vplsBgpRteTargetEntry 5 } vplsStatusNotifEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is set to true(1), then it enables the emission of vplsStatusChanged notification, otherwise this notification is not - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 emitted." REFERENCE "See also [RFC3413] for explanation that notifications are under the ultimate control of the MIB module in this document." DEFVAL { false } ::= { vplsObjects 7 } vplsNotificationMaxRate OBJECT-TYPE @@ -1153,21 +1152,21 @@ status has changed." ::= { vplsNotifications 1 } vplsFwdFullAlarmRaised NOTIFICATION-TYPE OBJECTS { vplsConfigVpnId, vplsConfigFwdFullHighWatermark, vplsConfigFwdFullLowWatermark } STATUS current - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 DESCRIPTION "The vplsFwdFullAlarmRaised notification is generated when the utilization of the Forwarding database is above the value specified by vplsConfigFwdFullHighWatermark. The object instances included in the notification are the ones associated with the VPLS service which has exceeded the threshold." ::= { vplsNotifications 2 } @@ -1203,21 +1202,21 @@ provide full support for VPLS-GENERIC-MIB. Such devices can then be monitored and configured using this MIB module." MODULE -- this module MANDATORY-GROUPS { vplsGroup, vplsPwBindGroup, vplsNotificationGroup } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 ::= { vplsCompliances 1 } -- Compliance requirement for read-only implementations. vplsModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for VPLS-GENERIC-MIB. @@ -1251,21 +1250,21 @@ OBJECT vplsConfigMacLearning MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT vplsConfigDiscardUnknownDest MIN-ACCESS read-only DESCRIPTION "Write access is not required." - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 OBJECT vplsConfigMacAging MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT vplsConfigFwdFullHighWatermark MIN-ACCESS read-only DESCRIPTION @@ -1300,21 +1299,21 @@ MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { vplsCompliances 2 } -- Units of conformance. vplsGroups OBJECT IDENTIFIER ::= { vplsConformance 2 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 vplsGroup OBJECT-GROUP OBJECTS { vplsConfigName, vplsBgpADConfigRouteDistinguisher, vplsBgpRteTargetRTType, vplsBgpRteTargetRT, vplsBgpRteTargetRowStatus, vplsBgpRteTargetStorageType, vplsBgpADConfigPrefix, @@ -1350,21 +1349,21 @@ vplsPwBindConfigType, vplsPwBindType, vplsPwBindRowStatus, vplsPwBindStorageType } STATUS current DESCRIPTION "The group of objects supporting management of - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 Pseudo Wire (PW) Binding to VPLS." ::= { vplsGroups 2 } vplsNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { vplsStatusChanged, vplsFwdFullAlarmRaised, vplsFwdFullAlarmCleared } @@ -1399,21 +1398,21 @@ FROM PW-STD-MIB vplsConfigIndex, vplsConfigName FROM VPLS-GENERIC-MIB; vplsLdpDraft01MIB MODULE-IDENTITY -- RFC Editor: Please replace vplsLdpDraft01MIB with -- vplsLdpMIB throughout the MIB and remove -- this note. - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 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, @@ -1448,21 +1447,21 @@ 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. -- Top-level components of this MIB. -- Notifications - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 vplsLdpNotifications OBJECT IDENTIFIER ::= { vplsLdpDraft01MIB 0 } -- Tables, Scalars vplsLdpObjects OBJECT IDENTIFIER ::= { vplsLdpDraft01MIB 1 } -- Conformance vplsLdpConformance OBJECT IDENTIFIER ::= { vplsLdpDraft01MIB 2 } @@ -1489,21 +1488,21 @@ A row is automatically created when a VPLS service is configured using LDP signaling. All of the writable objects values can be changed when vplsConfigRowStatus is in the active(1) state. " INDEX { vplsConfigIndex } ::= { vplsLdpConfigTable 1 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 VplsLdpConfigEntry ::= SEQUENCE { vplsLdpConfigMacAddrWithdraw TruthValue } vplsLdpConfigMacAddrWithdraw OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current @@ -1540,21 +1539,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 signaling is used to configure VPLS service. Each entry in this table provides LDP specific information for the VPLS represented by - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 vplsConfigIndex." INDEX { vplsConfigIndex, pwIndex } ::= { vplsLdpPwBindTable 1 } VplsLdpPwBindEntry ::= SEQUENCE { vplsLdpPwBindMacAddressLimit Unsigned32 } @@ -1588,21 +1587,21 @@ vplsLdpCompliances OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } -- Compliance requirement for fully compliant implementations vplsLdpModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 provide full support for VPLS-LDP-MIB. Such devices can then be monitored and configured using this MIB module." MODULE -- this module MANDATORY-GROUPS { vplsLdpGroup, vplsLdpNotificationGroup @@ -1636,21 +1635,21 @@ MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { vplsLdpCompliances 2 } -- Units of conformance. vplsLdpGroups OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 vplsLdpGroup OBJECT-GROUP OBJECTS { vplsLdpConfigMacAddrWithdraw, vplsLdpPwBindMacAddressLimit } STATUS current DESCRIPTION "The group of objects supporting management of L2VPN VPLS services using LDP." @@ -1685,21 +1684,21 @@ RowStatus, StorageType FROM SNMPv2-TC -- RFC2579 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC3411 pwIndex FROM PW-STD-MIB -- RFC5601 vplsConfigIndex - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 FROM VPLS-GENERIC-MIB ; vplsBgpDraft01MIB MODULE-IDENTITY -- 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) @@ -1735,21 +1734,21 @@ "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. -- Top-level components of this MIB. - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 -- Tables, Scalars vplsBgpObjects OBJECT IDENTIFIER ::= { vplsBgpDraft01MIB 1 } -- Conformance vplsBgpConformance OBJECT IDENTIFIER ::= { vplsBgpDraft01MIB 2 } -- Vpls Bgp Config Table @@ -1776,21 +1775,21 @@ A row is automatically created when a VPLS service is created that is configured to use BGP signaling. All of the writable objects values can be changed when vplsConfigRowStatus is in the active(1) state. " INDEX { vplsConfigIndex } ::= { vplsBgpConfigTable 1 } VplsBgpConfigEntry ::= - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 SEQUENCE { vplsBgpConfigVERangeSize Unsigned32 } vplsBgpConfigVERangeSize OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-write STATUS current DESCRIPTION @@ -1825,21 +1824,21 @@ Entries in this table may be created or deleted through SNMP, as side-effects of console or other non-SNMP management commands, or upon learning via autodiscovery. It is optional for the agent to allow entries to be created that point to non-existent entries in vplsConfigTable." INDEX { vplsConfigIndex, vplsBgpVEId } ::= { vplsBgpVETable 1 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 VplsBgpVEEntry ::= SEQUENCE { vplsBgpVEId Unsigned32, vplsBgpVEName SnmpAdminString, vplsBgpVEPreference Unsigned32, vplsBgpVERowStatus RowStatus, vplsBgpVEStorageType StorageType } vplsBgpVEId OBJECT-TYPE @@ -1875,21 +1874,21 @@ SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table. All other objects in this row must be set to valid values before this object can be set to active(1). - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 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 MAX-ACCESS read-create STATUS current @@ -1925,21 +1924,21 @@ to many association of service to pseudowire. An entry in this table in instantiated only when BGP signaling is used to configure VPLS service. Each entry in this table provides BGP specific information for the VPlS represented by vplsConfigIndex." INDEX { vplsConfigIndex, pwIndex } ::= { vplsBgpPwBindTable 1 } - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 VplsBgpPwBindEntry ::= SEQUENCE { vplsBgpPwBindLocalVEId Unsigned32, vplsBgpPwBindRemoteVEId Unsigned32 } vplsBgpPwBindLocalVEId OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current @@ -1972,21 +1971,21 @@ Such devices can then be monitored and configured using this MIB module." MODULE -- this module MANDATORY-GROUPS { vplsBgpConfigGroup, vplsBgpVEGroup, vplsBgpPwBindGroup - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 } ::= { vplsBgpCompliances 1 } -- Compliance requirement for read-only implementations. vplsBgpModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only @@ -2020,21 +2019,21 @@ OBJECT vplsBgpVERowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { vplsBgpCompliances 2 } -- Units of conformance. vplsBgpGroups - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 OBJECT IDENTIFIER ::= { vplsBgpConformance 2 } vplsBgpConfigGroup OBJECT-GROUP OBJECTS { vplsBgpConfigVERangeSize } STATUS current DESCRIPTION "The group of objects supporting configuration @@ -2070,21 +2069,21 @@ 7. Security Considerations It is clear that the MIB modules described in this document in association with the PW-STD-MIB [RFC5601] are potentially useful for monitoring of VPLS capable LERs. These MIB modules can also be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially undesirable results. While the read-write and read-create objects must be protected by - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 secure SNMP, none of them are especially disruptive. Similarly, while the read-only objects might present privacy concerns and due consideration should be given to protecting them with secure SNMP, none of these objects contain especially sensitive information. 8. IANA Considerations -- (Note to RFC-Editor:) -- IANA is requested to root the MIB modules @@ -2120,21 +2119,21 @@ Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002. [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. - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 [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) @@ -2166,34 +2165,34 @@ [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. [RFC6074] E. Rosen et. al., "Provisioning, Autodiscovery, and Signaling in L2VPNs", RFC 6074, January 2011. 10. Acknowledgments - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 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. 11. Authors' Addresses Thomas D. Nadeau - Juniper Networks - Email: tnadeau@juniper.net + Lucid Vision + Email: tnadeau@lucidvision.com A S Kiran Koushik Cisco Systems Inc. 12515 Research Blvd, Bldg 4, Austin, TX 78759 Email: kkoushik@cisco.com Rohit Mediratta Alcatel-Lucent, 701 E Middlefield Rd. @@ -2211,20 +2210,20 @@ 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 - VPLS Management Information Base Oct, 2013 + VPLS Management Information Base Jan, 2014 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.