Re: [OAUTH-WG] Simpilfying use of assertions when requesting an access token

Marius Scurtescu <mscurtescu@google.com> Thu, 23 September 2010 21:27 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 4E7DC3A685B for <oauth@core3.amsl.com>; Thu, 23 Sep 2010 14:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.852
X-Spam-Level:
X-Spam-Status: No, score=-103.852 tagged_above=-999 required=5 tests=[AWL=2.125, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, 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 93eq9MZeX-BM for <oauth@core3.amsl.com>; Thu, 23 Sep 2010 14:27:47 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 29D463A63EC for <oauth@ietf.org>; Thu, 23 Sep 2010 14:27:46 -0700 (PDT)
Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id o8NLSFOf031648 for <oauth@ietf.org>; Thu, 23 Sep 2010 14:28:16 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1285277296; bh=IT0e5Lz32gtbtCg6saB0qOOQ5VA=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=x1B863dbCEe/oFeMBfyFeyO9aznWSC4BHo7arj3/K57n7MzZokv/QRIZx+kffcaYS eP5YFGm9Ki1jm61ON3gsA==
Received: from ywl5 (ywl5.prod.google.com [10.192.12.5]) by wpaz29.hot.corp.google.com with ESMTP id o8NLRlBS017581 for <oauth@ietf.org>; Thu, 23 Sep 2010 14:28:14 -0700
Received: by ywl5 with SMTP id 5so1089425ywl.14 for <oauth@ietf.org>; Thu, 23 Sep 2010 14:28:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=NtLCyCd+HogJSRgdIc8RfjmeV94KZoZofmYlQIyEEqc=; b=vtfgKrkFKHGjeyIB9AwqI4DgsEnu0Axjv5nNCJEzzUq8kVtdoUnVrTpQTU9k/tYVM4 Ml2z/xEiIS2HPnBbI7pQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=lKlhjfFqztYpO27HTjSZEX0SC8M/koXn8X+/IPDhKiaElAn9pngqB/ATgnCDzkH/Bu rl81TCSB0xfnICVRqZ9Q==
Received: by 10.220.58.129 with SMTP id g1mr776824vch.78.1285277289826; Thu, 23 Sep 2010 14:28:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.180.74 with HTTP; Thu, 23 Sep 2010 14:27:49 -0700 (PDT)
In-Reply-To: <AANLkTi=bK6oVTs+fBdpNqD0KU+1XU5wM++W2zqs61DwS@mail.gmail.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3F35BE13@P3PW5EX1MB01.EX1.SECURESERVER.NET> <1283462840.3809.42.camel@localhost.localdomain> <90C41DD21FB7C64BB94121FBBC2E72343B3F35BE2D@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTinvch2Xc+LzMzVjQGjMx0yXHKheR=93D5ExJhzC@mail.gmail.com> <1285104656.15179.12.camel@localhost.localdomain> <AANLkTi=3iCCDzbtuzHx7iD1qVTGadiPMnBNpHuVyuC-b@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343D45D7F94F@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTi=bK6oVTs+fBdpNqD0KU+1XU5wM++W2zqs61DwS@mail.gmail.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 23 Sep 2010 14:27:49 -0700
Message-ID: <AANLkTi=G9ga5Rf+zhSrJhS7yyAnU81CyL29bOP_fGq8w@mail.gmail.com>
To: Brian Campbell <bcampbell@pingidentity.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Simpilfying use of assertions when requesting an access token
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, 23 Sep 2010 21:27:48 -0000

On Thu, Sep 23, 2010 at 2:08 PM, Brian Campbell
<bcampbell@pingidentity.com> wrote:
> Do parameters defined by grant types really need a registry?  I mean,
> a client only presents one access grant request at a time so it's not
> like there's potential for name conflicts. Am I missing something?

There could be conflicts with other extensions that send parameters
alongside a grant request, no?

Marius