RFC 9421 on HTTP Message Signatures
rfc-editor@rfc-editor.org Wed, 14 February 2024 19:07 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 60A87C151083 for <ietf-announce@ietfa.amsl.com>; Wed, 14 Feb 2024 11:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.958
X-Spam-Level:
X-Spam-Status: No, score=-3.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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 569p1dSK4Tn7 for <ietf-announce@ietfa.amsl.com>; Wed, 14 Feb 2024 11:07:08 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 26DFEC151084 for <ietf-announce@ietf.org>; Wed, 14 Feb 2024 11:07:08 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0E046E5F7D; Wed, 14 Feb 2024 11:07:08 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9421 on HTTP Message Signatures
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240214190708.0E046E5F7D@rfcpa.amsl.com>
Date: Wed, 14 Feb 2024 11:07:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/drfUHPPW09Lj078dfq11mR8iRWE>
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: Wed, 14 Feb 2024 19:07:12 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9421 Title: HTTP Message Signatures Author: A. Backman, Ed., J. Richer, Ed., M. Sporny Status: Standards Track Stream: IETF Date: February 2024 Mailbox: richanna@amazon.com, ietf@justin.richer.org, msporny@digitalbazaar.com Pages: 95 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-httpbis-message-signatures-19.txt URL: https://www.rfc-editor.org/info/rfc9421 DOI: 10.17487/RFC9421 This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer and where the message may be transformed (e.g., by intermediaries) before reaching the verifier. This document also describes a means for requesting that a signature be applied to a subsequent HTTP message in an ongoing HTTP exchange. This document is a product of the HTTP 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
- RFC 9421 on HTTP Message Signatures rfc-editor