The secret-token URI Scheme
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: firstname.lastname@example.org, The IESG <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Document Action: 'The secret-token URI Scheme' to Informational RFC (draft-nottingham-how-did-that-get-into-the-repo-01.txt) The IESG has approved the following document: - 'The secret-token URI Scheme' (draft-nottingham-how-did-that-get-into-the-repo-01.txt) as Informational RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Murray Kucherawy. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-nottingham-how-did-that-get-into-the-repo/
Technical Summary This document registers the "secret-token" URI scheme, to aid in the identification of authentication tokens. Working Group Summary This is an AD-sponsored document. It was discussed in DISPATCH/ARTAREA and had general support there. Document Quality There has been ample discussion in support of this proposal, largely on the ART list. I have not been able to find specific records of intent to support it, but I remember in the discussion at DISPATCH some meetings back that it would be in use (or is already in use?) at Github, for starters. Personnel Alexey Melnikov is the document shepherd. Murray Kucherawy is the responsible Area Director. Murray did the shepherd writeup before he and Alexey swapped roles.