[CFRG] Re: Should we spell out the star topology for VDAFs?

Christopher Patton <cpatton@cloudflare.com> Mon, 05 August 2024 22:31 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 23191C1D52F5 for <cfrg@ietfa.amsl.com>; Mon, 5 Aug 2024 15:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 jTDeFVUjZrPV for <cfrg@ietfa.amsl.com>; Mon, 5 Aug 2024 15:31:47 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 5C411C1D52F3 for <cfrg@irtf.org>; Mon, 5 Aug 2024 15:31:47 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id d75a77b69052e-44ff398cefcso964521cf.0 for <cfrg@irtf.org>; Mon, 05 Aug 2024 15:31:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google09082023; t=1722897106; x=1723501906; darn=irtf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=moSx+zfXxOaBDJTNAr39DsjvoODsbf9/pBqPecZTLnM=; b=aKGhrMIucFuVYLrrcXlkaE903sIpM/sAVVW7d2db7UPOjpKMSzpjJYh4mFds/JXCjf bsgklrb5nJ7DNnH5yuYwdylR7jgNscvBWumLlAqY2uo+CMzky5wTMNjQQv1YTBi+Ubkd XhIDGeGZAXY85ovdGFjpXC0fgCOaH1nR+42Zmky7GqQ7OhLT05MggcA8JgKGK8BKTYd/ NoOIbPGJ1XIak7BYojenXIT5wk3uFUrNVvTD/E7AAg00jaFV5QD82IO/w57lLMEMUEKi 5qntMdZxu/EN0N4zfiv79vPx0uOAZ4/Avx02imq+GexI41UeoeG6fJESRT46XAz4dzvR Z6RQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722897106; x=1723501906; h=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=moSx+zfXxOaBDJTNAr39DsjvoODsbf9/pBqPecZTLnM=; b=G8EnsCEwlJR4n7SPsF/deNAFf/5FqdSQmiaeSgZTAV+HwKHbS+kJJoMurcrweogzI8 HBrblhK40BhZxZZ5i9lEeKbzwWFHf1DWE27YI3vFxzvg0c8mplcxDewNPgbefH+Qm5Sv nglwngqd+4LbU/YbQXc742M9tI7tc9pvs14wBV+/VVcff74AP36EpCAqeAXBwIXbaDZU cgricU864SbzvaNF2f1eLhFjYp2UR8VZq40Uyf/s2HjA4NOn5fOce4miAYaSEbn9gVb2 wLInr2IqolaqkGSQd+ezKGc+gdZuuRCvSB5EV/z4/zXveCabuSfof7/dsnTUbpAnrl69 +KrQ==
X-Forwarded-Encrypted: i=1; AJvYcCU0Bte/wSaJWQXKnsQeQGKZDVwF033OPQQtwowckaaQgK0DcWwCxIwt2454eOpd1adlgcCXS8gMw58EjG0D
X-Gm-Message-State: AOJu0YzlZB64wqlIUxIdTcpkTekGNqJAt3xrRcbecRSy4eKVZEwvoIVq 7bq3+iHRm7RHyV3QUQ0mAH7T9ZnkG8myafM8xv/bTYDK/+VVC5QBZTpGfpooROU40h3JL6iuVqz /tj4sZlLkGfcKB2FKmILkUUWMaAzPE3pLD8viorBt2Hjw5KmuqOs=
X-Google-Smtp-Source: AGHT+IGHUMap1rPfh+9N5F9k0lI7TKOB7u2vumSlXtj2BHrWMEASR6BQUjpKRDgCKbFBVW1ygoqaKvkM/xeSPVTTMNM=
X-Received: by 2002:a05:622a:4d09:b0:451:a12d:b9e7 with SMTP id d75a77b69052e-451a12dbddfmr135403921cf.12.1722897106135; Mon, 05 Aug 2024 15:31:46 -0700 (PDT)
MIME-Version: 1.0
References: <CAG2Zi20Dt=x5BYqR_6fzQ3pfMbf+EtqzcAfFRP2GcWBC5LvU7w@mail.gmail.com>
In-Reply-To: <CAG2Zi20Dt=x5BYqR_6fzQ3pfMbf+EtqzcAfFRP2GcWBC5LvU7w@mail.gmail.com>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Mon, 05 Aug 2024 15:31:27 -0700
Message-ID: <CAG2Zi21Kx5X4sEwAC8gvddkZQ5hM8_ORp+R5HOXU8uqvPirqcQ@mail.gmail.com>
To: ppm <ppm@ietf.org>, CFRG <cfrg@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000ff0a3d061ef73d4e"
Message-ID-Hash: RQVLM263PUW53MVE34VOLJZDTRLMCG5L
X-Message-ID-Hash: RQVLM263PUW53MVE34VOLJZDTRLMCG5L
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [CFRG] Re: Should we spell out the star topology for VDAFs?
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/NjpWkd4IU6DCErVJsC6EQFSyv_g>
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>

Here is a PR for closing the issue by just sketching the star topology:
https://github.com/cfrg/draft-irtf-cfrg-vdaf/pull/390

Best,
Chris P.

On Fri, Aug 2, 2024 at 5:26 PM Christopher Patton <cpatton@cloudflare.com>
wrote:

> Hi PPM+CFRG,
>
> I'd like to get some feedback on what to do about this issue for the VDAF
> draft:
> https://github.com/cfrg/draft-irtf-cfrg-vdaf/issues/261
>
> Prior to DAP draft 05, we envisioned a "star topology" in which there is a
> single leader and any number of helpers. The idea was that for each round
> of preparation, the leader would broadcast the prep message to each of the
> helpers: each helper would respond with its prep share for the next round,
> which the leader would use to compute the prep message for the next round,
> and so on. In draft 05 we decided to specialize the protocol for a single
> leader and helper and adopt the ping-pong topology [1], which requires
> fewer round trips over the network to finish.
>
> In theory, a future specification could execute a VDAF in a star topology,
> so it may be useful to spell this out. Note however that not all VDAFs
> support more than two aggregators: Prio3 does, but Poplar1 doesn't.
>
> The VDAF draft spells out ping ponging in full detail. This is necessary
> because the DAP draft consumes this API directly. Do folks think we should
> spell out the star topology in the same level of detail?
>
> Since we don't currently have a use case for it, I don't think it's
> necessary to spell out in full detail. I suggest we just sketch it instead.
>
> Thanks!
> Chris P.
>
> [1]
> https://www.ietf.org/archive/id/draft-irtf-cfrg-vdaf-10.html#section-5.8
>