Re: [w3ctag/design-reviews] ReportingObserver (#195)

@mnot and @reschke are better folks to ask than me. https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-01#section-1 (note the non-current draft number) discusses why not to use JSON in HTTP headers, but of course doesn't apply to payloads.

Note that the latest version of draft-reschke-http-jfv is https://tools.ietf.org/html/draft-reschke-http-jfv-08, not the -02 that the Reporting spec refers to.

If you go to Structured Headers, the difficulty is that `Report-To` is an array containing maps (so far we're good with a [Parameterised List](https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-06#section-3.3)), containing an [array](http://wicg.github.io/reporting/#endpoints-member) (uh-oh, but sometimes doable with a space-delimited string), containing maps (nope).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/195#issuecomment-396729800