SFC transport considertation
draft-ao-sfc-transport-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
SFC WG                                                             T. Ao
Internet-Draft                                           ZTE Corporation
Intended status: Informational                                    W. Wei
Expires: April 23, 2019                                         Y. Zheng
                                                               ZTE Corp.
                                                        October 20, 2018

                      SFC transport considertation
                       draft-ao-sfc-transport-00

Abstract

   A Network Service Header(NSH) is imposed encapsulates a packet or a
   frame for Service Function Chaining.  The resulting packet, in turn,
   is encapsulate according to transport layer.  The NSH contains a
   Service Path Identifier (SPI) and a Service Index (SI).  The SPI is,
   as per its name, an identifier.  The SPI alone cannot be used to
   forward packets along a service path.  Rather, the SPI provides a
   level of indirection between the service path / topology and the
   network transport encapsulation.  For different transport
   encapsulations, this document provides the format information with
   transport and NSH, and gives operational constraints that transport
   technologies, used by NSH need to meet.

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 23, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Ao, et al.               Expires April 23, 2019                 [Page 1]
Internet-Draft         SFC transport consideration          October 2018

   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.  Conventions used in this document . . . . . . . . . . . . . .   4
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  Ethernet as transport . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Format in encapsulation . . . . . . . . . . . . . . . . .   4
     3.2.  Operation . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  VXLAN-GPE as transport  . . . . . . . . . . . . . . . . . . .   6
     4.1.  Format in encapsulation . . . . . . . . . . . . . . . . .   6
     4.2.  Operation . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  GRE as transport  . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Format in encapsulation . . . . . . . . . . . . . . . . .   7
     5.2.  Operation . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  GENEVE as transport . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Format in encapsulation . . . . . . . . . . . . . . . . .   8
     6.2.  Operation . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informational References . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   For SFC using NSH, NSH is imposed on original packets/frames.  NSH
   hearder format is defined in [RFC8300] as Figure 1.  NSH is transport
   encapsulation agnostic, and SFC packet can't be forwarded or
   transmitted along without the transport layer support.  So how does
   the different transport technologies bear SFC service traffic is what
   is discussed in this document.

Ao, et al.               Expires April 23, 2019                 [Page 2]
Show full document text