draft-ietf-l2vpn-vpls-mib-07.txt		draft-ietf-l2vpn-vpls-mib-08.txt
	L2VPN Working Group Thomas D. Nadeau (Ed.)		L2VPN Working Group Thomas D. Nadeau (Ed.)
	Internet Draft Juniper Networks		Internet Draft Juniper Networks
	Intended status: Standards Track		Intended status: Standards Track
	Expires: April 2013 A S Kiran Koushik (Ed.)		Expires: Aug 2013 A S Kiran Koushik (Ed.)
	Cisco Systems, Inc.		Cisco Systems, Inc.
	Rohit Mediratta (Ed.)		Rohit Mediratta (Ed.)
	Alcatel-Lucent		Alcatel-Lucent
	September 29, 2012		February 22, 2013
	Virtual Private Lan Services (VPLS) Management Information Base		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		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	This document may contain material from IETF Documents or IETF		This document may contain material from IETF Documents or IETF
	Contributions published or made publicly available before November		Contributions published or made publicly available before November
	10, 2008. The person(s) controlling the copyright in some of this		10, 2008. The person(s) controlling the copyright in some of this
	material may not have granted the IETF Trust the right to allow		material may not have granted the IETF Trust the right to allow
	skipping to change at page 2, line 14		skipping to change at page 2, line 14
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	This Internet-Draft will expire on April 2, 2013.		This Internet-Draft will expire on April 2, 2013.
	Copyright Notice		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.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with		carefully, as they describe your rights and restrictions with
	respect to this document. Code Components extracted from this		respect to this document. Code Components extracted from this
	document must include Simplified BSD License text as described in		document must include Simplified BSD License text as described in
	Section 4.e of the Trust Legal Provisions and are provided without		Section 4.e of the Trust Legal Provisions and are provided without
	skipping to change at page 3, line 25		skipping to change at page 3, line 25
	8. IANA Considerations...........................................43		8. IANA Considerations...........................................43
	9. References....................................................43		9. References....................................................43
	9.1. Normative References.....................................43		9.1. Normative References.....................................43
	9.2. Informative References...................................44		9.2. Informative References...................................44
	10. Acknowledgments..............................................45		10. Acknowledgments..............................................45
	11. Authors' Addresses...........................................45		11. Authors' Addresses...........................................45
	12. Full Copyright Statement.....................................45		12. Full Copyright Statement.....................................45
	1. Introduction		1. Introduction
	This memo defines a portion of the Management Information		This memo defines a portion of the Management Information
	Base(MIB) for use with network management protocols in the Internet		Base (MIB) for use with network management protocols in the Internet
	community. In particular, it defines a MIB module that can be used		community. In particular, it defines a MIB module that can be used
	to manage VPLS (Virtual Private LAN Services) for transmission over		to manage VPLS (Virtual Private LAN Services) for transmission over
	a packet Switched Network (PSN) using LDP [RFC4762] or BGP [RFC4761]		a packet Switched Network (PSN) using LDP [RFC4762] or BGP [RFC4761]
	signalling. This MIB module provides generic management of VPLS		signalling. This MIB module provides generic management of VPLS
	services as defined by the IETF L2VPN Working Group. Additional MIB		services as defined by the IETF L2VPN Working Group. Additional MIB
	modules are also defined for management of LDP VPLS and BGP VPLS		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		2. Terminology
	This document adopts the definitions, acronyms and mechanisms		This document adopts the definitions, acronyms and mechanisms
	described in [RFC3985]. Unless otherwise stated, the mechanisms of		described in [RFC3985]. Unless otherwise stated, the mechanisms of
	[RFC3985] apply and will not be re-described here.		[RFC3985] apply and will not be re-described here.
	2.1. Conventions used in this document		2.1. Conventions used in this document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"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		3. The Internet-Standard Management Framework
	For a detailed overview of the documents that describe the current		For a detailed overview of the documents that describe the current
	Internet-Standard Management Framework, please refer to section 7		Internet-Standard Management Framework, please refer to section 7
	of RFC 3410 [RFC3410].		of RFC 3410 [RFC3410].
	Managed objects are accessed via a virtual information store,		Managed objects are accessed via a virtual information store,
	termed the Management Information Base or MIB. MIB objects are		termed the Management Information Base or MIB. MIB objects are
	generally accessed through the Simple Network Management Protocol		generally accessed through the Simple Network Management Protocol
	(SNMP). Objects in the MIB are defined using the mechanisms		(SNMP). Objects in the MIB are defined using the mechanisms
	defined in the Structure of Management Information (SMI). This		defined in the Structure of Management Information (SMI). This
	memo specifies a set of MIB modules that are compliant to the SMIv2,		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		which is described in STD 58 [RFC2578][RFC2579][RFC2580].
	[RFC2580].
	4. VPLS MIB Module Architecture		4. VPLS MIB Module Architecture
	The MIB structure for defining a VPLS service is composed from		The MIB structure for defining a VPLS service is composed from
	three MIB modules.		three MIB modules.
	The first is the VPLS-GENERIC-MIB module, which configures general		The first is the VPLS-GENERIC-MIB module, which configures general
	parameters of the VPLS service that are common to all types of VPLS		parameters of the VPLS service that are common to all types of VPLS
	services.		services.
	skipping to change at page 4, line 46		skipping to change at page 4, line 45
	PW Mapping | | | |		PW Mapping | | | |
	-----> | PW-MIB |-->|PW-ENET/MPLS-MIB |		-----> | PW-MIB |-->|PW-ENET/MPLS-MIB |
	__________ / | | | |		__________ / | | | |
	| | / -------- -----------------		| | / -------- -----------------
	| VPLS MIB | / ------------		| VPLS MIB | / ------------
	| |----------------------> | |		| |----------------------> | |
	---------- MAC addr. mapping using | BRIDGE-MIB |		---------- MAC addr. mapping using | BRIDGE-MIB |
	[SNMP-CONTEXT-MAP-MIB] | |		[SNMP-CONTEXT-MAP-MIB] | |
	------------		------------
			Figure A
			--------
	Additionally service-specific modules may be defined in other		Additionally service-specific modules may be defined in other
	documents.		documents.
	4.1. VPLS-GENERIC-MIB Module Usage		4.1. VPLS-GENERIC-MIB Module Usage
	An entry in the vplsConfigTable MUST exist for a VPLS service.		An entry in the vplsConfigTable MUST exist for a VPLS service.
	This table holds generic parameters which apply to a VPLS service		This table holds generic parameters which apply to a VPLS service
	which can be signaled via LDP or BGP.		which can be signaled via LDP or BGP.
	A conceptual row can be created in the vplsConfigTable in one of		A conceptual row can be created in the vplsConfigTable in one of
	skipping to change at page 5, line 24		skipping to change at page 5, line 24
	1) The operator creates a row in the vplsConfigTable when		1) The operator creates a row in the vplsConfigTable when
	configuring the node for a new service. This mode MUST be		configuring the node for a new service. This mode MUST be
	supported by the agent, and MUST be used when creating a		supported by the agent, and MUST be used when creating a
	manually assigned VPLS service.		manually assigned VPLS service.
	2) The agent MAY create a row in the vplsConfigTable automatically		2) The agent MAY create a row in the vplsConfigTable automatically
	due to some auto discovery application, or based on		due to some auto discovery application, or based on
	configuration that is done through non-SNMP applications.		configuration that is done through non-SNMP applications.
	This mode is OPTIONAL.		This mode is OPTIONAL.
	An entry in the vplsPwBindTable MUST exist for a VPLS service.		An entry in the vplsPwBindTable MUST exist for a VPLS service.
	This binding table links one VPLS service with one or many		This binding table links one VPLS service with one or many
	pseudowires (defined in [RFC5601]). Each pseudowire may		pseudowires (defined in [RFC5601]). Each pseudowire may
	be used as a spoke or a mesh based on the parameters defined		be used as a spoke or as part of a mesh based on the parameters
	in this table.		defined in this table.
	An entry in the vplsBgpAdConfigTable MUST exist if		An entry in the vplsBgpAdConfigTable MUST exist if
	Auto-discovery has been enabled on this service. This table		Auto-discovery has been enabled on this service. This table
	stores the information required for auto-discovery.		stores the information required for auto-discovery.
	An entry in the vplsBgpRteTargetTable MUST exist if auto-discovery		An entry in the vplsBgpRteTargetTable MUST exist if auto-discovery
	has been configured on this service. One service can import		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)		The agent then creates the rows in the (locally supported)
	performance tables and reverse mapping tables in		performance tables and reverse mapping tables in
	VPLS-GENERIC-MIB module.		VPLS-GENERIC-MIB module.
	4.2. VPLS-LDP-MIB Module Usage		4.2. VPLS-LDP-MIB Module Usage
	An entry in the vplsLdpConfigTable MUST be created by the agent		An entry in the vplsLdpConfigTable MUST be created by the agent
	for a VPLS service signaled using LDP.		for a VPLS service signaled using LDP.
	4.3. VPLS-BGP-MIB Module Usage		4.3. VPLS-BGP-MIB Module Usage
	An entry in the vplsBgpConfigTable MUST be created by the agent		An entry in the vplsBgpConfigTable MUST be created by the agent
	for a VPLS service signaled using BGP.		for a VPLS service signaled using BGP.
	4.4. Relations to other MIB modules		4.4. Relations to other MIB modules
	- The vplsPwBindTable links the VPLS entry to the pwTable in		- The vplsPwBindTable links the VPLS entry to the pwTable in
	the [RFC5601]		[RFC5601]
	- The association of MAC addresses to VPLS entries is possible		- The association of MAC addresses to VPLS entries is possible
	by adding a turnstile function to interpret the entries in		by adding a turnstile function to interpret the entries in
	[SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB] there is		[SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB] there is
	a mapping between the vacmContextName [RFC3415] to		a mapping between the vacmContextName [RFC3415] to
	dot1dBasePort [RFC4188] and vplsConfigIndex. This mapping can		dot1dBasePort [RFC4188] and vplsConfigIndex. This mapping can
	be used to map the vplsConfigIndex to a dot1dBasePort		be used to map the vplsConfigIndex to a dot1dBasePort
	in the BRIDGE-MIB. This resulting value of dot1dBasePort		in the BRIDGE-MIB. This resulting value of dot1dBasePort
	can be used to access corresponding MAC addresses that belong		can be used to access corresponding MAC addresses that belong
	to a particular vplsConfigIndex.		to a particular vplsConfigIndex.
	skipping to change at page 6, line 38		skipping to change at page 6, line 38
	tables in [RFC5601]		tables in [RFC5601]
	5. Example of the VPLS MIB modules usage		5. Example of the VPLS MIB modules usage
	In this section we provide an example of using the MIB objects		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		described in section 7 to set up a VPLS service over MPLS. While
	this example is not meant to illustrate every permutation of the		this example is not meant to illustrate every permutation of the
	MIB, it is intended as an aid to understanding some of the key		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		concepts. It is meant to be read after going through the MIB
	itself.		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		signaling the pseudowire. The binding between the Vpls service and
	the pseudowire is reflected in the VplsPwBindTable.		the pseudowire is reflected in the VplsPwBindTable.
	The pseudowire configuration is defined in RFC 5601.		The pseudowire configuration is defined in RFC 5601.
	In the VPLS-GENERIC-MIB module:		In the VPLS-GENERIC-MIB module:
	In vplsConfigTable:		Row in vplsConfigTable:
	{		{
	vplsConfigIndex 10,		vplsConfigIndex 10,
	vplsConfigName "VPLS-A"		vplsConfigName "VPLS-A"
	vplsConfigAdminStatus 1(up),		vplsConfigAdminStatus 1(up),
	vplsConfigMacLearning 1(true),		vplsConfigMacLearning 1(true),
	vplsConfigDiscardUnknownDest 2(false),		vplsConfigDiscardUnknownDest 2(false),
	vplsConfigMacAging 1(true),		vplsConfigMacAging 1(true),
	vplsConfigVpnId "100:10"		vplsConfigVpnId "100:10"
	vplsConfigRowStatus 1(active)		vplsConfigRowStatus 1(active)
	}		}
	In vplsStatusTable:		Row in vplsStatusTable:
	{		{
	vplsStatusOperStatus 1(up),		vplsStatusOperStatus 1(up),
	}		}
	In VplsPwBindTable :		Row in VplsPwBindTable :
	{		{
	vplsPwBindConfigType manual,		vplsPwBindConfigType manual,
	vplsPwBindType spoke,		vplsPwBindType spoke,
	vplsPwBindRowStatus 1(active),		vplsPwBindRowStatus 1(active),
	vplsPwBindStorageType volatile		vplsPwBindStorageType volatile
	}		}
	In the VPLS-LDP-MIB module:		In the VPLS-LDP-MIB module:
	In vplsLdpConfigTable:		Row in vplsLdpConfigTable:
	{		{
	vplsLdpConfigMacAddrWithdraw 1(true),		vplsLdpConfigMacAddrWithdraw 1(true),
	}		}
	In vplsLdpPwBindTable:		Row in vplsLdpPwBindTable:
	{		{
	vplsLdpPwBindType 1(mesh),		vplsLdpPwBindType 1(mesh),
	vplsLdpPwBindMacAddressLimit 100		vplsLdpPwBindMacAddressLimit 100
	}		}
	6. Object definitions		6. Object definitions
	6.1. VPLS-GENERIC-MIB		6.1. VPLS-GENERIC-MIB
	This MIB module makes references to the following documents.		This MIB module makes references to the following documents.
	skipping to change at page 8, line 30		skipping to change at page 8, line 30
	SnmpAdminString		SnmpAdminString
	FROM SNMP-FRAMEWORK-MIB -- RFC3411		FROM SNMP-FRAMEWORK-MIB -- RFC3411
	pwIndex		pwIndex
	FROM PW-TC-STD-MIB		FROM PW-TC-STD-MIB
	VPNIdOrZero		VPNIdOrZero
	FROM VPN-TC-STD-MIB -- RFC4265		FROM VPN-TC-STD-MIB -- RFC4265
	-- Vpls BGP Auto-Discovery specific Textual Convention		-- VPLS BGP Auto-Discovery specific Textual Convention
	VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION		VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Syntax for a route distinguisher. For a complete		"Syntax for a route distinguisher. For a complete
	definition of a route distinguisher, see [RFC4364].		definition of a route distinguisher, see [RFC4364].
	For more details on use of a route distinguisher		For more details on use of a route distinguisher
	for a VPLS service, see [RFC4761]"		for a VPLS service, see [RFC4761]"
	REFERENCE		REFERENCE
	"[RFC4364]"		"[RFC4364]"
	SYNTAX OCTET STRING(SIZE (0..256))		SYNTAX OCTET STRING(SIZE (0..256))
	skipping to change at page 9, line 18		skipping to change at page 9, line 18
	"Used to define the type of a route target usage.		"Used to define the type of a route target usage.
	Route targets can be specified to be imported,		Route targets can be specified to be imported,
	exported, or both. For a complete definition of a		exported, or both. For a complete definition of a
	route target, see [RFC4364]."		route target, see [RFC4364]."
	REFERENCE		REFERENCE
	"[RFC4364]"		"[RFC4364]"
	SYNTAX INTEGER { import(1), export(2), both(3) }		SYNTAX INTEGER { import(1), export(2), both(3) }
	;		;
	vplsGenericDraft01MIB MODULE-IDENTITY		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)		ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
	Working Group"		Working Group"
	CONTACT-INFO		CONTACT-INFO
	"		"
	Thomas D. Nadeau		Thomas D. Nadeau
	Email: tnadeau@juniper.net		Email: tnadeau@juniper.net
	The L2VPN Working Group (email distribution l2vpn@ietf.org,		The L2VPN Working Group (email distribution l2vpn@ietf.org,
	http://www.ietf.org/html.charters/l2vpn-charter.html)		http://www.ietf.org/html.charters/l2vpn-charter.html)
	"		"
	DESCRIPTION		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.		version of this MIB module was published in RFC XXXX.
	-- RFC Editor: Please replace XXXX with RFC number & remove		-- RFC Editor: Please replace XXXX with RFC number & remove
	-- this note.		-- this note.
	For full legal notices see the RFC itself or see:		For full legal notices see the RFC itself or see:
	http://www.ietf.org/copyrights/ianamib.html		http://www.ietf.org/copyrights/ianamib.html
	This MIB module contains generic managed object definitions		This MIB module contains generic managed object definitions
	for Virtual Private LAN Services as define in [RFC4762] and		for Virtual Private LAN Services as define in [RFC4762] and
	[RFC4761]		[RFC4761]
	This MIB module enables the use of any underlying Pseudowire		This MIB module enables the use of any underlying Pseudowire
	network."		network."
	-- Revision history.		-- Revision history.
	REVISION		REVISION
	"201209291200Z" -- 29 September 2012 12:00:00 GMT		"201302221200Z" -- 22 Feb 2013 12:00:00 GMT
	DESCRIPTION		DESCRIPTION
	1) Changed the OID for vplsBgpRteTargetTable from vplsObjects.6 to		1) Changed the OID for vplsBgpRteTargetTable from vplsObjects.6 to
	vplsObjects.5		vplsObjects.5
	2) Index to VplsPwBindTable is now pwIndex, not vplsPwBindIndex.		2) Index to VplsPwBindTable is now pwIndex, not vplsPwBindIndex.
	3) vplsConfigMtu increased to upto 9192		3) vplsConfigMtu increased to upto 9192
	4) Default value for vplsConfigStorageType changed to nonvolatile.		4) Default value for vplsConfigStorageType changed to nonvolatile.
	5) vplsConfigServiceType should be a property of each PW. Deleting		5) vplsConfigServiceType should be a property of each PW. Deleting
	this object and adjusting the corresponding object indexes.		this object and adjusting the corresponding object indexes.
	skipping to change at page 20, line 23		skipping to change at page 20, line 23
	vplsBgpADConfigPrefix OBJECT-TYPE		vplsBgpADConfigPrefix OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	" In case of auto-discovery the default prefix advertised		" In case of auto-discovery the default prefix advertised
	is the IP address of the loopback. In case the user wants		is the IP address of the loopback. In case the user wants
	to override the loopback address, vplsBgpADConfigPrefix		to override the loopback address, vplsBgpADConfigPrefix
	should be set. When this value is non-zero this value is		should be set. When this value is non-zero this value is
	used along with vplsBgpADConfigRouteDistinguisher in the		used along with vplsBgpADConfigRouteDistinguisher in the
	NLRI, see [RFC 6074]		NLRI, see [RFC6074]
	"		"
	DEFVAL { 0 }		DEFVAL { 0 }
	::= { vplsBgpADConfigEntry 2 }		::= { vplsBgpADConfigEntry 2 }
	vplsBgpADConfigVplsId OBJECT-TYPE		vplsBgpADConfigVplsId OBJECT-TYPE
	SYNTAX VplsBgpRouteDistinguisher		SYNTAX VplsBgpRouteDistinguisher
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	" VplsId is a unique identifier for all VSIs belonging to		" VplsId is a unique identifier for all VSIs belonging to
	skipping to change at page 28, line 12		skipping to change at page 28, line 12
	"The group of notifications supporting		"The group of notifications supporting
	the Notifications generated for		the Notifications generated for
	VPLS Services"		VPLS Services"
	::= { vplsGroups 3 }		::= { vplsGroups 3 }
	END		END
	6.2. VPLS-LDP-MIB Object definitions		6.2. VPLS-LDP-MIB Object definitions
	This MIB module makes references to the following documents.		This MIB module makes references to the following documents.
	[RFC2578], [RFC2579], [RFC2580], [RFC3411],		[RFC2578], [RFC2579], [RFC2580], [RFC3411],
	[RFC2863], [RFC4001], [RFC4265] and [RFC3813].		[RFC2863], [RFC4001], [RFC4265] and [RFC3813].
	VPLS-LDP-MIB DEFINITIONS ::= BEGIN		VPLS-LDP-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE,		MODULE-IDENTITY, OBJECT-TYPE,
	Unsigned32, transmission		Unsigned32, transmission
	FROM SNMPv2-SMI -- RFC2578		FROM SNMPv2-SMI -- RFC2578
	MODULE-COMPLIANCE, OBJECT-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP
	skipping to change at page 28, line 34		skipping to change at page 28, line 34
	TruthValue		TruthValue
	FROM SNMPv2-TC -- RFC2579		FROM SNMPv2-TC -- RFC2579
	pwIndex		pwIndex
	FROM PW-TC-STD-MIB		FROM PW-TC-STD-MIB
	vplsConfigIndex		vplsConfigIndex
	FROM VPLS-GENERIC-MIB;		FROM VPLS-GENERIC-MIB;
	vplsLdpDraft01MIB MODULE-IDENTITY		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)		ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
	Working Group"		Working Group"
	CONTACT-INFO		CONTACT-INFO
	"		"
	Rohit Mediratta		Rohit Mediratta
	Email: Rohit.mediratta@alcatel-lucent.com		Email: Rohit.mediratta@alcatel-lucent.com
	The L2VPN Working Group (email distribution l2vpn@ietf.org,		The L2VPN Working Group (email distribution l2vpn@ietf.org,
	http://www.ietf.org/html.charters/l2vpn-charter.html)		http://www.ietf.org/html.charters/l2vpn-charter.html)
	"		"
	DESCRIPTION		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.		version of this MIB module was published in RFC XXXX.
	-- RFC Editor: Please replace XXXX with RFC number & remove		-- RFC Editor: Please replace XXXX with RFC number & remove
	-- this note.		-- this note.
	For full legal notices see the RFC itself or see:		For full legal notices see the RFC itself or see:
	http://www.ietf.org/copyrights/ianamib.html		http://www.ietf.org/copyrights/ianamib.html
	This MIB module contains managed object definitions for		This MIB module contains managed object definitions for
	LDP signaled Virtual Private LAN Services as in		LDP signaled Virtual Private LAN Services as in
	skipping to change at page 34, line 38		skipping to change at page 34, line 38
	FROM SNMPv2-TC -- RFC2579		FROM SNMPv2-TC -- RFC2579
	SnmpAdminString		SnmpAdminString
	FROM SNMP-FRAMEWORK-MIB -- RFC3411		FROM SNMP-FRAMEWORK-MIB -- RFC3411
	vplsConfigIndex		vplsConfigIndex
	FROM VPLS-GENERIC-MIB		FROM VPLS-GENERIC-MIB
	;		;
	vplsBgpDraft01MIB MODULE-IDENTITY		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)		ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
	Working Group"		Working Group"
	CONTACT-INFO		CONTACT-INFO
	"		"
	V. J. Shah		V. J. Shah
	Email: vshah@juniper.net		Email: vshah@juniper.net
	The L2VPN Working Group (email distribution l2vpn@ietf.org,		The L2VPN Working Group (email distribution l2vpn@ietf.org,
	http://www.ietf.org/html.charters/l2vpn-charter.html)		http://www.ietf.org/html.charters/l2vpn-charter.html)
	"		"
	DESCRIPTION		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.		version of this MIB module was published in RFC XXXX.
	-- RFC Editor: Please replace XXXX with RFC number & remove		-- RFC Editor: Please replace XXXX with RFC number & remove
	-- this note.		-- this note.
	For full legal notices see the RFC itself or see:		For full legal notices see the RFC itself or see:
	http://www.ietf.org/copyrights/ianamib.html		http://www.ietf.org/copyrights/ianamib.html
	This MIB module contains managed object definitions for		This MIB module contains managed object definitions for
	BGP signaled Virtual Private LAN Services as in		BGP signaled Virtual Private LAN Services as in
	[RFC4761]		[RFC4761]
	This MIB module enables the use of any underlying pseudowire		This MIB module enables the use of any underlying pseudowire
	network. "		network. "
	-- Revision history.		-- Revision history.
	REVISION		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."		DESCRIPTION "Initial version published as part of RFC YYYY."
	-- RFC Editor: please replace YYYY with IANA assigned value, and		-- RFC Editor: please replace YYYY with IANA assigned value, and
	-- delete this note.		-- delete this note.
	::= { transmission XXXX }		::= { transmission XXXX }
	-- RFC Editor: please replace XXXX with IANA assigned value, and		-- RFC Editor: please replace XXXX with IANA assigned value, and
	-- delete this note.		-- delete this note.
	-- VPLS BGP specific Textual Conventions.		-- VPLS BGP specific Textual Conventions.
	VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION		VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	skipping to change at page 44, line 40		skipping to change at page 44, line 40
	[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,		[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
	"Introduction and Applicability Statements for		"Introduction and Applicability Statements for
	Internet-Standard Management Framework", RFC 3410,		Internet-Standard Management Framework", RFC 3410,
	December 2002.		December 2002.
	[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An		[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
	Architecture for Describing Simple Network Management		Architecture for Describing Simple Network Management
	Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,		Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
	December 2002.		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-		[RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to-
	Edge (PWE3) Architecture", RFC 3985, March 2005.		Edge (PWE3) Architecture", RFC 3985, March 2005.
	[SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik,		[RFC6074] E. Rosen et. al., "Provisioning, Autodiscovery, and
	Nadeau, T, draft-kkoushik-snmp-context-map-mib.		Signaling in L2VPNs", RFC 6074, January 2011.
	10. Acknowledgments		10. Acknowledgments
	We wish to thank Marcelo Mourier and Reva Bailey for their		We wish to thank Marcelo Mourier and Reva Bailey for their
	valuable feedback. Some portion of the work has been referenced		valuable feedback. Some portion of the work has been referenced
	from their original Timetra Enterprise MIB work.		from their original Timetra Enterprise MIB work.
	We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo		We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo
	Jian, Feng Jun, Takeshi Usui for their feedback.		Jian, Feng Jun, Takeshi Usui for their feedback.
	skipping to change at page 45, line 34		skipping to change at page 45, line 34
	Email: kkoushik@cisco.com		Email: kkoushik@cisco.com
	Rohit Mediratta		Rohit Mediratta
	Alcatel-Lucent,		Alcatel-Lucent,
	701 E Middlefield Rd.		701 E Middlefield Rd.
	Mountain View, CA 94040		Mountain View, CA 94040
	Email: rohit.mediratta@alcatel-lucent.com		Email: rohit.mediratta@alcatel-lucent.com
	12. Full Copyright Statement		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.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with		carefully, as they describe your rights and restrictions with
	respect to this document. Code Components extracted from this		respect to this document. Code Components extracted from this
	document must include Simplified BSD License text as described in		document must include Simplified BSD License text as described in
	Section 4.e of the Trust Legal Provisions and are provided without		Section 4.e of the Trust Legal Provisions and are provided without
End of changes. 35 change blocks.
	37 lines changed or deleted		52 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/