[OAUTH-WG] Fwd: [IANA #596670] Protocol Action: 'The OAuth 2.0 Authorization Framework: Bearer Token Usage' to Proposed Standard (draft-ietf-oauth-v2-bearer-23.txt)

Dick Hardt <dick.hardt@gmail.com> Fri, 10 August 2012 20:04 UTC

Return-Path: <dick.hardt@gmail.com>
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 E2A3021F8694 for <oauth@ietfa.amsl.com>; Fri, 10 Aug 2012 13:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.572
X-Spam-Level:
X-Spam-Status: No, score=-3.572 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kgUdvBxjXNpB for <oauth@ietfa.amsl.com>; Fri, 10 Aug 2012 13:04:43 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1B01621F8690 for <oauth@ietf.org>; Fri, 10 Aug 2012 13:04:43 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so3215688pbb.31 for <oauth@ietf.org>; Fri, 10 Aug 2012 13:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version:x-mailer; bh=OPbvhELwMOyEeYP1+WqCeCLewAHtNTGcb6lquM1uruY=; b=SC0h3gzO5GSuRnpvTnmOnOtXU8lZ0RH0EaK31TDPEG4ntTqI2vL8BH9s+aC5iVQT3w sHDxcySHg//u/1Rel+gGqVQPyNesUj7QpiY1rY1DYE0Vj3HhnW8BBkZbybim8mPpLTU6 xW+XoCqk20pAQy5iVKB5XdEkqJDpf9o4NVhI9bfjd9E8UXSDBs4wGD12Y/Bm77j61DI/ WiH5oRAoaCl09GivuKr+YpMtvh5vjhbw8v2ulsnaRQApdvKzN23sEPYYPjci3zrjdNNH O8jPXM65jZhGK8I5myF5+eUDYPkJiCe5VbpLyffdi7UWKJmvjEcY7kGVqBYl4Re1Zdir c4Hw==
Received: by 10.68.239.103 with SMTP id vr7mr260746pbc.0.1344629082866; Fri, 10 Aug 2012 13:04:42 -0700 (PDT)
Received: from [10.0.0.4] (c-24-5-69-173.hsd1.ca.comcast.net. [24.5.69.173]) by mx.google.com with ESMTPS id st6sm2586368pbc.58.2012.08.10.13.04.32 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Aug 2012 13:04:39 -0700 (PDT)
From: Dick Hardt <dick.hardt@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CE471CD6-41F0-437D-8ED1-F7F14462AD5F"
Date: Fri, 10 Aug 2012 13:04:31 -0700
References: <rt-3.8.8-1361-1344626433-845.596670-7-0@icann.org>
To: "oauth@ietf.org WG" <oauth@ietf.org>
Message-Id: <B2C72DD9-FF38-4737-94C9-121527918BE4@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: [OAUTH-WG] Fwd: [IANA #596670] Protocol Action: 'The OAuth 2.0 Authorization Framework: Bearer Token Usage' to Proposed Standard (draft-ietf-oauth-v2-bearer-23.txt)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 10 Aug 2012 20:04:44 -0000

Once again, would be great to have a few more eyes checking the IANA registrations. 

Note these are for the Bearer Token spec. 

I like that the error registry items are sorted alphabetically already. :)

Begin forwarded message:

> From: "Amanda Baber via RT" <drafts-approval@iana.org>
> Subject: [IANA #596670] Protocol Action: 'The OAuth 2.0 Authorization Framework: Bearer Token Usage' to Proposed Standard (draft-ietf-oauth-v2-bearer-23.txt) 
> Date: August 10, 2012 12:20:33 PM PDT
> Cc: mbj@microsoft.com, dick.hardt@gmail.com, oauth-chairs@tools.ietf.org, oauth-ads@tools.ietf.org
> Reply-To: drafts-approval@iana.org
> 
> Dear Authors:
> 
> ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED 
> 
> We have completed the IANA Actions for RFC-to-be
> draft-ietf-oauth-v2-bearer-23
> 
> ACTION 1:
> 
> IANA has registered the following OAuth Access Token Type:
> 
> Name: Bearer
> Additional Endpoint Response Parameters: 
> HTTP Authentication Scheme(s): Bearer 
> Change Controller: IETF          
> Reference: [RFC-ietf-oauth-v2-bearer-23]
> 
> Please see
> http://www.iana.org/assignments/oauth-parameters
> 
> 
> ACTION 2:
> 
> IANA has registered the following in the OAuth Extensions Error Registry:
> 
> invalid_request  
> Usage Location: Resource access error response  
> Protocol Extension: Bearer access token type  
> Change Controller: IETF  
> Reference: [RFC-ietf-oauth-v2-bearer-23]
> 
> invalid_token
> Usage Location: Resource access error response  
> Protocol Extension: Bearer access token type  
> Change Controller: IETF  
> Reference: [RFC-ietf-oauth-v2-bearer-23]
> 
> insufficient_scope
> Usage Location: Resource access error response  
> Protocol Extension: Bearer access token type  
> Change Controller: IETF  
> Reference: [RFC-ietf-oauth-v2-bearer-23]
> 
> Please see
> http://www.iana.org/assignments/oauth-parameters
> 
> 
> Please let us know whether the above IANA Actions look OK. As 
> soon as we receive your confirmation, we'll notify the RFC Editor 
> that this document's IANA Actions are complete. (If this document 
> has a team of authors, one reply on behalf of everyone will suffice.)
> 
> Thanks,
> 
> Amanda Baber
> ICANN/IANA
>