diff --git a/cjpatton/54/1/draft-wang-ppm-dap-taskprov.html b/cjpatton/54/1/draft-wang-ppm-dap-taskprov.html index d942b9d..60e820f 100644 --- a/cjpatton/54/1/draft-wang-ppm-dap-taskprov.html +++ b/cjpatton/54/1/draft-wang-ppm-dap-taskprov.html @@ -1497,7 +1497,7 @@

Before a task can be executed, it is necessary to first provision the Clients, Aggregators, and Collector with the task's configuration. The core DAP specification does not define a mechanism for provisioning tasks. This section -describes a mechanism whose key feature is that task configuration is +describes a mechanism whose key feature is that task configuration is performed completely in-band, via HTTP request headers.

This method presumes the existence of a logical "task author" (written as "Author" hereafter) who is capable of pushing configurations to Clients. All @@ -1553,7 +1553,7 @@

4.2. Task Advertisement

-

To advertise a task to its peer, a Taskbind participant includes a header +

To advertise a task to its peer, a protocol participant includes a header "dap-taskprov" with a request incident to the task execution. The value is the TaskConfig structure defined Section 3.1, expanded into its URL-safe, unpadded Base 64 representation as specified in Sections 5 and 3.2 of [RFC4648].

diff --git a/cjpatton/54/1/draft-wang-ppm-dap-taskprov.txt b/cjpatton/54/1/draft-wang-ppm-dap-taskprov.txt index 2f4d027..1b3284f 100644 --- a/cjpatton/54/1/draft-wang-ppm-dap-taskprov.txt +++ b/cjpatton/54/1/draft-wang-ppm-dap-taskprov.txt @@ -417,7 +417,7 @@ struct { 4.2. Task Advertisement - To advertise a task to its peer, a Taskbind participant includes a + To advertise a task to its peer, a protocol participant includes a header "dap-taskprov" with a request incident to the task execution. The value is the TaskConfig structure defined Section 3.1, expanded into its URL-safe, unpadded Base 64 representation as specified in