< draft-ietf-lisp-signal-free-mutlicast-05.txt		draft-ietf-lisp-signal-free-mutlicast-06.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: January 21, 2018 lispers.net		Expires: January 28, 2018 lispers.net
	July 20, 2017		July 27, 2017
	Signal-Free LISP Multicast		Signal-Free LISP Multicast
	draft-ietf-lisp-signal-free-multicast-05		draft-ietf-lisp-signal-free-multicast-06
	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 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 January 21, 2018.		This Internet-Draft will expire on January 28, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 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-05 . . . 21		A.1. Changes to draft-ietf-lisp-signal-free-multicast-06 . . . 21
	A.2. Changes to draft-ietf-lisp-signal-free-multicast-04 . . . 21		A.2. Changes to draft-ietf-lisp-signal-free-multicast-05 . . . 21
	A.3. Changes to draft-ietf-lisp-signal-free-multicast-03 . . . 21		A.3. Changes to draft-ietf-lisp-signal-free-multicast-04 . . . 21
	A.4. Changes to draft-ietf-lisp-signal-free-multicast-02 . . . 21		A.4. Changes to draft-ietf-lisp-signal-free-multicast-03 . . . 22
	A.5. Changes to draft-ietf-lisp-signal-free-multicast-01 . . . 22		A.5. Changes to draft-ietf-lisp-signal-free-multicast-02 . . . 22
	A.6. Changes to draft-ietf-lisp-signal-free-multicast-00 . . . 22		A.6. Changes to draft-ietf-lisp-signal-free-multicast-01 . . . 22
	A.7. Changes to draft-farinacci-lisp-signal-free-multicast-04 22		A.7. Changes to draft-ietf-lisp-signal-free-multicast-00 . . . 22
	A.8. Changes to draft-farinacci-lisp-signal-free-multicast-03 22		A.8. Changes to draft-farinacci-lisp-signal-free-multicast-04 22
	A.9. Changes to draft-farinacci-lisp-signal-free-multicast-02 22		A.9. Changes to draft-farinacci-lisp-signal-free-multicast-03 23
	A.10. Changes to draft-farinacci-lisp-signal-free-multicast-01 22		A.10. Changes to draft-farinacci-lisp-signal-free-multicast-02 23
	A.11. Changes to draft-farinacci-lisp-signal-free-multicast-00 23		A.11. Changes to draft-farinacci-lisp-signal-free-multicast-01 23
			A.12. 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.
	skipping to change at page 14, line 19 ¶		skipping to change at page 14, line 19 ¶
	replicate to RLOC1 if it is reachable. When the required p-bit is		replicate to RLOC1 if it is reachable. When the required p-bit is
	also set, the RLOC-reachability mechanisms from [RFC6830] are		also set, the RLOC-reachability mechanisms from [RFC6830] are
	followed. If the ITR determines that RLOC1 is unreachable, it uses		followed. If the ITR determines that RLOC1 is unreachable, it uses
	RLOC2, as long as RLOC2 is reachable.		RLOC2, as long as RLOC2 is reachable.
	6.4. Multicast RLOCs for an ETR at a Receiver-Site		6.4. Multicast RLOCs for an ETR at a Receiver-Site
	This specification is focused on underlays without multicast support,		This specification is focused on underlays without multicast support,
	but does not preclude the use of multicast RLOCs in RLE entries.		but does not preclude the use of multicast RLOCs in RLE entries.
	ETRs MAY register multicast EID entries using multicast RLOCs. In		ETRs MAY register multicast EID entries using multicast RLOCs. In
	such cases the ETRs will join underlay multicast trees following the		such cases the ETRs will get joined to underlay multicast
	procedures specified in [RFC6831].		distribution trees by using IGMP as a multicast host using mechanisms
			in [RFC2236] and [RFC3376].
	7. PIM Any Source Multicast Trees		7. PIM Any Source Multicast Trees
	LISP signal-free multicast can support ASM Trees in limited but		LISP signal-free multicast can support ASM Trees in limited but
	acceptable topologies. It is suggested for the simplification of		acceptable topologies. It is suggested for the simplification of
	building ASM trees across the LISP overlay to have PIM-ASM run		building ASM trees across the LISP overlay to have PIM-ASM run
	independently in each LISP site. What this means, is that a PIM		independently in each LISP site. What this means, is that a PIM
	Rendezvous Point (RP) is configured in each LISP site so PIM Register		Rendezvous Point (RP) is configured in each LISP site so PIM Register
	procedures and (*,G) state maintenance is contained within the LISP		procedures and (*,G) state maintenance is contained within the LISP
	site.		site.
	skipping to change at page 19, line 35 ¶		skipping to change at page 19, line 35 ¶
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	[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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
			[RFC2236] Fenner, W., "Internet Group Management Protocol, Version
			2", RFC 2236, DOI 10.17487/RFC2236, November 1997,
			<http://www.rfc-editor.org/info/rfc2236>.
			[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
			Thyagarajan, "Internet Group Management Protocol, Version
			3", RFC 3376, DOI 10.17487/RFC3376, October 2002,
			<http://www.rfc-editor.org/info/rfc3376>.
	[RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source		[RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source
	Discovery Protocol (MSDP)", RFC 3618,		Discovery Protocol (MSDP)", RFC 3618,
	DOI 10.17487/RFC3618, October 2003,		DOI 10.17487/RFC3618, October 2003,
	<http://www.rfc-editor.org/info/rfc3618>.		<http://www.rfc-editor.org/info/rfc3618>.
	[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,		Protocol Specification (Revised)", RFC 4601,
	DOI 10.17487/RFC4601, August 2006,		DOI 10.17487/RFC4601, August 2006,
	<http://www.rfc-editor.org/info/rfc4601>.		<http://www.rfc-editor.org/info/rfc4601>.
	skipping to change at page 21, line 12 ¶		skipping to change at page 21, line 21 ¶
	Address Format (LCAF)", RFC 8060, DOI 10.17487/RFC8060,		Address Format (LCAF)", RFC 8060, DOI 10.17487/RFC8060,
	February 2017, <http://www.rfc-editor.org/info/rfc8060>.		February 2017, <http://www.rfc-editor.org/info/rfc8060>.
	[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,
	<http://www.rfc-editor.org/info/rfc8061>.		<http://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-05		A.1. Changes to draft-ietf-lisp-signal-free-multicast-06
			o Posted July 2017.
			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
			of RFC6831 is performed and which parts should not be performed.
			In the case of signal-free-multicast, join the underlay trees as a
			multicast host by using IGMP.
			A.2. 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.2. Changes to draft-ietf-lisp-signal-free-multicast-04		A.3. 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.3. Changes to draft-ietf-lisp-signal-free-multicast-03		A.4. 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.4. Changes to draft-ietf-lisp-signal-free-multicast-02		A.5. 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.5. Changes to draft-ietf-lisp-signal-free-multicast-01		A.6. 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.6. Changes to draft-ietf-lisp-signal-free-multicast-00		A.7. 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.7. Changes to draft-farinacci-lisp-signal-free-multicast-04		A.8. 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.8. Changes to draft-farinacci-lisp-signal-free-multicast-03		A.9. 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.9. Changes to draft-farinacci-lisp-signal-free-multicast-02		A.10. 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.10. Changes to draft-farinacci-lisp-signal-free-multicast-01		A.11. 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.11. Changes to draft-farinacci-lisp-signal-free-multicast-00		A.12. 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. 17 change blocks.
	28 lines changed or deleted		49 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/