[OAUTH-WG] RFC 8176 on Authentication Method Reference Values

rfc-editor@rfc-editor.org Fri, 16 June 2017 23:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D238129536; Fri, 16 Jun 2017 16:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 JHfjsWVfgXWs; Fri, 16 Jun 2017 16:58:19 -0700 (PDT)
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 C85A7127601; Fri, 16 Jun 2017 16:58:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D4BB0B80E0C; Fri, 16 Jun 2017 16:58:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, oauth@ietf.org
Message-Id: <20170616235804.D4BB0B80E0C@rfc-editor.org>
Date: Fri, 16 Jun 2017 16:58:04 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/GbLaAO0r-iu5uXMXwy8G_fUvBHU>
Subject: [OAUTH-WG] RFC 8176 on Authentication Method Reference Values
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jun 2017 23:58:22 -0000

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

        
        RFC 8176

        Title:      Authentication Method Reference Values 
        Author:     M. Jones, 
                    P. Hunt,
                    A. Nadalin
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2017
        Mailbox:    mbj@microsoft.com, 
                    phil.hunt@yahoo.com, 
                    tonynad@microsoft.com
        Pages:      15
        Characters: 30765
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-oauth-amr-values-08.txt

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

        DOI:        10.17487/RFC8176

The "amr" (Authentication Methods References) claim is defined and
registered in the IANA "JSON Web Token Claims" registry, but no
standard Authentication Method Reference values are currently
defined.  This specification establishes a registry for
Authentication Method Reference values and defines an initial set of
Authentication Method Reference values.

This document is a product of the Web Authorization Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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