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

Document Type Active Internet-Draft (mpls WG)
Last updated 2018-11-05
Replaces draft-malis-mpls-sfc-encapsulation
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS Working Group                                              A. Malis
Internet-Draft                                                 S. Bryant
Intended status: Informational                       Huawei Technologies
Expires: May 9, 2019                                          J. Halpern
                                                                Ericsson
                                                           W. Henderickx
                                                                   Nokia
                                                       November 05, 2018

                     MPLS Encapsulation for SFC NSH
                  draft-ietf-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 MPLS 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 May 9, 2019.

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

Malis, et al.              Expires May 9, 2019                  [Page 1]
Internet-Draft                 MPLSforSFC                  November 2018

   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.  MPLS Encapsulation Using an SFF Label . . . . . . . . . . . .   3
     2.1.  MPLS Label Stack Construction at the Sending Node . . . .   3
     2.2.  SFF Label Processing at the Destination Node  . . . . . .   4
   3.  Equal Cost Multipath (ECMP) Considerations  . . . . . . . . .   4
   4.  Operations, Administration, and Maintenance (OAM)
       Considerations  . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   As discussed in [RFC8300], a number of transport encapsulations for
   the Service Function Chaining (SFC) Network Service Header (NSH)
   already exist, such as Ethernet, GRE [RFC2784], and VXLAN-GPE
   [I-D.ietf-nvo3-vxlan-gpe].

   This document describes an MPLS transport encapsulation for the NSH,
   and also describes how to use a Service Function Forwarder (SFF)
   [RFC7665] Label to indicate the presence of the NSH in the MPLS
   packet payload.  This allows SFC packets using the NSH to be
   forwarded between SFFs in an MPLS transport network, where MPLS is
   used to interconnect the network nodes that contain one or more SFFs.
   The label is also used to select between multiple SFFs in the
   destination MPLS node.

   SFF Labels are similar to other service labels at the bottom of an
   MPLS label stack that denote the contents of the MPLS payload being
   other than 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.

Malis, et al.              Expires May 9, 2019                  [Page 2]
Internet-Draft                 MPLSforSFC                  November 2018

   This informational document follows well-established MPLS procedures
Show full document text