rfc7287v2.txt		rfc7287.txt
	skipping to change at page 2, line 49		skipping to change at page 3, line 5
	4.3.6. Handover Optimizations for PIM . . . . . . . . . . . 17		4.3.6. Handover Optimizations for PIM . . . . . . . . . . . 17
	4.4. BIDIR-PIM . . . . . . . . . . . . . . . . . . . . . . . . 17		4.4. BIDIR-PIM . . . . . . . . . . . . . . . . . . . . . . . . 17
	4.4.1. Routing Information Base for BIDIR-PIM . . . . . . . 18		4.4.1. Routing Information Base for BIDIR-PIM . . . . . . . 18
	4.4.2. Operations of BIDIR-PIM . . . . . . . . . . . . . . . 18		4.4.2. Operations of BIDIR-PIM . . . . . . . . . . . . . . . 18
	5. MLD Proxy Peering Function for Optimized Source Mobility in		5. MLD Proxy Peering Function for Optimized Source Mobility in
	PMIPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . 18		PMIPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
	5.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 19		5.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 19
	5.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 19		5.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 19
	5.3. Operations in Support of Multicast Senders . . . . . . . 19		5.3. Operations in Support of Multicast Senders . . . . . . . 19
	5.4. Operations in Support of Multicast Listeners . . . . . . 20		5.4. Operations in Support of Multicast Listeners . . . . . . 20
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 21		6. Security Considerations . . . . . . . . . . . . . . . . . . . 22
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
	8.1. Normative References . . . . . . . . . . . . . . . . . . 23		8.1. Normative References . . . . . . . . . . . . . . . . . . 23
	8.2. Informative References . . . . . . . . . . . . . . . . . 23		8.2. Informative References . . . . . . . . . . . . . . . . . 23
	Appendix A. Multiple Upstream Interface Proxy . . . . . . . . . 25		Appendix A. Multiple Upstream Interface Proxy . . . . . . . . . 25
	A.1. Operations for Local Multicast Sources . . . . . . . . . 25		A.1. Operations for Local Multicast Sources . . . . . . . . . 25
	A.2. Operations for Local Multicast Subscribers . . . . . . . 25		A.2. Operations for Local Multicast Subscribers . . . . . . . 25
	Appendix B. Implementation . . . . . . . . . . . . . . . . . . . 26		Appendix B. Implementation . . . . . . . . . . . . . . . . . . . 26
	1. Introduction		1. Introduction
	Proxy Mobile IPv6 (PMIPv6) [RFC5213] extends Mobile IPv6 (MIPv6)		Proxy Mobile IPv6 (PMIPv6) [RFC5213] extends Mobile IPv6 (MIPv6)
	skipping to change at page 21, line 5		skipping to change at page 21, line 5
	at most one (virtual) hop. Whenever certain group traffic (SSM		at most one (virtual) hop. Whenever certain group traffic (SSM
	channels) does not arrive from the peerings after a waiting time		channels) does not arrive from the peerings after a waiting time
	(default: 10 ms (node-local) and 25 ms (remote)), additional reports		(default: 10 ms (node-local) and 25 ms (remote)), additional reports
	(complementary reports, in the case of SSM) are sent to the standard		(complementary reports, in the case of SSM) are sent to the standard
	upstream interface.		upstream interface.
	Whenever traffic from a peering link arrives, an MLD proxy MUST		Whenever traffic from a peering link arrives, an MLD proxy MUST
	install source filters at its upstream interfaces (as described in		install source filters at its upstream interfaces (as described in
	RFC 4605) in the following way.		RFC 4605) in the following way.
	ASM with IGMPv2/MLDv1 In the presence of ASM using IGMPv2/MLDv1,		ASM with IGMPv2/MLDv1: In the presence of ASM using IGMPv2/MLDv1,
	only, the proxy cannot signal source filtering to its upstream.		only, the proxy cannot signal source filtering to its upstream.
	Correspondingly, it applies (S,*) ingress filters at its upstream		Correspondingly, it applies (S,*) ingress filters at its upstream
	interface for all sources S seen in traffic on the peering links.		interface for all sources S seen in traffic on the peering links.
	It is noteworthy that unwanted traffic is still replicated to the		It is noteworthy that unwanted traffic is still replicated to the
	proxy via the (wired) provider backbone, but it is not forwarded		proxy via the (wired) provider backbone, but it is not forwarded
	into the wireless access network.		into the wireless access network.
	ASM with IGMPv3/MLDv2 In the presence of source-specific signaling		ASM with IGMPv3/MLDv2: In the presence of source-specific signaling
	(IGMPv3/MLDv2), the upstream interface is set to (S,*) exclude		(IGMPv3/MLDv2), the upstream interface is set to (S,*) exclude
	mode for all sources S seen in traffic of the peering links. The		mode for all sources S seen in traffic of the peering links. The
	corresponding source-specific signaling will prevent forwarding of		corresponding source-specific signaling will prevent forwarding of
	duplicate traffic throughout the access network.		duplicate traffic throughout the access network.
	SSM In the presence of Source-Specific Multicast, the proxy will		SSM: In the presence of Source-Specific Multicast, the proxy will
	subscribe on its uplink interface to those (S,G) channels, only,		subscribe on its uplink interface to those (S,G) channels, only,
	that do not arrive via the peering links.		that do not arrive via the peering links.
	MLD proxies will install data-driven timers (source-timeout) for each		MLD proxies will install data-driven timers (source-timeout) for each
	source but common to all peering interfaces to detect interruptions		source but common to all peering interfaces to detect interruptions
	of data services from individual sources at proxy peers. Termination		of data services from individual sources at proxy peers. Termination
	of source-specific flows may be application specific, but also may be		of source-specific flows may be application specific, but also may be
	due to a source handover or a transmission failure. After a		due to a source handover or a transmission failure. After a
	handover, a mobile source may reattach at another MLD proxy with a		handover, a mobile source may reattach at another MLD proxy with a
	peering relation to the listener, or at a proxy that does not peer.		peering relation to the listener, or at a proxy that does not peer.
	skipping to change at page 23, line 45		skipping to change at page 23, line 48
	[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy		[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
	Mobile IPv6", RFC 5844, May 2010.		Mobile IPv6", RFC 5844, May 2010.
	[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support		[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support
	in IPv6", RFC 6275, July 2011.		in IPv6", RFC 6275, July 2011.
	8.2. Informative References		8.2. Informative References
	[MULTI-EXT]		[MULTI-EXT]
	Schmidt, T., Waehlisch, M., Koodli, R., Fairhurst, G., and		Schmidt, T., Ed., Waehlisch, M., Koodli, R., Fairhurst,
	D. Liu, "Multicast Listener Extensions for MIPv6 and		G., and D. Liu, "Multicast Listener Extensions for MIPv6
	PMIPv6 Fast Handovers", Work in Progress, March 2014.		and PMIPv6 Fast Handovers", Work in Progress, May 2014.
	[PEERING-ANALYSIS]		[PEERING-ANALYSIS]
	Schmidt, TC., Woelke, S., and M. Waehlisch, "Peer my Proxy		Schmidt, TC., Woelke, S., and M. Waehlisch, "Peer my Proxy
	- A Performance Study of Peering Extensions for Multicast		- A Performance Study of Peering Extensions for Multicast
	in Proxy Mobile IP Domains", Proc. of 7th IFIP Wireless		in Proxy Mobile IP Domains", Proc. of 7th IFIP Wireless
	and Mobile Networking Conference (WMNC 2014), IEEE Press,		and Mobile Networking Conference (WMNC 2014), IEEE Press,
	May 2014.		May 2014.
	[RFC2236] Fenner, W., "Internet Group Management Protocol, Version		[RFC2236] Fenner, W., "Internet Group Management Protocol, Version
	2", RFC 2236, November 1997.		2", RFC 2236, November 1997.
End of changes. 6 change blocks.
	8 lines changed or deleted		8 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/