RFC 9263 on Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers
rfc-editor@rfc-editor.org Tue, 09 August 2022 23:56 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37DCAC14CF10; Tue, 9 Aug 2022 16:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bea2awzpj13; Tue, 9 Aug 2022 16:56:54 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF7FFC157B41; Tue, 9 Aug 2022 16:56:54 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id E052814954A; Tue, 9 Aug 2022 16:56:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9263 on Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sfc@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220809235654.E052814954A@rfcpa.amsl.com>
Date: Tue, 09 Aug 2022 16:56:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GT5pIB_loO0NKiRK2QEFkp9JCWc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2022 23:56:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9263
Title: Network Service Header (NSH) Metadata
Type 2 Variable-Length Context Headers
Author: Y. Wei, Ed.,
U. Elzur,
S. Majee,
C. Pignataro,
D. Eastlake 3rd
Status: Standards Track
Stream: IETF
Date: August 2022
Mailbox: wei.yuehua@zte.com.cn,
uri.elzur@intel.com,
sum.majee@gmail.com,
cpignata@cisco.com,
d3e3e3@gmail.com
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sfc-nsh-tlv-15.txt
URL: https://www.rfc-editor.org/info/rfc9263
DOI: 10.17487/RFC9263
Service Function Chaining (SFC) uses the Network Service Header (NSH)
(RFC 8300) to steer and provide context metadata (MD) with each
packet. Such metadata can be of various types, including MD Type 2,
consisting of Variable-Length Context Headers. This document
specifies several such Context Headers that can be used within a
Service Function Path (SFP).
This document is a product of the Service Function Chaining Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC