IETF Logo Mail Archive

Re: [OAUTH-WG] Fwd: [IANA #596671] Protocol Action: 'The OAuth 2.0 Authorization Framework' to Proposed Standard (draft-ietf-oauth-v2-31.txt)

John Bradley <ve7jtb@ve7jtb.com> Wed, 08 August 2012 01:53 UTC

Return-Path: <ve7jtb@ve7jtb.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 3BEA411E80D2 for <oauth@ietfa.amsl.com>; Tue, 7 Aug 2012 18:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Level:
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=0.115, 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 1Tgy+Tuq8Jmm for <oauth@ietfa.amsl.com>; Tue, 7 Aug 2012 18:53:57 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 31DF611E80F1 for <oauth@ietf.org>; Tue, 7 Aug 2012 18:53:57 -0700 (PDT)
Received: by yhq56 with SMTP id 56so281833yhq.31 for <oauth@ietf.org>; Tue, 07 Aug 2012 18:53:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=UFUqctjtD3uXz58MJmQN0yj5KxUVu2tZtAIoNpKQ828=; b=kh0IzImZFp+vMTDFZBIV8FfqjPRZcELAWvdCJ8iWSMzypEK+lkk5HwcjUnr5UeiYfv p85QAGN1YSAIQXwmpr02ceExP0dVIGSuqpmyqXwZPbP3gKxO1RFwgJxEvVZT4QIHQO7q vZRAHzttMcFq5u1ghdLQFXX6xaPX5V0V85379AsBda6Yk/5zw/w1hfliebv4KOpFki7d K8a4aJyNMlF+FdhnUVRVo3f/iv4+fucU0/a+f5EOksIOU/nI5at80H6kJeO1JzyH4kjy lOFCu/DlOmjgfcQSN0rZxu1b2EAEP3UYRrBXlHehuZQIr+hfndE8695Dl+I6G1K5eeka Lpcw==
Received: by 10.236.178.38 with SMTP id e26mr15625447yhm.12.1344390836676; Tue, 07 Aug 2012 18:53:56 -0700 (PDT)
Received: from [192.168.1.211] (190-20-38-200.baf.movistar.cl. [190.20.38.200]) by mx.google.com with ESMTPS id t39sm19262211anh.3.2012.08.07.18.53.50 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Aug 2012 18:53:53 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_7FE8AF8B-3098-4F32-B25A-D84E34E92C64"; protocol="application/pkcs7-signature"; micalg="sha1"
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436676BD56@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Tue, 07 Aug 2012 21:54:40 -0400
Message-Id: <693AC132-C8CA-4DE3-A7D6-20861E110DBE@ve7jtb.com>
References: <rt-3.8.8-6133-1344386066-1919.596671-7-0@icann.org> <825EF775-C6BC-4630-AE00-4063C6458A46@gmail.com> <4E1F6AAD24975D4BA5B16804296739436676BD56@TK5EX14MBXC283.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1278)
X-Gm-Message-State: ALoCoQnlZ5tO4cyXYv5bEGc+sBskmhZdYM8rlq25spSZ3Eda8iwCwDGb2Rp6pNuRJv2CcjwxKSZr
Cc: oauth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Fwd: [IANA #596671] Protocol Action: 'The OAuth 2.0 Authorization Framework' to Proposed Standard (draft-ietf-oauth-v2-31.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: Wed, 08 Aug 2012 01:53:58 -0000

Yes I was just trying to work out what was going on with the OAuth Access token types.

The OAuth parameters are in the same order as the spec has them so not too surprising.  I can't make out any particular significance of the order,  having them make it alphabetical would not hurt.

Other than that looks fine.

John B.

On 2012-08-07, at 9:35 PM, Mike Jones wrote:

> The reference for the OAuth Access Token Types registry should be http://tools.ietf.org/html/draft-ietf-oauth-v2-31 - nothttp://tools.ietf.org/html/draft-ietf-oauth-urn-sub-ns-06.
>  
> Other than that, looks good.
>  
>                                                             -- Mike
>  
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Dick Hardt
> Sent: Tuesday, August 07, 2012 5:53 PM
> To: oauth WG
> Subject: [OAUTH-WG] Fwd: [IANA #596671] Protocol Action: 'The OAuth 2.0 Authorization Framework' to Proposed Standard (draft-ietf-oauth-v2-31.txt)
>  
> Would appreciate a few others checking to make sure the IANA entries are valid. 
>  
> -- Dick
>  
> Begin forwarded message:
> 
> 
> From: "Amanda Baber via RT" <drafts-approval@iana.org>
> Subject: [IANA #596671] Protocol Action: 'The OAuth 2.0 Authorization Framework' to Proposed Standard (draft-ietf-oauth-v2-31.txt)
> Date: August 7, 2012 5:34:26 PM PDT
> Cc: dick.hardt@gmail.com, oauth-chairs@tools.ietf.org, oauth-ads@tools.ietf.org
> Reply-To: drafts-approval@iana.org
>  
> Dear Author:
> 
> ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED 
> 
> We have completed the IANA Actions for RFC-to-be
> draft-ietf-oauth-v2-31
> 
> IANA has created the OAuth Access Token Types, OAuth Parameters, OAuth
> Authorization Endpoint Response Types, and OAuth Extensions Errors
> registries at
> 
> 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. 
> 
> Thanks,
> 
> Amanda Baber
> ICANN/IANA
> 
>  
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email