Return-Path: 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 C8E7728C175 for ; Fri, 25 Jun 2010 11:12:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.468 X-Spam-Level: X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599] 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 fCOs0zOGUnLw for ; Fri, 25 Jun 2010 11:12:58 -0700 (PDT) Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id ECED828C172 for ; Fri, 25 Jun 2010 11:12:57 -0700 (PDT) Received: by pvc21 with SMTP id 21so1396008pvc.31 for ; Fri, 25 Jun 2010 11:12:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=IJCJkGQeVkvWj8uIREJPLekHcXSU+MLbhv8fL1iM370=; b=nbYhegJL9heQA1H1yH1QCMj0xYw26+GAwp7eKUZKgt+uO7HWwEy9yLAFWsM4kV96Iu S6KD+CGsrRnbUvWNuNGyllMtMPIvKyQ7huNEkkITXMa/VIoApi1jdisxotm/BaBjVCbj GWtRU1vUW+bzP60WiO14BfOU9h6XQuf64G8JE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=SHsFN+q+UHkAVRNiLCaWfC0ZBy+njFckAml+0fvqnhJxAbQ4k/BhSAfPe4BoDz99/Q hxpx6V1GztYJfrU9vHcoLRAxFBVQts//bJ98cmSy5ZVMRBsdkFK0e6gJq/1oZEd/Vwbb 7gSaSMSLckuam03/1Ev0lBBoHlocCegYJWvXw= Received: by 10.114.188.3 with SMTP id l3mr1332483waf.150.1277489578039; Fri, 25 Jun 2010 11:12:58 -0700 (PDT) Received: from [192.168.1.2] (c-24-130-32-55.hsd1.ca.comcast.net [24.130.32.55]) by mx.google.com with ESMTPS id c22sm70123269wam.6.2010.06.25.11.12.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 25 Jun 2010 11:12:57 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Dick Hardt In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3EC84973@P3PW5EX1MB01.EX1.SECURESERVER.NET> Date: Fri, 25 Jun 2010 11:12:55 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3D3C75174CB95F42AD6BCC56E5555B4502BE07CC@FIESEXC015.nsn-intra.net> <90C41DD21FB7C64BB94121FBBC2E72343B3EC84973@P3PW5EX1MB01.EX1.SECURESERVER.NET> To: Eran Hammer-Lahav X-Mailer: Apple Mail (2.1078) Cc: "Tschofenig, Hannes \(NSN - FI/Espoo\)" , OAuth WG Subject: Re: [OAUTH-WG] Extensibility for OAuth? X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2010 18:13:01 -0000 Would you elaborate on your reasons here? Do you think we have = enumerated all the possibilities?=20 On 2010-06-25, at 10:59 AM, Eran Hammer-Lahav wrote: > I would rather limit the ability to extend the two endpoints beyond = their current architecture, and instead, allow others to specify new = endpoints (e.g. a device endpoint for getting an authorization code = without using browser redirection) that work in addition to the token = endpoint (using an existing grant type or assertion).