draft-ietf-roll-trickle-mcast-08.txt		draft-ietf-roll-trickle-mcast-09.txt
	ROLL J. Hui		ROLL J. Hui
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track R. Kelsey		Intended status: Standards Track R. Kelsey
	Expires: September 29, 2014 Silicon Labs		Expires: October 16, 2014 Silicon Labs
	March 28, 2014		April 14, 2014
	Multicast Protocol for Low power and Lossy Networks (MPL)		Multicast Protocol for Low power and Lossy Networks (MPL)
	draft-ietf-roll-trickle-mcast-08		draft-ietf-roll-trickle-mcast-09
	Abstract		Abstract
	This document specifies the Multicast Protocol for Low power and		This document specifies the Multicast Protocol for Low power and
	Lossy Networks (MPL) that provides IPv6 multicast forwarding in		Lossy Networks (MPL) that provides IPv6 multicast forwarding in
	constrained networks. MPL avoids the need to construct or maintain		constrained networks. MPL avoids the need to construct or maintain
	any multicast forwarding topology, disseminating messages to all MPL		any multicast forwarding topology, disseminating messages to all MPL
	Forwarders in an MPL Domain. MPL uses the Trickle algorithm to		Forwarders in an MPL Domain. MPL uses the Trickle algorithm to
	manage message transmissions for both control and data-plane		manage message transmissions for both control and data-plane
	messages. Different Trickle parameter configurations allow MPL to		messages. Different Trickle parameter configurations allow MPL to
	skipping to change at page 1, line 38		skipping to change at page 1, line 38
	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 September 29, 2014.		This Internet-Draft will expire on October 16, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 10, line 50		skipping to change at page 10, line 50
	CONTROL_MESSAGE_K The redundancy constant, as defined in [RFC6206],		CONTROL_MESSAGE_K The redundancy constant, as defined in [RFC6206],
	for MPL Control Message transmissions. CONTROL_MESSAGE_K has a		for MPL Control Message transmissions. CONTROL_MESSAGE_K has a
	default value of 1.		default value of 1.
	CONTROL_MESSAGE_TIMER_EXPIRATIONS The number of Trickle timer		CONTROL_MESSAGE_TIMER_EXPIRATIONS The number of Trickle timer
	expirations that occur before terminating the Trickle algorithm		expirations that occur before terminating the Trickle algorithm
	for MPL Control Message transmissions.		for MPL Control Message transmissions.
	CONTROL_MESSAGE_TIMER_EXPIRATIONS has a default value of 10.		CONTROL_MESSAGE_TIMER_EXPIRATIONS has a default value of 10.
	Following [RFC6206], it is RECOMMENDED that all MPL Interfaces		As described in [RFC6206], if different nodes have different
	attached to the same link of a given MPL Domain use the same values		configuration parameters, Trickle may have unintended behaviors.
	for the Trickle Parameters above for a given MPL Domain. The
	mechanism for setting the Trickle Parameters is not specified within		Therefore, it is RECOMMENDED that all MPL Interfaces attached to the
	this document.		same link of a given MPL Domain use the same values for the Trickle
			Parameters above for a given MPL Domain. The mechanism for setting
			the Trickle Parameters is not specified within this document.
	The default MPL parameters specify a forwarding strategy that		The default MPL parameters specify a forwarding strategy that
	utilizes both proactive and reactive techniques. Using these default		utilizes both proactive and reactive techniques. Using these default
	values, an MPL Forwarder proactively transmits any new MPL Data		values, an MPL Forwarder proactively transmits any new MPL Data
	Messages it receives then uses MPL Control Messages to trigger		Messages it receives then uses MPL Control Messages to trigger
	additional MPL Data Message retransmissions where message drops are		additional MPL Data Message retransmissions where message drops are
	detected. Setting DATA_MESSAGE_IMAX to the same as DATA_MESSAGE_IMIN		detected. Setting DATA_MESSAGE_IMAX to the same as DATA_MESSAGE_IMIN
	in this case is acceptable since subsequent MPL Data Message		in this case is acceptable since subsequent MPL Data Message
	retransmissions are triggered by MPL Control Messages, where		retransmissions are triggered by MPL Control Messages, where
	CONTROL_MESSAGE_IMAX is greater than CONTROL_MESSAGE_IMIN.		CONTROL_MESSAGE_IMAX is greater than CONTROL_MESSAGE_IMIN.
	skipping to change at page 23, line 32		skipping to change at page 23, line 32
	MPL uses the Trickle algorithm to manage message transmissions and		MPL uses the Trickle algorithm to manage message transmissions and
	the security considerations described in [RFC6206] apply.		the security considerations described in [RFC6206] apply.
	14. References		14. References
	14.1. Normative References		14.1. Normative References
	[I-D.ietf-6man-multicast-scopes]		[I-D.ietf-6man-multicast-scopes]
	Droms, R., "IPv6 Multicast Address Scopes", draft-ietf-		Droms, R., "IPv6 Multicast Address Scopes", draft-ietf-
	6man-multicast-scopes-03 (work in progress), February		6man-multicast-scopes-04 (work in progress), March 2014.
	2014.
	[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,		[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,
	August 1996.		August 1996.
	[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.
	[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6		[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
	(IPv6) Specification", RFC 2460, December 1998.		(IPv6) Specification", RFC 2460, December 1998.
End of changes. 5 change blocks.
	11 lines changed or deleted		12 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/