Protocol Action: 'Network Service Header (NSH)' to Proposed Standard (draft-ietf-sfc-nsh-28.txt)

The IESG <iesg-secretary@ietf.org> Mon, 06 November 2017 16:50 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: Protocol Action: 'Network Service Header (NSH)' to Proposed Standard (draft-ietf-sfc-nsh-28.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, sfc-chairs@ietf.org, sfc@ietf.org, "Joel M. Halpern" <jmh@joelhalpern.com>, akatlas@gmail.com, draft-ietf-sfc-nsh@ietf.org, jmh@joelhalpern.com, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <150998702854.29155.16639075248455079571.idtracker@ietfa.amsl.com>
Date: Mon, 06 Nov 2017 08:50:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/o-UpxBUjYIMZcc6O1jPOGXftYQE>

The IESG has approved the following document:
- 'Network Service Header (NSH)'
  (draft-ietf-sfc-nsh-28.txt) as Proposed Standard

This document is the product of the Service Function Chaining Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard.

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




Technical Summary

This document describes a Network Service Header (NSH) inserted onto packets or frames to realize service function paths.  NSH also provides a mechanism for metadata exchange along the instantiated service path. NSH is the SFC encapsulation required to support the Service Function Chaining (SFC) Architecture (defined in RFC7665).


Working Group Summary

The working group has had many discussions on this document.  Many individuals from many companies have helped bring together this solution.  Over the last 9 months significant effort has gone into fixing issues raised by earlier reviews.  While there is still some disagreement (such as on the fact that the WG selected TTL mechanism is a compromise with some accepted imperfections), all technical limitations are identified in the document and dealt with in fashions acceptable to the rough consensus of the working group.

Document Quality

There are multiple implementations of this work, some from open source and some proprietary.


Personnel

   Document Shepherd:  Joel Halpern
   Responsible AD: Alia Atlas

Protocol Action: 'Network Service Header (NSH)' t… The IESG