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

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 15 January 2016 14:55 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 145101ACE82 for <apps-discuss@ietfa.amsl.com>; Fri, 15 Jan 2016 06:55:10 -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 7VA_NoWYEeJx for <apps-discuss@ietfa.amsl.com>; Fri, 15 Jan 2016 06:55:09 -0800 (PST)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (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 A6EFF1ACE80 for <apps-discuss@ietf.org>; Fri, 15 Jan 2016 06:55:08 -0800 (PST)
Received: by mail-lb0-x235.google.com with SMTP id bc4so315214417lbc.2 for <apps-discuss@ietf.org>; Fri, 15 Jan 2016 06:55:08 -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:content-type; bh=Fy10XWM5s9OJgHCndHyeQeeU6Rfn5H7DfsV+32nuG4Y=; b=kLfg2chBiNhXvS/QmZVQYwM4Xc7IdcaXN9DFt3At8adrQ2aynPEP0yxgPRGj1QE9ha U6zGO0p75Sw0X/Hp8ouSO2sTsASMTcSShDSRUhAF12JYLEbBMzMwdTRAy/9Zu9cuFHUk 1pHM6QFCtAlsv/g3/mWBhhIEs0koFGWJzV+BpBh8sjClUyVNLJ66beVy4yJ0TrWc08w0 5VAQopkSyhiuvgZ4McHxvuK/psTJVcS9MueGl1LFYxk3YpyuqvcuYLyJHQvwWQcTHXQF erbMB7m5pqUEZwmVS3arq8W9VTJK0VIxxFh4abu8TNxcDuZmIsJA6FGqjRz3XT2fwwYx E5fg==
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:content-type; bh=Fy10XWM5s9OJgHCndHyeQeeU6Rfn5H7DfsV+32nuG4Y=; b=F7N+0mV1yvi/BuXs4iwfBF971AU2pfeYjyrqWBy9TytMvmG8l8zd30C6UvQOsGio0M lA4yn0FUOl61VJRtCfYHwWgkyCqfR17FbOVXnZPVHxjP1gsnCOA51Opn5UAbpZpkQSc9 r7Dy1vRdKn31I7osgegpHjerSmy7H/YOODkR1wkG5MCOEyS1vkS9prs7xvqf/frlHzmL BK3Rg5dK2THctmbJH63xaJpGrkjTqauw5TPCiLnhKk2YsjBzjSQ38KShGPm6N/HXviru pLtGz3+fyDnJDkjgbajXPUTDha6v7R04xxXMf3nnLKjF0u0+X+elX1OShj8P4j9gGUOW AJSQ==
X-Gm-Message-State: ALoCoQmUwrrUcK9mDpbXV3hjh2udtBrLnLDxHgO2YvnC4QYsQCPIofHBKl7b7drCqlo7MM4dF6tHGKqtL+kqyP2Do46TRW49NQ==
MIME-Version: 1.0
X-Received: by 10.112.198.72 with SMTP id ja8mr3423654lbc.142.1452869706564; Fri, 15 Jan 2016 06:55:06 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.1.33 with HTTP; Fri, 15 Jan 2016 06:55:06 -0800 (PST)
In-Reply-To: <CAMm+LwiDJXwqMXmNcksTJeh0sn6_rvsGdnGu6-KtDcdGy1Wbvg@mail.gmail.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> <CAMm+LwiDJXwqMXmNcksTJeh0sn6_rvsGdnGu6-KtDcdGy1Wbvg@mail.gmail.com>
Date: Fri, 15 Jan 2016 09:55:06 -0500
X-Google-Sender-Auth: JIyoHU19DuXEX1XRBvijjZ0VkNw
Message-ID: <CAMm+LwjanCXwdqAPruTi6f7PLWHfHb0brQGEObKauui-5rWkVw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: General discussion of application-layer protocols <apps-discuss@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/HRvKcgAOSiwcQIA-PL1MsJ5OAfU>
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: Fri, 15 Jan 2016 14:55:10 -0000

Just to clarify a point people have brought up with me in private.

Yes, I am aware that Mark Nottingham is the DE for assignment of
.well-known URIs and not Mr Fielding.

That is something I was hoping Mark would point out himself. The
information is public, but it isn't necessarily something people
reading the conversation are aware of.

The reason I originally brought this up is because of complaints about
IETF process that I have received. The external perception of IETF is
that there is an inside clique who effectively gets to decide
everything through control of registration of code points. And right
now I have to agree with them.


I want this registry gone because I think it is an anathema to what
the IETF claims to stand for. Review by a Designated Expert is not an
open process. Review by a DE is not a consensus process. Review by a
DE is a distinctly unequal situation in which one party is Pope, the
other a supplicant.

Now there are cases where DE review is necessary because the code
points are limited. But this is not one of those cases and those cases
simply should not exist above the Transport layer.

The way to get architectural consistency is to describe an
architecture with sufficient clarity that people follow it as the
natural and easiest course to follow. My experience of multiple DE
reviews of URIs is that each has made demands that are completely the
opposite of the previous reviewers.

There is also a policy issue here which I think we are going to need
to discuss on the IETF list rather than here which is what level
policy should be set on such issues. Introducing a gatekeeper into the
process of deploying Internet applications is not a matter for one
working group or even one area.