SRv6 NET-PGM extension: Insertion
draft-filsfils-spring-srv6-net-pgm-insertion-00

Document Type Active Internet-Draft (individual)
Last updated 2019-09-24
Stream (None)
Intended RFC status (None)
Formats plain text 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)
SPRING                                                  C. Filsfils, Ed.
Internet-Draft                                         P. Camarillo, Ed.
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: March 26, 2020                                         J. Leddy
                                                  Individual Contributor
                                                                D. Voyer
                                                             Bell Canada
                                                           S. Matsushima
                                                                SoftBank
                                                                   Z. Li
                                                     Huawei Technologies
                                                      September 23, 2019

                   SRv6 NET-PGM extension: Insertion
            draft-filsfils-spring-srv6-net-pgm-insertion-00

Abstract

   Traffic traversing an SR domain is encapsulated in an outer IPv6
   header for its journey through the SR domain.

   To implement transport services strictly within the SR domain, the SR
   domain may require insertion or deletion of an SRH after the outer
   IPv6 header of the SR domain.  Any segment within the SRH is strictly
   contained within the SR domain.

   This document extends SRv6 Network Programming
   [I-D.ietf-spring-srv6-network-programming] with new SR endpoint and
   transit behaviors to be performed only within the SR domain in any
   packet owned by the domain.

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.

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

Filsfils, et al.         Expires March 26, 2020                 [Page 1]
Internet-Draft      SRv6 NET-PGM extension: Insertion     September 2019

   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 March 26, 2020.

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
   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.  SRv6 endpoint behaviors . . . . . . . . . . . . . . . . . . .   3
     2.1.  End.B6.Insert: Endpoint bound to an SRv6 policy . . . . .   3
     2.2.  End.B6.Insert.Red: [...] with reduced SRH . . . . . . . .   4
   3.  Transit behaviors . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  T.Insert: Transit with insertion of an SRv6 Policy  . . .   5
     3.2.  T.Insert.Red: Transit with reduced insertion  . . . . . .   5
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Packets transiting an SR Domain may be steered into an SR Policy for
   a variety of reasons.  For example, a PLR router reroutes traffic on
   a TI-LFA repair path [I-D.ietf-rtgwg-segment-routing-ti-lfa] or when
   a Binding-SID is expanded [I-D.ietf-spring-segment-routing-policy].

Filsfils, et al.         Expires March 26, 2020                 [Page 2]
Internet-Draft      SRv6 NET-PGM extension: Insertion     September 2019

   This document extends the SRv6 Network Programming
   [I-D.ietf-spring-srv6-network-programming] model with new endpoint
Show full document text