gt; From: Alexey Melnikov [mailto:alexey.melni...@isode.com]
> Sent: Saturday, May 07, 2011 3:15 AM
> To: Eran Hammer-Lahav
> Cc: Barry Leiba; OAuth WG
> Subject: Re: [OAUTH-WG] Closing a few issues
>
> Eran Hammer-Lahav wrote:
>
> >Hi Alexey,
> >
> >
> >
Eran Hammer-Lahav wrote:
Hi Alexey,
-Original Message-
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
Of Alexey Melnikov
Sent: Tuesday, May 03, 2011 4:17 AM
#10 8.4. Defining Additional Error Codes
http://trac.tools.ietf.org/wg/oauth/trac/ticket/10
>> This is mostly fine, but I am wondering if the ACAP vendor name registry (RFC
>> 6075), the OID vendor names, or DNS names can be recommended for the
>> prefix (to satisfy the "SHOULD be prefixed by an identifying name when
>> possible" requirement)?
...
> The main reason for allowing this kind
Hi Alexey,
> -Original Message-
> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
> Of Alexey Melnikov
> Sent: Tuesday, May 03, 2011 4:17 AM
> >#10 8.4. Defining Additional Error Codes
> >http://trac.tools.ietf.org/wg/oauth/trac/ticket/10
> >
> >
> This is mostly f
> #8 4.1.2.1 and 4.2.2.1, text for 4xx or 5xx HTTP status code
> http://trac.tools.ietf.org/wg/oauth/trac/ticket/8
>
> #9 5.2, text for non-400 & 401 error conditions
> http://trac.tools.ietf.org/wg/oauth/trac/ticket/9
I will close these later today, as I said in my original note:
http:/
: Friday, April 29, 2011 11:05 AM
To: OAuth WG
Subject: [OAUTH-WG] Closing a few issues
There are three issues in the tracker that are just looking for consensus on
text that's in the document -- Eran had flagged them as "pending consensus" in
the -15 version. Let's look at
Hi Barry,
Barry Leiba wrote:
There are three issues in the tracker that are just looking for
consensus on text that's in the document -- Eran had flagged them as
"pending consensus" in the -15 version. Let's look at closing those
issues now. The issues are
#8 4.1.2.1 and 4.2.2.1, text f
There are three issues in the tracker that are just looking for
consensus on text that's in the document -- Eran had flagged them as
"pending consensus" in the -15 version. Let's look at closing those
issues now. The issues are
#8 4.1.2.1 and 4.2.2.1, text for 4xx or 5xx HTTP status code
ht
