Last Call: <draft-ietf-spring-nsh-sr-11.txt> (Integration of Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 16 June 2022 13:18 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-spring-nsh-sr-11.txt> (Integration of Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: andrew-ietf@liquid.tech, bruno.decraene@orange.com, draft-ietf-spring-nsh-sr@ietf.org, spring-chairs@ietf.org, spring@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <165538550768.60947.15805385276751056406@ietfa.amsl.com>
Date: Thu, 16 Jun 2022 06:18:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/v3v-AzGOEOjUo4cljKh3yAy1dT0>

The IESG has received a request from the Source Packet Routing in Networking
WG (spring) to consider the following document: - 'Integration of Network
Service Header (NSH) and Segment Routing for
   Service Function Chaining (SFC)'
  <draft-ietf-spring-nsh-sr-11.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-06-30. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document describes the integration of the Network Service Header
   (NSH) and Segment Routing (SR), as well as encapsulation details, 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.

   Combining these technologies allows SR to be used for steering
   packets between Service Function Forwarders (SFF) along a given
   Service Function Path (SFP) while NSH has the responsibility for
   maintaining the integrity of the service plane, the SFC instance
   context, and any associated metadata.

   This integration demonstrates that NSH and SR can work cooperatively
   and provide a network operator with the flexibility to use whichever
   transport technology makes sense in specific areas of their network
   infrastructure while still maintaining an end-to-end service plane
   using NSH.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-spring-nsh-sr/


The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/4626/
   https://datatracker.ietf.org/ipr/3695/

Last Call: <draft-ietf-spring-nsh-sr-11.txt> (Int… The IESG