< draft-ietf-bess-l2l3-vpn-mcast-mib-09.txt		draft-ietf-bess-l2l3-vpn-mcast-mib-10.txt >
	Network Working Group Z. Zhang		Network Working Group Z. Zhang
	Internet-Draft Juniper Networks, Inc.		Internet-Draft Juniper Networks, Inc.
	Intended status: Standards Track H. Tsunoda		Intended status: Standards Track H. Tsunoda
	Expires: December 23, 2017 Tohoku Institute of Technology		Expires: February 28, 2018 Tohoku Institute of Technology
	June 21, 2017		August 27, 2017
	L2L3 VPN Multicast MIB		L2L3 VPN Multicast MIB
	draft-ietf-bess-l2l3-vpn-mcast-mib-09		draft-ietf-bess-l2l3-vpn-mcast-mib-10
	Abstract		Abstract
	This memo defines a portion of the Management Information Base (MIB)		This memo defines a portion of the Management Information Base (MIB)
	for use with network management protocols in the Internet community.		for use with network management protocols in the Internet community.
	In particular, it describes two MIB modules which will be used by		In particular, it describes two MIB modules which will be used by
	other MIB modules for monitoring and/or configuring Layer 2 and Layer		other MIB modules for monitoring and/or configuring Layer 2 and Layer
	3 Virtual Private Networks that support multicast.		3 Virtual Private Networks that support multicast.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on December 23, 2017.		This Internet-Draft will expire on February 28, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3		1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
	2. The Internet-Standard Management Framework . . . . . . . . . 4		2. The Internet-Standard Management Framework . . . . . . . . . 4
	3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4		3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4
	4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4		4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
	4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 5		4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 5
	4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 9		4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 9
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 16		5. Security Considerations . . . . . . . . . . . . . . . . . . . 16
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
	7.1. Normative References . . . . . . . . . . . . . . . . . . 17		7.1. Normative References . . . . . . . . . . . . . . . . . . 17
	7.2. Informative References . . . . . . . . . . . . . . . . . 19		7.2. Informative References . . . . . . . . . . . . . . . . . 20
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
	1. Introduction		1. Introduction
	In BGP/MPLS Virtual Private Networks (VPN), Border Gateway Protocol		In BGP/MPLS Virtual Private Networks (VPN), Border Gateway Protocol
	(BGP) is used for distributing routes and MultiProtocol Label		(BGP) is used for distributing routes and MultiProtocol Label
	Switching (MPLS) is used for forwarding packets accross service		Switching (MPLS) is used for forwarding packets accross service
	provider networks.		provider networks.
	The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN		The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN
	are specified in [RFC6513]. The procedures for supporting multicast		are specified in [RFC6513]. The procedures for supporting multicast
	skipping to change at page 3, line 25 ¶		skipping to change at page 3, line 25 ¶
	(a) the tunnel type of a P-tunnel and		(a) the tunnel type of a P-tunnel and
	(b) the identifier of a P-tunnel		(b) the identifier of a P-tunnel
	respectively.		respectively.
	This document also describes common MOs that provide the information		This document also describes common MOs that provide the information
	in a PMSI tunnel attribute and corresponding tunnel information to		in a PMSI tunnel attribute and corresponding tunnel information to
	other MIB modules.		other MIB modules.
	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].
	1.1. Terminology		1.1. Terminology
	This document adopts the definitions, acronyms and mechanisms		This document adopts the definitions, acronyms and mechanisms
	described in [RFC6513] [RFC6514] [RFC7117] and other documents that		described in [RFC6513] [RFC6514] [RFC7117] and other documents that
	they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN,		they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN,
	Multicast VPN concepts and/or mechanisms is assumed. Some terms		Multicast VPN concepts and/or mechanisms is assumed. Some terms
	specifically related to this document are explained below.		specifically related to this document are explained below.
	"Provider Multicast Service Interface (PMSI)" [RFC6513] is a		"Provider Multicast Service Interface (PMSI)" [RFC6513] is a
	conceptual interface instantiated by a P-tunnel, a transport		conceptual interface instantiated by a P-tunnel, a transport
	skipping to change at page 4, line 5 ¶		skipping to change at page 3, line 48 ¶
	There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and		There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and
	"Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that		"Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that
	enables a PE attached to a particular Multicast VPN to transmit a		enables a PE attached to a particular Multicast VPN to transmit a
	message to all PEs in the same VPN. An S-PMSI is a PMSI that enables		message to all PEs in the same VPN. An S-PMSI is a PMSI that enables
	a PE attached to a particular Multicast VPN to transmit a message to		a PE attached to a particular Multicast VPN to transmit a message to
	some of the PEs in the same VPN.		some of the PEs in the same VPN.
	Throughout this document, we will use the term "PMSI" to refer both		Throughout this document, we will use the term "PMSI" to refer both
	"I-PMSI" and "S-PMSI."		"I-PMSI" and "S-PMSI."
			The key words "MUST", "SHOULD", "RECOMMENDED", and "MAY" in this
			document are to be interpreted as described in [RFC2119].
	2. The Internet-Standard Management Framework		2. 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 of		Internet-Standard Management Framework, please refer to section 7 of
	RFC 3410 [RFC3410].		RFC 3410 [RFC3410].
	Managed objects are accessed via a virtual information store, termed		Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. MIB objects are generally		the Management Information Base or MIB. MIB objects are generally
	accessed through the Simple Network Management Protocol (SNMP).		accessed through the Simple Network Management Protocol (SNMP).
	Objects in the MIB are defined using the mechanisms defined in the		Objects in the MIB are defined using the mechanisms defined in the
	skipping to change at page 4, line 33 ¶		skipping to change at page 4, line 33 ¶
	L2L3-VPN-MCAST-MIB.		L2L3-VPN-MCAST-MIB.
	o L2L3-VPN-MCAST-TC-MIB contains two Textual Conventions:		o L2L3-VPN-MCAST-TC-MIB contains two Textual Conventions:
	L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId.		L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId.
	L2L3VpnMcastProviderTunnelType provides an enumeration of the		L2L3VpnMcastProviderTunnelType provides an enumeration of the
	P-tunnel types. L2L3VpnMcastProviderTunnelId represents an		P-tunnel types. L2L3VpnMcastProviderTunnelId represents an
	identifier of a P-tunnel.		identifier of a P-tunnel.
	o L2L3-VPN-MCAST-MIB defines a table		o L2L3-VPN-MCAST-MIB defines a table
	l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table		l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table
	corresponds to a PMSI Tunnel Attribute (PTA) advertised/received		corresponds to the attribute information of a specific P-tunnel on
	by a PE router. Entries in this table will be used by other MIB		a PE router. Entries in this table will be used by other MIB
	modules for monitoring and/or configuring L2L3VpnMCast. The table		modules for monitoring and/or configuring L2L3VpnMCast. The table
	index uniquely identifies a tunnel. It is composed of a set of		index uniquely identifies a tunnel. It is composed of a tunnel
	attributes which depend on the tunnel type. The table may also be		type and a tunnel indentifier. The table may also be used in
	used in conjunction with other MIBs, such as MPLS Traffic		conjunction with other MIBs, such as MPLS Traffic Engineering MIB
	Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further		(MPLS-TE-STD-MIB) [RFC3812], to obtain further information of a
	information of a tunnel by following the row pointer of the		tunnel by following the row pointer of the corresponding tunnel's
	corresponding tunnel's row in this table. It may also be used in		row in this table. It may also be used in conjunction with
	conjunction with Interfaces Group MIB (IF-MIB) [RFC2863] to obtain		Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further
	further information of the interface corresponding to the tunnel		information of the interface corresponding to the tunnel by
	by following the row pointer of the corresponding tunnel's row in		following the row pointer of the corresponding tunnel's row in
	this table.		this table.
	4. Definitions		4. Definitions
	4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions		4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions
	L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN		L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, mib-2		MODULE-IDENTITY, mib-2
	FROM SNMPv2-SMI -- [RFC2578]		FROM SNMPv2-SMI -- [RFC2578]
	TEXTUAL-CONVENTION		TEXTUAL-CONVENTION
	FROM SNMPv2-TC; -- [RFC2579]		FROM SNMPv2-TC; -- [RFC2579]
	l2L3VpnMcastTCMIB MODULE-IDENTITY		l2L3VpnMcastTCMIB MODULE-IDENTITY
	LAST-UPDATED "201706211200Z" -- 21th June, 2017		LAST-UPDATED "201708211200Z" -- 21th August, 2017
	ORGANIZATION "IETF BESS Working Group."		ORGANIZATION "IETF BESS Working Group."
	CONTACT-INFO		CONTACT-INFO
	" Zhaohui Zhang		" Zhaohui Zhang
	Juniper Networks, Inc.		Juniper Networks, Inc.
	10 Technology Park Drive		10 Technology Park Drive
	Westford, MA 01886		Westford, MA 01886
	USA		USA
	Email: zzhang@juniper.net		Email: zzhang@juniper.net
	Hiroshi Tsunoda		Hiroshi Tsunoda
	skipping to change at page 5, line 46 ¶		skipping to change at page 5, line 46 ¶
	"This MIB module specifies textual conventions for		"This MIB module specifies textual conventions for
	Border Gateway Protocol/MultiProtocol Label		Border Gateway Protocol/MultiProtocol Label
	Switching Layer 2 and Layer 3 Virtual Private Network		Switching Layer 2 and Layer 3 Virtual Private Network
	that support multicast (L2L3VpnMCast).		that support multicast (L2L3VpnMCast).
	Copyright (C) The Internet Society (2017).		Copyright (C) The Internet Society (2017).
	"		"
	-- Revision history.		-- Revision history.
	REVISION "201706211200Z" -- 21th June, 2017		REVISION "201708211200Z" -- 21th August, 2017
	DESCRIPTION		DESCRIPTION
	"Initial version, published as RFC XXXX."		"Initial version, published as RFC XXXX."
	-- RFC Ed.: replace XXXX with actual RFC number and remove this note		-- RFC Ed.: replace XXXX with actual RFC number and remove this note
	::= { mib-2 AAAA }		::= { mib-2 AAAA }
	-- IANA Reg.: Please assign a value for "AAAA" under the		-- IANA Reg.: Please assign a value for "AAAA" under the
	-- 'mib-2' subtree and record the assignment in the SMI		-- 'mib-2' subtree and record the assignment in the SMI
	-- Numbers registry.		-- Numbers registry.
	skipping to change at page 6, line 31 ¶		skipping to change at page 6, line 31 ¶
	representing the type of a provider tunnel (P-tunnel)		representing the type of a provider tunnel (P-tunnel)
	used for L2L3VpnMCast.		used for L2L3VpnMCast.
	These labeled numbers are aligned with the definition		These labeled numbers are aligned with the definition
	of Tunnel types in Section 5 of [RFC6514] and		of Tunnel types in Section 5 of [RFC6514] and
	Section 14.1 of [RFC7524].		Section 14.1 of [RFC7524].
	The enumerated values and the corresponding tunnel type		The enumerated values and the corresponding tunnel type
	are as follows:		are as follows:
	noTunnelInfo (0) : no tunnel information present		noTunnelInfo (0) : no tunnel information present
	rsvpP2mp (1) : RSVP-TE P2MP LSP		rsvpP2mp (1) : RSVP-TE P2MP LSP [RFC4875]
	ldpP2mp (2) : mLDP P2MP LSP		ldpP2mp (2) : mLDP P2MP LSP [RFC6388]
	pimSsm (3) : PIM-SSM Tree		pimSsm (3) : PIM-SSM Tree [RFC7761]
	pimAsm (4) : PIM-SM Tree		pimAsm (4) : PIM-SM Tree [RFC7761]
	pimBidir (5) : BIDIR-PIM Tree		pimBidir (5) : BIDIR-PIM Tree [RFC5015]
	ingressReplication (6) : Ingress Replication		ingressReplication (6) : Ingress Replication [RFC6513]
	ldpMp2mp (7) : mLDP MP2MP LSP		ldpMp2mp (7) : mLDP MP2MP LSP [RFC6388]
	transportTunnel (8) : Transport Tunnel		transportTunnel (8) : Transport Tunnel [RFC7524]
	These numbers are registered at IANA.		These numbers are registered at IANA.
	A current list of assignments can be found at		A current list of assignments can be found at
	<https://www.iana.org/assignments/bgp-parameters/		<https://www.iana.org/assignments/bgp-parameters/
	bgp-parameters.xhtml#pmsi-tunnel-types>.		bgp-parameters.xhtml#pmsi-tunnel-types>.
	"		"
	REFERENCE		REFERENCE
	"RFC6514, Section 5		"RFC4875
			RFC6388
			RFC6513
			RFC6514, Section 5
	RFC7385		RFC7385
	RFC7524, Section 14.1		RFC7524, Section 14.1
			RFC7761
	"		"
	SYNTAX INTEGER		SYNTAX INTEGER
	{		{
	noTunnelInfo (0), -- no tunnel information present		noTunnelInfo (0),
	rsvpP2mp (1), -- RSVP-TE P2MP LSP		rsvpP2mp (1),
	ldpP2mp (2), -- mLDP P2MP LSP		ldpP2mp (2),
	pimSsm (3), -- PIM-SSM Tree		pimSsm (3),
	pimAsm (4), -- PIM-SM Tree		pimAsm (4),
	pimBidir (5), -- BIDIR-PIM Tree		pimBidir (5),
	ingressReplication (6), -- Ingress Replication		ingressReplication (6),
	ldpMp2mp (7), -- mLDP MP2MP LSP		ldpMp2mp (7),
	transportTunnel (8) -- Transport Tunnel		transportTunnel (8)
	}		}
	L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION		L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This textual convention represents the tunnel identifier		"This textual convention represents the tunnel identifier
	of a P-tunnel.		of a P-tunnel.
	The size of the identifier depends on the address family		The size of the identifier depends on the address family
	(IPv4 or IPv6) and the value of the corresponding		(IPv4 or IPv6) and the value of the corresponding
	skipping to change at page 7, line 48 ¶		skipping to change at page 8, line 4 ¶
	pimSsm (PIM-SSM Tree) 8 32		pimSsm (PIM-SSM Tree) 8 32
	pimAsm (PIM-SM Tree) 8 32		pimAsm (PIM-SM Tree) 8 32
	pimBidir (BIDIR-PIM Tree) 8 32		pimBidir (BIDIR-PIM Tree) 8 32
	ingressReplication (Ingress Replication) 4 16		ingressReplication (Ingress Replication) 4 16
	ldpMp2mp (mLDP MP2MP LSP) 17 29		ldpMp2mp (mLDP MP2MP LSP) 17 29
	transportTunnel (Transport Tunnel) 8 32		transportTunnel (Transport Tunnel) 8 32
	A L2L3VpnMcastProviderTunnelType object of value		A L2L3VpnMcastProviderTunnelType object of value
	noTunnelInfo(0) indicates that the corresponding		noTunnelInfo(0) indicates that the corresponding
	Provider Multicast Service Interface (PMSI) Tunnel		Provider Multicast Service Interface (PMSI) Tunnel
	attribute does not have tunnel information.		attribute does not have a Tunnel Identifier.
	The value of the corresponding L2L3VpnMcastProviderTunnelId		The value of the corresponding L2L3VpnMcastProviderTunnelId
	object will be a string of length zero.		object will be a string of length zero.
	When the L2L3VpnMcastProviderTunnelType object is of value		When the L2L3VpnMcastProviderTunnelType object is of value
	rsvpP2mp(1), the corresponding Tunnel Identifier is composed of		rsvpP2mp(1), the corresponding Tunnel Identifier is composed of
	Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6),		Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6),
	Reserved (2 octets), Tunnel ID (2 octets), and		Reserved (2 octets), Tunnel ID (2 octets), and
	P2MP ID (4 octets).		P2MP ID (4 octets).
	The size of the corresponding L2L3VpnMcastProviderTunnelId		The size of the corresponding L2L3VpnMcastProviderTunnelId
	object will be 12 octets in IPv4 and 24 octets in IPv6.		object will be 12 octets in IPv4 and 24 octets in IPv6.
	skipping to change at page 8, line 40 ¶		skipping to change at page 8, line 43 ¶
	object will be 4 octets in IPv4 and 16 octets in IPv6.		object will be 4 octets in IPv4 and 16 octets in IPv6.
	When the L2L3VpnMcastProviderTunnelType object is of value		When the L2L3VpnMcastProviderTunnelType object is of value
	ldpMp2mp(7), the Tunnel Identifier is MP2MP FEC Element		ldpMp2mp(7), the Tunnel Identifier is MP2MP FEC Element
	[RFC6388].		[RFC6388].
	The size of the corresponding L2L3VpnMcastProviderTunnelId		The size of the corresponding L2L3VpnMcastProviderTunnelId
	object will be 17 octets in IPv4 and 29 octets in IPv6.		object will be 17 octets in IPv4 and 29 octets in IPv6.
	When the L2L3VpnMcastProviderTunnelType object is of value		When the L2L3VpnMcastProviderTunnelType object is of value
	transportTunnel(8), the Tunnel Identifier is a tuple of		transportTunnel(8), the Tunnel Identifier is a tuple of
	Source PE Address (4 octets in IPv4, 16 octets in IPv6) and		Source PE Address and Local Number, which is a number
	Local Number (the same length as the Source PE Address)		that is unique to the Source PE [RFC7524].
	[RFC7524].		Both Source PE Address and Local Number are 4 octets in IPv4
			and 16 octets in IPv6.
	The size of the corresponding L2L3VpnMcastProviderTunnelId		The size of the corresponding L2L3VpnMcastProviderTunnelId
	object will be 8 octets in IPv4 and 32 octets in IPv6.		object will be 8 octets in IPv4 and 32 octets in IPv6.
	"		"
	REFERENCE		REFERENCE
	"RFC6514, Section 5		"RFC6514, Section 5
	RFC4875, Section 19.1		RFC4875, Section 19.1
	RFC6388, Section 2.2 and 3.2		RFC6388, Section 2.2 and 3.2
	RFC7524, Section 14.1		RFC7524, Section 14.1
	"		"
	SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )		SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )
	skipping to change at page 9, line 31 ¶		skipping to change at page 9, line 36 ¶
	MplsLabel		MplsLabel
	FROM MPLS-TC-STD-MIB -- [RFC3811]		FROM MPLS-TC-STD-MIB -- [RFC3811]
	L2L3VpnMcastProviderTunnelType,		L2L3VpnMcastProviderTunnelType,
	L2L3VpnMcastProviderTunnelId		L2L3VpnMcastProviderTunnelId
	FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX]		FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX]
	-- RFC Ed.: replace XXXX with actual RFC number and remove this note		-- RFC Ed.: replace XXXX with actual RFC number and remove this note
	l2L3VpnMcastMIB MODULE-IDENTITY		l2L3VpnMcastMIB MODULE-IDENTITY
	LAST-UPDATED "201706211200Z" -- 21th June, 2017		LAST-UPDATED "201708211200Z" -- 21th August, 2017
	ORGANIZATION "IETF BESS Working Group."		ORGANIZATION "IETF BESS Working Group."
	CONTACT-INFO		CONTACT-INFO
	" Zhaohui Zhang		" Zhaohui Zhang
	Juniper Networks, Inc.		Juniper Networks, Inc.
	10 Technology Park Drive		10 Technology Park Drive
	Westford, MA 01886		Westford, MA 01886
	USA		USA
	Email: zzhang@juniper.net		Email: zzhang@juniper.net
	Hiroshi Tsunoda		Hiroshi Tsunoda
	skipping to change at page 9, line 47 ¶		skipping to change at page 10, line 4 ¶
	Westford, MA 01886		Westford, MA 01886
	USA		USA
	Email: zzhang@juniper.net		Email: zzhang@juniper.net
	Hiroshi Tsunoda		Hiroshi Tsunoda
	Tohoku Institute of Technology		Tohoku Institute of Technology
	35-1, Yagiyama Kasumi-cho		35-1, Yagiyama Kasumi-cho
	Taihaku-ku, Sendai, 982-8577		Taihaku-ku, Sendai, 982-8577
	Japan		Japan
	Email: tsuno@m.ieice.org		Email: tsuno@m.ieice.org
	Comments and discussion to bess@ietf.org		Comments and discussion to bess@ietf.org
	"		"
	DESCRIPTION		DESCRIPTION
	"This MIB module will be used by other MIB modules designed for		"This MIB module defines a table representing the attribute
			information of P-tunnels on a PE router.
			This MIB module will be used by other MIB modules designed for
	monitoring and/or configuring Border Gateway		monitoring and/or configuring Border Gateway
	Protocol/MultiProtocol Label Switching		Protocol/MultiProtocol Label Switching
	Layer 2 and Layer 3 Virtual Private		Layer 2 and Layer 3 Virtual Private
	Network that support multicast (L2L3VpnMCast).		Network that support multicast (L2L3VpnMCast).
	Copyright (C) The Internet Society (2017).		Copyright (C) The Internet Society (2017).
	"		"
	-- Revision history.		-- Revision history.
	REVISION "201706211200Z" -- 21th June, 2017		REVISION "201708211200Z" -- 21th August, 2017
	DESCRIPTION		DESCRIPTION
	"Initial version, published as RFC XXXX."		"Initial version, published as RFC XXXX."
	-- RFC Ed.: replace XXXX with actual RFC number and remove this note		-- RFC Ed.: replace XXXX with actual RFC number and remove this note
	::= { mib-2 BBBB }		::= { mib-2 BBBB }
	-- IANA Reg.: Please assign a value for "BBBB" under the		-- IANA Reg.: Please assign a value for "BBBB" under the
	-- 'mib-2' subtree and record the assignment in the SMI		-- 'mib-2' subtree and record the assignment in the SMI
	-- Numbers registry.		-- Numbers registry.
	skipping to change at page 10, line 42 ¶		skipping to change at page 10, line 49 ¶
	::= { l2L3VpnMcastMIB 2 }		::= { l2L3VpnMcastMIB 2 }
	-- tables, scalars, conformance information		-- tables, scalars, conformance information
	-- Table of PMSI Tunnel Attributes		-- Table of PMSI Tunnel Attributes
	l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE		l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE
	SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry		SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table corresponds to a		"An entry in this table corresponds to
	(Provider Multicast Service Interface) PMSI Tunnel		the attribute information of a specific
	attribute and is maintained by a PE router		P-tunnel on a PE router.
	that advertises and receives the attribute.
			A part of attributes correspond to fields in
			a Provider Multicast Service Interface (PMSI) Tunnel
			attribute advertised and received by a PE router.
	The entries will be referred to by other MIB modules		The entries will be referred to by other MIB modules
	for monitoring and/or configuring L2L3VpnMCast.		for monitoring and/or configuring L2L3VpnMCast.
	"		"
	REFERENCE		REFERENCE
	"RFC6514, Section 5"		"RFC6514, Section 5"
	::= { l2L3VpnMcastStates 1 }		::= { l2L3VpnMcastStates 1 }
	l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE		l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
	SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry		SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A conceptual row corresponding to a PTA		"A conceptual row corresponding to a specific
	that is advertised/received on this router.		P-tunnel on this router.
	"		"
	REFERENCE		REFERENCE
	"RFC6514, Section 5"		"RFC6514, Section 5"
	INDEX {		INDEX {
	l2L3VpnMcastPmsiTunnelAttributeFlags,
	l2L3VpnMcastPmsiTunnelAttributeType,		l2L3VpnMcastPmsiTunnelAttributeType,
	l2L3VpnMcastPmsiTunnelAttributeLabel,
	l2L3VpnMcastPmsiTunnelAttributeId		l2L3VpnMcastPmsiTunnelAttributeId
	}		}
	::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }		::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
	L2L3VpnMcastPmsiTunnelAttributeEntry ::=		L2L3VpnMcastPmsiTunnelAttributeEntry ::=
	SEQUENCE {		SEQUENCE {
	l2L3VpnMcastPmsiTunnelAttributeFlags		l2L3VpnMcastPmsiTunnelAttributeFlags
	OCTET STRING,		OCTET STRING,
	l2L3VpnMcastPmsiTunnelAttributeAddlFlags		l2L3VpnMcastPmsiTunnelAttributeAddlFlags
	OCTET STRING,		OCTET STRING,
	skipping to change at page 11, line 43 ¶		skipping to change at page 11, line 51 ¶
	l2L3VpnMcastPmsiTunnelAttributeId		l2L3VpnMcastPmsiTunnelAttributeId
	L2L3VpnMcastProviderTunnelId,		L2L3VpnMcastProviderTunnelId,
	l2L3VpnMcastPmsiTunnelPointer		l2L3VpnMcastPmsiTunnelPointer
	RowPointer,		RowPointer,
	l2L3VpnMcastPmsiTunnelIf		l2L3VpnMcastPmsiTunnelIf
	RowPointer		RowPointer
	}		}
	l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE		l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE
	SYNTAX OCTET STRING (SIZE (1))		SYNTAX OCTET STRING (SIZE (1))
	MAX-ACCESS not-accessible		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object represents the Flags field in the PMSI Tunnel		"This object represents the Flags field in the PMSI Tunnel
	attribute. The Flags field has the following format.		attribute. The Flags field has the following format.
	0 1 2 3 4 5 6 7		0 1 2 3 4 5 6 7
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	|U|E| U |L|		|U|E| U |L|
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	E: Extension flag [RFC7902]		E: Extension flag [RFC7902]
	U: Unassigned		U: Unassigned
	L: Leaf Information Required flag [RFC6514]		L: Leaf Information Required flag [RFC6514]
	When BGP-based PMSI signaling is used, the value of		When BGP-based PMSI signaling is used, the value of
	this object corresponds to the Flags field in		this object corresponds to the Flags field in
	an advertised/received PMSI auto-discovery (A-D) route.		an advertised/received PMSI auto-discovery (A-D) route.
	When UDP-based S-PMSI signaling is used, the value of		When UDP-based S-PMSI signaling is used, the value of
	this object is zero.		this object is zero.
	skipping to change at page 12, line 28 ¶		skipping to change at page 12, line 37 ¶
	bgp-parameters.xhtml#pmsi-tunnel-attributes>.		bgp-parameters.xhtml#pmsi-tunnel-attributes>.
	"		"
	REFERENCE		REFERENCE
	"RFC6514, Section 5		"RFC6514, Section 5
	RFC7902		RFC7902
	"		"
	::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }		::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
	l2L3VpnMcastPmsiTunnelAttributeAddlFlags OBJECT-TYPE		l2L3VpnMcastPmsiTunnelAttributeAddlFlags OBJECT-TYPE
	SYNTAX OCTET STRING (SIZE (6))		SYNTAX OCTET STRING (SIZE (6))
	MAX-ACCESS not-accessible		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object represents BGP Additional PMSI		"This object represents BGP Additional PMSI
	Tunnel Attribute Flags Extended Community		Tunnel Attribute Flags Extended Community
	defined in [RFC7902].		defined in [RFC7902].
	Additional PMSI Tunnel Attribute Flags is		Additional PMSI Tunnel Attribute Flags is
	48 one-bit Flags and has the following format.		48 one-bit Flags and has the following format.
	0 1 2		0 1 2
	skipping to change at page 13, line 44 ¶		skipping to change at page 14, line 4 ¶
	When BGP-based PMSI signaling is used, the value of		When BGP-based PMSI signaling is used, the value of
	this object corresponds to the Tunnel Type field in		this object corresponds to the Tunnel Type field in
	an advertised/received PMSI auto-discovery (A-D) route.		an advertised/received PMSI auto-discovery (A-D) route.
	When UDP-based S-PMSI signaling is used, the value of		When UDP-based S-PMSI signaling is used, the value of
	this object will be one of pimAsm (3), pimSsm (4), or		this object will be one of pimAsm (3), pimSsm (4), or
	pimBidir (5).		pimBidir (5).
	"		"
	REFERENCE		REFERENCE
	"RFC6514, Section 5"		"RFC6514, Section 5"
	::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }		::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
	l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE		l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE
	SYNTAX MplsLabel		SYNTAX MplsLabel
	MAX-ACCESS not-accessible		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The MPLS Label field in a PMSI Tunnel attribute.		"The MPLS Label field in a PMSI Tunnel attribute.
	When BGP-based PMSI signaling is used, the value of		When BGP-based PMSI signaling is used, the value of
	this object corresponds to the MPLS Label field in		this object corresponds to the MPLS Label field in
	an advertised/received PMSI A-D route.		an advertised/received PMSI A-D route.
	When UDP-based S-PMSI signaling is used, the value of		When UDP-based S-PMSI signaling is used, the value of
	this object is zero that indicates the absence of MPLS		this object is zero that indicates the absence of MPLS
	skipping to change at page 15, line 16 ¶		skipping to change at page 15, line 26 ¶
	"If the tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId		"If the tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId
	has a corresponding entry in the ifXTable [RFC2863],		has a corresponding entry in the ifXTable [RFC2863],
	this object will point to the row pertaining to the entry		this object will point to the row pertaining to the entry
	in the ifXTable. Otherwise, this object MUST be set to		in the ifXTable. Otherwise, this object MUST be set to
	zeroDotZero."		zeroDotZero."
	DEFVAL { zeroDotZero }		DEFVAL { zeroDotZero }
	::= { l2L3VpnMcastPmsiTunnelAttributeEntry 7 }		::= { l2L3VpnMcastPmsiTunnelAttributeEntry 7 }
	-- Conformance Information		-- Conformance Information
	l2L3VpnMcastGroups OBJECT IDENTIFIER
	::= { l2L3VpnMcastConformance 1 }
	l2L3VpnMcastCompliances OBJECT IDENTIFIER		l2L3VpnMcastCompliances OBJECT IDENTIFIER
			::= { l2L3VpnMcastConformance 1 }
			l2L3VpnMcastGroups OBJECT IDENTIFIER
	::= { l2L3VpnMcastConformance 2 }		::= { l2L3VpnMcastConformance 2 }
	-- Compliance Statements		-- Compliance Statements
	l2L3VpnMcastCompliance MODULE-COMPLIANCE		l2L3VpnMcastCompliance MODULE-COMPLIANCE
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The compliance statement: no mandatory groups "		"The compliance statement for SNMP entities which implement
			this L2L3-VPN-MCAST-MIB Module."
	MODULE -- this module		MODULE -- this module
			MANDATORY-GROUPS {
			l2L3VpnMcastPmsiFieldGroup
			}
	GROUP l2L3VpnMcastOptionalGroup		GROUP l2L3VpnMcastOptionalGroup
	DESCRIPTION		DESCRIPTION
	"This group is optional."		"This group is optional."
	::= { l2L3VpnMcastCompliances 1 }		::= { l2L3VpnMcastCompliances 1 }
	-- units of conformance		-- units of conformance
			l2L3VpnMcastPmsiFieldGroup OBJECT-GROUP
			OBJECTS {
			l2L3VpnMcastPmsiTunnelAttributeFlags,
			l2L3VpnMcastPmsiTunnelAttributeAddlFlags,
			l2L3VpnMcastPmsiTunnelAttributeLabel
			}
			STATUS current
			DESCRIPTION
			"Support of these objects is required."
			::= { l2L3VpnMcastGroups 1 }
	l2L3VpnMcastOptionalGroup OBJECT-GROUP		l2L3VpnMcastOptionalGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
	l2L3VpnMcastPmsiTunnelPointer,		l2L3VpnMcastPmsiTunnelPointer,
	l2L3VpnMcastPmsiTunnelIf		l2L3VpnMcastPmsiTunnelIf
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Support of these objects is not required."		"Support of these objects is optional."
	::= { l2L3VpnMcastGroups 1 }		::= { l2L3VpnMcastGroups 2 }
	END		END
	5. Security Considerations		5. Security Considerations
	There are no management objects defined in these MIB modules that		There are no management objects defined in these MIB modules that
	have a MAX-ACCESS clause of read-write and/or read-create. So, if		have a MAX-ACCESS clause of read-write and/or read-create. So, if
	this MIB module is implemented correctly, then there is no risk that		this MIB module is implemented correctly, then there is no risk that
	an intruder can alter or create any management objects of this MIB		an intruder can alter or create any management objects of this MIB
	module via direct SNMP SET operations.		module via direct SNMP SET operations.
	skipping to change at page 17, line 18 ¶		skipping to change at page 17, line 41 ¶
	IANA is requested to root MIB objects in the MIB module contained in		IANA is requested to root MIB objects in the MIB module contained in
	this document under the mib-2 subtree.		this document under the mib-2 subtree.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/		Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
	RFC2119, March 1997,		RFC2119, March 1997, <https://www.rfc-editor.org/info/
	<http://www.rfc-editor.org/info/rfc2119>.		rfc2119>.
	[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.		[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
	Schoenwaelder, Ed., "Structure of Management Information		Schoenwaelder, Ed., "Structure of Management Information
	Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/		Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/
	RFC2578, April 1999,		RFC2578, April 1999, <https://www.rfc-editor.org/info/
	<http://www.rfc-editor.org/info/rfc2578>.		rfc2578>.
	[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.		[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
	Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD		Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
	58, RFC 2579, DOI 10.17487/RFC2579, April 1999,		58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
	<http://www.rfc-editor.org/info/rfc2579>.		<https://www.rfc-editor.org/info/rfc2579>.
	[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.		[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
	Schoenwaelder, Ed., "Conformance Statements for SMIv2",		Schoenwaelder, Ed., "Conformance Statements for SMIv2",
	STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,		STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
	<http://www.rfc-editor.org/info/rfc2580>.		<https://www.rfc-editor.org/info/rfc2580>.
	[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group		[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
	MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,		MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
	<http://www.rfc-editor.org/info/rfc2863>.		<https://www.rfc-editor.org/info/rfc2863>.
	[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model		[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
	(USM) for version 3 of the Simple Network Management		(USM) for version 3 of the Simple Network Management
	Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/		Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/
	RFC3414, December 2002,		RFC3414, December 2002, <https://www.rfc-editor.org/info/
	<http://www.rfc-editor.org/info/rfc3414>.		rfc3414>.
	[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,		[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
	"Multiprotocol Label Switching (MPLS) Traffic Engineering		"Multiprotocol Label Switching (MPLS) Traffic Engineering
	(TE) Management Information Base (MIB)", RFC 3812, DOI		(TE) Management Information Base (MIB)", RFC 3812, DOI
	10.17487/RFC3812, June 2004,		10.17487/RFC3812, June 2004, <https://www.rfc-
	<http://www.rfc-editor.org/info/rfc3812>.		editor.org/info/rfc3812>.
	[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The		[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
	Advanced Encryption Standard (AES) Cipher Algorithm in the		Advanced Encryption Standard (AES) Cipher Algorithm in the
	SNMP User-based Security Model", RFC 3826, DOI 10.17487/		SNMP User-based Security Model", RFC 3826, DOI 10.17487/
	RFC3826, June 2004,		RFC3826, June 2004, <https://www.rfc-editor.org/info/
	<http://www.rfc-editor.org/info/rfc3826>.		rfc3826>.
	[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, DOI 10.17487/		[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, DOI 10.17487/
	RFC4087, June 2005,		RFC4087, June 2005, <https://www.rfc-editor.org/info/
	<http://www.rfc-editor.org/info/rfc4087>.		rfc4087>.
			[RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S.
			Yasukawa, Ed., "Extensions to Resource Reservation
			Protocol - Traffic Engineering (RSVP-TE) for Point-to-
			Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI
			10.17487/RFC4875, May 2007, <https://www.rfc-
			editor.org/info/rfc4875>.
	[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model		[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
	for the Simple Network Management Protocol (SNMP)", STD		for the Simple Network Management Protocol (SNMP)", STD
	78, RFC 5591, DOI 10.17487/RFC5591, June 2009,		78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
	<http://www.rfc-editor.org/info/rfc5591>.		<https://www.rfc-editor.org/info/rfc5591>.
	[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure		[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
	Shell Transport Model for the Simple Network Management		Shell Transport Model for the Simple Network Management
	Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June		Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
	2009, <http://www.rfc-editor.org/info/rfc5592>.		2009, <https://www.rfc-editor.org/info/rfc5592>.
	[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport		[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
	Model for the Simple Network Management Protocol (SNMP)",		Model for the Simple Network Management Protocol (SNMP)",
	STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,		STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
	<http://www.rfc-editor.org/info/rfc6353>.		<https://www.rfc-editor.org/info/rfc6353>.
			[RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B.
			Thomas, "Label Distribution Protocol Extensions for Point-
			to-Multipoint and Multipoint-to-Multipoint Label Switched
			Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011,
			<https://www.rfc-editor.org/info/rfc6388>.
	[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/		[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
	BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February		BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
	2012, <http://www.rfc-editor.org/info/rfc6513>.		2012, <https://www.rfc-editor.org/info/rfc6513>.
	[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP		[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
	Encodings and Procedures for Multicast in MPLS/BGP IP		Encodings and Procedures for Multicast in MPLS/BGP IP
	VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,		VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
	<http://www.rfc-editor.org/info/rfc6514>.		<https://www.rfc-editor.org/info/rfc6514>.
	[RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and		[RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and
	C. Kodeboniya, "Multicast in Virtual Private LAN Service		C. Kodeboniya, "Multicast in Virtual Private LAN Service
	(VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014,		(VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014,
	<http://www.rfc-editor.org/info/rfc7117>.		<https://www.rfc-editor.org/info/rfc7117>.
	[RFC7385] Andersson, L. and G. Swallow, "IANA Registry for		[RFC7385] Andersson, L. and G. Swallow, "IANA Registry for
	P-Multicast Service Interface (PMSI) Tunnel Type Code		P-Multicast Service Interface (PMSI) Tunnel Type Code
	Points", RFC 7385, DOI 10.17487/RFC7385, October 2014,		Points", RFC 7385, DOI 10.17487/RFC7385, October 2014,
	<http://www.rfc-editor.org/info/rfc7385>.		<https://www.rfc-editor.org/info/rfc7385>.
	[RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T.,		[RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T.,
	Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area		Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area
	Point-to-Multipoint (P2MP) Segmented Label Switched Paths		Point-to-Multipoint (P2MP) Segmented Label Switched Paths
	(LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015,		(LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015,
	<http://www.rfc-editor.org/info/rfc7524>.		<https://www.rfc-editor.org/info/rfc7524>.
			[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
			Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
			Multicast - Sparse Mode (PIM-SM): Protocol Specification
			(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
			2016, <https://www.rfc-editor.org/info/rfc7761>.
	7.2. Informative References		7.2. Informative References
	[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 Internet-		"Introduction and Applicability Statements for Internet-
	Standard Management Framework", RFC 3410, DOI 10.17487/		Standard Management Framework", RFC 3410, DOI 10.17487/
	RFC3410, December 2002,		RFC3410, December 2002, <https://www.rfc-editor.org/info/
	<http://www.rfc-editor.org/info/rfc3410>.		rfc3410>.
	Authors' Addresses		Authors' Addresses
	Zhaohui (Jeffrey) Zhang		Zhaohui (Jeffrey) Zhang
	Juniper Networks, Inc.		Juniper Networks, Inc.
	10 Technology Park Drive		10 Technology Park Drive
	Westford, MA 01886		Westford, MA 01886
	USA		USA
	Email: zzhang@juniper.net		Email: zzhang@juniper.net
End of changes. 53 change blocks.
	90 lines changed or deleted		133 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/