RPL Capabilities
draft-ietf-roll-capabilities-00

Document Type Active Internet-Draft (roll WG)
Last updated 2020-02-11
Replaces draft-ietf-roll-mopex-cap
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ROLL                                                      R. Jadhav, Ed.
Internet-Draft                                               Huawei Tech
Intended status: Standards Track                              P. Thubert
Expires: August 13, 2020                                           Cisco
                                                           M. Richardson
                                                Sandelman Software Works
                                                           R. Sahoo, Ed.
                                                       February 10, 2020

                            RPL Capabilities
                    draft-ietf-roll-capabilities-00

Abstract

   This draft enables the discovery, advertisement and query of
   capabilities for RPL nodes.

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 August 13, 2020.

Copyright Notice

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

Jadhav, et al.           Expires August 13, 2020                [Page 1]
Internet-Draft               RPL Capabilties               February 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language and Terminology . . . . . . . . . .   3
     1.2.  What are Capabilities?  . . . . . . . . . . . . . . . . .   3
   2.  Requirements for this document  . . . . . . . . . . . . . . .   4
     2.1.  How are Capabilities different from MOP or DIO
           Configuration Option? . . . . . . . . . . . . . . . . . .   4
   3.  Capabilities  . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Capability Catagories . . . . . . . . . . . . . . . . . .   5
     3.2.  Capability Control Message Option . . . . . . . . . . . .   5
     3.3.  Capabilities Handshake  . . . . . . . . . . . . . . . . .   6
     3.4.  ROLL Capabilities . . . . . . . . . . . . . . . . . . . .   6
       3.4.1.  Projected Route Capability  . . . . . . . . . . . . .   6
         3.4.1.1.  Format of Projected Route Capability  . . . . . .   7
       3.4.2.  6LoRH Capability  . . . . . . . . . . . . . . . . . .   8
         3.4.2.1.  Format of 6LoRH Capability  . . . . . . . . . . .   9
       3.4.3.  Routing Resource Capability . . . . . . . . . . . . .   9
         3.4.3.1.  Format of Routing Resource Capability . . . . . .  10
       3.4.4.  Neighbor Cache Capability . . . . . . . . . . . . . .  11
         3.4.4.1.  Format of Neighbor Cache Capability . . . . . . .  12
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  New option: Capabilities  . . . . . . . . . . . . . . . .  12
     5.2.  New Registry for Capabilities Flags . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Capability Handshake Example . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   RPL [RFC6550] specifies a proactive distance-vector based routing
   scheme.  The protocol creates a DAG-like structure which operates
   with a given "Mode of Operation" (MOP) determining the minimal and
   mandatory set of primitives to be supported by all the participating
   nodes.

   This document adds a notion of capabilities using which the nodes in
   the network could inform its peers about its additional capabilities/
   features.  This document highlights the differences of capabilities
Show full document text