IETF Logo Mail Archive

Re: [OAUTH-WG] Versioning

Justin Richer <jricher@mitre.org> Thu, 01 July 2010 19:07 UTC

Return-Path: <jricher@mitre.org>
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 EFF9B28C0ED for <oauth@core3.amsl.com>; Thu, 1 Jul 2010 12:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.89
X-Spam-Level:
X-Spam-Status: No, score=-5.89 tagged_above=-999 required=5 tests=[AWL=0.709, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 FmsrXaGw3jMN for <oauth@core3.amsl.com>; Thu, 1 Jul 2010 12:07:05 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id E593B3A6A1A for <oauth@ietf.org>; Thu, 1 Jul 2010 12:07:04 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o61J7GR9013401 for <oauth@ietf.org>; Thu, 1 Jul 2010 15:07:16 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o61J7GJu013395; Thu, 1 Jul 2010 15:07:16 -0400
Received: from [129.83.50.65] (129.83.50.65) by imchub2.MITRE.ORG (129.83.29.74) with Microsoft SMTP Server id 8.2.254.0; Thu, 1 Jul 2010 15:07:16 -0400
From: Justin Richer <jricher@mitre.org>
To: Marius Scurtescu <mscurtescu@google.com>
In-Reply-To: <AANLkTikZg5FlHsSCVaNJaF9qXL8x7iz9HPImXeJZqLWC@mail.gmail.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> <AANLkTikZg5FlHsSCVaNJaF9qXL8x7iz9HPImXeJZqLWC@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 01 Jul 2010 15:07:15 -0400
Message-ID: <1278011235.28743.223.camel@localhost.localdomain>
MIME-Version: 1.0
X-Mailer: Evolution 2.28.3
Content-Transfer-Encoding: 7bit
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 19:07:06 -0000

OAuth tokens as a form-encoded element in a post body? Yes. Keep it.

 -- Justin

On Thu, 2010-07-01 at 14:47 -0400, Marius Scurtescu wrote:
> 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
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

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