draft-ietf-bess-mvpn-mib-09.txt		draft-ietf-bess-mvpn-mib-10.txt
	Network Working Group H. Tsunoda		Network Working Group H. Tsunoda
	Internet-Draft Tohoku Institute of Technology		Internet-Draft Tohoku Institute of Technology
	Intended status: Standards Track August 09, 2018		Intended status: Standards Track August 11, 2018
	Expires: February 10, 2019		Expires: February 12, 2019
	BGP/MPLS Layer 3 VPN Multicast Management Information Base		BGP/MPLS Layer 3 VPN Multicast Management Information Base
	draft-ietf-bess-mvpn-mib-09		draft-ietf-bess-mvpn-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 managed objects to configure and/or		In particular, it describes managed objects to configure and/or
	monitor Multicast communication over IP Virtual Private Networks		monitor Multicast communication over IP Virtual Private Networks
	(VPNs) supported by MultiProtocol Label Switching/Border Gateway		(VPNs) supported by MultiProtocol Label Switching/Border Gateway
	Protcol (MPLS/BGP) on a Provider Edge router.		Protcol (MPLS/BGP) on a Provider Edge router.
	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 February 10, 2019.		This Internet-Draft will expire on February 12, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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 12 ¶		skipping to change at page 2, line 12 ¶
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2		1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
	2. The Internet-Standard Management Framework . . . . . . . . . 3		2. The Internet-Standard Management Framework . . . . . . . . . 3
	3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 3		3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4		3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4
	3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5		3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 50		4. Security Considerations . . . . . . . . . . . . . . . . . . . 50
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53
	6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 53		6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 53
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 53		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 53
	7.1. Normative References . . . . . . . . . . . . . . . . . . 53		7.1. Normative References . . . . . . . . . . . . . . . . . . 54
	7.2. Informative References . . . . . . . . . . . . . . . . . 56		7.2. Informative References . . . . . . . . . . . . . . . . . 56
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 56		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 56
	1. Introduction		1. Introduction
	[RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting		[RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting
	multicast in Border Gateway Protocol/MultiProtocol Label Switching		multicast in Border Gateway Protocol/MultiProtocol Label Switching
	(BGP/MPLS) Layer 3 (IP) Virtual Private Networks (VPNs). Throughout		(BGP/MPLS) Layer 3 (IP) Virtual Private Networks (VPNs). Throughout
	this document, we will use the term "Multicast VPN" (MVPN) [RFC6513]		this document, we will use the term "Multicast VPN" (MVPN) [RFC6513]
	to refer to a BGP/MPLS IP VPN that supports multicast.		to refer to a BGP/MPLS IP VPN that supports multicast.
	skipping to change at page 3, line 28 ¶		skipping to change at page 3, line 28 ¶
	particular MVPN to transmit a message to all PEs in the same MVPN.		particular MVPN to transmit a message to all PEs in the same MVPN.
	An S-PMSI enables a PE to transmit a message to a selected set of PEs		An S-PMSI enables a PE to transmit a message to a selected set of PEs
	in the same MVPN.		in the same MVPN.
	As described in [RFC4382], each PE maintains one default forwarding		As described in [RFC4382], each PE maintains one default forwarding
	table and zero or more "Virtual Routing and Forwarding tables"		table and zero or more "Virtual Routing and Forwarding tables"
	(VRFs). Throughout this document, we will use the term "multicast		(VRFs). Throughout this document, we will use the term "multicast
	VRF" (MVRF) to refer to a VRF that contains multicast routing		VRF" (MVRF) to refer to a VRF that contains multicast routing
	information.		information.
	The key words "MUST", "SHOULD", "RECOMMENDED", and "MAY" in this		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	document are to be interpreted as described in [RFC2119].		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
			"OPTIONAL" in this document are to be interpreted as described in BCP
			14 [RFC2119] [RFC8174] when, and only when, they appear in all
			capitals, as shown here.
	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).
	skipping to change at page 5, line 37 ¶		skipping to change at page 5, line 43 ¶
	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
	FROM SNMPv2-CONF -- [RFC2580]		FROM SNMPv2-CONF -- [RFC2580]
	RowPointer, TimeStamp, DateAndTime		RowPointer, TimeStamp, DateAndTime
	FROM SNMPv2-TC -- [RFC2579]		FROM SNMPv2-TC -- [RFC2579]
	InterfaceIndex, InterfaceIndexOrZero		InterfaceIndex, InterfaceIndexOrZero
	FROM IF-MIB -- [RFC2863]		FROM IF-MIB -- [RFC2863]
	InetAddress, InetAddressType, InetAddressPrefixLength		InetAddress, InetAddressType, InetAddressPrefixLength
	FROM INET-ADDRESS-MIB -- [RFC3291]		FROM INET-ADDRESS-MIB -- [RFC4001]
	mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher		mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher
	FROM MPLS-L3VPN-STD-MIB -- [RFC4382]		FROM MPLS-L3VPN-STD-MIB -- [RFC4382]
	IANAipRouteProtocol, IANAipMRouteProtocol		IANAipRouteProtocol, IANAipMRouteProtocol
	FROM IANA-RTPROTO-MIB -- [RTPROTO]		FROM IANA-RTPROTO-MIB -- [RTPROTO]
	L2L3VpnMcastProviderTunnelType		L2L3VpnMcastProviderTunnelType
	FROM L2L3-VPN-MCAST-TC-MIB;		FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX]
			-- RFC Ed.: replace XXXX with actual RFC number and remove this note
	mvpnMIB MODULE-IDENTITY		mvpnMIB MODULE-IDENTITY
	LAST-UPDATED "201808091200Z" -- 9th August 2018 12:00:00 GMT		LAST-UPDATED "201808101200Z" -- 10th August 2018 12:00:00 GMT
	ORGANIZATION "IETF BESS Working Group."		ORGANIZATION "IETF BESS Working Group."
	CONTACT-INFO		CONTACT-INFO
	" 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"
	skipping to change at page 6, line 24 ¶		skipping to change at page 6, line 32 ¶
	"This MIB module contains managed object definitions to		"This MIB module contains managed object definitions to
	configure and/or monitor Multicast communication over IP		configure and/or monitor Multicast communication over IP
	Virtual Private Networks (VPNs) supported by MultiProtocol		Virtual Private Networks (VPNs) supported by MultiProtocol
	Label Switching/Border Gateway Protcol (MPLS/BGP) on a		Label Switching/Border Gateway Protcol (MPLS/BGP) on a
	Provider Edge router (PE).		Provider Edge router (PE).
	Copyright (C) The Internet Society (2018).		Copyright (C) The Internet Society (2018).
	"		"
	-- Revision history.		-- Revision history.
	REVISION "201808091200Z" -- 9th August, 2018		REVISION "201808101200Z" -- 10th August, 2018
	DESCRIPTION		DESCRIPTION
	"Initial version, published as RFC XXXX."		"Initial version, published as RFC YYYY."
	-- RFC Ed. replace XXXX with the actual RFC number and		-- RFC Ed. replace YYYY with the actual RFC number and
	-- remove this note		-- remove this note
	::= { mib-2 YYYY }		::= { mib-2 AAAA }
	-- IANA Reg.: Please assign a value for "YYYY" 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.
	-- RFC Ed.: When the above assignment has been made, please		-- RFC Ed.: When the above assignment has been made, please
	-- remove the above note		-- remove the above note
	-- replace "YYYY" here with the assigned value and		-- replace "AAAA" here with the assigned value and
	-- remove this note.		-- remove this note.
	-- Top level components of this MIB module.		-- Top level components of this MIB module.
	mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 }		mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 }
	-- scalars, tables		-- scalars, tables
	mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 }		mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 }
	-- conformance information		-- conformance information
	mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 }		mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 }
	-- mvpn Objects		-- mvpn Objects
	mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 }		mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 }
	-- Scalar Objects		-- Scalar Objects
	mvpnMvrfs OBJECT-TYPE		mvpnMvrfs OBJECT-TYPE
	SYNTAX Gauge32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 53, line 20 ¶		skipping to change at page 53, line 23 ¶
	the objects only to those principals (users) that have legitimate		the objects only to those principals (users) that have legitimate
	rights to indeed GET or SET (change/create/delete) them.		rights to indeed GET or SET (change/create/delete) them.
	5. IANA Considerations		5. IANA Considerations
	The MIB module in this document uses the following IANA-assigned		The MIB module in this document uses the following IANA-assigned
	OBJECT IDENTIFIER values recorded in the SMI Numbers registry:		OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
	Descriptor OBJECT IDENTIFIER value		Descriptor OBJECT IDENTIFIER value
	---------- -----------------------		---------- -----------------------
	mvpnMIB { mib-2 YYYY }		mvpnMIB { mib-2 AAAA }
	Editor's Note (to be removed prior to publication): the IANA is		Editor's Note (to be removed prior to publication): the IANA is
	requested to assign a value for "YYYY" under the 'mib-2' subtree and		requested to assign a value for "AAAA" under the 'mib-2' subtree and
	to record the assignment in the SMI Numbers registry. When the		to record the assignment in the SMI Numbers registry. When the
	assignment has been made, the RFC Editor is asked to replace "YYYY"		assignment has been made, the RFC Editor is asked to replace "AAAA"
	(here and in the MIB module) with the assigned value and to remove		(here and in the MIB module) with the assigned value and to remove
	this note.		this note.
	6. Acknowledgement		6. Acknowledgement
	An earlier draft version of this document was coauthored by Zhaohui		An earlier draft version of this document was coauthored by Zhaohui
	(Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep		(Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep
	G. Jain, based on an earlier draft written by Susheela Vaidya,		G. Jain, based on an earlier draft written by Susheela Vaidya,
	Thomas D. Nadeau, and Harmen Van der Linde.		Thomas D. Nadeau, and Harmen Van der Linde.
	skipping to change at page 54, line 40 ¶		skipping to change at page 54, line 45 ¶
	[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,
	<https://www.rfc-editor.org/info/rfc2863>.		<https://www.rfc-editor.org/info/rfc2863>.
	[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,		[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
	Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack		Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
	Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,		Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,
	<https://www.rfc-editor.org/info/rfc3032>.		<https://www.rfc-editor.org/info/rfc3032>.
	[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
	Schoenwaelder, "Textual Conventions for Internet Network
	Addresses", RFC 3291, DOI 10.17487/RFC3291, May 2002,
	<https://www.rfc-editor.org/info/rfc3291>.
	[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, <https://www.rfc-editor.org/info/		RFC3414, December 2002, <https://www.rfc-editor.org/info/
	rfc3414>.		rfc3414>.
	[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, <https://www.rfc-editor.org/info/		RFC3826, June 2004, <https://www.rfc-editor.org/info/
	rfc3826>.		rfc3826>.
			[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
			Schoenwaelder, "Textual Conventions for Internet Network
			Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005,
			<https://www.rfc-editor.org/info/rfc4001>.
	[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private		[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
	Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February		Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
	2006, <https://www.rfc-editor.org/info/rfc4364>.		2006, <https://www.rfc-editor.org/info/rfc4364>.
	[RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer		[RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer
	3 Virtual Private Network (VPN) Management Information		3 Virtual Private Network (VPN) Management Information
	Base", RFC 4382, DOI 10.17487/RFC4382, February 2006,		Base", RFC 4382, DOI 10.17487/RFC4382, February 2006,
	<https://www.rfc-editor.org/info/rfc4382>.		<https://www.rfc-editor.org/info/rfc4382>.
	[RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast		[RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast
	skipping to change at page 56, line 11 ¶		skipping to change at page 56, line 16 ¶
	Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",		Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",
	RFC 6625, DOI 10.17487/RFC6625, May 2012,		RFC 6625, DOI 10.17487/RFC6625, May 2012,
	<https://www.rfc-editor.org/info/rfc6625>.		<https://www.rfc-editor.org/info/rfc6625>.
	[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,		[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
	Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent		Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
	Multicast - Sparse Mode (PIM-SM): Protocol Specification		Multicast - Sparse Mode (PIM-SM): Protocol Specification
	(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March		(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
	2016, <https://www.rfc-editor.org/info/rfc7761>.		2016, <https://www.rfc-editor.org/info/rfc7761>.
			[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
			2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
			May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RTPROTO] IANA, "IP Route Protocol MIB", 2016,		[RTPROTO] IANA, "IP Route Protocol MIB", 2016,
	<http://www.iana.org/assignments/ianaiprouteprotocol-mib>.		<http://www.iana.org/assignments/ianaiprouteprotocol-mib>.
	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, <https://www.rfc-editor.org/info/		RFC3410, December 2002, <https://www.rfc-editor.org/info/
	rfc3410>.		rfc3410>.
End of changes. 23 change blocks.
	25 lines changed or deleted		36 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/