MPLS Encapsulation for SFC NSH
draft-malis-mpls-sfc-encapsulation-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-06-19
Replaced by rfc8596, draft-ietf-mpls-sfc-encapsulation
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 Working Group                                               A. Malis
Internet-Draft                                                 S. Bryant
Intended status: Informational                       Huawei Technologies
Expires: December 21, 2018                                    J. Halpern
                                                                Ericsson
                                                           June 19, 2018

                     MPLS Encapsulation for SFC NSH
                 draft-malis-mpls-sfc-encapsulation-00

Abstract

   This document describes how to use a Service Function Forwarder (SFF)
   Label (similar to a pseudowire label or VPN label) to indicate the
   presence of a Service Function Chaining (SFC) Network Service Header
   (NSH) between an MPLS label stack and the packet payload.  This
   allows SFC packets using the NSH to be forwarded between SFFs over an
   MPLS network, and the selection between multiple SFFs in the
   destination node.

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 December 21, 2018.

Copyright Notice

   Copyright (c) 2018 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

Malis, et al.           Expires December 21, 2018               [Page 1]
Internet-Draft                 MPLSforSFC                      June 2018

   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.  MPLS Encapsulation  . . . . . . . . . . . . . . . . . . . . .   2
   3.  SFF Label . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security considerations . . . . . . . . . . . . . . . . . . .   3
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   As discussed in [RFC8300], a number of encapsulations for the Service
   Function Chaining (SFC) Network Service Header (NSH) already exist,
   such as in Ethernet, GRE [RFC2784], and VXLAN-GPE
   [I-D.ietf-nvo3-vxlan-gpe].  This document describes an MPLS
   encapsulation for the NSH, and also describes how to use an Service
   Function Forwarder (SFF) [RFC7665] Label to indicate the presence of
   the NSH header in the MPLS packet payload.  This allows SFC packets
   using the NSH to be forwarded between SFFs over an MPLS network, and
   the selection between multiple SFFs in the destination node.

   SFF Labels are similar to other labels at the bottom of an MPLS label
   stack that denote the contents of the MPLS payload being other than
   globally routed IP, such as a layer 2 pseudowire, an IP packet that
   is routed in a VPN context with a private address, or an Ethernet
   virtual private wire service.

   This informational document follows well-established MPLS procedures
   and does not require any actions by IANA or any new protocol
   elements.

2.  MPLS Encapsulation

   The encapsulation is simply a standard MPLS label stack [RFC3032]
   with the SFF Label at the bottom of the stack, followed by a NSH as
   defined by [RFC8300] and the NSH payload.

   As discussed by [RFC4928] and [RFC7325], there are Equal Cost
   Multipath (ECMP) considerations for payloads carried by MPLS.  Many

Malis, et al.           Expires December 21, 2018               [Page 2]
Internet-Draft                 MPLSforSFC                      June 2018

   existing routers use deep packet inspection to examine the payload of
   an MPLS packet, and if the first nibble of the payload is equal to
Show full document text