[CFRG] Performance improvements for Prio3
Christopher Patton <cpatton@cloudflare.com> Mon, 27 October 2025 16:23 UTC
Return-Path: <cpatton@cloudflare.com>
X-Original-To: cfrg@mail2.ietf.org
Delivered-To: cfrg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8D6757CEE017 for <cfrg@mail2.ietf.org>; Mon, 27 Oct 2025 09:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cloudflare.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FLPh5wuR9FPP for <cfrg@mail2.ietf.org>; Mon, 27 Oct 2025 09:23:17 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1E93A7CEE00A for <cfrg@irtf.org>; Mon, 27 Oct 2025 09:23:16 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id d75a77b69052e-4ed06acf75dso2389751cf.1 for <cfrg@irtf.org>; Mon, 27 Oct 2025 09:23:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google09082023; t=1761582196; x=1762186996; darn=irtf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=jdjLcrVNxG/8DsMit2S5s79l+Bqey9HTL7w/eUv6JkA=; b=N5gDBVzGg+yBB5I88YGmTQY/lw+HyJ16C80EFX75r81WoXXhj5001ZLvL0m/iq6W2A 2cJn1OdyHqL3Te4ayGPCee/7lOoipxVIfmcUY7qoGY/qZhKEL/bICWTIOV7l8tq2K3sv 75tjC+opnxGs/fm7XafUp6LEaoWaSDO8CBTYbIRpCCl2sI6DBaq8UA5/c/A32IKzw5Ar eq0r/UigD4cV00OQJLBAE/8tX0e9/vIOe7M+zcQLmpp2bpUCB2k1qbOl96rIh2GbBmGR y9681mVn7OhLxu49Y7DVOQG9vGtaCOhLRtkaytzgcRmgEZf+k514q5SrNnG8N/ZaD1Q5 05kA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761582196; x=1762186996; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=jdjLcrVNxG/8DsMit2S5s79l+Bqey9HTL7w/eUv6JkA=; b=GZv1Mx/vwOkax3kK7zJVhI/yoSxgqx7x5fEgmGcmdPsdsuNCgkjP1K0EQ4PJyPw4ae dXU9NLdkPOvmcVVg2rBYpb44D3fqHUu4GVlhdwJUy8haJk3LNJITATiZ4RvkiW2AZwQB V2NTHMrKiPXZtLcCTCg5qyG1rgEgGo72qJu1Xrhy5eebo04MHe5tfF3q46ynG2dZRRL4 EaPo3ctcUscpkQwGrWiXDVfuchXGR/FhXTerLBIDwG0jZgYTJS7nSv9mYwFPGmfSwfnU Y4D29HUtqS8vODZmhXKkdU3EVYBE2wr2SNEZBf2DbfrlsdhTkUQF0FTYhVPlyun9h5m3 trPg==
X-Forwarded-Encrypted: i=1; AJvYcCVf34quV1UIzY75vxtoxayjOJ1qWz7MYmIGN2tsrUrQ7fiqFTn1Ma39flDuQCSIWW5jIJii@irtf.org
X-Gm-Message-State: AOJu0Ywk5Ld4pjqT2w5CaayDrRdTz84reVrhrqQuWMmmletLOwbxk7xH d5wQ2pe3QxCG//1Gt7wRLxYR9U34Qk4ZaHlVYWHUUe5UfgcQzIRl+nDtpKlTtK1R9DJoPjGJ0qD YzkS7N7BOkAIEElro+66HtXPrF9DT4cc6JumPnfWPCw==
X-Gm-Gg: ASbGncszTqafiqRL36m9NG326uHd1QLrL/0MsLMUy7L8S558dUIHCv/imH6OyqXI2uB WhWbxiXN54JmUh2T+hIFmxoEA7OxFCqLFhSvV/AsnDx+pkP/Xcj6JB0q4g9q5U0ZF1UKpiWwS3a Rrw2AC5/lsnWWZqgL6AOZSdD+bHmx+x8Y6lV/f/8aOICj+1Zo2Xbn6Ot+4GmU7fa2BK/tPgt14B 2vjbfcCJoT3VVt9mlwCXFoHSpz+w8bcgs48jaL5Z3BPhD06OLDrs/oJ+TXZJojIPQU3IVPlFYLp cJY5NPhGiYpi
X-Google-Smtp-Source: AGHT+IHLXpjMdf4mYW4nEvCe4VVw0z84p2tpeSQdVTcoggBvfWaWLZFNe9tvyLlPR34AM+xwMk640+zNRY8MAUhSzu8=
X-Received: by 2002:a05:622a:5e16:b0:4e8:955b:ac0d with SMTP id d75a77b69052e-4ed08a0b56bmr493441cf.37.1761582195691; Mon, 27 Oct 2025 09:23:15 -0700 (PDT)
MIME-Version: 1.0
From: Christopher Patton <cpatton@cloudflare.com>
Date: Mon, 27 Oct 2025 09:23:04 -0700
X-Gm-Features: AWmQ_blPvjDBItN5Dd_SraES9n8WiEVHcAp0HK5IeXxcyA66zXttKy1KK8mu03w
Message-ID: <CAG2Zi23OWPAho94RDhAUy75KY3zCcwpabnWv0fah8jH-hR+1Dg@mail.gmail.com>
To: ppm <ppm@ietf.org>, CFRG <cfrg@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000000469d406422651ae"
Message-ID-Hash: XI56WPJPSIPCBFWFC2NZU3KMFAIC3X4J
X-Message-ID-Hash: XI56WPJPSIPCBFWFC2NZU3KMFAIC3X4J
X-MailFrom: cpatton@cloudflare.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cfrg.irtf.org-0; header-match-cfrg.irtf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [CFRG] Performance improvements for Prio3
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/Q07Ax_RYDp5IrYrNo74ZrtEMwgU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Owner: <mailto:cfrg-owner@irtf.org>
List-Post: <mailto:cfrg@irtf.org>
List-Subscribe: <mailto:cfrg-join@irtf.org>
List-Unsubscribe: <mailto:cfrg-leave@irtf.org>
Hi PPM + CFRG, The VDAF draft (draft-irtf-cfrg-vdaf) is just about ready for RGLC. We have completed panel review and addressed nearly all feedback. The two remaining issues are non-trivial: https://github.com/cfrg/draft-irtf-cfrg-vdaf/issues/549 points out an improved range check that would reduce the cost of the Sum circuit and make the SumVec circuit a lot more useful. This would be a breaking change because we're changing the circuits for the corresponding Prio3 instances. https://github.com/cfrg/draft-irtf-cfrg-vdaf/issues/574 points out an algorithmic improvement due to Armando Faz that siginifiantly reduces the runtime cost of proving and querying the FLP. This would also be a breaking change because it changes the representation of polynomials on the wire. (Armando will discuss that in more detail at CFRG next week.) The editors feel these improvements are significant enough that we should take them, even if that means RGLC. However, we would like to hear from implementers as well as CFRG participants at large before we do: 1. As an implementer, are you willing to make a breaking change at this point? 2. Is it appropriate to make these changes given that we've already completed panel review for this document? Thanks in advance, Chris P. on behalf of the editors
- [CFRG] Re: Performance improvements for Prio3 Christopher Patton
- [CFRG] Performance improvements for Prio3 Christopher Patton
- [CFRG] Re: [Ppm] Re: Performance improvements for… Tim Geoghegan
- [CFRG] Re: [Ppm] Re: Performance improvements for… David Cook
- [CFRG] Re: Performance improvements for Prio3 Christopher Patton