When to use RFC 6553, 6554 and IPv6-in-IPv6
draft-robles-roll-useofrplinfo-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-06-27
Replaced by draft-ietf-roll-useofrplinfo
Stream (None)
Intended RFC status (None)
Formats 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 Working Group                                           M.I. Robles
Internet-Draft                                                  Ericsson
Intended status: Informational                             M. Richardson
Expires: December 29, 2015                                           SSW
                                                           June 27, 2015

              When to use RFC 6553, 6554 and IPv6-in-IPv6
                   draft-robles-roll-useofrplinfo-00

Abstract

   This document states different cases where RFC 6553, RFC 6554 and
   IPv6-in-IPv6 encapsulation is required to set the bases to help
   defining the compression of RPL routing information in LLN
   environments.

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 December 29, 2015.

Copyright Notice

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

Robles & Richardson    Expires December 29, 2015                [Page 1]
Internet-Draft                 Useof6553                       June 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology and Requirements Language . . . . . . . . . . . .   2
   3.  Sample/reference topology . . . . . . . . . . . . . . . . . .   3
   4.  Example flow from leaf to root  . . . . . . . . . . . . . . .   4
     4.1.  Non-storing . . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Storing . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Example flow from leaf to Internet  . . . . . . . . . . . . .   6
     5.1.  Non-storing . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Storing . . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Example flow from leaf to leaf  . . . . . . . . . . . . . . .   7
     6.1.  Traditional storing . . . . . . . . . . . . . . . . . . .   7
     6.2.  Traditional non-storing . . . . . . . . . . . . . . . . .   7
     6.3.  P2P non-storing . . . . . . . . . . . . . . . . . . . . .   7
   7.  Example flow from Internet to leaf  . . . . . . . . . . . . .   7
     7.1.  Storing . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.2.  Non-storing . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Example flow from root to leaf  . . . . . . . . . . . . . . .   7
     8.1.  Storing . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.2.  Non-storing . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   8
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     12.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   RPL [RFC6550] defines RPL Option to transmit routing information.
   RFC 6553 [RFC6553] defines how to transmit in a Hop-By-Hop Option RPL
   Information,such as information to avoid and detect loops.  RFC 6554
   [RFC6554] defines the use of Extension header for Source Routing.

   Several discussions in ROLL/6lo/6tisch Mailing Lists took place
   focusing in the definition how to compress RPL Information in
   constrained environment.  ROLL Virtual Interim Meeting (02-2015)
   concluded that there is a need to define how to use RFC 6553, RFC6554
   and tunneling (IP-in-IP) to be able to set the correct environment
   for compression.

2.  Terminology and Requirements Language

Robles & Richardson    Expires December 29, 2015                [Page 2]
Internet-Draft                 Useof6553                       June 2015
Show full document text