No-Path DAO modifications
draft-jadhav-roll-efficient-npdao-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-05-13
|
|
Replaces |
|
draft-jadhav-roll-no-path-dao-ps
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
ROLL R. Jadhav, Ed.
Internet-Draft R. Sahoo
Intended status: Standards Track Z. Cao
Expires: November 13, 2017 Huawei Tech
May 12, 2017
No-Path DAO modifications
draft-jadhav-roll-efficient-npdao-01
Abstract
This document describes the problems associated with the use of No-
Path DAO messaging in RPL and a signaling changes to improve route
invalidation efficiency.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 13, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Jadhav, et al. Expires November 13, 2017 [Page 1]
Internet-Draft No-Path DAO modifications May 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language and Terminology . . . . . . . . . . 3
1.2. Current No-Path DAO messaging . . . . . . . . . . . . . . 3
1.3. Cases when No-Path DAO may be used . . . . . . . . . . . 4
1.4. Why No-Path DAO is important? . . . . . . . . . . . . . . 5
2. Problems with current No-Path DAO messaging . . . . . . . . 5
2.1. Lost NP-DAO due to link break to the previous parent . . 5
2.2. Invalidate routes to dependent nodes of the switching
node . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Route downtime caused by asynchronous operation of
NPDAO and DAO . . . . . . . . . . . . . . . . . . . . . . 6
3. Requirements for the No-Path DAO Optimization . . . . . . . . 6
3.1. Req#1: Tolerant to the link failures to the previous
parents . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Req#2: Dependent nodes route invalidation on parent
switching . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Req#3: No impact on traffic while NP-DAO operation in
progress . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Proposed changes to NPDAO signaling . . . . . . . . . . . . . 7
4.1. Change in NPDAO semantics . . . . . . . . . . . . . . . . 7
4.2. DAO message format changes . . . . . . . . . . . . . . . 7
4.2.1. Path Sequence number in the reverse NPDAO . . . . . . 9
4.3. Example messaging . . . . . . . . . . . . . . . . . . . . 9
4.4. Other considerations . . . . . . . . . . . . . . . . . . 10
4.4.1. Dependent Nodes invalidation . . . . . . . . . . . . 10
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
RPL [RFC6550] specifies a proactive distance-vector based routing
scheme. The specification has an optional messaging in the form of
DAO messages using which the 6LBR can learn route towards any of the
Show full document text