[OAUTH-WG] RFC 7591 on OAuth 2.0 Dynamic Client Registration Protocol

rfc-editor@rfc-editor.org Thu, 09 July 2015 23:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id B64041A6F13; Thu, 9 Jul 2015 16:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xaOnJFDqqa7f; Thu, 9 Jul 2015 16:20:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 640DC1A6F0E; Thu, 9 Jul 2015 16:20:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B1689180206; Thu, 9 Jul 2015 16:17:07 -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
Message-Id: <20150709231707.B1689180206@rfc-editor.org>
Date: Thu, 9 Jul 2015 16:17:07 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/QKkjcpaRS0vbl4WVAkwrkknl8Yg>
Cc: drafts-update-ref@iana.org, oauth@ietf.org, rfc-editor@rfc-editor.org
Subject: [OAUTH-WG] RFC 7591 on OAuth 2.0 Dynamic Client Registration Protocol
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 09 Jul 2015 23:20:46 -0000

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

        RFC 7591

        Title:      OAuth 2.0 Dynamic Client Registration 
        Author:     J. Richer, Ed.,
                    M. Jones, 
                    J. Bradley,
                    M. Machulak,
                    P. Hunt
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2015
        Mailbox:    ietf@justin.richer.org, 
        Pages:      39
        Characters: 87811
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-oauth-dyn-reg-30.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7591

This specification defines mechanisms for dynamically registering
OAuth 2.0 clients with authorization servers.  Registration requests
send a set of desired client metadata values to the authorization
server.  The resulting registration responses return a client
identifier to use at the authorization server and the client metadata
values registered for the client.  The client can then use this
registration information to communicate with the authorization server
using the OAuth 2.0 protocol.  This specification also defines a set
of common client metadata fields and values for clients to use during

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

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

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