Return-Path: 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 E4C3521E803D for ; Tue, 14 Aug 2012 11:51:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.711 X-Spam-Level: X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 M0eLO1THnzdr for ; Tue, 14 Aug 2012 11:51:21 -0700 (PDT) Received: from nm20-vm0.bullet.mail.ne1.yahoo.com (nm20-vm0.bullet.mail.ne1.yahoo.com [98.138.91.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9F87521E803C for ; Tue, 14 Aug 2012 11:51:21 -0700 (PDT) Received: from [98.138.90.57] by nm20.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2012 18:51:21 -0000 Received: from [98.138.226.164] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2012 18:51:21 -0000 Received: from [127.0.0.1] by omp1065.mail.ne1.yahoo.com with NNFMP; 14 Aug 2012 18:51:21 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 253724.3610.bm@omp1065.mail.ne1.yahoo.com Received: (qmail 94935 invoked by uid 60001); 14 Aug 2012 18:51:20 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1344970280; bh=xu1F4IfMoXtrsFL7Ih3+IY3bL3VJRVG65pneEVVVw8w=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=ZdJ9RxBmV9yuuMh0goYhtNJF7eKMbnBeB5mv9YnbtCb88Qc/zG4LwmBNoLVXwls2YbCajQQTW14zp7W3vnnygzCcde0wjwIStKCWWb9BHXn9J3ntnkgd7hr620/GFRlGiY4NdhM70xzr4lHAauMe4TVnOJ8zD5m7NDov0+hHCwM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=moKw0o3xYp7ZwTcTCRrC/QoCZKUSpPYZlmoZaJEzuBWFAwlYxhFZ5bc/snV1dER+IrGwldq/IpwMOI++jBEOZM1NQ07ItIIIGf7WgMLmNNU/YEmI/eAVSxRbr1gA+TIN2b3OMWMUUS876N9+oJEKZ9RgjaFHb0GimjOywNhoASc=; X-YMail-OSG: HKXaPRAVM1ncMk8.K5iBIqWdTlTqe9yUPDcXrJ7bHhodTzN 3j.147TympWndZXp3v8eonGcJF7uJ6TTCgjDCAUBVuSWGW6QZNMW49jWtgix TVA29faQLENSacmt67ThTt699VeawWSSJUGNfTmlZeZM2jjVV1GrEf4KyhEf LZ0NYYd9akOIz9XkvgwBx7kbXnaUqrf3eR70xmR6MAEnOpmBxvuCjEV9cgno y4rMeQKybB2Csi_7Vr8SGSyoKjd7hEG34GIH0JgzfW3wzBSF.yKA4hyyknrp gYCUooV1NZQqzQyh8nLRvPUjO60q4zjBhTV8qT5ew74E.ssbvdH19wtD_jcE sHx1zRUrre8locF7TfAPOAkw2yr.0_xI26ea.uAPIyUdKDDqM5YYBO3_F2lz JfhxvuL.A3WSctW8wzUCVlUFw_CzOiJzWtas8nlixSDU_Kem7qOPhHDuVQ.W TiFBWJIk39bd942gYVcrDFZwQFik3qIk11tatBvHZx4v.VlwM8m._fwAUOt9 rvQ-- Received: from [209.131.62.113] by web31805.mail.mud.yahoo.com via HTTP; Tue, 14 Aug 2012 11:51:20 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <1344875668.20926.YahooMailNeo@web31807.mail.mud.yahoo.com> <4E1F6AAD24975D4BA5B1680429673943667777B8@TK5EX14MBXC283.redmond.corp.microsoft.com> Message-ID: <1344970280.72536.YahooMailNeo@web31805.mail.mud.yahoo.com> Date: Tue, 14 Aug 2012 11:51:20 -0700 (PDT) From: William Mills To: Mike Jones , Dick Hardt , "oauth@ietf.org WG" In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943667777B8@TK5EX14MBXC283.redmond.corp.microsoft.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-551393103-832967850-1344970280=:72536" 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 Reply-To: William Mills List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2012 18:51:23 -0000 ---551393103-832967850-1344970280=:72536 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks.=0A=0A=0A________________________________=0A From: Mike Jones =0ATo: William Mills ; Dick = Hardt ; "oauth@ietf.org WG" =0ASent:= Tuesday, August 14, 2012 11:43 AM=0ASubject: RE: [OAUTH-WG] Fwd: [IANA #59= 6670] Protocol Action: 'The OAuth 2.0 Authorization Framework: Bearer Token= Usage' to Proposed Standard (draft-ietf-oauth-v2-bearer-23.txt)=0A =0A=0A = =0A=E2=80=9CSpecification Required=E2=80=9D is correct, as that=E2=80=99s w= hat=E2=80=99s used in OAuth Core.=C2=A0 I believe that the case insensitivi= ty comes from RFC 2617, which for instance, seems to use =E2=80=9CBasic=E2= =80=9D and =E2=80=9Cbasic=E2=80=9D interchangeably.=0A=C2=A0=0A=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mike= =0A=C2=A0=0AFrom:oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On = Behalf Of William Mills=0ASent: Monday, August 13, 2012 9:34 AM=0ATo: Dick = Hardt; oauth@ietf.org WG=0ASubject: Re: [OAUTH-WG] Fwd: [IANA #596670] Prot= ocol Action: 'The OAuth 2.0 Authorization Framework: Bearer Token Usage' to= Proposed Standard (draft-ietf-oauth-v2-bearer-23.txt)=0A=C2=A0=0A1) Is it = a problem that everything here seems to have "specification required" for t= he "Registration Procedures"?=0A=C2=A0=0A2) In HTTP Authentication schemes,= is the case insensitivity implicit here? (I=C2=A0think=C2=A0so)=0A=C2=A0= =0A-bill=0A=C2=A0=0A=C2=A0=0A=C2=A0=0A=0A________________________________= =0A =0AFrom:Dick Hardt =0ATo: "oauth@ietf.org WG" =0ASent: Friday, August 10, 2012 1:04 PM=0ASubject: [OAUTH-WG= ] Fwd: [IANA #596670] Protocol Action: 'The OAuth 2.0 Authorization Framewo= rk: Bearer Token Usage' to Proposed Standard (draft-ietf-oauth-v2-bearer-23= .txt)=0A=C2=A0=0AOnce again, would be great to have a few more eyes checkin= g the IANA registrations.=C2=A0=0A=C2=A0=0ANote these are for the Bearer To= ken spec.=C2=A0=0A=C2=A0=0AI like that the error registry items are sorted = alphabetically already. :)=0A=C2=A0=0ABegin forwarded message:=0A=0A=0AFrom= : "Amanda Baber via RT" =0ASubject: [IANA #596670= ] Protocol Action: 'The OAuth 2.0 Authorization Framework: Bearer Token Usa= ge' to Proposed Standard (draft-ietf-oauth-v2-bearer-23.txt) =0ADate: Augus= t 10, 2012 12:20:33 PM PDT=0ACc: mbj@microsoft.com, dick.hardt@gmail.com, o= auth-chairs@tools.ietf.org, oauth-ads@tools.ietf.org=0AReply-To: drafts-app= roval@iana.org=0A=C2=A0=0ADear Authors:=0A=0AATTENTION: A RESPONSE TO THIS = MESSAGE IS NEEDED =0A=0AWe have completed the IANA Actions for RFC-to-be=0A= draft-ietf-oauth-v2-bearer-23=0A=0AACTION 1:=0A=0AIANA has registered the f= ollowing OAuth Access Token Type:=0A=0AName: Bearer=0AAdditional Endpoint R= esponse Parameters: =0AHTTP Authentication Scheme(s): Bearer =0AChange Cont= roller: IETF =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=0ARefer= ence: [RFC-ietf-oauth-v2-bearer-23]=0A=0APlease see=0Ahttp://www.iana.org/a= ssignments/oauth-parameters=0A=0A=0AACTION 2:=0A=0AIANA has registered the = following in the OAuth Extensions Error Registry:=0A=0Ainvalid_request =C2= =A0=0AUsage Location: Resource access error response =C2=A0=0AProtocol Exte= nsion: Bearer access token type =C2=A0=0AChange Controller: IETF =C2=A0=0AR= eference: [RFC-ietf-oauth-v2-bearer-23]=0A=0Ainvalid_token=0AUsage Location= : Resource access error response =C2=A0=0AProtocol Extension: Bearer access= token type =C2=A0=0AChange Controller: IETF =C2=A0=0AReference: [RFC-ietf-= oauth-v2-bearer-23]=0A=0Ainsufficient_scope=0AUsage Location: Resource acce= ss error response =C2=A0=0AProtocol Extension: Bearer access token type =C2= =A0=0AChange Controller: IETF =C2=A0=0AReference: [RFC-ietf-oauth-v2-bearer= -23]=0A=0APlease see=0Ahttp://www.iana.org/assignments/oauth-parameters=0A= =0A=0APlease let us know whether the above IANA Actions look OK. As =0Asoon= as we receive your confirmation, we'll notify the RFC Editor =0Athat this = document's IANA Actions are complete. (If this document =0Ahas a team of au= thors, one reply on behalf of everyone will suffice.)=0A=0AThanks,=0A=0AAma= nda Baber=0AICANN/IANA=0A=C2=A0=0A=0A______________________________________= _________=0AOAuth mailing list=0AOAuth@ietf.org=0Ahttps://www.ietf.org/mail= man/listinfo/oauth ---551393103-832967850-1344970280=:72536 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Thanks.

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>
Sent: Tuesday, August 14, 2012 11:43 AM
Subject: RE: [OAUTH-WG] Fwd: [IANA #= 596670] Protocol Action: 'The OAuth 2.0 Authorization Framework: Bearer Tok= en Usage' to Proposed Standard (draft-ietf-oauth-v2-bearer-23.txt)
<= br>=0A
=0A=0A =0A =0A