The "secret-token" URI Scheme
draft-nottingham-how-did-that-get-into-the-repo-02

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, rfc-editor@rfc-editor.org, draft-nottingham-how-did-that-get-into-the-repo@ietf.org, The IESG <iesg@ietf.org>, superuser@gmail.com, alexey.melnikov@isode.com
Subject: Document Action: 'The secret-token URI Scheme' to Informational RFC (draft-nottingham-how-did-that-get-into-the-repo-02.txt)

The IESG has approved the following document:
- 'The secret-token URI Scheme'
  (draft-nottingham-how-did-that-get-into-the-repo-02.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/

Ballot Text

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.

RFC Editor Note