SRv6 Tagging proxy
draft-eden-srv6-tagging-proxy-00

Document Type Active Internet-Draft (individual)
Last updated 2019-10-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda spring at IETF-106
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SPRING                                                      Y. Ueno, Ed.
Internet-Draft                            NTT Communications Corporation
Intended status: Standards Track                             R. Nakamura
Expires: April 29, 2020                          The University of Tokyo
                                                               T. Kamata
                                                     Cisco Systems, Inc.
                                                        October 27, 2019

                           SRv6 Tagging proxy
                    draft-eden-srv6-tagging-proxy-00

Abstract

   This document describes the tagging method of SRv6 proxy.  SRv6 proxy
   is an SR endpoint behavior for processing SRv6 traffic on behalf of
   an SR-unaware service.

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 April 29, 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

Ueno, et al.             Expires April 29, 2020                 [Page 1]
Internet-Draft             SRv6 Tagging proxy               October 2019

   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
   3.  SRv6 Tagging proxy  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  SRv6 pseudocode . . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  Tagging proxy for inner type IPv4 . . . . . . . . . .   4
       3.1.2.  Tagging proxy for inner type IPv6 . . . . . . . . . .   5
   4.  Implementation status . . . . . . . . . . . . . . . . . . . .   5
   5.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  SRv6 Endpoint Behaviors . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Segment Routing (SR) is a source routing architecture defined in
   [RFC8402].  SR uses segment identifiers (SIDs) to identify each
   entity in an SR network.  SR can be applied two types of data plane,
   MPLS and IPv6.  IPv6 based SR is called Segment Routing IPv6 (SRv6)
   and its header format is defined in
   [I-D.ietf-6man-segment-routing-header].  As for the SRv6 packets, the
   SIDs are embedded in packets in the form of a list with the current
   index of the list, called SegmentsLeft (SL).  Packets with Segment
   Routing Headers (SRHs) are steered through the ordered list of SIDs.
   Note that the proxy behavior defined in this document can only be
   applied for SRv6 packets.

   Because SR can steer packets through arbitrary SR nodes, SR can be
   applied to Service Function Chaining (SFC).  SFC, defined in
   [RFC7665], is an architecture that realizes the on-demand
   instantiation of an ordered set of service functions.  Although there
   are differences in the specific packet steering method, SR defined in
   [RFC8402] can realize SFC and
   [I-D.xuclad-spring-sr-service-programming] describes SR proxy
   behaviors to integrate SR-unaware services to it.

   This document describes a new SRv6 proxy, called tagging proxy.  The
   tagging proxy, which is a variant of the dynamic SR proxy, supports

Ueno, et al.             Expires April 29, 2020                 [Page 2]
Internet-Draft             SRv6 Tagging proxy               October 2019
Show full document text