Re: [apps-discuss] RFC 5785: Registration of .well-known services under HTTP to First Come

"Roy T. Fielding" <fielding@gbiv.com> Thu, 14 January 2016 18:15 UTC

Return-Path: <fielding@gbiv.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60DA1A8789 for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jan 2016 10:15:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bHplLS8AQbqx for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jan 2016 10:15:35 -0800 (PST)
Received: from homiemail-a54.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3451A8785 for <apps-discuss@ietf.org>; Thu, 14 Jan 2016 10:15:35 -0800 (PST)
Received: from homiemail-a54.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTP id 7096840133B1B; Thu, 14 Jan 2016 10:15:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=0urHgeEZj1VPM+42zPK9PPiXm80=; b=hBkgIh/JzRSG8GlEzIQ7Q+sG3hGs eOxPGmGbFuophQrdSrPsY8F/mPgO/QN/o9KkC4N5gK7mvijraeGbWTRMAk/RZonq BE0ppRDOWA3rbscbj8txiuYMyDR2LgkK1inF2tt8qD2qdCQCTnrs83sCUBlp95Cm XKgg/AhLei32h5s=
Received: from [192.168.1.2] (ip68-228-71-159.oc.oc.cox.net [68.228.71.159]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTPSA id E790640133B0D; Thu, 14 Jan 2016 10:15:26 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <5697B833.3000703@cisco.com>
Date: Thu, 14 Jan 2016 10:15:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1D4E4A5-3BB2-43C0-955C-FC3755951B22@gbiv.com>
References: <CAMm+Lwj=A+KbxOvxFrURZmTmYJuGD3rXvnRToLZ_L+v-Qv_L_w@mail.gmail.com> <F87BF4D5-98EB-4476-B07B-969BEF842EE2@mnot.net> <CAMm+LwiT+bATrwK4guD6qtqPBDiOkXqUeF4+jjLJoP5TYqi3_w@mail.gmail.com> <E5435AB2-4830-4C08-AC3D-AE1FB6E66C53@mnot.net> <5697B833.3000703@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/s0JohIW0qcr7ajHUDyJD4bJP86U>
Cc: Mark Nottingham <mnot@mnot.net>, General discussion of application-layer protocols <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] RFC 5785: Registration of .well-known services under HTTP to First Come
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2016 18:15:37 -0000

> On Jan 14, 2016, at 7:01 AM, Eliot Lear <lear@cisco.com> wrote:
> 
> Mark,
> 
> On 1/14/16 6:34 AM, Mark Nottingham wrote:
>> You can also register /.well-known/phks-protocols/ and do whatever you like under it.
> 
> By your own words, that's simply not true unless there is a
> specification tied to it, and personally I think that's a very high
> bar.

Why is it a high bar to require a written description of the identified
space?  It doesn't require an IETF spec.  Mark is right -- if there is a
spec of why the identifier exists, the owner can do anything with further
identifiers under that space.  A review is desired because almost half of
all proposed uses of .well-known are poorly conceived and more effectively
accomplished with a single link.  But the review does not require consent.

For example, PHB wants to do a standard name search of SRV after doing a
DNS lookup and then use the SRV record to redirect to a reserved URI space.
Sorry, that is brain-numbingly poor use of those protocols.  If the
standard name is standard enough to use under .well-known, then it is
standard enough to assign directly within DNS (just like www) by the
same admin that would have crafted an SRV record, which saves two
completely useless application redirects and a whole lot of ridiculous
discussion on IETF registration lists.

The discussion does not prevent a person from registering the space
anyway, if they happen to be as stubborn as any one of us, but at least
it gives us a record of why the identifier exists and maybe some legacy
understanding of bad uses of that space.

....Roy