Re: Request to register 2 new HTTP field names

Thanks for your thoughts, Jeffrey -- we'll be processing the request in due time.

Cheers,


> On 5 Feb 2025, at 11:11 am, Jeffrey Yasskin <jyasskin@google.com> wrote:
> 
> https://github.com/protocol-registries/http-fields?tab=readme-ov-file#creating-a-registration-request says the necessary information is
>     • 
> Field name
>     • Status
>     • Specification document(s)
>     • Comments
> all of which Chris provided, for both fields. Perhaps these should be "provisional" instead of "permanent" if the experts decide that they're not in enough use, but just telling Chris to read the documentation, which he clearly already read, doesn't help get that change made.
> 
> Jeffrey
> 
> On Tue, Feb 4, 2025 at 4:06 PM Mark Nottingham <mnot@mnot.net> wrote:
> It is -- it's just that the GitHub page has all of the necessary information.
> 
> Cheers,
> 
> 
> > On 5 Feb 2025, at 11:04 am, Jeffrey Yasskin <jyasskin@google.com> wrote:
> > 
> > If the mailing list is no longer an option for field registration requests, it'd be good to remove it from https://github.com/protocol-registries/http-fields?tab=readme-ov-file#submitting-your-request, https://www.iana.org/assignments/http-fields/http-fields.xhtml#:~:text=or%20the%20mailing%20list, and https://www.rfc-editor.org/rfc/rfc9110.html#name-field-name-registry:~:text=sending%20an%20email.
> > 
> > Jeffrey
> > 
> > On Tue, Feb 4, 2025 at 3:29 PM Mark Nottingham <mnot@mnot.net> wrote:
> > Hi Chris,
> > 
> > See in particular <https://github.com/protocol-registries/http-fields>.
> > 
> > 
> > > On 5 Feb 2025, at 3:44 am, Julian Reschke <julian.reschke@gmx.de> wrote:
> > > 
> > > On 04.02.2025 17:25, Chris Fredrickson wrote:
> > >> Hello,
> > >> 
> > >> I would like to register two new HTTP field names:
> > >> 
> > >> Field name: Sec-Fetch-Storage-Access
> > >> Status: permanent
> > >> Structured type: Token
> > >> Specification document: https://privacycg.github.io/storage-access-headers/
> > >> 
> > >> Field name: Activate-Storage-Access
> > >> Status: permanent
> > >> Structured type: Item
> > >> Specification document: https://privacycg.github.io/storage-access-headers/
> > >> 
> > >> 
> > >> Comments: These field names are in use in Google Chrome (as of Chrome 133),
> > >> with positive signals from other browser vendors (Mozilla
> > >> <https://github.com/mozilla/standards-positions/issues/1084>, Apple
> > >> <https://github.com/WebKit/standards-positions/issues/412>).
> > >> 
> > >> Please let me know if any other information would be useful/necessary for
> > >> this request. Thank you!
> > >> 
> > >> Chris
> > > 
> > > <https://www.rfc-editor.org/rfc/rfc9110.html#fields.extensibility> might
> > > be helpful.
> > > 
> > > Best regards, Julian
> > > 
> > 
> > --
> > Mark Nottingham   https://www.mnot.net/
> > 
> > 
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 

--
Mark Nottingham   https://www.mnot.net/

Received on Wednesday, 5 February 2025 00:13:02 UTC