[sfc] RFC 9145 on Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context Headers
rfc-editor@rfc-editor.org Mon, 13 December 2021 17:23 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3A63A08C4; Mon, 13 Dec 2021 09:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sy_HWPziBTAQ; Mon, 13 Dec 2021 09:22:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1C223A0934; Mon, 13 Dec 2021 09:22:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 0288AEF286; Mon, 13 Dec 2021 09:22:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20211213172255.0288AEF286@rfc-editor.org>
Date: Mon, 13 Dec 2021 09:22:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/yiBt_OmGCawzCAE5-r4P5HwZRdM>
Subject: [sfc] RFC 9145 on Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context Headers
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2021 17:23:04 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9145
Title: Integrity Protection for the Network
Service Header (NSH) and Encryption of
Sensitive Context Headers
Author: M. Boucadair,
T. Reddy.K,
D. Wing
Status: Standards Track
Stream: IETF
Date: December 2021
Mailbox: mohamed.boucadair@orange.com,
kondtir@gmail.com,
dwing-ietf@fuggles.com
Pages: 25
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sfc-nsh-integrity-09.txt
URL: https://www.rfc-editor.org/info/rfc9145
DOI: 10.17487/RFC9145
This specification presents an optional method to add integrity
protection directly to the Network Service Header (NSH) used for
Service Function Chaining (SFC). Also, this specification allows for
the encryption of sensitive metadata (MD) that is carried in the NSH.
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