[Privacy-pass] Call for adoption: draft-yun-cfrg-arc-01 (Ends 2025-09-30)

Benjamin Schwartz via Datatracker <noreply@ietf.org> Tue, 09 September 2025 15:37 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: privacy-pass@ietf.org
Delivered-To: privacy-pass@mail2.ietf.org
Received: from [10.244.8.59] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 970285FD5331; Tue, 9 Sep 2025 08:37:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Schwartz via Datatracker <noreply@ietf.org>
To: draft-yun-cfrg-arc@ietf.org, privacy-pass@ietf.org, privacypass-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <175743223656.3028082.18038260620878661871@dt-datatracker-f7c8fdcb7-pjx77>
Date: Tue, 09 Sep 2025 08:37:16 -0700
Message-ID-Hash: 2VOS2GMPCU6MITDFXAC2EWSU42RG54JQ
X-Message-ID-Hash: 2VOS2GMPCU6MITDFXAC2EWSU42RG54JQ
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Reply-To: Benjamin Schwartz <ietf@bemasc.net>
Subject: [Privacy-pass] Call for adoption: draft-yun-cfrg-arc-01 (Ends 2025-09-30)
List-Id: Privacy Pass Protocol <privacy-pass.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/privacy-pass/--JXbGvkHnLq1iHQKJAnfn5eH9A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/privacy-pass>
List-Help: <mailto:privacy-pass-request@ietf.org?subject=help>
List-Owner: <mailto:privacy-pass-owner@ietf.org>
List-Post: <mailto:privacy-pass@ietf.org>
List-Subscribe: <mailto:privacy-pass-join@ietf.org>
List-Unsubscribe: <mailto:privacy-pass-leave@ietf.org>

Subject: Call for adoption: draft-yun-cfrg-arc-01  (Ends 2025-09-30)

This message starts a 3-week Call for Adoption for this document.

Abstract:
   This document specifies the Anonymous Rate-Limited Credential (ARC)
   protocol, a specialization of keyed-verification anonymous
   credentials with support for rate limiting.  ARC credentials can be
   presented from client to server up to some fixed number of times,
   where each presentation is cryptographically bound to client secrets
   and application-specific public information, such that each
   presentation is unlinkable from the others as well as the original
   credential creation.  ARC is useful in applications where a server
   needs to throttle or rate-limit access from anonymous clients.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-yun-cfrg-arc/

Please reply to this message keeping privacy-pass@ietf.org in copy by
indicating whether you support or not the adoption of this draft as a WG
document. Comments to motivate your preference are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/