Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)
draft-ietf-spring-nsh-sr-15

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, andrew-ietf@liquid.tech, bruno.decraene@orange.com, draft-ietf-spring-nsh-sr@ietf.org, rfc-editor@rfc-editor.org, spring-chairs@ietf.org, spring@ietf.org
Subject: Protocol Action: 'Integration of Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)' to Proposed Standard (draft-ietf-spring-nsh-sr-14.txt)

The IESG has approved the following document:
- 'Integration of Network Service Header (NSH) and Segment Routing for
   Service Function Chaining (SFC)'
  (draft-ietf-spring-nsh-sr-14.txt) as Proposed Standard

This document is the product of the Source Packet Routing in Networking
Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-nsh-sr/

Ballot Text

Technical Summary

   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.

Working Group Summary

   There were a number of comments on this document through the last call, but the comments were all addressed during the last call through multiple revisions of the document. 

Document Quality

   There are no implementations or implementation plans that have been publicly shared. All in all I found the document to be clear and well drafted.

Personnel

   Document Shepard: Bruno Decraene
   Responsible AD: Andrew Alston

RFC Editor Note