IETF Logo Mail Archive

Re: [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)

Mike Jones <Michael.Jones@microsoft.com> Tue, 14 August 2012 18:43 UTC

Return-Path: <Michael.Jones@microsoft.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 8541C21F8790 for <oauth@ietfa.amsl.com>; Tue, 14 Aug 2012 11:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level:
X-Spam-Status: No, score=-3.8 tagged_above=-999 required=5 tests=[AWL=-0.202, 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 HHnoTKWwm7lk for <oauth@ietfa.amsl.com>; Tue, 14 Aug 2012 11:43:26 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id C992A21F87A0 for <oauth@ietf.org>; Tue, 14 Aug 2012 11:43:26 -0700 (PDT)
Received: from mail200-co1-R.bigfish.com (10.243.78.244) by CO1EHSOBE007.bigfish.com (10.243.66.70) with Microsoft SMTP Server id 14.1.225.23; Tue, 14 Aug 2012 18:43:17 +0000
Received: from mail200-co1 (localhost [127.0.0.1]) by mail200-co1-R.bigfish.com (Postfix) with ESMTP id C9D66A20351; Tue, 14 Aug 2012 18:43:17 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14MLTC102.redmond.corp.microsoft.com; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: VS-20(zf7Iz9371Ic85fh4015I9a6kzz1202hzz1033IL8275bh8275dhz2fh2a8h668h839hd25hf0ah107ah)
Received-SPF: pass (mail200-co1: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=Michael.Jones@microsoft.com; helo=TK5EX14MLTC102.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail200-co1 (localhost.localdomain [127.0.0.1]) by mail200-co1 (MessageSwitch) id 1344969795638313_20956; Tue, 14 Aug 2012 18:43:15 +0000 (UTC)
Received: from CO1EHSMHS013.bigfish.com (unknown [10.243.78.242]) by mail200-co1.bigfish.com (Postfix) with ESMTP id 98FAE340044; Tue, 14 Aug 2012 18:43:15 +0000 (UTC)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.8) by CO1EHSMHS013.bigfish.com (10.243.66.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 14 Aug 2012 18:43:14 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.132]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.02.0298.005; Tue, 14 Aug 2012 18:43:13 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: William Mills <wmills_92105@yahoo.com>, Dick Hardt <dick.hardt@gmail.com>, "oauth@ietf.org WG" <oauth@ietf.org>
Thread-Topic: [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)
Thread-Index: AQHNdzNnM13UPCZ7D0qBrM7NqoksbZdX9JwAgAGz6tA=
Date: Tue, 14 Aug 2012 18:43:12 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943667777B8@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <rt-3.8.8-1361-1344626433-845.596670-7-0@icann.org> <B2C72DD9-FF38-4737-94C9-121527918BE4@gmail.com> <1344875668.20926.YahooMailNeo@web31807.mail.mud.yahoo.com>
In-Reply-To: <1344875668.20926.YahooMailNeo@web31807.mail.mud.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943667777B8TK5EX14MBXC283r_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Subject: Re: [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: Tue, 14 Aug 2012 18:43:29 -0000

"Specification Required" is correct, as that's what's used in OAuth Core.  I believe that the case insensitivity comes from RFC 2617, which for instance, seems to use "Basic" and "basic" interchangeably.

                                                                -- Mike

From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of William Mills
Sent: Monday, August 13, 2012 9:34 AM
To: Dick Hardt; oauth@ietf.org WG
Subject: Re: [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)

1) Is it a problem that everything here seems to have "specification required" for the "Registration Procedures"?

2) In HTTP Authentication schemes, is the case insensitivity implicit here? (I think so)

-bill



________________________________
From: Dick Hardt <dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>>
To: "oauth@ietf.org WG<mailto:oauth@ietf.org%20WG>" <oauth@ietf.org<mailto:oauth@ietf.org>>
Sent: Friday, August 10, 2012 1:04 PM
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)

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<mailto: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<mailto:mbj@microsoft.com>, dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>, oauth-chairs@tools.ietf.org<mailto:oauth-chairs@tools.ietf.org>, oauth-ads@tools.ietf.org<mailto:oauth-ads@tools.ietf.org>
Reply-To: drafts-approval@iana.org<mailto: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


_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email