NSH and Segment Routing Integration for Service Function Chaining (SFC)
draft-guichard-spring-nsh-sr-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-27
Replaces draft-guichard-sfc-nsh-sr
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)
SPRING                                                  J. Guichard, Ed.
Internet-Draft                                                   H. Song
Intended status: Standards Track                                  Huawei
Expires: March 31, 2019                                      J. Tantsura
                                                          Nuage Networks
                                                              J. Halpern
                                                                Ericsson
                                                           W. Henderickx
                                                                   Nokia
                                                            M. Boucadair
                                                                  Orange
                                                      September 27, 2018

NSH and Segment Routing Integration for Service Function Chaining (SFC)
                    draft-guichard-spring-nsh-sr-00

Abstract

   This document describes two application scenarios where Network
   Service Header (NSH) and Segment Routing (SR) techniques can be
   deployed together to support Service Function Chaining (SFC) in an
   efficient manner while maintaining separation of the service and
   transport planes as originally intended by the SFC architecture.

   In the first scenario, an NSH-based SFC is created using SR as the
   transport between SFFs.  SR in this case is just one of many
   encapsulations that could be used to maintain the transport-
   independent nature of NSH-based service chains.

   In the second scenario, SR is used to represent each service hop of
   the NSH-based SFC as a segment within the segment-list.  SR and NSH
   in this case are integrated.

   In both scenarios SR is responsible for steering packets between SFFs
   along a given SFP while NSH is responsible for maintaining the
   integrity of the service plane, the SFC instance context, and any
   associated metadata.

   These application scenarios demonstrate that NSH and SR can work
   jointly and complement each other leaving the network operator with
   the flexibility to use whichever transport technology makes sense in
   specific areas of their network infrastructure, and still maintain an
   end-to-end service plane using NSH.

Guichard, et al.         Expires March 31, 2019                 [Page 1]
Internet-Draft                 NSH-SR SFC                 September 2018

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 March 31, 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  SFC Overview and Rationale  . . . . . . . . . . . . . . .   3
     1.2.  SFC within SR Networks  . . . . . . . . . . . . . . . . .   4
   2.  NSH-based SFC with SR-based transport tunnel  . . . . . . . .   5
   3.  SR-based SFC with Integrated NSH Service Plane  . . . . . . .   9
   4.  Encapsulation Details . . . . . . . . . . . . . . . . . . . .  11
     4.1.  NSH using MPLS-SR Transport . . . . . . . . . . . . . . .  11
     4.2.  NSH using SRv6 Transport  . . . . . . . . . . . . . . . .  12
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  UDP Port Number for NSH . . . . . . . . . . . . . . . . .  13
     6.2.  Protocol Number for NSH . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14

Guichard, et al.         Expires March 31, 2019                 [Page 2]
Show full document text