< draft-ietf-lisp-signal-free-multicast-07.txt		draft-ietf-lisp-signal-free-multicast-08.txt >
	Network Working Group V. Moreno		Network Working Group V. Moreno
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Experimental D. Farinacci		Intended status: Experimental D. Farinacci
	Expires: June 1, 2018 lispers.net		Expires: August 30, 2018 lispers.net
	November 28, 2017		February 26, 2018
	Signal-Free LISP Multicast		Signal-Free LISP Multicast
	draft-ietf-lisp-signal-free-multicast-07		draft-ietf-lisp-signal-free-multicast-08
	Abstract		Abstract
	When multicast sources and receivers are active at LISP sites, the		When multicast sources and receivers are active at LISP sites, the
	core network is required to use native multicast so packets can be		core network is required to use native multicast so packets can be
	delivered from sources to group members. When multicast is not		delivered from sources to group members. When multicast is not
	available to connect the multicast sites together, a signal-free		available to connect the multicast sites together, a signal-free
	mechanism can be used to allow traffic to flow between sites. The		mechanism can be used to allow traffic to flow between sites. The
	mechanism within here uses unicast replication and encapsulation over		mechanism within here uses unicast replication and encapsulation over
	the core network for the data-plane and uses the LISP mapping		the core network for the data-plane and uses the LISP mapping
	skipping to change at page 1, line 45 ¶		skipping to change at page 1, line 45 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 1, 2018.		This Internet-Draft will expire on August 30, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 2, line 51 ¶		skipping to change at page 2, line 51 ¶
	6.4. Multicast RLOCs for an ETR at a Receiver-Site . . . . . . 14		6.4. Multicast RLOCs for an ETR at a Receiver-Site . . . . . . 14
	7. PIM Any Source Multicast Trees . . . . . . . . . . . . . . . 14		7. PIM Any Source Multicast Trees . . . . . . . . . . . . . . . 14
	8. Signal-Free Multicast for Replication Engineering . . . . . . 15		8. Signal-Free Multicast for Replication Engineering . . . . . . 15
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 18		9. Security Considerations . . . . . . . . . . . . . . . . . . . 18
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19		11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 19		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
	12.1. Normative References . . . . . . . . . . . . . . . . . . 19		12.1. Normative References . . . . . . . . . . . . . . . . . . 19
	12.2. Informative References . . . . . . . . . . . . . . . . . 20		12.2. Informative References . . . . . . . . . . . . . . . . . 20
	Appendix A. Document Change Log . . . . . . . . . . . . . . . . 21		Appendix A. Document Change Log . . . . . . . . . . . . . . . . 21
	A.1. Changes to draft-ietf-lisp-signal-free-multicast-07 . . . 21		A.1. Changes to draft-ietf-lisp-signal-free-multicast-08 . . . 21
	A.2. Changes to draft-ietf-lisp-signal-free-multicast-06 . . . 21		A.2. Changes to draft-ietf-lisp-signal-free-multicast-07 . . . 21
	A.3. Changes to draft-ietf-lisp-signal-free-multicast-05 . . . 21		A.3. Changes to draft-ietf-lisp-signal-free-multicast-06 . . . 21
	A.4. Changes to draft-ietf-lisp-signal-free-multicast-04 . . . 21		A.4. Changes to draft-ietf-lisp-signal-free-multicast-05 . . . 21
	A.5. Changes to draft-ietf-lisp-signal-free-multicast-03 . . . 22		A.5. Changes to draft-ietf-lisp-signal-free-multicast-04 . . . 22
	A.6. Changes to draft-ietf-lisp-signal-free-multicast-02 . . . 22		A.6. Changes to draft-ietf-lisp-signal-free-multicast-03 . . . 22
	A.7. Changes to draft-ietf-lisp-signal-free-multicast-01 . . . 22		A.7. Changes to draft-ietf-lisp-signal-free-multicast-02 . . . 22
	A.8. Changes to draft-ietf-lisp-signal-free-multicast-00 . . . 22		A.8. Changes to draft-ietf-lisp-signal-free-multicast-01 . . . 22
	A.9. Changes to draft-farinacci-lisp-signal-free-multicast-04 22		A.9. Changes to draft-ietf-lisp-signal-free-multicast-00 . . . 22
	A.10. Changes to draft-farinacci-lisp-signal-free-multicast-03 23		A.10. Changes to draft-farinacci-lisp-signal-free-multicast-04 23
	A.11. Changes to draft-farinacci-lisp-signal-free-multicast-02 23		A.11. Changes to draft-farinacci-lisp-signal-free-multicast-03 23
	A.12. Changes to draft-farinacci-lisp-signal-free-multicast-01 23		A.12. Changes to draft-farinacci-lisp-signal-free-multicast-02 23
	A.13. Changes to draft-farinacci-lisp-signal-free-multicast-00 23		A.13. Changes to draft-farinacci-lisp-signal-free-multicast-01 23
			A.14. Changes to draft-farinacci-lisp-signal-free-multicast-00 23
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
	1. Introduction		1. Introduction
	When multicast sources and receivers are active at LISP sites, and		When multicast sources and receivers are active at LISP sites, and
	the core network between the sites does not provide multicast		the core network between the sites does not provide multicast
	support, a signal-free mechanism can be used to create an overlay		support, a signal-free mechanism can be used to create an overlay
	that will allow multicast traffic to flow between sites and connect		that will allow multicast traffic to flow between sites and connect
	the multicast trees at the different sites.		the multicast trees at the different sites.
	The signal-free mechanism here proposed does not extend PIM [RFC7761]		The signal-free mechanism proposed here does not extend PIM [RFC7761]
	over the overlay as proposed in [RFC6831], nor does the mechanism		over the overlay as proposed in [RFC6831], nor does the mechanism
	utilize direct signaling between the Receiver-ETRs and Sender-ITRs as		utilize direct signaling between the Receiver-ETRs and Sender-ITRs as
	described in [I-D.farinacci-lisp-mr-signaling]. The signal-free		described in [I-D.farinacci-lisp-mr-signaling]. The signal-free
	mechanism proposed reduces the amount of signaling required between		mechanism proposed reduces the amount of signaling required between
	sites to a minimum and is centered around the registration of		sites to a minimum and is centered around the registration of
	Receiver-sites for a particular multicast-group or multicast-channel		Receiver-sites for a particular multicast-group or multicast-channel
	with the LISP Mapping System.		with the LISP Mapping System.
	Registrations from the different receiver-sites will be merged at the		Registrations from the different receiver-sites will be merged at the
	Mapping System to assemble a multicast-replication-list inclusive of		Mapping System to assemble a multicast-replication-list inclusive of
	skipping to change at page 5, line 40 ¶		skipping to change at page 5, line 43 ¶
	sites replicate to the lowest (smaller value) level number RTRs in a		sites replicate to the lowest (smaller value) level number RTRs in a
	RLE entry. And then RTRs at a given level replicate to the next		RLE entry. And then RTRs at a given level replicate to the next
	higher level of RTRs. The number of RTRs at each level are		higher level of RTRs. The number of RTRs at each level are
	engineered to control the fan-out or replication factor so a tradeoff		engineered to control the fan-out or replication factor so a tradeoff
	between the width of the level versus the number of levels can be		between the width of the level versus the number of levels can be
	selected.		selected.
	ASM: Any-Source Multicast as defined in [RFC3569] and [RFC7761] where		ASM: Any-Source Multicast as defined in [RFC3569] and [RFC7761] where
	multicast distribution trees are built with a Rendezvous Point.		multicast distribution trees are built with a Rendezvous Point.
	SSM: Single-Source Multicast as defined in [RFC3569] where multicast		SSM: Source Specific Multicast as defined in [RFC3569] where
	distribution trees are built and rooted at the multicast router(s)		multicast distribution trees are built and rooted at the multicast
	directly connected to the multicast source.		router(s) directly connected to the multicast source.
	3. Reference Model		3. Reference Model
	The reference model that will be used for the discussion of the		The reference model that will be used for the discussion of the
	Signal-Free multicast tree interconnection is illustrated in		Signal-Free multicast tree interconnection is illustrated in
	Figure 1.		Figure 1.
	MS/MR		MS/MR
	+---+		+---+
	| |		| |
	skipping to change at page 15, line 5 ¶		skipping to change at page 15, line 5 ¶
	default route for the address-family) to the mapping system.		default route for the address-family) to the mapping system.
	3. In a Source-site, the RP is colocated with the ITR. RPs for		3. In a Source-site, the RP is colocated with the ITR. RPs for
	different groups can be spread across each ITR, but is not		different groups can be spread across each ITR, but is not
	required.		required.
	4. When a multicast source sends a packet, a PIM Register message is		4. When a multicast source sends a packet, a PIM Register message is
	delivered to the ITR and the procedures in Section 4.2 are		delivered to the ITR and the procedures in Section 4.2 are
	followed.		followed.
	5. When the the ITR sends a Map-Request for (S,G) and no Receiver-		5. When the ITR sends a Map-Request for (S,G) and no Receiver-site
	site has registered for (S,G), the mapping system will return the		has registered for (S,G), the mapping system will return the
	(0/0,G) entry to the ITR so it has a replication list of all the		(0/0,G) entry to the ITR so it has a replication list of all the
	ETRs that have received (*,G) state.		ETRs that have received (*,G) state.
	6. The ITR stores the replication-list in its map-cache for (S,G).		6. The ITR stores the replication-list in its map-cache for (S,G).
	It replicates packets to all ETRs in the list.		It replicates packets to all ETRs in the list.
	7. ETRs decapsulate packets and forward based on (*,G) state in		7. ETRs decapsulate packets and forward based on (*,G) state in
	their site.		their site.
	8. When last-hop PIM routers join the newly discovered (S,G), the		8. When last-hop PIM routers join the newly discovered (S,G), the
	skipping to change at page 21, line 17 ¶		skipping to change at page 21, line 17 ¶
	Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-14		Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-14
	(work in progress), October 2017.		(work in progress), October 2017.
	[RFC8061] Farinacci, D. and B. Weis, "Locator/ID Separation Protocol		[RFC8061] Farinacci, D. and B. Weis, "Locator/ID Separation Protocol
	(LISP) Data-Plane Confidentiality", RFC 8061,		(LISP) Data-Plane Confidentiality", RFC 8061,
	DOI 10.17487/RFC8061, February 2017,		DOI 10.17487/RFC8061, February 2017,
	<https://www.rfc-editor.org/info/rfc8061>.		<https://www.rfc-editor.org/info/rfc8061>.
	Appendix A. Document Change Log		Appendix A. Document Change Log
	A.1. Changes to draft-ietf-lisp-signal-free-multicast-07		A.1. Changes to draft-ietf-lisp-signal-free-multicast-08
			o Posted February 2018.
			o Fixed last call editorial comments.
			A.2. Changes to draft-ietf-lisp-signal-free-multicast-07
	o Posted November 2017.		o Posted November 2017.
	o Changes after shepherd review and RFC1918 terminology compliant.		o Changes after shepherd review and RFC1918 terminology compliant.
	A.2. Changes to draft-ietf-lisp-signal-free-multicast-06		A.3. Changes to draft-ietf-lisp-signal-free-multicast-06
	o Posted July 2017.		o Posted July 2017.
	o Stig made a comment about referencing RFC6831 when an RLOC is a		o Stig made a comment about referencing RFC6831 when an RLOC is a
	multicast address. It opens up a lot of assumptions on what parts		multicast address. It opens up a lot of assumptions on what parts
	of RFC6831 is performed and which parts should not be performed.		of RFC6831 is performed and which parts should not be performed.
	In the case of signal-free-multicast, join the underlay trees as a		In the case of signal-free-multicast, join the underlay trees as a
	multicast host by using IGMP.		multicast host by using IGMP.
	A.3. Changes to draft-ietf-lisp-signal-free-multicast-05		A.4. Changes to draft-ietf-lisp-signal-free-multicast-05
	o Posted July 2017.		o Posted July 2017.
	o Make it clear that when a RLE is sent by an ETR and it is already		o Make it clear that when a RLE is sent by an ETR and it is already
	in the merged RLE list on the Map-Server, that the Map-Server		in the merged RLE list on the Map-Server, that the Map-Server
	replaces the RLE entry (versus adding a duplicate RLE entry to the		replaces the RLE entry (versus adding a duplicate RLE entry to the
	list).		list).
	o Make it clear that an RLOC can be a unicast or multicast address.		o Make it clear that an RLOC can be a unicast or multicast address.
	Then make a reference to RFC6831 about mechanisms to support		Then make a reference to RFC6831 about mechanisms to support
	multicast RLOCs.		multicast RLOCs.
	o Fix some typos.		o Fix some typos.
	A.4. Changes to draft-ietf-lisp-signal-free-multicast-04		A.5. Changes to draft-ietf-lisp-signal-free-multicast-04
	o Posted May 2017.		o Posted May 2017.
	o Make it clear that recieiver-ETRs need configuraiton information		o Make it clear that recieiver-ETRs need configuraiton information
	for what Map-Servers (S,G) entries are registered to.		for what Map-Servers (S,G) entries are registered to.
	o Make it clear this document indicates what RTR layered hierarchy		o Make it clear this document indicates what RTR layered hierarchy
	to use and not if its the best hierarchy to use.		to use and not if its the best hierarchy to use.
	A.5. Changes to draft-ietf-lisp-signal-free-multicast-03		A.6. Changes to draft-ietf-lisp-signal-free-multicast-03
	o Posted April 2017.		o Posted April 2017.
	o Add "Multi-Homing Considerations" section to describe the case		o Add "Multi-Homing Considerations" section to describe the case
	where a source LISP site has multiple ITRs and the multicast		where a source LISP site has multiple ITRs and the multicast
	distribution tree at the source site branches to more than one		distribution tree at the source site branches to more than one
	ITR. And at receiver sites where there are multiple ETRs and		ITR. And at receiver sites where there are multiple ETRs and
	multiple RLOCs per ETR.		multiple RLOCs per ETR.
	A.6. Changes to draft-ietf-lisp-signal-free-multicast-02		A.7. Changes to draft-ietf-lisp-signal-free-multicast-02
	o Posted October 2016.		o Posted October 2016.
	o Updated document expiration timer.		o Updated document expiration timer.
	A.7. Changes to draft-ietf-lisp-signal-free-multicast-01		A.8. Changes to draft-ietf-lisp-signal-free-multicast-01
	o Posted April 2016.		o Posted April 2016.
	o Add text to define RTRs and indicate how RTR level number is used		o Add text to define RTRs and indicate how RTR level number is used
	for LISP-RE.		for LISP-RE.
	o Draw figure 2 that shows a LISP-RE topology.		o Draw figure 2 that shows a LISP-RE topology.
	o Indicate that PIM-ASM or (*,G) trees can be supported in LISP		o Indicate that PIM-ASM or (*,G) trees can be supported in LISP
	Signal-Free Multicast.		Signal-Free Multicast.
	A.8. Changes to draft-ietf-lisp-signal-free-multicast-00		A.9. Changes to draft-ietf-lisp-signal-free-multicast-00
	o Posted late December 2015.		o Posted late December 2015.
	o Converted draft-farinacci-lisp-signal-free-multicast-04 into LISP		o Converted draft-farinacci-lisp-signal-free-multicast-04 into LISP
	working group draft.		working group draft.
	A.9. Changes to draft-farinacci-lisp-signal-free-multicast-04		A.10. Changes to draft-farinacci-lisp-signal-free-multicast-04
	o Posted early December 2015.		o Posted early December 2015.
	o Update references and document timer.		o Update references and document timer.
	A.10. Changes to draft-farinacci-lisp-signal-free-multicast-03		A.11. Changes to draft-farinacci-lisp-signal-free-multicast-03
	o Posted June 2015.		o Posted June 2015.
	o Update references and document timer.		o Update references and document timer.
	A.11. Changes to draft-farinacci-lisp-signal-free-multicast-02		A.12. Changes to draft-farinacci-lisp-signal-free-multicast-02
	o Posted December 2014.		o Posted December 2014.
	o Added section about how LISP-RE can use the mechanisms from		o Added section about how LISP-RE can use the mechanisms from
	signal-free-multicast so we can avoid head-end replication and		signal-free-multicast so we can avoid head-end replication and
	avoid signalling across a layered RE topology.		avoid signalling across a layered RE topology.
	A.12. Changes to draft-farinacci-lisp-signal-free-multicast-01		A.13. Changes to draft-farinacci-lisp-signal-free-multicast-01
	o Posted June 2014.		o Posted June 2014.
	o Changes based on implementation experience of this draft.		o Changes based on implementation experience of this draft.
	A.13. Changes to draft-farinacci-lisp-signal-free-multicast-00		A.14. Changes to draft-farinacci-lisp-signal-free-multicast-00
	o Posted initial draft February 2014.		o Posted initial draft February 2014.
	Authors' Addresses		Authors' Addresses
	Victor Moreno		Victor Moreno
	Cisco Systems		Cisco Systems
	170 Tasman Drive		170 Tasman Drive
	San Jose, California 95134		San Jose, California 95134
	USA		USA
End of changes. 21 change blocks.
	37 lines changed or deleted		44 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/