Re: [DNSOP] Please review in terminology-bis: Global DNS and Private DNS

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 15 January 2018 16:58 UTC

Return-Path: <ajs@anvilwalrusden.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 250F212E874 for <dnsop@ietfa.amsl.com>; Mon, 15 Jan 2018 08:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=kgVgUYrC; dkim=pass (1024-bit key) header.d=yitter.info header.b=i28qXjXG
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 TsP89Ms41yLx for <dnsop@ietfa.amsl.com>; Mon, 15 Jan 2018 08:58:20 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A746812E86C for <dnsop@ietf.org>; Mon, 15 Jan 2018 08:58:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 62251BDA57 for <dnsop@ietf.org>; Mon, 15 Jan 2018 16:57:49 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1516035469; bh=oJ1oybEJ6AT4kqFWf9d98rRE9tcXMPReMCIcDBKc35U=; h=Date:From:To:Subject:References:In-Reply-To:From; b=kgVgUYrC8+pkvAhRnKVrxTwq8FOKtuJhgHVJXuKvQXJTTB7JZsN3xqh05SLTFCNRP stW0BOfj1SoOmKXZ/et7Ib/nUx4KeuwoNo23BvKRSKKCteUcjMGWZhqONcdd8EuDJ0 QHxPHBoIF/iLKbyog69Tx5ParDdwH2rosK7LLgH8=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cMnGvjxeuBiK for <dnsop@ietf.org>; Mon, 15 Jan 2018 16:57:47 +0000 (UTC)
Date: Mon, 15 Jan 2018 11:57:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1516035467; bh=oJ1oybEJ6AT4kqFWf9d98rRE9tcXMPReMCIcDBKc35U=; h=Date:From:To:Subject:References:In-Reply-To:From; b=i28qXjXG9MV0j6zaeWeap8slurORiTql5CUkoBhZx2BSQMGzKraRJ88xzsPB4nsqs K5o003A2ECsbow1ea02MbEW51Stc9Kkqpa4IZ3T5JLhJc/y6efVd1r4+7DUOjh+a3F SsE36oE/eVA3BwuX/EVfHBlgW7gO8Zt/lHnpcdaM=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20180115165746.pg5mizheeyvj4hoe@mx4.yitter.info>
References: <8CB86DAB-B80E-469A-9BDA-7F1361634933@vpnc.org> <20171218135211.nul66bgdxczmg4lp@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20171218135211.nul66bgdxczmg4lp@nic.fr>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/fkS4Y3I7rvN6J5OdBAkN2XQmnQ8>
Subject: Re: [DNSOP] Please review in terminology-bis: Global DNS and Private DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 15 Jan 2018 16:58:22 -0000

Hi,

On Mon, Dec 18, 2017 at 02:52:11PM +0100, Stephane Bortzmeyer wrote:

> I think that it would be better to remove "global DNS". It is not a
> technical definition and it assumes things like the mythical "names
> operational community".

I don't believe the "names operational community" is mythical, since
it specifies behaviour through a formal mechanism for something that
goes in an IANA registry.  But the discussion of Global DNS is
imperfect, I agree.

> This draft is about DNS terminology. From the
> point of view of the DNS, ICANN and OpenNIC are the same (same
> protocols, same concepts, same names) even if their registration
> (i.e. non-DNS) policies are different.

I think that description is, however, inaccurate.  One of those DNS
operations is the public Internet name system -- the one with the root
published by IANA -- and the other one is not.  This is not different
from the distinction between split-horizon names, where some of them
can get answers from the public Internet and others cannot.  It is
also the way we can reasonably make the distinction between something
like local., which is a domain name that is not part of the DNS;
home., which is not delegated in the "global DNS" but might be in use
in the DNS in some locations; and com., which is delgated in the
"global DNS".  I think this is an important notion that impinges on
the DNS, and I think we need to be able to define a term to cover it,
but if people hate "global DNS" maybe we need a different term?

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com