Observations on RPL: IPv6 Routing Protocol for Low power and Lossy Networks
draft-clausen-lln-rpl-experiences-11

Document Type Active Internet-Draft (individual)
Last updated 2018-05-15 (latest revision 2018-03-27)
Stream ISE
Intended RFC status Informational
Formats plain text pdf html bibtex
IETF conflict review conflict-review-clausen-lln-rpl-experiences
Stream ISE state In IESG Review
Consensus Boilerplate Unknown
Document shepherd Nevil Brownlee
Shepherd write-up Show (last changed 2018-05-13)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Nevil Brownlee <n.brownlee@auckland.ac.nz>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Network Working Group                                         T. Clausen
Internet-Draft                                      A. Colin de Verdiere
Intended status: Informational
Expires: September 28, 2018                                        J. Yi
                                                     Ecole Polytechnique
                                                              U. Herberg

                                                             Y. Igarashi
                                        Hitachi, Ltd., Yokohama Research
                                                              Laboratory
                                                          March 27, 2018

   Observations on RPL: IPv6 Routing Protocol for Low power and Lossy
                                Networks
                  draft-clausen-lln-rpl-experiences-11

Abstract

   With RPL - the "IPv6 Routing Protocol for Low-power Lossy Networks" -
   published as a Proposed Standard after a ~2-year development cycle,
   this document presents an observation of the resulting protocol, of
   its applicability, and of its limits.  The documents presents a
   selection of observations on the protocol characteristics, exposes
   experiences acquired when producing various prototype implementations
   of RPL, and presents results obtained from testing this protocol - by
   way of network simulations, in network testbeds and in deployments.
   The document aims at providing a better understanding of possible
   limits of RPL, notably the possible directions that further protocol
   developments should explore, in order to address these.

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 September 28, 2018.

Clausen, et al.        Expires September 28, 2018               [Page 1]
Internet-Draft             Observations on RPL                March 2018

Copyright Notice

   Copyright (c) 2018 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.

Clausen, et al.        Expires September 28, 2018               [Page 2]
Internet-Draft             Observations on RPL                March 2018

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  RPL Overview . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  RPL Message Emission Timing - Trickle Timers . . . . . . .  7
   4.  Requirement Of DODAG Root  . . . . . . . . . . . . . . . . . .  8
     4.1.  Observations . . . . . . . . . . . . . . . . . . . . . . .  8
   5.  RPL Data Traffic Flows . . . . . . . . . . . . . . . . . . . .  9
     5.1.  Observations . . . . . . . . . . . . . . . . . . . . . . . 10
   6.  Fragmentation Of RPL Control Messages And Data Packet  . . . . 12
     6.1.  Observations . . . . . . . . . . . . . . . . . . . . . . . 13
   7.  The DAO Mechanism: Downward and Point-to-Point Routes  . . . . 15
     7.1.  Observations . . . . . . . . . . . . . . . . . . . . . . . 15
   8.  Address Aggregation and Summarization  . . . . . . . . . . . . 17
     8.1.  Observations . . . . . . . . . . . . . . . . . . . . . . . 18
   9.  Link Bidirectionality Verification . . . . . . . . . . . . . . 19
     9.1.  Observations . . . . . . . . . . . . . . . . . . . . . . . 19
   10. Neighbor Unreachability Detection For Unidirectional Links . . 20
     10.1. Observations . . . . . . . . . . . . . . . . . . . . . . . 21
   11. RPL Implementability and Complexity  . . . . . . . . . . . . . 22
     11.1. Observations . . . . . . . . . . . . . . . . . . . . . . . 23
   12. Underspecification . . . . . . . . . . . . . . . . . . . . . . 23
     12.1. Observations . . . . . . . . . . . . . . . . . . . . . . . 23
Show full document text