Make terminology more consistent with the rest of the document
Move the note about multi-collection to the end of the section
Change the architecture diagram to illustrate who makes requests
Get rid of the "Aggregator" bullet in the list of participants because it's redundant (it's already clear that Leader and Helper are types of Aggregators)
Mention that not all task parameters are distributed to all parties
Remove the following, which is not super relevant (delayed aggregation will be the exception rather than the rule once we do https://github.com/ietf-wg-ppm/draft-ietf-ppm-dap/issues/581; and it's rare enough to not mention in the overview).
Depending on the VDAF, it may be possible to incrementally process
each report as it comes in, or may be necessary to wait until the
entire batch of reports is received.
cjpatton
commented
1 month ago
Stacked on #615.
Main changes:
Align mathematical notation with the VDAF draft
Make terminology more consistent with the rest of the document
Move the note about multi-collection to the end of the section
Change the architecture diagram to illustrate who makes requests
Get rid of the "Aggregator" bullet in the list of participants because it's redundant (it's already clear that Leader and Helper are types of Aggregators)
Mention that not all task parameters are distributed to all parties
Remove the following, which is not super relevant (delayed aggregation will be the exception rather than the rule once we do https://github.com/ietf-wg-ppm/draft-ietf-ppm-dap/issues/581; and it's rare enough to not mention in the overview).
Define "VDAF preparation" more clearly