draft-ietf-lisp-multicast-01.txt		draft-ietf-lisp-multicast-02.txt
	Network Working Group D. Farinacci		Network Working Group D. Farinacci
	Internet-Draft D. Meyer		Internet-Draft D. Meyer
	Intended status: Experimental J. Zwiebel		Intended status: Experimental J. Zwiebel
	Expires: November 29, 2009 S. Venaas		Expires: April 2, 2010 S. Venaas
	cisco Systems		cisco Systems
	May 28, 2009		September 29, 2009
	LISP for Multicast Environments		LISP for Multicast Environments
	draft-ietf-lisp-multicast-01.txt		draft-ietf-lisp-multicast-02.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 34		skipping to change at page 1, line 34
	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."
	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 November 29, 2009.		This Internet-Draft will expire on April 2, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 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 in effect on the date of		Provisions Relating to IETF Documents in effect on the date of
	publication of this document (http://trustee.ietf.org/license-info).		publication of this document (http://trustee.ietf.org/license-info).
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 43		skipping to change at page 2, line 43
	9.3. Making a Multicast Interworking Decision . . . . . . . . . 25		9.3. Making a Multicast Interworking Decision . . . . . . . . . 25
	10. Considerations when RP Addresses are Embedded in Group		10. Considerations when RP Addresses are Embedded in Group
	Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 26		Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 26
	11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 27		11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 27
	12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 28		12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 28
	13. Security Considerations . . . . . . . . . . . . . . . . . . . 29		13. Security Considerations . . . . . . . . . . . . . . . . . . . 29
	14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30		14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30
	15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31		15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
	15.1. Normative References . . . . . . . . . . . . . . . . . . . 31		15.1. Normative References . . . . . . . . . . . . . . . . . . . 31
	15.2. Informative References . . . . . . . . . . . . . . . . . . 31		15.2. Informative References . . . . . . . . . . . . . . . . . . 31
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33		Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 33
			A.1. Changes to draft-ietf-lisp-multicsat-02.txt . . . . . . . 33
			A.2. Changes to draft-ietf-lisp-multicsat-01.txt . . . . . . . 33
			A.3. Changes to draft-ietf-lisp-multicsat-00.txt . . . . . . . 33
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
	1. Requirements Notation		1. Requirements Notation
	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 [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. Introduction		2. Introduction
	The Locator/ID Separation Architecture [LISP] provides a mechanism to		The Locator/ID Separation Architecture [LISP] provides a mechanism to
	skipping to change at page 8, line 29		skipping to change at page 8, line 29
	their (S-EID,G) PIM Join/Prune message to. mPTRs are used so LISP		their (S-EID,G) PIM Join/Prune message to. mPTRs are used so LISP
	source multicast sites can send multicast packets using source		source multicast sites can send multicast packets using source
	addresses from the EID namespace. mPTRs act as Proxy ETRs for		addresses from the EID namespace. mPTRs act as Proxy ETRs for
	supporting multicast routing in a LISP infrastructure.		supporting multicast routing in a LISP infrastructure.
	Mixed Locator-Sets: this is a locator-set for a LISP database		Mixed Locator-Sets: this is a locator-set for a LISP database
	mapping entry where the RLOC addresses in the locator-set are in		mapping entry where the RLOC addresses in the locator-set are in
	both IPv4 and IPv6 format.		both IPv4 and IPv6 format.
	Unicast Encapsulated PIM Join/Prune Message: this is a standard PIM		Unicast Encapsulated PIM Join/Prune Message: this is a standard PIM
	Join/Prune message (LISP encapsulated with destination UDP port		Join/Prune message (encapsulated in a LISP Encapsulated Control
	4341) which is sent by ETRs at multicast receiver sites to an ITR		Message with destination UDP port 4342) which is sent by ETRs at
	at a multicast source site. This message is sent periodically as		multicast receiver sites to an ITR at a multicast source site.
	long as there are interfaces in the oif-list for the (S-EID,G)		This message is sent periodically as long as there are interfaces
	entry the ETR is joining for.		in the oif-list for the (S-EID,G) entry the ETR is joining for.
	4. Basic Overview		4. Basic Overview
	LISP, when used for unicast routing, increases the site's ability to		LISP, when used for unicast routing, increases the site's ability to
	control ingress traffic flows. Egress traffic flows are controlled		control ingress traffic flows. Egress traffic flows are controlled
	by the IGP in the source site. For multicast, the IGP coupled with		by the IGP in the source site. For multicast, the IGP coupled with
	PIM can decide which path multicast packets ingress. By using the		PIM can decide which path multicast packets ingress. By using the
	traffic engineering features of LISP, a multicast source site can		traffic engineering features of LISP, a multicast source site can
	control the egress of its multicast traffic. By controlling the		control the egress of its multicast traffic. By controlling the
	priorities of locators from a mapping database entry, a source		priorities of locators from a mapping database entry, a source
	skipping to change at page 32, line 5		skipping to change at page 32, line 5
	[ALT] Farinacci, D., Fuller, V., and D. Meyer, "LISP Alternative		[ALT] Farinacci, D., Fuller, V., and D. Meyer, "LISP Alternative
	Topology (LISP-ALT)", draft-ietf-lisp-alt-01.txt (work in		Topology (LISP-ALT)", draft-ietf-lisp-alt-01.txt (work in
	progress), May 2009.		progress), May 2009.
	[INTWORK] Lewis, D., Meyer, D., and D. Farinacci, "Interworking LISP		[INTWORK] Lewis, D., Meyer, D., and D. Farinacci, "Interworking LISP
	with IPv4 and IPv6", draft-ietf-lisp-interworking-00.txt		with IPv4 and IPv6", draft-ietf-lisp-interworking-00.txt
	(work in progress), May 2009.		(work in progress), May 2009.
	[LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,		[LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
	"Locator/ID Separation Protocol (LISP)",		"Locator/ID Separation Protocol (LISP)",
	draft-ietf-lisp-01.txt (work in progress), May 2009.		draft-ietf-lisp-05.txt (work in progress), September 2009.
	[MLISP] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas,		[MLISP] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas,
	"LISP for Multicast Environments",		"LISP for Multicast Environments",
	draft-farinacci-lisp-multicast-01.txt (work in progress),		draft-farinacci-lisp-multicast-01.txt (work in progress),
	November 2008.		November 2008.
	[MNAT] Wing, D. and T. Eckert, "Multicast Requirements for a		[MNAT] Wing, D. and T. Eckert, "Multicast Requirements for a
	Network Address (and port) Translator (NAT)",		Network Address (and port) Translator (NAT)",
	draft-ietf-behave-multicast-07.txt (work in progress),		draft-ietf-behave-multicast-07.txt (work in progress),
	June 2007.		June 2007.
	[MTRACE] Asaeda, H., Jinmei, T., Fenner, W., and S. Casner, "Mtrace		[MTRACE] Asaeda, H., Jinmei, T., Fenner, W., and S. Casner, "Mtrace
	Version 2: Traceroute Facility for IP Multicast",		Version 2: Traceroute Facility for IP Multicast",
	draft-ietf-mboned-mtrace-v2-03.txt (work in progress),		draft-ietf-mboned-mtrace-v2-03.txt (work in progress),
	March 2009.		March 2009.
	[RPFV] Wijnands, IJ., Boers, A., and E. Rosen, "The RPF Vector		[RPFV] Wijnands, IJ., Boers, A., and E. Rosen, "The RPF Vector
	TLV", draft-ietf-pim-rpf-vector-06.txt (work in progress),		TLV", draft-ietf-pim-rpf-vector-06.txt (work in progress),
	February 2008.		February 2008.
			Appendix A. Document Change Log
			A.1. Changes to draft-ietf-lisp-multicsat-02.txt
			o Posted September 2009.
			o Added Document Change Log appendix.
			o Specify that the LISP Encapsulated Control Message be used for
			unicasting PIM Join/Prune messages from ETRs to ITRs.
			A.2. Changes to draft-ietf-lisp-multicsat-01.txt
			o Posted November 2008.
			o Specified that PIM Join/Prune unicast messages that get sent from
			ETRs to ITRs of a source multicast site get LISP encapsulated in
			destination UDP port 4342.
			o Add multiple RLOCs per ITR per Yiqun's comments.
			o Indicate how static RPs can be used when LISP is run using Bidir-
			PIM in the core.
			o Editorial changes per Liming comments.
			o Add Mttrace Considersations section.
			A.3. Changes to draft-ietf-lisp-multicsat-00.txt
			o Posted April 2008.
			o Renamed from draft-farinacci-lisp-multicast-01.txt.
	Authors' Addresses		Authors' Addresses
	Dino Farinacci		Dino Farinacci
	cisco Systems		cisco Systems
	Tasman Drive		Tasman Drive
	San Jose, CA		San Jose, CA
	USA		USA
	Email: dino@cisco.com		Email: dino@cisco.com
End of changes. 8 change blocks.
	11 lines changed or deleted		49 lines changed or added
This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/