Re: [OAUTH-WG] Mandatory-to-implement token type

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 02 December 2011 01:44 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 3B86211E8107 for <oauth@ietfa.amsl.com>; Thu, 1 Dec 2011 17:44:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level:
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FNtSewbRQMKB for <oauth@ietfa.amsl.com>; Thu, 1 Dec 2011 17:44:04 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 81DF511E8081 for <oauth@ietf.org>; Thu, 1 Dec 2011 17:44:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id DCB381541B0; Fri, 2 Dec 2011 01:44:03 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1322790243; bh=8hra5KpKTbYZGd nxccFkNmg39bfi26tQz+7pWCxafbU=; b=UOCVCgUD16gPZxigBRR7hsFf8loev2 tJCcFHrhyyK4JRFaawT1tRgODoIAJQYJQeqrkdUUHWukRXJicQ92xi/lcRqONkgy JdUIzMKXLY/nBdmgnAqOB8DQ4+cSa2FHKik4jJh6nvfSN+RjjdDsNWNCW26suHMN NrwjDUdXM4iyRsZar4O9jVo4fhJ3CfaRaLTO0lffVszHzffKQn3RbIlf9b+t5/8q dE0j1nz2kvXo66MCrr30nSjmZBLtvzYp1ApRzzVtrzhPE/uOr56rvKXMkFebsM25 qkae1D2P6iR8GEhH5nQQOJ/TTk+SuFuCSUUDpFKPC+Q070fj2V977dtw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id q-V7LQlaAV31; Fri, 2 Dec 2011 01:44:03 +0000 (GMT)
Received: from [10.87.48.9] (unknown [86.41.14.223]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 7071F1541AF; Fri, 2 Dec 2011 01:44:03 +0000 (GMT)
Message-ID: <4ED82D62.3070800@cs.tcd.ie>
Date: Fri, 02 Dec 2011 01:44:02 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Michael D Adams <mike@automattic.com>
References: <CALaySJJ+2au5rxEQmSSpXO42KmgCu=NhiLPBCx-3AH0hud=5CQ@mail.gmail.com> <CAH-8B6sjim_tcBkTPFWc1SnjhtHDQTR7sVT+aOjnYv7cs8JssA@mail.gmail.com>
In-Reply-To: <CAH-8B6sjim_tcBkTPFWc1SnjhtHDQTR7sVT+aOjnYv7cs8JssA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, oauth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Mandatory-to-implement token type
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, 02 Dec 2011 01:44:05 -0000

Hiya,

On 12/02/2011 01:38 AM, Michael D Adams wrote:
> I echo Justin Richer's comments.
>
> On Thu, Nov 17, 2011 at 12:28 AM, Barry Leiba<barryleiba@computer.org>  wrote:
>> 1. Should we specify some token type as mandatory to implement?  Why
>> or why not (*briefly*)?
>
> No.  There's no mechanism in the spec for clients to request a
> particular token type, so there's no opportunity for the authorization
> server to decide what token type to send.  The only thing the
> authorization server can do is pick its own preference.
>
> If there's an MTI token type, and with the absence of a client
> preference, the authorization server will have to pick the MTI token
> type.
>
> So an MTI token type + no client preference is equivalent to there
> only existing one token type.

Maybe.

However, no MTI token type + no client preference = no interop.

So I don't get your argument. (When thinking of interop.)

S.

>
> Mike
>
> PS: I sent this 2011/11/17 but apparently hit reply instead of reply all.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>