Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements

I don't think that is possible, unfortunately.  A non-rec-track best practice note cannot create new HTTP headers such as Accept-Profile. As far as I understand [Process](, the equivalent [RFC2026]( and the IETF/W3C [liaison process](, we can sponsor an RFC that will be well received (but not rubber stamped) because IETF recognizes the W3C process as sufficiently robust to generate appropriate quality specifications. We should discuss with Heather Flanagan and Mark Nottingham, hopefully before TPAC to avoid leaving it down to the wire.

If the group does not consider the registration of the Accept-Profile header with IETF to be in scope, then it should probably recharter as it cannot fulfill its deliverables, as there won't be an RFC to reference.

GitHub Notification of comment by azaroth42
Please view or discuss this issue at using your GitHub account

Received on Monday, 25 June 2018 22:40:28 UTC