Routing for RPL Leaves
draft-thubert-roll-unaware-leaves-04

Document Type Active Internet-Draft (individual)
Last updated 2018-03-19
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                                                     P. Thubert, Ed.
Internet-Draft                                                     Cisco
Updates: 6550, 6775 (if approved)                         March 18, 2018
Intended status: Standards Track
Expires: September 19, 2018

                         Routing for RPL Leaves
                  draft-thubert-roll-unaware-leaves-04

Abstract

   This specification updates RFC 6550 and RFC 6775 unicast routing
   service in a RPL domain to 6LoWPAN ND nodes that do not participate
   to the routing protocol.

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 https://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 19, 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
   (https://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.

Thubert                Expires September 19, 2018               [Page 1]
Internet-Draft           Routing for RPL Leaves               March 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Updating RFC 6775 Update  . . . . . . . . . . . . . . . . . .   5
   5.  Dependencies on 6LN . . . . . . . . . . . . . . . . . . . . .   5
   6.  Protocol Operations . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  General Flow  . . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  6LN Operation . . . . . . . . . . . . . . . . . . . . . .   8
     6.3.  6LR Operation . . . . . . . . . . . . . . . . . . . . . .   9
     6.4.  RPL Root Operation  . . . . . . . . . . . . . . . . . . .  10
     6.5.  6LBR Operation  . . . . . . . . . . . . . . . . . . . . .  11
   7.  Implementation Status . . . . . . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     11.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Appendix A.  Subset of a 6LoWPAN Glossary . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The design of Low Power and Lossy Networks (LLNs) is generally
   focused on saving energy, which is the most constrained resource of
   all.  Other design constraints, such as a limited memory capacity,
   duty cycling of the LLN devices and low-power lossy transmissions,
   derive from that primary concern.

   The IETF produced the "Routing Protocol for Low Power and Lossy
   Networks" [RFC6550] (RPL) to provide routing services within such
   constraints.  RPL is a Distance-Vector protocol, which, compared to
   link-state protocols, limits the amount of topological knowledge that
   needs to be installed and maintained in each node.  In order to
   operate in constrained networks, RPL allows a Routing Stretch (see
   [RFC6687]), whereby routing is only performed along a DODAG as
   opposed to straight along a shortest path between 2 peers, whatever
   that would mean in a given LLN.  This trades the quality of peer-to-
   peer (P2P) paths for a vastly reduced amount of control traffic and
   routing state that would be required to operate a any-to-any shortest
   path protocol.  Finally, broken routes may be fixed lazily and on-
   demand, based on dataplane inconsistency discovery, which avoids
   wasting energy in the proactive repair of unused paths.

   In order to cope with lossy transmissions, RPL forms Direction-
   Oriented Directed Acyclic Graphs (DODAGs) using DODAG Information
Show full document text