IETF Logo Mail Archive

Re: [OAUTH-WG] Mail regarding draft-ietf-oauth-v2

William Mills <wmills_92105@yahoo.com> Fri, 13 July 2012 16:56 UTC

Return-Path: <wmills_92105@yahoo.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 BD25C11E8103 for <oauth@ietfa.amsl.com>; Fri, 13 Jul 2012 09:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[AWL=-0.799, BAYES_00=-2.599, J_CHICKENPOX_22=0.6]
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 Le2SqOhkdqzy for <oauth@ietfa.amsl.com>; Fri, 13 Jul 2012 09:56:24 -0700 (PDT)
Received: from nm11-vm0.bullet.mail.ac4.yahoo.com (nm11-vm0.bullet.mail.ac4.yahoo.com [98.139.53.196]) by ietfa.amsl.com (Postfix) with SMTP id B683B11E80E1 for <oauth@ietf.org>; Fri, 13 Jul 2012 09:56:23 -0700 (PDT)
Received: from [98.139.52.196] by nm11.bullet.mail.ac4.yahoo.com with NNFMP; 13 Jul 2012 16:56:56 -0000
Received: from [98.139.52.145] by tm9.bullet.mail.ac4.yahoo.com with NNFMP; 13 Jul 2012 16:56:56 -0000
Received: from [127.0.0.1] by omp1028.mail.ac4.yahoo.com with NNFMP; 13 Jul 2012 16:56:56 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 835563.19363.bm@omp1028.mail.ac4.yahoo.com
Received: (qmail 2419 invoked by uid 60001); 13 Jul 2012 16:56:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1342198616; bh=lt8DUb2UbwAsLH+0mGRMrSIVUerfMIMUanjR2MT7QfQ=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nkfTa7AJMWtNySx8tnANd0IC3E6hTBtLXro4MflN13+JoyAq6xXwr3+gKmIk5dwDqtg9XRuvegVyh0mN4+erH3CA2ULwmY4bOLLB7GZkNw4oindd0Jp7k9QpjulG6idOL1j4zm8LOXSjpDZ6pXAHmYubIanJLmin0s3iVx04dsA=
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:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=6VVJvEP0tCxlALu1Yn75RSERIHyW52Vf59rtbnm3Hf1jy7y3Ivhtshf491igX0yey5Uckhrlg5guM1bLCbAa3G2DRQ3EdmwRLm5a763/LMcc61szE2sRur6JvCCDuJxeJr5BUTOp5cl5O7rpTmdaLkPHduvJQrqD1LBZfSzWCbE=;
X-YMail-OSG: DF0C7YgVM1lT7IWYoDopwACFRfZtUGP3yYdmNh6jmEKZeN5 Wx.VlLKX5yMpznES.idMbyQ.pOHEzU__6glSBnHXYwFCnXHdo6XvNiniV1Yu pANbq2ZIHHvRkSLS32vp3sjxWVsw8.UI4NzH_wmm_V1AygcHC5tTJpkY3sOW x.jlZQKaoN9JSx0VMJjYyFx99JFdmg7OWrrMKkjjNtVqgBM7OZBtjcJsgcSI zr38pzQ1A59CPXtfCyBSuK4I3j6izvgD4ryPijJ1g1yvhXQkKLOoKJQpkIOX IdEmK00kMTEkKZKiO9nmTLCYMrCVPplenqR.SiDDX1PDAiEunn5LO5fzTvu3 v2kPgsolUoG7kNRBjj1AEPi6WdS3oG0RaiPrAeZECpg6vxujaH9hR5XFmeVB T7ejWY9lEd4r9EHwIP4226JReD6lYZChibQ92fAu9xT4SCCxVQUcnLtIUETi Kss9z.TkN_McMVoiI1u2iCWaDtB9WqTz9RCSEZ8fbIQLrY7GG4Bz2ISiEgDp kth4-
Received: from [99.31.212.42] by web31812.mail.mud.yahoo.com via HTTP; Fri, 13 Jul 2012 09:56:55 PDT
X-Mailer: YahooMailWebService/0.8.120.356233
References: <CC2485A3.C8C3%charles_honton@intuit.com> <AD29164A-87F3-439A-99C8-C434259C7EA7@gmail.com> <6785B651-064E-4E81-9E6C-38A47C499E29@ve7jtb.com>
Message-ID: <1342198615.80652.YahooMailNeo@web31812.mail.mud.yahoo.com>
Date: Fri, 13 Jul 2012 09:56:55 -0700
From: William Mills <wmills_92105@yahoo.com>
To: John Bradley <ve7jtb@ve7jtb.com>, Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <6785B651-064E-4E81-9E6C-38A47C499E29@ve7jtb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "draft-ietf-oauth-v2@tools.ietf.org" <draft-ietf-oauth-v2@tools.ietf.org>, "Honton, Charles" <Charles_Honton@intuit.com>, "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Mail regarding draft-ietf-oauth-v2
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: William Mills <wmills_92105@yahoo.com>
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, 13 Jul 2012 16:56:25 -0000

I agree that we don't want things like Internal Server Error (500) duplicated in OAuth specific errors.  The only thing I might add to 5.2 is something like "Other HTTP status codes such as 500 (Internal Server Error) may be returned with no OAuth specific parameters."

-bill


________________________________
From: John Bradley <ve7jtb@ve7jtb.com>
To: Dick Hardt <dick.hardt@gmail.com> 
Cc: draft-ietf-oauth-v2@tools.ietf.org; "Honton, Charles" <Charles_Honton@intuit.com>; "oauth@ietf.org WG" <oauth@ietf.org> 
Sent: Friday, July 13, 2012 4:04 AM
Subject: Re: [OAUTH-WG] Mail regarding draft-ietf-oauth-v2


FRom what I can see in a similar discussion Eran pointed out that this is a direct communication, communication between the client and token endpoint.

Server Error and temporarily unavailable are not OAuth specific and are handled by existing HTTP error codes.

I don't see a need for a change.

Unless something else dramatic comes up I would like to see draft 29 go to the RFC editor.

(Though one person mentioned to me that 30 is a nicer number:)

John B.


On 2012-07-12, at 8:09 PM, Dick Hardt wrote:

Charles
>
>
>Thanks for the suggestion. I just did publish a new draft that included a number of items that had been discussed and I would like to get some feedback on your suggestion before incorporating it (or not).
>
>
>Does anyone have feedback on the change below? (+/-)
>
>
>-- Dick
>
>
>On Jul 12, 2012, at 1:45 PM, Honton, Charles wrote:
>
>E. Hammer, D. Recordon, D. Hardt, et.al,
>>
>>
>>I'm looking at draft 28 (http://tools.ietf.org/html/draft-ietf-oauth-v2-28).
>>
>>
>>In Section 5.2 the error code should probably include:
>>
>>
>>server_error The authorization server encountered an unexpected condition which prevented it from fulfilling the request. temporarily_unavailable The authorization server is currently unable to handle the request due to a temporary overloading or maintenance of the server.
>>
>>
>>
>>
>>Regards,
>>chas
>>
>>
>_______________________________________________
>OAuth mailing list
>OAuth@ietf.org
>https://www.ietf.org/mailman/listinfo/oauth
>

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

v2.14.0 | Report a Bug | By Email