Routing for RPL Leaves
draft-ietf-roll-unaware-leaves-06

Document Type Active Internet-Draft (roll WG)
Last updated 2019-11-02
Replaces draft-thubert-roll-unaware-leaves
Stream IETF
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized bibtex
Stream WG state WG Document (wg milestone: Dec 2019 - Initial submission o... )
On Agenda roll at IETF-106
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
ROLL                                                     P. Thubert, Ed.
Internet-Draft                                             Cisco Systems
Updates: 6550, 8505 (if approved)                          M. Richardson
Intended status: Standards Track                               Sandelman
Expires: 5 May 2020                                      2 November 2019

                         Routing for RPL Leaves
                   draft-ietf-roll-unaware-leaves-06

Abstract

   This specification extends RFC6550 and RFC8505 to provide unicast and
   multicast routing services in a RPL domain to 6LNs that are plain
   hosts and do not participate to RPL.

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 5 May 2020.

Copyright Notice

   Copyright (c) 2019 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 & Richardson       Expires 5 May 2020                   [Page 1]
Internet-Draft             RPL Unaware Leaves              November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  BCP 14  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  References  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  6LoWPAN Neighbor Discovery  . . . . . . . . . . . . . . . . .   6
     3.1.  RFC 6775  . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  RFC 8505 Extended ARO . . . . . . . . . . . . . . . . . .   7
       3.2.1.  R Flag  . . . . . . . . . . . . . . . . . . . . . . .   8
       3.2.2.  TID, I Field and Opaque Fields  . . . . . . . . . . .   8
       3.2.3.  ROVR  . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.3.  RFC 8505 Extended DAR/DAC . . . . . . . . . . . . . . . .   9
   4.  Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . .   9
   5.  Updating RFC 8505 . . . . . . . . . . . . . . . . . . . . . .  10
   6.  6LN Requirements to be a RPL-Unware Leaf  . . . . . . . . . .  10
     6.1.  Support of 6LoWPAN ND . . . . . . . . . . . . . . . . . .  10
     6.2.  External Routes and RPL Artifacts . . . . . . . . . . . .  11
       6.2.1.  Support of the HbH Header . . . . . . . . . . . . . .  12
       6.2.2.  Support of the Routing Header . . . . . . . . . . . .  12
       6.2.3.  Support of IPv6 Encapsulation . . . . . . . . . . . .  12
   7.  Updated RPL Status  . . . . . . . . . . . . . . . . . . . . .  12
   8.  Updated RPL Target option . . . . . . . . . . . . . . . . . .  13
   9.  Protocol Operations for Unicast Addresses . . . . . . . . . .  14
     9.1.  General Flow  . . . . . . . . . . . . . . . . . . . . . .  14
       9.1.1.  In RPL Non-Storing-Mode . . . . . . . . . . . . . . .  15
       9.1.2.  In RPL Storing-Mode . . . . . . . . . . . . . . . . .  18
     9.2.  Operation . . . . . . . . . . . . . . . . . . . . . . . .  18
       9.2.1.  By the 6LN  . . . . . . . . . . . . . . . . . . . . .  19
       9.2.2.  By the 6LR  . . . . . . . . . . . . . . . . . . . . .  20
       9.2.3.  By the RPL Root . . . . . . . . . . . . . . . . . . .  22
       9.2.4.  By the 6LBR . . . . . . . . . . . . . . . . . . . . .  23
   10. Protocol Operations for Multicast Addresses . . . . . . . . .  23
   11. Implementation Status . . . . . . . . . . . . . . . . . . . .  25
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  25
   13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  26
     13.1.  RPL Target Option Flags  . . . . . . . . . . . . . . . .  26
     13.2.  New Subsubregistry for the RPL Non-Rejection Status
            values . . . . . . . . . . . . . . . . . . . . . . . . .  26
Show full document text