IETF Logo Mail Archive

Re: [OAUTH-WG] register prefixes as opposed to full parameter names

"William Mills" <wmills@yahoo-inc.com> Tue, 06 July 2010 20:00 UTC

Return-Path: <wmills@yahoo-inc.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 016E83A6899 for <oauth@core3.amsl.com>; Tue, 6 Jul 2010 13:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.431
X-Spam-Level:
X-Spam-Status: No, score=-17.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 FWkdxpopNe3I for <oauth@core3.amsl.com>; Tue, 6 Jul 2010 13:00:41 -0700 (PDT)
Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by core3.amsl.com (Postfix) with ESMTP id EBAFC3A69DE for <oauth@ietf.org>; Tue, 6 Jul 2010 13:00:41 -0700 (PDT)
Received: from SNV-EXPF01.ds.corp.yahoo.com (snv-expf01.ds.corp.yahoo.com [207.126.227.250]) by mrout1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o66JxVux020066; Tue, 6 Jul 2010 12:59:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:x-mimeole:content-class:mime-version: content-type:content-transfer-encoding:subject:date:message-id: in-reply-to:x-ms-has-attach:x-ms-tnef-correlator:thread-topic: thread-index:references:from:to:cc:return-path:x-originalarrivaltime; b=2qtdXXsmDf/NRY4hqMmA8MqS041ooyiQFFzIac6ovxHAhczHOnyNBzeW7iL1MxNB
Received: from SNV-EXVS08.ds.corp.yahoo.com ([207.126.227.8]) by SNV-EXPF01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 6 Jul 2010 12:59:31 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 06 Jul 2010 12:59:30 -0700
Message-ID: <012AB2B223CB3F4BB846962876F47217059B6A5F@SNV-EXVS08.ds.corp.yahoo.com>
In-Reply-To: <1278439815.2445.8.camel@localhost.localdomain>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OAUTH-WG] register prefixes as opposed to full parameter names
Thread-Index: AcsdNq1xsYDYUUHCQxacatk1i4M0UwADwIlA
References: <AANLkTin7zWi7m_evTgI49JKXLPuVqYBFlCR8CtSYRKDM@mail.gmail.com><90C41DD21FB7C64BB94121FBBC2E72343B3ED4C4E2@P3PW5EX1MB01.EX1.SECURESERVER.NET><AANLkTik_f9MRWIK4kZ3c5pANtPloOsxyzYeL6bqMFhbs@mail.gmail.com><90C41DD21FB7C64BB94121FBBC2E72343B3ED4C528@P3PW5EX1MB01.EX1.SECURESERVER.NET><AANLkTilrV6thlDrCx1yVVtpRqYWd7A4wAn6kCrwCO6T6@mail.gmail.com><90C41DD21FB7C64BB94121FBBC2E72343B3ED4C567@P3PW5EX1MB01.EX1.SECURESERVER.NET> <1278439815.2445.8.camel@localhost.localdomain>
From: William Mills <wmills@yahoo-inc.com>
To: Justin Richer <jricher@mitre.org>, Eran Hammer-Lahav <eran@hueniverse.com>
X-OriginalArrivalTime: 06 Jul 2010 19:59:31.0596 (UTC) FILETIME=[BFAD84C0:01CB1D45]
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] register prefixes as opposed to full parameter names
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: Tue, 06 Jul 2010 20:00:43 -0000

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] 
> On Behalf Of Justin Richer
> Sent: Tuesday, July 06, 2010 11:10 AM
> To: Eran Hammer-Lahav
> Cc: OAuth WG
> Subject: Re: [OAUTH-WG] register prefixes as opposed to full 
> parameter names
> 
> > > When receiving an OAuth request MediaWiki will have two title 
> > > parameters, the damage is already done.
> > 
> > Yes, they might need to change their platform to support 
> it. I'm ok with that.
> 
> I think this is an unfortunate hubris of the spec-defining 
> community here. For most people, if it comes down to "change 

+1

> my platform or don't support oauth", the answer is going to 
> be "don't support oauth". 
> 
>  -- Justin
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

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