< draft-ietf-roll-efficient-npdao-01.txt		draft-ietf-roll-efficient-npdao-02.txt >
	ROLL R. Jadhav, Ed.		ROLL R. Jadhav, Ed.
	Internet-Draft R. Sahoo		Internet-Draft Huawei
	Intended status: Standards Track Z. Cao		Intended status: Standards Track P. Thubert
	Expires: April 20, 2018 Huawei Tech		Expires: September 22, 2018 Cisco
	October 17, 2017		R. Sahoo
			Z. Cao
			Huawei
			March 21, 2018
	No-Path DAO modifications		No-Path DAO modifications
	draft-ietf-roll-efficient-npdao-01		draft-ietf-roll-efficient-npdao-02
	Abstract		Abstract
	This document describes the problems associated with the use of No-		This document describes the problems associated with the use of No-
	Path DAO messaging in RPL and a signaling changes to improve route		Path DAO messaging in RPL and a signaling changes to improve route
	invalidation efficiency.		invalidation efficiency.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 36 ¶
	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 April 20, 2018.		This Internet-Draft will expire on September 22, 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 24 ¶		skipping to change at page 2, line 26 ¶
	2.2. Invalidate routes to dependent nodes of the switching		2.2. Invalidate routes to dependent nodes of the switching
	node . . . . . . . . . . . . . . . . . . . . . . . . . . 5		node . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	2.3. Route downtime caused by asynchronous operation of		2.3. Route downtime caused by asynchronous operation of
	NPDAO and DAO . . . . . . . . . . . . . . . . . . . . . . 6		NPDAO and DAO . . . . . . . . . . . . . . . . . . . . . . 6
	3. Requirements for the No-Path DAO Optimization . . . . . . . . 6		3. Requirements for the No-Path DAO Optimization . . . . . . . . 6
	3.1. Req#1: Tolerant to the link failures to the previous		3.1. Req#1: Tolerant to the link failures to the previous
	parents . . . . . . . . . . . . . . . . . . . . . . . . . 6		parents . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.2. Req#2: Dependent nodes route invalidation on parent		3.2. Req#2: Dependent nodes route invalidation on parent
	switching . . . . . . . . . . . . . . . . . . . . . . . . 6		switching . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.3. Req#3: No impact on traffic while NP-DAO operation in		3.3. Req#3: No impact on traffic while NP-DAO operation in
	progress . . . . . . . . . . . . . . . . . . . . . . . . 6		progress . . . . . . . . . . . . . . . . . . . . . . . . 7
	4. Proposed changes to RPL signaling . . . . . . . . . . . . . . 7		4. Proposed changes to RPL signaling . . . . . . . . . . . . . . 7
	4.1. Change in NPDAO semantics . . . . . . . . . . . . . . . . 7		4.1. Change in NPDAO semantics . . . . . . . . . . . . . . . . 7
	4.2. DAO message format changes . . . . . . . . . . . . . . . 7		4.2. DAO message format changes . . . . . . . . . . . . . . . 7
	4.3. Destination Cleanup Object (DCO) . . . . . . . . . . . . 8		4.3. Destination Cleanup Object (DCO) . . . . . . . . . . . . 8
	4.3.1. DCO Options . . . . . . . . . . . . . . . . . . . . . 10		4.3.1. DCO Options . . . . . . . . . . . . . . . . . . . . . 10
	4.3.2. Path Sequence number in the DCO . . . . . . . . . . . 10		4.3.2. Path Sequence number in the DCO . . . . . . . . . . . 10
	4.3.3. Destination Cleanup Option Acknowledgement (DCO-ACK) 10		4.3.3. Destination Cleanup Option Acknowledgement (DCO-ACK) 10
	4.4. Example messaging . . . . . . . . . . . . . . . . . . . . 11		4.4. Example messaging . . . . . . . . . . . . . . . . . . . . 11
	4.5. Other considerations . . . . . . . . . . . . . . . . . . 12		4.5. Other considerations . . . . . . . . . . . . . . . . . . 12
	4.5.1. Dependent Nodes invalidation . . . . . . . . . . . . 12		4.5.1. Dependent Nodes invalidation . . . . . . . . . . . . 12
	skipping to change at page 13, line 38 ¶		skipping to change at page 13, line 38 ¶
	The secure versions of DCO and DCO-ACK also have to be considered in		The secure versions of DCO and DCO-ACK also have to be considered in
	the future. The seucrity considerations applicable to DAO, DAO-ACK		the future. The seucrity considerations applicable to DAO, DAO-ACK
	messaging in RPL is also applicable here.		messaging in RPL is also applicable here.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-6tisch-architecture]		[I-D.ietf-6tisch-architecture]
	Thubert, P., "An Architecture for IPv6 over the TSCH mode		Thubert, P., "An Architecture for IPv6 over the TSCH mode
	of IEEE 802.15.4", draft-ietf-6tisch-architecture-12 (work		of IEEE 802.15.4", draft-ietf-6tisch-architecture-13 (work
	in progress), August 2017.		in progress), November 2017.
	[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,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,		[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
	Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,		Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
	JP., and R. Alexander, "RPL: IPv6 Routing Protocol for		JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
	Low-Power and Lossy Networks", RFC 6550,		Low-Power and Lossy Networks", RFC 6550,
	skipping to change at page 14, line 22 ¶		skipping to change at page 14, line 22 ¶
	DOI 10.17487/RFC3552, July 2003,		DOI 10.17487/RFC3552, July 2003,
	<https://www.rfc-editor.org/info/rfc3552>.		<https://www.rfc-editor.org/info/rfc3552>.
	Appendix A. Additional Stuff		Appendix A. Additional Stuff
	This becomes an Appendix.		This becomes an Appendix.
	Authors' Addresses		Authors' Addresses
	Rahul Arvind Jadhav (editor)		Rahul Arvind Jadhav (editor)
	Huawei Tech		Huawei
	Kundalahalli Village, Whitefield,		Kundalahalli Village, Whitefield,
	Bangalore, Karnataka 560037		Bangalore, Karnataka 560037
	India		India
	Phone: +91-080-49160700		Phone: +91-080-49160700
	Email: rahul.ietf@gmail.com		Email: rahul.ietf@gmail.com
			Pascal Thubert
			Cisco Systems, Inc
			Building D
			45 Allee des Ormes - BP1200
			MOUGINS - Sophia Antipolis 06254
			FRANCE
			Phone: +33 497 23 26 34
			Email: pthubert@cisco.com
	Rabi Narayan Sahoo		Rabi Narayan Sahoo
	Huawei Tech		Huawei
	Kundalahalli Village, Whitefield,		Kundalahalli Village, Whitefield,
	Bangalore, Karnataka 560037		Bangalore, Karnataka 560037
	India		India
	Phone: +91-080-49160700		Phone: +91-080-49160700
	Email: rabinarayans@huawei.com		Email: rabinarayans@huawei.com
	Zhen Cao		Zhen Cao
	Huawei Tech		Huawei
	W Chang'an Ave		W Chang'an Ave
	Beijing 560037		Beijing 560037
	China		China
	Email: zhencao.ietf@gmail.com		Email: zhencao.ietf@gmail.com
End of changes. 11 change blocks.
	14 lines changed or deleted		26 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/