The IPv6 Compressed Routing Header (CRH)
draft-bonica-6man-comp-rtg-hdr-02

Document Type Active Internet-Draft (individual)
Last updated 2019-03-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda spring at IETF-104
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
6man                                                           R. Bonica
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                                   X. Xu
Expires: September 10, 2019                                  Alibaba Inc
                                                                 G. Chen
                                                                   Baidu
                                                                  Y. Zhu
                                                                 G. Yang
                                                           China Telecom
                                                           March 9, 2019

                The IPv6 Compressed Routing Header (CRH)
                   draft-bonica-6man-comp-rtg-hdr-02

Abstract

   This document defines the Compressed Routing Header (CRH).  The CRH,
   like any other Routing header, contains a list of segment identifiers
   (SID).  The CRH differs from other Routing headers in that its
   segment identifiers can be 8, 16 or 32 bits long.

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 September 10, 2019.

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

Bonica, et al.         Expires September 10, 2019               [Page 1]
Internet-Draft       IPv6 Compressed Routing Header           March 2019

   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.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  The Compressed Routing Header (CRH) . . . . . . . . . . . . .   4
   4.  Segment Identifiers (SID) . . . . . . . . . . . . . . . . . .   6
   5.  Processing Rules  . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  CRH Specific  . . . . . . . . . . . . . . . . . . . . . .   7
       5.2.1.  Computing Minimum CRH Length  . . . . . . . . . . . .   8
   6.  Mutability  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Management Considerationsinclude  . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     11.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A.  CRH Processing Examples  . . . . . . . . . . . . . .  11
     A.1.  Loose Source Routing  . . . . . . . . . . . . . . . . . .  13
     A.2.  Loose Source Routing Preserving The First SID . . . . . .  13
     A.3.  Strict Source Routing . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   An IPv6 [RFC8200] source node can steer a packet through a specific
   path to its destination.  The source node defines the path as an
   ordered list of segments and encodes the path in an IPv6 Routing
   header.  As per [RFC8200], all Routing headers includes the following
   fields:

   o  Next Header - Identifies the header immediately following the
      Routing header.

   o  Hdr Ext Len - Length of the Routing header.

   o  Routing Type - Identifies the particular Routing header variant.

   o  Segments Left - The number of segments still to be traversed
      before reaching the destination.

Bonica, et al.         Expires September 10, 2019               [Page 2]
Internet-Draft       IPv6 Compressed Routing Header           March 2019
Show full document text