I-D Action: draft-ietf-spring-nsh-sr-00.txt

internet-drafts@ietf.org Wed, 14 August 2019 01:41 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: spring@ietf.org
Subject: I-D Action: draft-ietf-spring-nsh-sr-00.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: spring@ietf.org
Message-ID: <156574687577.24187.16540040593524388407@ietfa.amsl.com>
Date: Tue, 13 Aug 2019 18:41:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/wVbxfB2MlkLba8hUvppfgBwlM8Y>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Source Packet Routing in Networking WG of the IETF.

        Title           : Network Service Header (NSH) and Segment Routing Integration for Service Function Chaining (SFC)
        Authors         : James N Guichard
                          Haoyu Song
                          Jeff Tantsura
                          Joel Halpern
                          Wim Henderickx
                          Mohamed Boucadair
                          Syed Hassan
	Filename        : draft-ietf-spring-nsh-sr-00.txt
	Pages           : 16
	Date            : 2019-08-07

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 Service Function Forwarders (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 Service Function Path (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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-nsh-sr/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-spring-nsh-sr-00
https://datatracker.ietf.org/doc/html/draft-ietf-spring-nsh-sr-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-ietf-spring-nsh-sr-00.txt internet-drafts