draft-ietf-mpls-mldp-in-band-signaling-05.txt		draft-ietf-mpls-mldp-in-band-signaling-06.txt
	Network Working Group IJ. Wijnands, Ed.		Network Working Group IJ. Wijnands, Ed.
	Internet-Draft T. Eckert		Internet-Draft T. Eckert
	Intended status: Standards Track Cisco Systems, Inc.		Intended status: Standards Track Cisco Systems, Inc.
	Expires: June 3, 2012 N. Leymann		Expires: December 24, 2012 N. Leymann
	Deutsche Telekom		Deutsche Telekom
	M. Napierala		M. Napierala
	AT&T Labs		AT&T Labs
	December 1, 2011		June 22, 2012
	Multipoint LDP in-band signaling for Point-to-Multipoint and Multipoint-		Multipoint LDP in-band signaling for Point-to-Multipoint and Multipoint-
	to-Multipoint Label Switched Paths		to-Multipoint Label Switched Paths
	draft-ietf-mpls-mldp-in-band-signaling-05		draft-ietf-mpls-mldp-in-band-signaling-06
	Abstract		Abstract
	Consider an IP multicast tree, constructed by Protocol Independent		Consider an IP multicast tree, constructed by Protocol Independent
	Multicast (PIM), needs to pass through an MPLS domain in which		Multicast (PIM), needs to pass through an MPLS domain in which
	Multipoint LDP (mLDP) Point-to-Multipoint and/or Multipoint-to-		Multipoint LDP (mLDP) Point-to-Multipoint and/or Multipoint-to-
	Multipoint Labels Switched Paths (LSPs) can be created. The part of		Multipoint Labels Switched Paths (LSPs) can be created. The part of
	the IP multicast tree that traverses the MPLS domain can be		the IP multicast tree that traverses the MPLS domain can be
	instantiated as a multipoint LSP. When a PIM Join message is		instantiated as a multipoint LSP. When a PIM Join message is
	received at the border of the MPLS domain, information from that		received at the border of the MPLS domain, information from that
	skipping to change at page 1, line 46		skipping to change at page 1, line 46
	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 3, 2012.		This Internet-Draft will expire on December 24, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2012 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 12, line 22		skipping to change at page 12, line 22
	8.1. Normative References		8.1. Normative References
	[RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP		[RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP
	Specification", RFC 5036, October 2007.		Specification", RFC 5036, October 2007.
	[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, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[I-D.ietf-mpls-ldp-p2mp]		[I-D.ietf-mpls-ldp-p2mp]
	Minei, I., Kompella, K., Wijnands, I., and B. Thomas,		Minei, I., Wijnands, I., Kompella, K., and B. Thomas,
	"Label Distribution Protocol Extensions for Point-to-		"Label Distribution Protocol Extensions for Point-to-
	Multipoint and Multipoint-to-Multipoint Label Switched		Multipoint and Multipoint-to-Multipoint Label Switched
	Paths", draft-ietf-mpls-ldp-p2mp-11 (work in progress),		Paths", draft-ietf-mpls-ldp-p2mp-15 (work in progress),
	October 2010.		August 2011.
	8.2. Informative References		8.2. Informative References
	[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,		[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
	"Protocol Independent Multicast - Sparse Mode (PIM-SM):		"Protocol Independent Multicast - Sparse Mode (PIM-SM):
	Protocol Specification (Revised)", RFC 4601, August 2006.		Protocol Specification (Revised)", RFC 4601, August 2006.
	[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for		[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
	IP", RFC 4607, August 2006.		IP", RFC 4607, August 2006.
	skipping to change at page 13, line 4		skipping to change at page 13, line 4
	[RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery		[RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery
	Protocol (MSDP)", RFC 3618, October 2003.		Protocol (MSDP)", RFC 3618, October 2003.
	[I-D.ietf-l3vpn-2547bis-mcast]		[I-D.ietf-l3vpn-2547bis-mcast]
	Aggarwal, R., Bandi, S., Cai, Y., Morin, T., Rekhter, Y.,		Aggarwal, R., Bandi, S., Cai, Y., Morin, T., Rekhter, Y.,
	Rosen, E., Wijnands, I., and S. Yasukawa, "Multicast in		Rosen, E., Wijnands, I., and S. Yasukawa, "Multicast in
	MPLS/BGP IP VPNs", draft-ietf-l3vpn-2547bis-mcast-10 (work		MPLS/BGP IP VPNs", draft-ietf-l3vpn-2547bis-mcast-10 (work
	in progress), January 2010.		in progress), January 2010.
	[I-D.rekhter-pim-sm-over-mldp]		[I-D.rekhter-pim-sm-over-mldp]
	Rekhter, Y., Aggarwal, R., and N. Leymann, "Carrying		Rekhter, Y. and R. Aggarwal, "Carrying PIM-SM in ASM mode
	PIM-SM in ASM mode Trees over P2MP mLDP LSPs",		Trees over P2MP mLDP LSPs",
	draft-rekhter-pim-sm-over-mldp-02 (work in progress),		draft-rekhter-pim-sm-over-mldp-04 (work in progress),
	August 2010.		August 2011.
	[I-D.rosen-l3vpn-mvpn-mspmsi]		[I-D.rosen-l3vpn-mvpn-mspmsi]
	Boers, A., Cai, Y., Napierala, M., Rosen, E., and I.		Cai, Y., Rosen, E., Wijnands, I., Napierala, M., and A.
	Wijnands, "MVPN: Optimized use of PIM via MS-PMSIs",		Boers, "MVPN: Optimized use of PIM via MS-PMSIs",
	draft-rosen-l3vpn-mvpn-mspmsi-08 (work in progress),		draft-rosen-l3vpn-mvpn-mspmsi-09 (work in progress),
	January 2011.		August 2011.
	Authors' Addresses		Authors' Addresses
	IJsbrand Wijnands (editor)		IJsbrand Wijnands (editor)
	Cisco Systems, Inc.		Cisco Systems, Inc.
	De kleetlaan 6a		De kleetlaan 6a
	Diegem 1831		Diegem 1831
	Belgium		Belgium
	Email: ice@cisco.com		Email: ice@cisco.com
End of changes. 9 change blocks.
	16 lines changed or deleted		16 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/