SRH TLV Processing Programming
draft-li-spring-srh-tlv-processing-programming-00

Document Type Active Internet-Draft (individual)
Authors Cheng Li  , Yang Xia  , Dhruv Dhody  , Zhenbin Li 
Last updated 2020-12-08
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
SPRING Working Group                                               C. Li
Internet-Draft                                                    Y. Xia
Intended status: Standards Track                                D. Dhody
Expires: June 12, 2021                                             Z. Li
                                                     Huawei Technologies
                                                        December 9, 2020

                     SRH TLV Processing Programming
           draft-li-spring-srh-tlv-processing-programming-00

Abstract

   This document proposes a mechanism to program the processing rules of
   Segment Routig Header (SRH) optional TLVs explicitly on the ingress
   node.  In this mechanism, there is no need to configure local
   configuration at the node to support SRH TLV processing.  A network
   operator can program to process specific TLVs on specific segment
   endpoint nodes for specific packets on the ingress node, which is
   more efficient for SRH TLV processing.

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 June 12, 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

Li, et al.                Expires June 12, 2021                 [Page 1]
Internet-Draft                   SRH TPP                   December 2020

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   3.  SRH TLV Processing Programming  . . . . . . . . . . . . . . .   3
     3.1.  TLV Processing Indicator Flavor . . . . . . . . . . . . .   4
     3.2.  TLV Processing Indicator TLV  . . . . . . . . . . . . . .   4
   4.  Illustration  . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Segment routing (SR) [RFC8402] is a source routing paradigm that
   explicitly indicates the forwarding path for packets at the ingress
   node by inserting an ordered list of instructions, called segments.

   When segment routing is deployed on the IPv6 data plane, it is called
   SRv6 [RFC8754].  For support of SR, a new routing header called
   Segment Routing Header (SRH), containing a list of segments, optional
   TLVs and other information, has been defined in [RFC8754].

   Currently, when TLVs are carried in an SRH, they are ignored by the
   nodes by default, unless there are some local policies on nodes to
   enable the SRH TLV processing [RFC8754].

   When a node is configured to process a TLV, it needs to examine all
   the SRH TLVs for processing a single TLV (TLVs except HMAC in SRH MAY
   appear in any order), which is inefficient.

   Furthermore, in order to deploy a new service, network operators need
   to configure multiple nodes along the path to support SRH TLVs
   processing, which is complicated.  Also, it is not easy to
   dynamically adjustment the local policy for meeting dynamic service
   requirements.  However, SRv6 does not have the compability to program
   the rules of SRH TLVs processing on the ingress node currently.
Show full document text