Re: [DNSOP] WGLC for draft-ietf-dnsop-let-localhost-be-localhost-02

Joe Abley <jabley@hopcount.ca> Fri, 02 February 2018 02:57 UTC

Return-Path: <jabley@hopcount.ca>
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 013F512EB14 for <dnsop@ietfa.amsl.com>; Thu, 1 Feb 2018 18:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 M13FussfUNyN for <dnsop@ietfa.amsl.com>; Thu, 1 Feb 2018 18:57:39 -0800 (PST)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (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 1DBCF124B17 for <dnsop@ietf.org>; Thu, 1 Feb 2018 18:57:39 -0800 (PST)
Received: by mail-yw0-x232.google.com with SMTP id b16so9324428ywh.12 for <dnsop@ietf.org>; Thu, 01 Feb 2018 18:57:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XE+RLBx3lCiOOfGjS1oYFEwYVIj+0haWpHuDqQ290sQ=; b=OM/HiK2w6v4OqHV2xDuvCSE3EoLR4buwnanNsaGkb+lDurCPxx3JfkNLNr09EiPaO1 ZRkVAnWV4RSrioTaDsSb2Yuqyu8mWsRHXfWGSFeWNMiQgXlse2rFKAP2mc6BSVVpxdt1 Px/liXVcx4OsHL3hTG+vUYIHUkVaN7C2EJJCY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XE+RLBx3lCiOOfGjS1oYFEwYVIj+0haWpHuDqQ290sQ=; b=QTJ/Kh3NECXJzwcM4I7rgwGt1AmvXi+PSE2Hcm6IPWAUcJpVptqTUHhrtx5hAFKZaA 95s2PimIMtrMn3BgtgXPA35SILFv48R9enUYijX3QsdJArRmbb6YlIEub8ytmLgNTvrz B4zTQhq8Gtc6e2T8iJOuE6uAXlA0pMBcQpBFBdZ02ZK9EcxNydhUq+YJGdX8d0RawkFn BweXRvNPG/HUilQlS/Ul56cnCzUcWRkcO8uS+gGkS+e1H3oFaYlrIfTkrbP3ZjmFt+Zn gv/n0ZXLGc5J3Uhg5NyitN9s2e9DkfBTWU/UzCWdQTjXogOFPFtltcAVHsgY4+pDzxVK am2g==
X-Gm-Message-State: AKwxytcPdu+M72IaZ0P2OiHJxhZtap4Ko6UtU6pWM06sJ7pwAIJYiGfT IQQTuDMIFwA3fOF8WEdkgrNp2tEhsGk=
X-Google-Smtp-Source: AH8x227h2DVbfq3sUQXZFdcjaruFJ4DIOUiUkXbiSA4TG1GvfM1Myj5iiZeaAhuCLaZIIQjbW7L+tg==
X-Received: by 10.13.250.3 with SMTP id k3mr26337305ywf.21.1517540257946; Thu, 01 Feb 2018 18:57:37 -0800 (PST)
Received: from ?IPv6:2607:f2c0:101:3:4807:15a5:8535:186? (node-131dv3xxjyn3t8n4au.ipv6.teksavvy.com. [2607:f2c0:101:3:4807:15a5:8535:186]) by smtp.gmail.com with ESMTPSA id c188sm439405ywf.18.2018.02.01.18.57.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 18:57:36 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-63D07649-514D-4EF9-BD9C-E0396AE7AA75
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (15D60)
In-Reply-To: <7E650D7B-AE5D-4AF1-91D1-A11C0DADEE17@fugue.com>
Date: Thu, 1 Feb 2018 21:57:35 -0500
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, dnsop@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <78719D30-A64C-437D-9237-B810D0FCEBD6@hopcount.ca>
References: <5A6F5CF1.4080706@redbarn.org> <CA+nkc8D7tne5SxGOUhvJqstmDa=1=RmvcHQte1byAab5dUd5sQ@mail.gmail.com> <AE634FC4-0EAF-4F54-8860-61E41284F873@fugue.com> <20180130185919.GJ19193@mx4.yitter.info> <3b57a486-df8e-ca57-ab89-c167cea0dcc9@bellis.me.uk> <20180131161507.GP3322@mournblade.imrryr.org> <20180201172644.GD26453@mx4.yitter.info> <1D7693F7-000C-451A-8F7A-45B94366240F@fugue.com> <20180201204833.GA27125@mx4.yitter.info> <777C7B4A-A8D6-4E14-9DBF-360B6BDF4A95@fugue.com> <20180201214101.GA27672@mx4.yitter.info> <F9120EAD-486F-414C-9797-CA5CA05B42A6@fugue.com> <778568AB-F162-43BA-925F-B8FDF187C5F3@hopcount.ca> <7E650D7B-AE5D-4AF1-91D1-A11C0DADEE17@fugue.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PHvf84fnc9ZgXuur2psCIJa7T8U>
Subject: Re: [DNSOP] WGLC for draft-ietf-dnsop-let-localhost-be-localhost-02
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: Fri, 02 Feb 2018 02:57:41 -0000

> On Feb 1, 2018, at 21:03, Ted Lemon <mellon@fugue.com> wrote:
> 
>> On Feb 1, 2018, at 7:46 PM, Joe Abley <jabley@hopcount.ca> wrote:
>> Can we take a brief pause to acknowledge that "the DNS" as a phrase is highly ambiguous and think about whether we mean the protocol, any particular implementation, any particular installation or the namespace (and if so, which one, since there are many, even if our context is a single Root Server System serving a single Root Zone, note capitals, which I think it should be).
> 
> This is the distinction I was trying to hit (and that I think Andrew agreed on) when I made the distinction between the set of all domain names, and the set of names "in the DNS."

Which distinction? I think I listed at least four degrees of freedom.