[sfc] Protocol Action: 'Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers' to Proposed Standard (draft-ietf-sfc-nsh-tlv-15.txt)

The IESG <iesg-secretary@ietf.org> Fri, 06 May 2022 13:28 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>
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, andrew-ietf@liquid.tech, draft-ietf-sfc-nsh-tlv@ietf.org, gregimirsky@gmail.com, rfc-editor@rfc-editor.org, sfc-chairs@ietf.org, sfc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <165184373624.20817.18317343479530141254@ietfa.amsl.com>
Date: Fri, 06 May 2022 06:28:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/2lP2y5ieiFAQFbgfSl_c60dbxTc>
Subject: [sfc] Protocol Action: 'Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers' to Proposed Standard (draft-ietf-sfc-nsh-tlv-15.txt)

The IESG has approved the following document:
- 'Network Service Header (NSH) Metadata Type 2 Variable-Length Context
   Headers'
  (draft-ietf-sfc-nsh-tlv-15.txt) as Proposed Standard

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

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

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





Technical Summary

   Service Function Chaining (SFC) uses the Network Service Header, defined in RFC 8300, to steer and provide context Metadata with each packet. 
   Such Metadata can be of various types including MD Type 2 variable-length optional context headers. 
   The document specifies several such context headers, e.g., Forwarding Context, Flow ID, that can be used within a service function path.

Working Group Summary

   The document received a good amount of comments from the WG community.
   Resulting from the WG discussion, some of the originally proposed context headers were taken out for consideration in the future.

Document Quality

   The document is well-written and is easy to read. All technical aspects received a thorough review from the WG.
   Several vendor companies indicated their plans to implement MD Type 2 context headers defined in this specification.

Personnel

   Greg Mirsky is the Document Shepherd.
   Andrew Alston is the Responsible Area Director.

[sfc] Protocol Action: 'Network Service Header (N… The IESG