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

Phillip Hallam-Baker <ietf@hallambaker.com> Thu, 14 January 2016 19:51 UTC

Return-Path: <hallam@gmail.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 283391AC427 for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jan 2016 11:51:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 2d8XE8XjRXq5 for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jan 2016 11:51:36 -0800 (PST)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EB611AC426 for <apps-discuss@ietf.org>; Thu, 14 Jan 2016 11:51:36 -0800 (PST)
Received: by mail-lf0-x233.google.com with SMTP id m198so122439746lfm.0 for <apps-discuss@ietf.org>; Thu, 14 Jan 2016 11:51:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=dsnvAtPwhp3rfISOQhUXCb/lcnJThCUTNVzGGobrYtU=; b=awfxKy1eLx5GtYmho0m2mgVRC/pmz5QsDcV8yOQRl1NzogxfC6tkznHRVEGegB2Vk5 YWRfIgvuM153vK2k4pgdwCOgXSBZbS9FqRjuN9qD4JgSJni2077MaAu6Pi1nyKl4XTHZ w/2BiLUZlnUmhHDMVm6mQDU5bHg3EWkKYhYRQCDXbD32GM8rYmatpvJu7GNbYT28tH/W 1KciHLEcakbq0znlitHiVerYOGShZqw1E4zHsH2MK+X4K2NXDE2hgX+QEP/w1HDkPrnZ cFNpIhsk/TdOf+n72nOxGK05cTjfp2gx1EIzT5Qqw7DYi6KTKPQkBMf2W8OijWSEYUPN +YKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dsnvAtPwhp3rfISOQhUXCb/lcnJThCUTNVzGGobrYtU=; b=C12Pcsp+NLtB4VuxtcwN87QBxZLu1bMxq2tN0lZPv9hoSXobP5fxpDffKsZ8brr5yQ qfQt3IK8IDICBA7AfFVjzZ9AnZuqQkWVNON9hJ7Qpxla9HFDsn+ZqtGHpl8me80TVVtQ GkoXEsfHccg0VUO7BiUBGJUp3ZFWAPllwq1aLXKrqZQxlalrG6f3TSd/e1DUwVG3teMK GsxQ4QvRv6n0AUSpz+w3QSGbN8D62lsNqJ4E6MuPPCrthPKZohDb5FKUxqnHqyFi0erD RqIRSbTJD6cXKFEAZekABBn4PemaKHGv2SUwpuxE/ZLiviw6ih4rJcpKS2FytoPxGi4O B4hQ==
X-Gm-Message-State: AG10YOSk/99/w04fhMER0WAh20esbkPIuNk3SqRIcpuNqkQdAyf7Fw6zOX6sofIYXF8i0re2zBj+gyBM1PDh9Q==
MIME-Version: 1.0
X-Received: by 10.25.170.203 with SMTP id t194mr967335lfe.48.1452801094530; Thu, 14 Jan 2016 11:51:34 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.1.33 with HTTP; Thu, 14 Jan 2016 11:51:34 -0800 (PST)
In-Reply-To: <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> <C1D4E4A5-3BB2-43C0-955C-FC3755951B22@gbiv.com>
Date: Thu, 14 Jan 2016 14:51:34 -0500
X-Google-Sender-Auth: 1iFlxY3gNLqyYZCcrgc67hird6Y
Message-ID: <CAMm+Lwj76ZQK3FDYU8qMKLovA69fC1_BfVvBpVMUj6YviUr1Dw@mail.gmail.com>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/z0jIf1ymeNpPkNSjPc4kD_RLfLA>
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 19:51:38 -0000

On Thu, Jan 14, 2016 at 1:15 PM, Roy T. Fielding <fielding@gbiv.com> wrote:
>
>> 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.

How about you apologize for the insult and try again?


You are certainly not expert enough in this space to be calling anyone
or their proposal mind numbingly stupid.

In fact it is precisely the attitude you are demonstrating here that
is the reason why I want to eliminate the registry troll from this
particular process.

No, being a designated expert is not an excuse to piss over other
people's proposals from a great height.

I will explain the reason for my architecture after you have apologized.



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
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss