IETF Logo Mail Archive

Re: [OAUTH-WG] Encoding of Errors in the Base and in the Bearer Spec

Eran Hammer <eran@hueniverse.com> Fri, 11 May 2012 13:57 UTC

Return-Path: <eran@hueniverse.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 E24CF21F8484 for <oauth@ietfa.amsl.com>; Fri, 11 May 2012 06:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level:
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599]
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 AxnC2UL5c7EZ for <oauth@ietfa.amsl.com>; Fri, 11 May 2012 06:57:38 -0700 (PDT)
Received: from p3plex2out01.prod.phx3.secureserver.net (p3plex2out01.prod.phx3.secureserver.net [184.168.131.12]) by ietfa.amsl.com (Postfix) with ESMTP id 6D41C21F845B for <oauth@ietf.org>; Fri, 11 May 2012 06:57:38 -0700 (PDT)
Received: from P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) by p3plex2out01.prod.phx3.secureserver.net with bizsmtp id 8dxd1j0030Dcg9U01dxdVu; Fri, 11 May 2012 06:57:37 -0700
Received: from P3PWEX2MB008.ex2.secureserver.net ([169.254.8.88]) by P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) with mapi id 14.02.0247.003; Fri, 11 May 2012 06:57:37 -0700
From: Eran Hammer <eran@hueniverse.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>, "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Encoding of Errors in the Base and in the Bearer Spec
Thread-Index: AQHNL304m3igpnkMGkWgvho/M7VBEJbEnMng
Date: Fri, 11 May 2012 13:57:37 +0000
Message-ID: <0CBAEB56DDB3A140BA8E8C124C04ECA20102A14C@P3PWEX2MB008.ex2.secureserver.net>
References: <7D98C51F-84D8-48AA-B94D-EABE4D0921DB@gmx.net> <0CBAEB56DDB3A140BA8E8C124C04ECA201026B48@P3PWEX2MB008.ex2.secureserver.net> <4E1F6AAD24975D4BA5B1680429673943664CE3AE@TK5EX14MBXC283.redmond.corp.microsoft.com> <0CBAEB56DDB3A140BA8E8C124C04ECA201026CA8@P3PWEX2MB008.ex2.secureserver.net> <6.2.5.6.2.20120510235528.0a735658@resistor.net> <0CBAEB56DDB3A140BA8E8C124C04ECA201029A8A@P3PWEX2MB008.ex2.secureserver.net> <9452079D1A51524AA5749AD23E00392811E21F@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E00392811E21F@exch-mbx901.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.74.213.174]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Encoding of Errors in the Base and in the Bearer Spec
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, 11 May 2012 13:57:39 -0000

Ok. Would the document shepherd for the bearer specification please raise your hand?

EH

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Murray S. Kucherawy
> Sent: Friday, May 11, 2012 6:52 AM
> To: oauth@ietf.org
> Subject: Re: [OAUTH-WG] Encoding of Errors in the Base and in the Bearer
> Spec
> 
> > -----Original Message-----
> > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> > Of Eran Hammer
> > Sent: Friday, May 11, 2012 12:19 AM
> > To: SM
> > Cc: oauth@ietf.org
> > Subject: Re: [OAUTH-WG] Encoding of Errors in the Base and in the
> > Bearer Spec
> >
> > Don't know. In the 5 RFCs I've worked on, I - as editor - was the only
> > personal who interacted with the IESG. Either way, it is usually the
> > editor who is addressing questions about the text and proposing
> > changes.
> 
> It sounds like you've had some pretty hands-off shepherds in your
> experience (as have I), or you dealt with the issues yourself which obviated
> the need for that person to act.  But formally, SM is correct about the
> Document Shepherd's function.  See RFC4858.
> 
> -MSK
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email