< draft-ietf-l3vpn-mldp-vrf-in-band-signaling-00.txt		draft-ietf-l3vpn-mldp-vrf-in-band-signaling-01.txt >
	Network Working Group IJ. Wijnands, Ed.		Network Working Group IJ. Wijnands, Ed.
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track P. Hitchen		Intended status: Standards Track P. Hitchen
	Expires: June 23, 2013 BT		Expires: December 23, 2013 BT
	N. Leymann		N. Leymann
	Deutsche Telekom		Deutsche Telekom
	W. Henderickx		W. Henderickx
	Alcatel-Lucent		Alcatel-Lucent
	A. Gulko		A. Gulko
	Thomson Reuters		Thomson Reuters
	December 20, 2012		June 21, 2013
	Multipoint Label Distribution Protocol		Multipoint Label Distribution Protocol
	In-Band Signaling in a VRF Context		In-Band Signaling in a VRF Context
	draft-ietf-l3vpn-mldp-vrf-in-band-signaling-00		draft-ietf-l3vpn-mldp-vrf-in-band-signaling-01
	Abstract		Abstract
	Sometimes an IP multicast distribution tree (MDT) traverses both		Sometimes an IP multicast distribution tree (MDT) traverses both
	MPLS-enabled and non-MPLS-enabled regions of a network. Typically		MPLS-enabled and non-MPLS-enabled regions of a network. Typically
	the MDT begins and ends in non-MPLS regions, but travels through an		the MDT begins and ends in non-MPLS regions, but travels through an
	MPLS region. In such cases, it can be useful to begin building the		MPLS region. In such cases, it can be useful to begin building the
	MDT as a pure IP MDT, then convert it to an MPLS Multipoint LSP		MDT as a pure IP MDT, then convert it to an MPLS Multipoint LSP
	(Label Switched Path) when it enters an MPLS-enabled region, and then		(Label Switched Path) when it enters an MPLS-enabled region, and then
	convert it back to a pure IP MDT when it enters a non-MPLS-enabled		convert it back to a pure IP MDT when it enters a non-MPLS-enabled
	skipping to change at page 2, line 7 ¶		skipping to change at page 2, line 7 ¶
	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 June 23, 2013.		This Internet-Draft will expire on December 23, 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 respect		carefully, as they describe your rights and restrictions with respect
	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
	skipping to change at page 11, line 21 ¶		skipping to change at page 11, line 21 ¶
	The same security considerations apply as for the base LDP		The same security considerations apply as for the base LDP
	specification, described in [RFC5036], and the base mLDP		specification, described in [RFC5036], and the base mLDP
	specification, described in [RFC6388]		specification, described in [RFC6388]
	5. IANA considerations		5. IANA considerations
	[RFC6388] defines a registry for "The LDP MP Opaque Value Element		[RFC6388] defines a registry for "The LDP MP Opaque Value Element
	Basic Type". This document requires the assignment of four new code		Basic Type". This document requires the assignment of four new code
	points in this registry:		points in this registry:
	Transit VPNv4 Source TLV type		Transit VPNv4 Source TLV type - requested 250
	Transit VPNv6 Source TLV type		Transit VPNv6 Source TLV type - requested 251
	Transit VPNv4 Bidir TLV type		Transit VPNv4 Bidir TLV type - requested 9
	Transit VPNv6 Bidir TLV type		Transit VPNv6 Bidir TLV type - requested 10
	6. Acknowledgments		6. Acknowledgments
	Thanks to Eric Rosen, Andy Green and Yakov Rekhter for their comments		Thanks to Eric Rosen, Andy Green and Yakov Rekhter for their comments
	on the draft.		on the draft.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
End of changes. 9 change blocks.
	9 lines changed or deleted		9 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/