Consider using Structured Fields to define ADPC headers

[mnot]

See the specification.

The advantages are that the parsing and serialisation rules are already defined for you, avoiding the security and interoperability issues of defining your own syntax (or not defining it).

Happy to help with the integration if there's interest. Also, you might want to get some early review from the W3C TAG and the HTTP WG to help identify issues early.

[gb-noyb]

Structured Field Values looks like a good idea, I wish we knew about them before starting on this spec. I suppose that adopting this now would require some syntactic changes, which could however be worth it. Thanks for offering to help with this! I would not want to waste your time though, so perhaps we’d better first make sure that we are happy with the content/semantics before putting more effort in the syntax details.