Last Call: <draft-ietf-oauth-dyn-reg-24.txt> (OAuth 2.0 Dynamic Client Registration Protocol) to Proposed Standard

The IESG <> Mon, 02 March 2015 17:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 161971A1BCA; Mon, 2 Mar 2015 09:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9bN8aWnhFHz7; Mon, 2 Mar 2015 09:09:47 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id DC75E1A1BA7; Mon, 2 Mar 2015 09:09:47 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-oauth-dyn-reg-24.txt> (OAuth 2.0 Dynamic Client Registration Protocol) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 02 Mar 2015 09:09:47 -0800
Archived-At: <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 Mar 2015 17:09:49 -0000

The IESG has received a request from the Web Authorization Protocol WG
(oauth) to consider the following document:
- 'OAuth 2.0 Dynamic Client Registration Protocol'
  <draft-ietf-oauth-dyn-reg-24.txt> as Proposed Standard

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 mailing lists by 2015-03-16. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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

The file can be obtained via

IESG discussion can be tracked via

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