From 94f9cbc99ab4686892ace38fff389e9b041e544d Mon Sep 17 00:00:00 2001 From: ID Bot Date: Mon, 2 Dec 2024 18:22:55 +0000 Subject: [PATCH] Script updating gh-pages from 24baddf. [ci skip] --- draft-ietf-ppm-dap-taskprov.html | 8 ++++---- draft-ietf-ppm-dap-taskprov.txt | 10 +++++----- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/draft-ietf-ppm-dap-taskprov.html b/draft-ietf-ppm-dap-taskprov.html index 81ec476..740c8c0 100644 --- a/draft-ietf-ppm-dap-taskprov.html +++ b/draft-ietf-ppm-dap-taskprov.html @@ -1302,7 +1302,7 @@

agreement on the task parameters. On the other hand, disagreement between a Client and the Aggregators should prevent reports uploaded by that Client from being processed.

-

Section 3 specifies a report extension (Section 4.4.3 of [DAP]) that +

Section 3 specifies a report extension (Section 4.5.3 of [DAP]) that endows DAP with this property. First, it specifies an encoding of all task parameters that are relevant to all parties. This excludes cryptographic assets, such as the secret VDAF verification key (Section 5 of [VDAF]) or @@ -1421,7 +1421,7 @@

3. The Taskbind Extension

To use the Taskbind extension, the Client includes the following extension in -the report extensions for each Aggregator as described in Section 4.4.3 of [DAP]:

+the report extensions for each Aggregator as described in Section 4.5.3 of [DAP]:

 enum {
@@ -1557,7 +1557,7 @@ 

 
This section defines the payload of TaskConfig.vdaf_config for each VDAF
 specified in [VDAF]. In some cases, the VDAF supports more than two
 Aggregators; but since DAP only supports two Aggregators, we do not include the
-number of Aggregators in the encoding (cf. Appendix C of [VDAF]).

+number of Aggregators in the encoding (cf. Section 7 of [VDAF]).

 

 

           

@@ -2030,7 +2030,7 @@ 

         

 
The following entry will be (RFC EDITOR: change "will be" to "has been") added
 to the "Report Extension Identifiers" registry of the "Distributed Aggregation
-Protocol (DAP)" page created by [VDAF]:

+Protocol (DAP)" page created by [DAP]:

 

           
Value:

           

diff --git a/draft-ietf-ppm-dap-taskprov.txt b/draft-ietf-ppm-dap-taskprov.txt
index 4b3c4f8..ee1873a 100644
--- a/draft-ietf-ppm-dap-taskprov.txt
+++ b/draft-ietf-ppm-dap-taskprov.txt
@@ -133,7 +133,7 @@ Table of Contents
    hand, disagreement between a Client and the Aggregators should
    prevent reports uploaded by that Client from being processed.
 
-   Section 3 specifies a report extension (Section 4.4.3 of [DAP]) that
+   Section 3 specifies a report extension (Section 4.5.3 of [DAP]) that
    endows DAP with this property.  First, it specifies an encoding of
    all task parameters that are relevant to all parties.  This excludes
    cryptographic assets, such as the secret VDAF verification key
@@ -227,7 +227,7 @@ Table of Contents
 
    To use the Taskbind extension, the Client includes the following
    extension in the report extensions for each Aggregator as described
-   in Section 4.4.3 of [DAP]:
+   in Section 4.5.3 of [DAP]:
 
    enum {
        taskbind(0xff00),
@@ -359,8 +359,8 @@ Table of Contents
    This section defines the payload of TaskConfig.vdaf_config for each
    VDAF specified in [VDAF].  In some cases, the VDAF supports more than
    two Aggregators; but since DAP only supports two Aggregators, we do
-   not include the number of Aggregators in the encoding (cf.
-   Appendix C of [VDAF]).
+   not include the number of Aggregators in the encoding (cf.  Section 7
+   of [VDAF]).
 
 3.2.1.  Prio3Count
 
@@ -761,7 +761,7 @@ Table of Contents
 
    The following entry will be (RFC EDITOR: change "will be" to "has
    been") added to the "Report Extension Identifiers" registry of the
-   "Distributed Aggregation Protocol (DAP)" page created by [VDAF]:
+   "Distributed Aggregation Protocol (DAP)" page created by [DAP]:
 
    Value:  0xff00