An Enhanced Source Routing Header Based on RH3
draft-han-6man-enhanced-source-routing-header-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Han Jie 
Last updated 2020-10-29
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) 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)
L                                                                 H. Jie
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                        October 29, 2020
Expires: May 2, 2021

             An Enhanced Source Routing Header Based on RH3
            draft-han-6man-enhanced-source-routing-header-00

Abstract

   IPv6 Routing header type 3 (termed as RH3) is defined and used in
   Low-Power and Lossy Networks (LLNs) that are typically constrained in
   resources (limited communication data rate, processing power, energy
   capacity, memory).  Based on the mechanisms introduced by RH3, this
   document specifies an new IPv6 Routing Header type that provides
   encapsulation capability of segments with various lengths and can be
   applied to more scenarios.

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 May 2, 2021.

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

Jie                        Expires May 2, 2021                  [Page 1]
Internet-Draft       Enhanced Source Routing Header         October 2020

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Format of the Source Routing Header . . . . . . . . . . . . .   3
   4.  Format of the Enhanced Source Routing Header  . . . . . . . .   3
   5.  Generating E-SRH  . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Processing E-SRH  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Routing headers are defined in [RFC8200].  [RFC6554] specifies the
   Source Routing Header (SRH), i.e., IPv6 Routing header type 3 (termed
   as RH3), for use strictly between RPL routers in the Low-Power and
   Lossy Networks (LLNs) [RFC6550], which are typically constrained in
   resources (limited communication data rate, processing power, energy
   capacity, memory).  It introduces mechanisms to compact the source
   route entries when all entries share the same prefix with the IPv6
   Destination Address of a packet carrying an RH3, a typical scenario
   in LLNs using source routing.  The compaction mechanism reduces
   consumption of scarce resources such as channel capacity.  However,
   it is challenging when all entries do not have the same prefix, for
   example, only a part of entries share the same prefix, but still want
   to encode all routries in a single routing header and reduce the
   overhead.

   This document specifies an enhanced Source Routing Header (termed as
   E-SRH) to enhance the encapsulation capability of segments with
   various lengths and attempt to apply to more scenarios that using
   source routing mechanism.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Jie                        Expires May 2, 2021                  [Page 2]
Internet-Draft       Enhanced Source Routing Header         October 2020

3.  Format of the Source Routing Header

   The Source Routing Header defined in [RFC6554] has the following
   format:

        0                   1                   2                   3
Show full document text