IETF Logo Mail Archive

Re: [OAUTH-WG] Versioning

Marius Scurtescu <mscurtescu@google.com> Thu, 01 July 2010 18:47 UTC

Return-Path: <mscurtescu@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EF653A6A15 for <oauth@core3.amsl.com>; Thu, 1 Jul 2010 11:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.553
X-Spam-Level:
X-Spam-Status: No, score=-101.553 tagged_above=-999 required=5 tests=[AWL=0.424, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xjbo54ceKM94 for <oauth@core3.amsl.com>; Thu, 1 Jul 2010 11:47:30 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 240753A6A2F for <oauth@ietf.org>; Thu, 1 Jul 2010 11:47:29 -0700 (PDT)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id o61IlfT5001176 for <oauth@ietf.org>; Thu, 1 Jul 2010 11:47:41 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1278010061; bh=vgtLduZ/+R13lR9/zxGshvByXc8=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=MatK9lUbUF04HzQQTw/MVYJ8fZlXWQXNcVaZottLZ4K34wsMSSahULFEARGDCNFYT 2rTLXsYSqGlhqUH7BXq9Q==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=MtSM1yPPwsZjyJESR4k4gsghW2IsBR2NkcSwVuz6u+ULiq8VuqGknu9EfawfF5ZCv eKJz3PX/a0Vmo8bJd73Sg==
Received: from gyf3 (gyf3.prod.google.com [10.243.50.67]) by hpaq11.eem.corp.google.com with ESMTP id o61IldtF011485 for <oauth@ietf.org>; Thu, 1 Jul 2010 11:47:40 -0700
Received: by gyf3 with SMTP id 3so1886876gyf.27 for <oauth@ietf.org>; Thu, 01 Jul 2010 11:47:39 -0700 (PDT)
Received: by 10.101.170.33 with SMTP id x33mr13272149ano.265.1278010059405; Thu, 01 Jul 2010 11:47:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.132.22 with HTTP; Thu, 1 Jul 2010 11:47:19 -0700 (PDT)
In-Reply-To: <012AB2B223CB3F4BB846962876F47217059B694F@SNV-EXVS08.ds.corp.yahoo.com>
References: <4C2C6D4A.5010401@cdatazone.org> <90C41DD21FB7C64BB94121FBBC2E72343B3ED4C3E6@P3PW5EX1MB01.EX1.SECURESERVER.NET> <012AB2B223CB3F4BB846962876F47217059B693B@SNV-EXVS08.ds.corp.yahoo.com> <90C41DD21FB7C64BB94121FBBC2E72343B3ED4C454@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTikjW5OqYJIzwxrooAmHoWR5tNX1522TTBLH5rBT@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3ED4C475@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTilTDOVNjJw9K0ZismTzbbNeuVcEBktE-8ojDfVR@mail.gmail.com> <012AB2B223CB3F4BB846962876F47217059B694F@SNV-EXVS08.ds.corp.yahoo.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 01 Jul 2010 11:47:19 -0700
Message-ID: <AANLkTikZg5FlHsSCVaNJaF9qXL8x7iz9HPImXeJZqLWC@mail.gmail.com>
To: William Mills <wmills@yahoo-inc.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Versioning
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 01 Jul 2010 18:47:31 -0000

On Thu, Jul 1, 2010 at 11:42 AM, William Mills <wmills@yahoo-inc.com> wrote:
>
>
>> -----Original Message-----
>> From: Marius Scurtescu [mailto:mscurtescu@google.com]
>> Sent: Thursday, July 01, 2010 11:36 AM
>> To: Eran Hammer-Lahav
>> Cc: William Mills; Rob Richards; oauth@ietf.org
>> Subject: Re: [OAUTH-WG] Versioning
>>
>> On Thu, Jul 1, 2010 at 11:24 AM, Eran Hammer-Lahav
>> <eran@hueniverse.com> wrote:
>> >
>> > If you would like to discuss a version for the header,
>> please provide examples and requirements for what changes in
>> the future you would like to support.
>>
>> Not sure about the future, but looking at OAuth 1 vs OAuth 2.
>> A protected resource request filter may want to decide early
>> what protocol it deals with so it can call the appropriate
>> handler, or to enforce HTTPS for OAuth 2 for example. Sure,
>> it can apply heuristics right now, but it would be nice to
>> have a more deterministic way which can also be extended in
>> the future. You can always embed the protocol version inside
>> the token I guess, so I don't think this is a huge issue.
>
> Yeah, unfortunately early selection of a handler might require peeking into the post body.

Is anybody really using or needing this feature? Can we drop this option?

Marius

v2.46.0 | Report a Bug | By Email | System Status