I had hoped it would be possible to re-generate the task config on the fly from the long-lived pre-shared key, but this turned out to be somewhat tricky in the implementation of draft-02. In the next draft we should consider what changes would be needed to avoid replicating this data.
The taskprov header should appear in all requests from Leader -> Helper for the aggregation and collection flows.l
If we re-generate the task config on-the-fly, then there is a chance of opting out of a task that we previously opted into. Should this be permissible in the spec? In practice it should be unlikely.
I had hoped it would be possible to re-generate the task config on the fly from the long-lived pre-shared key, but this turned out to be somewhat tricky in the implementation of draft-02. In the next draft we should consider what changes would be needed to avoid replicating this data.
See https://github.com/cloudflare/daphne/issues/257.