Re: [DNSOP] on private use TLDS
Brian Dickson <brian.peter.dickson@gmail.com> Fri, 29 November 2019 19:10 UTC
Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7850120105 for <dnsop@ietfa.amsl.com>; Fri, 29 Nov 2019 11:10:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 af-O7elquong for <dnsop@ietfa.amsl.com>; Fri, 29 Nov 2019 11:10:36 -0800 (PST)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (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 295FE1200BA for <dnsop@ietf.org>; Fri, 29 Nov 2019 11:10:36 -0800 (PST)
Received: by mail-vs1-xe33.google.com with SMTP id n9so20101975vsa.12 for <dnsop@ietf.org>; Fri, 29 Nov 2019 11:10:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BY5oy6QJmewLybcl+CgOVpnqO6E88tUwjsdYDwsP9jI=; b=QueG6Ix1QofYfeB8JXolxXiv0A2JgHfGQjFXtMpoyW+5sELXa2o9f50QHvkMjItarS a3/C3KRWNNnn4xmFIc2/REmyISkcm0K4dw4r5AeBFp5+BesRweVPTjLwLfcnb64yiTf0 6E1prjYksf73a8Bmah1jxtAo3INXVmLLcffeNp/CRoy+W4XKCgFv+SqskS09NSPcV4JN LMd7URulcyOYuZG1saw50KMLLqVdDJvJT3KoFVfpPdFpovmMQspDJIy4yYrF76C3GytG n4hYy2lZXh4IL/BwRtiTP+se18aSEohx5vY2jUCGd06/DCDZuT9jYXnXuzzM5+r+7Hd1 WosA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BY5oy6QJmewLybcl+CgOVpnqO6E88tUwjsdYDwsP9jI=; b=tiZ1MTIJeGQFPKVh/bi3CN2LQ8SzW6kbsBpIaCRqPlscz/zMPmUwTa5VHLreXr8OPf Q8K/oevrfSrkcC6aiqv7HI/CVccrlYuiQugu7bz+2iF3vLrkSJxdasne/8mjfJWs+/mM 5pUG+S5VTVPm2fFGyOnOm+LKxgjvFASlTmA/h/CNS2Vz2/jdDymSOXv1u4DIHEzAOJzL Ak3KCkOAhhkU/O2TKCyju4WKnEGSkPvLipKLVyOkSCeghjBzWv0yfi97qK8VTQ2iPIhf M9RQJYc15WrjD4wbKX2yAfqqVqtnmK99+GWGmG+6WkGRZVvUQw1tQpqQwvWl3yNba2bV 7tXg==
X-Gm-Message-State: APjAAAUDd/0piJDxoBs6ZYMN5UgMkoXDC44qQNDJ3TNuGLT7oucCV0oG 2bL3UMIxeWmq8uc4ecZ1uKCqxTe0v/7U1O2tV60=
X-Google-Smtp-Source: APXvYqzAlpohSVkzQP9fI7Gg6LeCkRBOLlaDtIp6gwc2Ngf3osBxKFfH2kOPN2rja0wtq5zYyWEFj7NY4QIZA/gPtQM=
X-Received: by 2002:a05:6102:98:: with SMTP id t24mr3743076vsp.136.1575054635052; Fri, 29 Nov 2019 11:10:35 -0800 (PST)
MIME-Version: 1.0
References: <20191128165507.2A60BFDF451@ary.qy> <fb307c7a-348a-03d3-3d8e-8e683cec603d@dougbarton.us> <73256f09-8083-4b36-ad1e-f82f382a0b9c@Canary> <97b59027-2a25-d44f-c9b4-d1287cc211c1@dougbarton.us>
In-Reply-To: <97b59027-2a25-d44f-c9b4-d1287cc211c1@dougbarton.us>
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Fri, 29 Nov 2019 11:10:23 -0800
Message-ID: <CAH1iCiqhOn3yxNX3veJAAui=kHSLmcA3MaeZTTZ8n-a7pFOeow@mail.gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000633c6059880fcf2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/GVs3sZ8Q8qhLu62Vj9W0vlGf14A>
Subject: Re: [DNSOP] on private use TLDS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 19:10:39 -0000
On Thu, Nov 28, 2019 at 2:52 PM Doug Barton <dougb@dougbarton.us> wrote: > On 11/28/19 2:20 PM, Joe Abley wrote: > > > - has the advice to anchor a private namespace in a registered domain in > > the private namespace really been received and judged to be > > insufficient? > > Yes. > > > Or has it just not been received? Could such advice be > > delivered in a more effective way? > > The market has rejected this advice. I could bore you with examples and > reasoning, but I have never worked with a client in an enterprise larger > than a taco stand that didn't have at least one private domains set up. > > I don't think anyone doubts that you have tons of experience with lots of customers. However, there are very important differences between anecdotes and proper statistical studies. There are any number of reasons for why those might differ in meaningful ways. There could be populations which, for whatever reason, don't overlap with your set of clients, with different characteristics. There could be an inherent selection bias, in how your clients choose you or how you find your clients. Certainly, the size of your client set, is not very likely to be anywhere near large enough to be statistically significant, compared to the number of domain registrants worldwide (hundreds of millions). What folks are trying to say is, in order to build rough consensus, which is how the IETF works, it helps to have something (anything) to support your assertions, preferably something that can be easily confirmed ([citation needed]). And, does the use case you are concerned with, actually need to be at the TLD level? Would something like "internal.zz" not be just as suitable, assuming you concur with the ".zz" usability? (Substitute arpa for zz if you prefer.) Brian
- [DNSOP] on private use TLDS Roy Arends
- Re: [DNSOP] on private use TLDS Jim Reid
- Re: [DNSOP] on private use TLDS Bill Woodcock
- Re: [DNSOP] on private use TLDS Ted Lemon
- Re: [DNSOP] on private use TLDS David Conrad
- Re: [DNSOP] on private use TLDS Matthew Pounsett
- Re: [DNSOP] [Ext] on private use TLDS Paul Hoffman
- Re: [DNSOP] [Ext] on private use TLDS Matthew Pounsett
- Re: [DNSOP] [Ext] on private use TLDS Brian Dickson
- Re: [DNSOP] [Ext] on private use TLDS Paul Hoffman
- Re: [DNSOP] [Ext] on private use TLDS Petr Špaček
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Ted Lemon
- Re: [DNSOP] on private use TLDS John Levine
- Re: [DNSOP] on private use TLDS Joe Abley
- Re: [DNSOP] on private use TLDS Paul Vixie
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] [Ext] on private use TLDS Paul Hoffman
- Re: [DNSOP] on private use TLDS Joe Abley
- Re: [DNSOP] [Ext] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Roy Arends
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Joe Abley
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS John R Levine
- Re: [DNSOP] on private use TLDS John R Levine
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Jaap Akkerhuis
- Re: [DNSOP] on private use TLDS Brian Dickson
- Re: [DNSOP] on private use TLDS Brian Dickson
- Re: [DNSOP] on private use TLDS David Conrad
- Re: [DNSOP] [Ext] on private use TLDS David Conrad