[OAUTH-WG] draft-ietf-oauth-dyn-reg-11 section 4.1
Tim Bray <twbray@google.com> Wed, 05 June 2013 21:01 UTC
Return-Path: <twbray@google.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1885021F8F78 for <oauth@ietfa.amsl.com>; Wed, 5 Jun 2013 14:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level:
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHKPJal+cdy1 for <oauth@ietfa.amsl.com>; Wed, 5 Jun 2013 14:01:13 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 9B43E21F8EAD for <oauth@ietf.org>; Wed, 5 Jun 2013 14:01:12 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id 10so5155334ied.28 for <oauth@ietf.org>; Wed, 05 Jun 2013 14:01:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=aohSZ6p414+8VkZ7Rsuyeoxqp2l+Wf4AdDf1m3bK4K4=; b=FdUeYDUEWD3RMDianfnpIQHJaJHc20QjZdp6NZac53exXm1r+mJPdLu3nf2VWA3zWe V9JCphIyBn1YllJP9bPoX50sonDTJufYffdoHEpzcaSyCmTezAhmGoXvk7bDCtkiCsUb eyhkDLsvJAFjuY6PQWnDnKSF1qmx7LB/qBRKby+uqMe9Biyv+/KnWN1qZX0urlMbChvq F3qw7GzXeuQ+N5LyZVSRqvtK0YOLr4FJTR8eqnBL+J6U1dkWnl7pBAZyYvgcPfTEDNGR 4jJr0xE3wd9ceNHmjhrbfAlLW8Ur2nzeT2N17q8G0aXvNcOJw2OSRJ2sjOTrQIGvTITg fNCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-gm-message-state; bh=aohSZ6p414+8VkZ7Rsuyeoxqp2l+Wf4AdDf1m3bK4K4=; b=airCILeDNqwYed1NJzDbyt5/LR/C90MQBvdohfEIpj7xbNXUJ2iwY2sKOX6l8+Q78i sboDS0LyVabrq3xikqOsm2JneTlqE3W+RfHcAtdegfxH6bKQLwWdX+i0NRRv9AF9WaMz p6WDDxXiCPWOCWzz6WRvk+a0dzn9LueYRAu8HtRZov94MlvaelCc5oSqIfOMiz9asD1s 9xNkFGTF9U0L4mAxq7JRzi0SI78PJHv2VOpYj9osKOL4QKopqSvNpGmCqxw41rAHsO/2 6hxd/2+nkJU7GMnjXh1rACVfAW060aqfURLnb8GFxnoDV4U+f4g96alAATr0VPWpo8lz tnvA==
X-Received: by 10.50.85.51 with SMTP id e19mr4168922igz.106.1370466069583; Wed, 05 Jun 2013 14:01:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.23.103 with HTTP; Wed, 5 Jun 2013 14:00:39 -0700 (PDT)
From: Tim Bray <twbray@google.com>
Date: Wed, 05 Jun 2013 14:00:39 -0700
Message-ID: <CA+ZpN27-anFCKX7os5SrU_0eRE2RJPg2z1xpqTDKUwe2ZhoHtQ@mail.gmail.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="089e0149bbb841858f04de6e7ff5"
X-Gm-Message-State: ALoCoQlmxPcvOJMW5abVbKGEwvH9AaJjxrtve0urGZEU5886DBeAu++LnT0euHCuVW2h1fBt4G9eTBkIMCF+86IojtuI8RP+Q71x10rg/WHgMAip32m1qIfbamYGH/GyKcuVNm9IdiWa85+Hqx/g8XAgYj4dXDkH5FQmYp73IL2wKl2j+w0LUxqaUAjDet4Am1qaP8VimNMy
Subject: [OAUTH-WG] draft-ietf-oauth-dyn-reg-11 section 4.1
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 05 Jun 2013 21:01:15 -0000
Section 4.1. Forming the Client Configuration Endpoint URL Why not discard the last three paragraphs? Server side implementers have a problem in how to create a client-config endpoint & remember what it applies to. I can think of several different ways you could approach this, the spec guidance is superfluous.