Last Call: <draft-nottingham-how-did-that-get-into-the-repo-01.txt> (The secret-token URI Scheme) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 13 February 2020 14:21 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B66AE120106; Thu, 13 Feb 2020 06:21:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-nottingham-how-did-that-get-into-the-repo-01.txt> (The secret-token URI Scheme) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.117.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: alexey.melnikov@isode.com, superuser@gmail.com, draft-nottingham-how-did-that-get-into-the-repo@ietf.org
Content-Transfer-Encoding: 7bit
Reply-To: last-call@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <158160368967.20528.17627719451688873097.idtracker@ietfa.amsl.com>
Date: Thu, 13 Feb 2020 06:21:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/pJrPmBKiKBWK1Hm5C3RyBV9CrV8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2020 14:21:30 -0000

The IESG has received a request from an individual submitter to consider the
following document: - 'The secret-token URI Scheme'
  <draft-nottingham-how-did-that-get-into-the-repo-01.txt> as Informational
  RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-03-12. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document registers the "secret-token" URI scheme, to aid in the
   identification of authentication tokens.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-nottingham-how-did-that-get-into-the-repo/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-nottingham-how-did-that-get-into-the-repo/ballot/


No IPR declarations have been submitted directly on this I-D.