RFC 9576 on The Privacy Pass Architecture
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 890FBC14F700; Thu, 13 Jun 2024 15:46:36 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id E63687FA60; Thu, 13 Jun 2024 15:46:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9576 on The Privacy Pass Architecture
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240613224635.E63687FA60@rfcpa.rfc-editor.org>
Date: Thu, 13 Jun 2024 15:46:35 -0700
Message-ID-Hash: 2KGB6N6ZX7UFXB5NM7P3GCHZFLKUJFPE
X-Message-ID-Hash: 2KGB6N6ZX7UFXB5NM7P3GCHZFLKUJFPE
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/f5Kh03veJwVdJndFDzMc8WSrwR8>
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 9576 Title: The Privacy Pass Architecture Author: A. Davidson, J. Iyengar, C. A. Wood Status: Informational Stream: IETF Date: June 2024 Mailbox: alex.davidson92@gmail.com, jri@fastly.com, caw@heapingbits.net Pages: 25 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-privacypass-architecture-16.txt URL: https://www.rfc-editor.org/info/rfc9576 DOI: 10.17487/RFC9576 This document specifies the Privacy Pass architecture and requirements for its constituent protocols used for authorization based on privacy-preserving authentication mechanisms. It describes the conceptual model of Privacy Pass and its protocols, its security and privacy goals, practical deployment models, and recommendations for each deployment model, to help ensure that the desired security and privacy goals are fulfilled. This document is a product of the Privacy Pass Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 9576 on The Privacy Pass Architecture rfc-editor