Re: [OAUTH-WG] How do we deal with unrecognized elements in requests and responses?
Robert Sayre <sayrer@gmail.com> Thu, 01 July 2010 03:03 UTC
Return-Path: <sayrer@gmail.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 36E3C3A6867 for <oauth@core3.amsl.com>; Wed, 30 Jun 2010 20:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, GB_I_LETTER=-2]
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 rxI+jGB6Bm+c for <oauth@core3.amsl.com>; Wed, 30 Jun 2010 20:03:25 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 4F2C13A688D for <oauth@ietf.org>; Wed, 30 Jun 2010 20:03:25 -0700 (PDT)
Received: by vws14 with SMTP id 14so174643vws.31 for <oauth@ietf.org>; Wed, 30 Jun 2010 20:03:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=MB3RDApAgVSiwJ+tXLMLJ+by3Y9chc0H9EVKz4gIUJQ=; b=qow6qrN1Bl32lkHFGDriCqaVfJT7HLOZOJxLlNzW5qEK48HwSNbnPngh5+eGrfYMv4 Q3PaVGB7EonYFpedXfwrFwNdlRGh5lbxwf2U/gvIVA9RHsFI46kDCTI7KDllsR6t/u58 53DDQwngzfTp7GsPpohNiwG2solpMTVponcJA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VgZVuWnYEhvqh9uL3JbaBPpbNmtRDoV9OZyc0q2SCcd4PMjorfLCrxll/OMsgVLGn6 HIHPvpdq0hX75J/8F80QHlVMauJN5VkOmrbRDmPKrlxlCAcgGAwwFY6Y8dXwNjprs23u 1vt+OBswtcXP6FpDhTN8q2/9iN30+Ap6L9MsU=
MIME-Version: 1.0
Received: by 10.229.224.196 with SMTP id ip4mr5633064qcb.129.1277953413667; Wed, 30 Jun 2010 20:03:33 -0700 (PDT)
Received: by 10.229.102.18 with HTTP; Wed, 30 Jun 2010 20:03:33 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3ED4BCB4@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <7C01E631FF4B654FA1E783F1C0265F8C579D0F52@TK5EX14MBXC117.redmond.corp.microsoft.com> <90C41DD21FB7C64BB94121FBBC2E72343B3ED4BCB0@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTin2cvQnXB7x9abGLF4xQyfrv9IzZCzxOHnJqlHQ@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3ED4BCB4@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Wed, 30 Jun 2010 20:03:33 -0700
Message-ID: <AANLkTimid0CPqqpFM3Cg7tnS2Z3fKk04aybduYSaA_7W@mail.gmail.com>
From: Robert Sayre <sayrer@gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] How do we deal with unrecognized elements in requests and responses?
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 03:03:26 -0000
On Mon, Jun 28, 2010 at 6:17 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote: > There are times when the client wants the server to fail if it doesn’t > support an extension. Implementations that have such requirements also have the option of making a new protocol that shares a lot of code with OAuth. How much feature negotiation to allow in a protocol can be a tough question, but it's probably not a goal to allow any combination of mandatory extensions to be called "OAuth". -- Robert Sayre "I would have written a shorter letter, but I did not have the time."
- [OAUTH-WG] How do we deal with unrecognized eleme… Yaron Goland
- Re: [OAUTH-WG] How do we deal with unrecognized e… Marius Scurtescu
- Re: [OAUTH-WG] How do we deal with unrecognized e… Ian McKellar
- Re: [OAUTH-WG] How do we deal with unrecognized e… Eran Hammer-Lahav
- Re: [OAUTH-WG] How do we deal with unrecognized e… David Recordon
- Re: [OAUTH-WG] How do we deal with unrecognized e… Eran Hammer-Lahav
- Re: [OAUTH-WG] How do we deal with unrecognized e… Igor Faynberg
- Re: [OAUTH-WG] How do we deal with unrecognized e… Yaron Goland
- Re: [OAUTH-WG] How do we deal with unrecognized e… Zeltsan, Zachary (Zachary)
- Re: [OAUTH-WG] How do we deal with unrecognized e… Robert Sayre
- Re: [OAUTH-WG] How do we deal with unrecognized e… Justin Richer
- Re: [OAUTH-WG] How do we deal with unrecognized e… Pelle Braendgaard
- Re: [OAUTH-WG] How do we deal with unrecognized e… Eran Hammer-Lahav
- Re: [OAUTH-WG] How do we deal with unrecognized e… Marius Scurtescu
- Re: [OAUTH-WG] How do we deal with unrecognized e… Justin Richer