[CFRG] Re: Comment on draft-irtf-cfrg-vdaf

Christopher Patton <cpatton@cloudflare.com> Tue, 20 August 2024 17:52 UTC

Return-Path: <cpatton@cloudflare.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD5BC169434 for <cfrg@ietfa.amsl.com>; Tue, 20 Aug 2024 10:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cloudflare.com
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 TGM3lJrRcV2m for <cfrg@ietfa.amsl.com>; Tue, 20 Aug 2024 10:52:53 -0700 (PDT)
Received: from mail-oo1-xc36.google.com (mail-oo1-xc36.google.com [IPv6:2607:f8b0:4864:20::c36]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 1E00DC14CE51 for <cfrg@ietf.org>; Tue, 20 Aug 2024 10:52:53 -0700 (PDT)
Received: by mail-oo1-xc36.google.com with SMTP id 006d021491bc7-5d5bb03fe42so3312616eaf.3 for <cfrg@ietf.org>; Tue, 20 Aug 2024 10:52:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google09082023; t=1724176372; x=1724781172; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c9iC6x9UT3cw0p60dHPh3ApPx2UYWPExBat0tG3CwmI=; b=XqB5/acY/jm4U1mnAKE/Rjtb1EA0iFqAeHRS9+3VB382CSV8T2vbTjGjz8he4hHiyI apYtDow6VXAdLWczWHkLlX+5Exq3xv+GkkoR8b+R5k/oXO5Zq64UETe1fBeSEcZsg4+m Ib6KvHGf23WfITEWh5FtvcByY+zLV5CrlUyUtw6lA7CxhxwuEM8LCB3Re4A9TcykuC3e FOgbJ7w2rvGaUKQDew/raKyc5xSK40ia+hcb9FrfwKBUK5GsVhL0tfswUh0vrI+S0Ulo ZD/00OaaBUHKi0OgTff1urs6CnzPw59f0gHuT3Ezd6Sdr5jv99zziiLmAQELTZF/il2K ylgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724176372; x=1724781172; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=c9iC6x9UT3cw0p60dHPh3ApPx2UYWPExBat0tG3CwmI=; b=KlMxTOFMsdQoBDaO/tIf9vj3zaFIqbK0mlqcNDviIfdKS1tltlP1POMUp3KRI90Zgx rdzlVD6G6AAZFqLUvKHIgWgp47gEUmWPtvXErXzbQHfz1TQHs+PB02HvKsb0ASjKd7v0 FUNTpMrkqo1vmiQUZeSYeQEnU1y1Gw3uCYPUIxOBHx5Oo3WwuS92qQMLX2qqLfmT6C10 NEPdkDNlas2oYRE5X8IkaqJe34A2dioZurYwxu92apwDdZ8QmkSv/nP9B23qwpyP3U/k mDNGeNIxybHnIj+quUlmUcsfr3p+TneFIZ2l+25a5J0bG4Og4T+TmpWYhObouuD4faGu 386w==
X-Gm-Message-State: AOJu0Yyv0erPZnTWmXQPqEbCO8bXQt7YI4kqkXPUakaY0dHnovm/tnct gV1le4J9ntiFQBtE42bepFToKmei25HtuK3glklh996SkZjtJ4dTPaLYbrKdHOMC56cXmp3Eamo +ICxKQe0UFFGu7e7Vwk8XleAmc5ef2a+Y3E3fgFAaZE6FTdxlACc=
X-Google-Smtp-Source: AGHT+IFqdU8g3tykBgwz4d2tkZE9/6zb3vJjbTEkN1VjwGQ8vUFDOeE5Z7pKtW7oTwzEIina1sb+XcLvGUArzWO8N5o=
X-Received: by 2002:a05:6358:60c3:b0:1b1:ac2e:b30f with SMTP id e5c5f4694b2df-1b59fce1ac4mr17361355d.21.1724176371877; Tue, 20 Aug 2024 10:52:51 -0700 (PDT)
MIME-Version: 1.0
References: <AM9PR10MB50058DF8751EEC48B45E0839F28D2@AM9PR10MB5005.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <AM9PR10MB50058DF8751EEC48B45E0839F28D2@AM9PR10MB5005.EURPRD10.PROD.OUTLOOK.COM>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Tue, 20 Aug 2024 10:52:40 -0700
Message-ID: <CAG2Zi21wHaStkcEuPDiBjqK8VMQMNFLC7_ppSF-Vwes4-W+ptA@mail.gmail.com>
To: Gilles VAN ASSCHE <gilles.vanassche=40st.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002d516d06202118ca"
Message-ID-Hash: 64YHC4KCK6FB57BBOYXJP2S5X5RZNFDN
X-Message-ID-Hash: 64YHC4KCK6FB57BBOYXJP2S5X5RZNFDN
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; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "cfrg@ietf.org" <cfrg@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [CFRG] Re: Comment on draft-irtf-cfrg-vdaf
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/uhbnhRnic7uYlMQ3Yj-160Dxhkg>
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>

Thanks Gilles, this is a great suggestion. I'll benchmark and report back.

Chris P.

On Tue, Aug 20, 2024 at 8:17 AM Gilles VAN ASSCHE <gilles.vanassche=
40st.com@dmarc.ietf.org> wrote:

> Hi Chris,
>
> I just wanted to comment on something you wrote recently about
> draft-irtf-cfrg-vdaf and its use of TurboSHAKE:
>
> > I'll add my own data point: draft-irtf-cfrg-vdaf. This draft specifies
> an incremental distributed point function (IDPF), a type of function secret
> sharing used in some MPC protocols. Most of the computation is spent on XOF
> evaluation. For performance reasons, we try to use AES wherever we can in
> order to get hardware support. We end up with a mix of TurboSHAKE128 and
> AES, which is not ideal. It would be much nicer if we could afford to use a
> dedicated XOF, but TurboSHAKE128 is not fast enough in software.
>
> A simple way to improve the throughput of TurboSHAKE's output in this
> application would be to use it in counter mode. This would allow platforms
> that support SIMD instructions to get a significant speed-up (e.g., 3× with
> AVX2 on a typical Haswell or Skylake architecture).
>
> More specifically, this would work like XofFixedKeyAes128 to produce a
> fixed key. But, instead of using AES in counter mode, you could concatenate
> the outputs of TurboSHAKE128(fixed key || i, D, 168) with i a running
> counter coded on a fixed number of bits and D an available domain
> separation value. Parallelizing using SIMD instructions then becomes
> straightforward.
>
> Kind regards,
> Gilles
>
>