No-Path DAO modifications
draft-jadhav-roll-efficient-npdao-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-15 (latest revision 2017-02-14)
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: August 18, 2017                                     Huawei Tech
                                                       February 14, 2017

                       No-Path DAO modifications
                  draft-jadhav-roll-efficient-npdao-00

Abstract

   This document describes the problems associated with the use of No-
   Path DAO messaging in RPL and a signaling improvement 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 August 18, 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 August 18, 2017                [Page 1]
Internet-Draft          No-Path DAO modifications          February 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  . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Existing Solution . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  NP-DAO can be generated by the parent node who detects
           link failure to the child . . . . . . . . . . . . . . . .   7
     4.2.  NP-DAO can be generated once the link is restored to
           the previous parent . . . . . . . . . . . . . . . . . . .   8
   5.  Proposed changes to NPDAO signaling . . . . . . . . . . . . .   8
     5.1.  Change in NPDAO semantics . . . . . . . . . . . . . . . .   8
     5.2.  DAO message format changes  . . . . . . . . . . . . . . .   9
       5.2.1.  Path Sequence number in the reverse NPDAO . . . . . .  11
     5.3.  Example messaging . . . . . . . . . . . . . . . . . . . .  11
     5.4.  Other considerations  . . . . . . . . . . . . . . . . . .  12
       5.4.1.  Dependent Nodes invalidation  . . . . . . . . . . . .  12
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Additional Stuff . . . . . . . . . . . . . . . . . .  14
Show full document text