RFC 8959 on The "secret-token" URI Scheme

rfc-editor@rfc-editor.org Fri, 29 January 2021 20:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2A33A12B1 for <ietf-announce@ietfa.amsl.com>; Fri, 29 Jan 2021 12:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zaoAywKJR-d9 for <ietf-announce@ietfa.amsl.com>; Fri, 29 Jan 2021 12:33:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3D003A12AF for <ietf-announce@ietf.org>; Fri, 29 Jan 2021 12:33:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5E907F4071B; Fri, 29 Jan 2021 12:32:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8959 on The "secret-token" URI Scheme
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210129203259.5E907F4071B@rfc-editor.org>
Date: Fri, 29 Jan 2021 12:32:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/rqJyryEBT3wbLFVCjn-3fdF1AyQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 29 Jan 2021 20:33:09 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8959

        Title:      The "secret-token" URI Scheme 
        Author:     M. Nottingham
        Status:     Informational
        Stream:     IETF
        Date:       January 2021
        Mailbox:    mnot@mnot.net
        Pages:      5
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-nottingham-how-did-that-get-into-the-repo-02.txt

        URL:        https://www.rfc-editor.org/info/rfc8959

        DOI:        10.17487/RFC8959

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC