Eliding and Querying RPL Information
draft-thubert-roll-eliding-dio-information-03

Document Type Active Internet-Draft (individual)
Last updated 2019-11-17
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized 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 Systems
Updates: 6550 (if approved)                                  R.A. Jadhav
Intended status: Standards Track                             Huawei Tech
Expires: 20 May 2020                                             L. Zhao
                                                           Cisco Systems
                                                              D. Barthel
                                                             Orange Labs
                                                        17 November 2019

                  Eliding and Querying RPL Information
             draft-thubert-roll-eliding-dio-information-03

Abstract

   This document presents a method to safely elide a group of RPL
   options in a DIO message by synchronizing the state associated with
   each of these options between parent and child using a new sequence
   counter in DIO messages.  A child that missed a DIO message with an
   update of any of those protected options detects it by the change of
   sequence counter and queries the update with a DIS Message.  The
   draft also provides a method to fully elide the options in a DAO
   message.

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

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Thubert, et al.            Expires 20 May 2020                  [Page 1]
Internet-Draft              Eliding RPL Info               November 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  BCP 14  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  References  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Message Formats . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Updated DIO Base Object . . . . . . . . . . . . . . . . .   6
     4.2.  Updated DIS Base Object . . . . . . . . . . . . . . . . .   6
     4.3.  New Abbreviated Option Option . . . . . . . . . . . . . .   7
     4.4.  Updated DAO Base Object . . . . . . . . . . . . . . . . .   8
   5.  RCSS Operation  . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Updating the RCSS . . . . . . . . . . . . . . . . . . . .   9
     5.2.  RCSS Freshness and Parent selection . . . . . . . . . . .  10
     5.3.  RCSS of an Option . . . . . . . . . . . . . . . . . . . .  10
   6.  Synchronizing Options . . . . . . . . . . . . . . . . . . . .  12
   7.  Abbreviating the DAO Message  . . . . . . . . . . . . . . . .  12
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     9.1.  New DODAG Information Solicitation Flags  . . . . . . . .  14
     9.2.  New DODAG Advertisement Object Flag . . . . . . . . . . .  14
     9.3.  New RPL Control Message Option  . . . . . . . . . . . . .  14
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  15
   12. Informative References  . . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   Classical Link State protocol synchronize their Link State Database
   (LSDB) by sequencing every change.  Each interested node maintains
   the last sequence of the LSDB it is synchronizing with.  If the last
Show full document text