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

Brandon Pitman <bran@divviup.org> Wed, 07 August 2024 22:58 UTC

Return-Path: <bran@divviup.org>
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 4E67FC14F6E2 for <cfrg@ietfa.amsl.com>; Wed, 7 Aug 2024 15:58:35 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=divviup.org
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 kOaM0zi8f8fm for <cfrg@ietfa.amsl.com>; Wed, 7 Aug 2024 15:58:31 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 A4BADC1840FA for <cfrg@irtf.org>; Wed, 7 Aug 2024 15:58:31 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-70d28023accso390644b3a.0 for <cfrg@irtf.org>; Wed, 07 Aug 2024 15:58:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=divviup.org; s=google; t=1723071511; x=1723676311; darn=irtf.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=ZSm0eqkHovTdbpx+LNzG5GWxR0BI+pdhmUikRHkpenM=; b=VSRSVii9Gh4Lw+UwnhR/de/P+qLtmIajRnSbSk9tg2vOQZzBJ0Wz2IoVsF//30H0d8 SFOuLnMOTX0Zg3+s5or0662o8g6NMdiH6u8r7qIhEowbZ+N0RI/HXEAS3pZ+t8rzjltB sOagOn7yPMm8meHGjKAmQ/IuELpQ89STD0b19IkNqwVEjYGmiBrKkkUCa8XJm2ihJ++K jlDkc9fRmT9Z+C/AOMydbuyXcQkNUngD9T06vQSq6UUlnRZfyx4dFW5szeYWMnlhZv0w mN5iPUwgvY8hq+hZxB5l+0PFdwrMHrATxvv7ipxxzy6VAfGwVldlWz37XxWxbdZZmjlo YXhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723071511; x=1723676311; 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=ZSm0eqkHovTdbpx+LNzG5GWxR0BI+pdhmUikRHkpenM=; b=L3+cC+rt8XLdZEh71JmRZssrR8xd0l/axOiANT4joN8VLNcCxAQNXYqCDXdiu9yidd Ux/gtB4N/+OigtLzQP4/kVt+IXRWKbPQEHZuFks26wUzSJbfuY6XtjL+dp9Wo2gGVurV BRz5hetGW4LSTEr804PRLPLZuCK04a6PHMtLf5fmNfzwMkdeCmVQ7AdA+kVZV/i5jyXL Ld/Y/SsEUREcKKF8A4PI6NfL3jHJ7gIJ2K00sLvonuSUPjfUXtKFQETDURgN/2riH3M3 jbB9U+xZ1oe3esCzXozfe0Hrj+ESG7z59p/9lQ2Y9BH3cE9hzyqOxtTC8OChABy2lIAF Q2Ww==
X-Forwarded-Encrypted: i=1; AJvYcCV1/QbcsPliI+7DkHe5+dkBwI/+ndcwJRpXrzSVKscOLPLR7DpW5LWC08zTyYX3Dc9gvTbS/Kbsc1paODL4
X-Gm-Message-State: AOJu0YyyHs9vHL4PdYCIS7R1HKRfKkEUoU8ER2FMqSZoDBuCRUQ60aHo PRJTmQV45D1vkHz2uLqGZirjhbZJ5CDXhdFN7ssQGsqIznGObEvPWbPrbPfrXv1T+/Zi9v6WwM3 cWfi5NqOxZ49Uw1Kwyifr8oUfbbvoEYVjrnbF+1L/bRBLyeEqKmQ=
X-Google-Smtp-Source: AGHT+IGXfgcE3qiXMfkhPmD6NZYP8tvwyjG5tS1zM53zi7iE0ieLhonREoJyr8PBoWcoOkHdD98RmI2zHui+LZ79jGs=
X-Received: by 2002:a05:6a00:1891:b0:70d:2a4d:2eeb with SMTP id d2e1a72fcca58-710cad3f97amr191066b3a.3.1723071510979; Wed, 07 Aug 2024 15:58:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAG2Zi20Dt=x5BYqR_6fzQ3pfMbf+EtqzcAfFRP2GcWBC5LvU7w@mail.gmail.com> <CAG2Zi21Kx5X4sEwAC8gvddkZQ5hM8_ORp+R5HOXU8uqvPirqcQ@mail.gmail.com>
In-Reply-To: <CAG2Zi21Kx5X4sEwAC8gvddkZQ5hM8_ORp+R5HOXU8uqvPirqcQ@mail.gmail.com>
From: Brandon Pitman <bran@divviup.org>
Date: Wed, 07 Aug 2024 15:58:20 -0700
Message-ID: <CALbTCT2-Ufz3rt=Rf6TFRT_pZFOfVKVRo8MMdyFRFDaVkjEpEQ@mail.gmail.com>
To: Christopher Patton <cpatton=40cloudflare.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000055c464061f1fd9b9"
Message-ID-Hash: HQK6HGASAT3RCCATRQB4KIHVUDOEXZBC
X-Message-ID-Hash: HQK6HGASAT3RCCATRQB4KIHVUDOEXZBC
X-MailFrom: bran@divviup.org
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: ppm <ppm@ietf.org>, CFRG <cfrg@irtf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [CFRG] Re: [Ppm] 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/j4rujHjqmQ6X6Rl5v6DAGi2ZxgU>
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>

I think it's OK to just sketch out the star topology, for a few reasons:

1) We don't have a current consumer for this topology.
2) This topology is simpler than the ping-pong topology, and is close to a
direct usage of the VDAF interface -- section 5.2
<https://www.ietf.org/archive/id/draft-irtf-cfrg-vdaf-10.html#section-5.2>
roughly lays out the communication pattern of this topology.

Thanks,
Bran

On Mon, Aug 5, 2024 at 3:34 PM Christopher Patton <cpatton=
40cloudflare.com@dmarc.ietf.org> wrote:

> 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
>>
> --
> Ppm mailing list -- ppm@ietf.org
> To unsubscribe send an email to ppm-leave@ietf.org
>