RFC 9577 on The Privacy Pass HTTP Authentication Scheme
rfc-editor@rfc-editor.org Thu, 13 June 2024 22:46 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 E982EC14F700; Thu, 13 Jun 2024 15:46:39 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 37B1F7FA60; Thu, 13 Jun 2024 15:46:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9577 on The Privacy Pass HTTP Authentication Scheme
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240613224639.37B1F7FA60@rfcpa.rfc-editor.org>
Date: Thu, 13 Jun 2024 15:46:39 -0700
Message-ID-Hash: MKVPUESBRTMDC3O5QEXPTFTDCWZ3FZMV
X-Message-ID-Hash: MKVPUESBRTMDC3O5QEXPTFTDCWZ3FZMV
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, privacy-pass@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/aPm9rPvPwwXd6kvEVLgkbz7yeXM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9577
Title: The Privacy Pass HTTP Authentication Scheme
Author: T. Pauly,
S. Valdez,
C. A. Wood
Status: Standards Track
Stream: IETF
Date: June 2024
Mailbox: tpauly@apple.com,
svaldez@chromium.org,
caw@heapingbits.net
Pages: 25
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-privacypass-auth-scheme-15.txt
URL: https://www.rfc-editor.org/info/rfc9577
DOI: 10.17487/RFC9577
This document defines an HTTP authentication scheme for Privacy Pass,
a privacy-preserving authentication mechanism used for authorization.
The authentication scheme specified in this document can be used by
Clients to redeem Privacy Pass tokens with an Origin. It can also be
used by Origins to challenge Clients to present Privacy Pass tokens.
This document is a product of the Privacy Pass 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