Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-terminology-bis

Joe Abley <jabley@hopcount.ca> Tue, 03 July 2018 15:40 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 46F48130F23 for <dnsop@ietfa.amsl.com>; Tue, 3 Jul 2018 08:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 gUOH23FXuqNm for <dnsop@ietfa.amsl.com>; Tue, 3 Jul 2018 08:40:39 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::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 1257D130E50 for <dnsop@ietf.org>; Tue, 3 Jul 2018 08:40:39 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id j185-v6so3482314ite.1 for <dnsop@ietf.org>; Tue, 03 Jul 2018 08:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=rCGrdhmAtyJ/oPbjWsvLcymLAvFbmFggxoWSYCSG9rM=; b=YXBScftfgV0SrejnkXxNGcl5Of86MeLlv9n/1pOzQ91vbaeWWt7OrXC1v7jxeTAywb DuV8/haEhF9xoqkCtn2w/3wqh7/Poqx051MxkjVAguK3oGTbri+hzS7FHGn6MnuTOjF1 DqG0iLD/9meltdrt4aAWLM39FevmpNi/evO7c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=rCGrdhmAtyJ/oPbjWsvLcymLAvFbmFggxoWSYCSG9rM=; b=p1nkamrd149E5+v9XjU3zERzH9xSvffv6eTNpW+e49brGEekZkd2jj9W9Mbvsq3a31 ZeX/tgj9K1tZqMjS4XzFK+7ocomxvJaOfoCWdO+3ailJU9JttQls/eC4cZBkpHoPSl6b BUTyqXC3tIySN/U0BSIJ0DLHs4fIdtcBwVaaERRCCEqpdZGBDjno0+Ue4OxUK9aejemV ojOEWKIL5URFOw9jBgAhFKYQCZsFqXfcNP4/7jAo6+jg5LUKzv99MWuREPqVNk+vmPJ2 tcwmsEVFdJ/yZC/RoHd5spnE94RKCktKcTitRwVmp6yijYAZ9yXy8+ZHaVSr3aY82i6t +wPQ==
X-Gm-Message-State: APt69E1cwyaOmQk/879nIh9w0u2IRaWjUc9SEsQfLcMu7DCmZivhZWv3 Jv4fWomx5uQNkEfYKSUE5tDnRou4fI8=
X-Google-Smtp-Source: AAOMgpfbreG7tC2RvrtPGghrqnLZjUdyw/jusygAgV+kUD2H1G22vrSuNYhq69kC3rkL/LY9fImhGQ==
X-Received: by 2002:a24:1344:: with SMTP id 65-v6mr10237929itz.82.1530632438332; Tue, 03 Jul 2018 08:40:38 -0700 (PDT)
Received: from node-131fehozrcv7qa1ba8.ipv6.teksavvy.com ([2607:f2c0:101:203:69a6:ec16:e5e1:1160]) by smtp.gmail.com with ESMTPSA id x8-v6sm644780ith.17.2018.07.03.08.40.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Jul 2018 08:40:37 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Message-Id: <4B65C153-BF80-4266-A800-6B6DD6E1C6D6@hopcount.ca>
Content-Type: multipart/signed; boundary="Apple-Mail=_F287E480-1996-44CC-AC47-EEBED49FAB13"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Date: Tue, 03 Jul 2018 11:40:35 -0400
In-Reply-To: <CAAiTEH-7bqUZJZbfPSP+2+r6fswixKsFdaNeMLzEQd6YfHpCsw@mail.gmail.com>
Cc: dnsop <dnsop@ietf.org>
To: Matthew Pounsett <matt@conundrum.com>
References: <17A1E6A9-E43F-41AB-B24D-4B29F17FCC07@gmail.com> <CAAiTEH-7bqUZJZbfPSP+2+r6fswixKsFdaNeMLzEQd6YfHpCsw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/78inG0scI396ZAVg4uyUaWCOM1c>
Subject: Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-terminology-bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 03 Jul 2018 15:40:43 -0000

On 3 Jul 2018, at 09:11, Matthew Pounsett <matt@conundrum.com> wrote:

> This is not a complete review of the latest revision.. I'm hoping to get to that in a day or two.   But I've got a question about whether something should be added to the document..
> 
> A question came up in conversation recently about the use of the verb "to publish" in reference to managing DNS data.  It quickly became clear that there may be a common overloading of terms, where the same word means different things to different people.  I wasn't sure this fell into the scope of the terminology document, but I just checked and it does use "publish" in reference to DNS data, so perhaps we should come up with a definition for that.
> 
> To me, publishing DNS data has always meant the generation of the zone and the data it contains, as distinct from distributing the zone (to name servers, possibly though zone transfer) and serving the zone (making it available to be queried on a name server).  To the person I was speaking to, "publishing" meant putting that data on Internet-facing name servers that would answer queries about it.

To me, DNS data is published when it is made available to actors who wish to consume it. That means serving the data (i.e. having servers with the data available to answer queries). I have never heard "publish" used to mean zone generation. A zone, once generated, is not published until it is available for access by others.

If there is actually widespread confusion about this I agree it might make sense to clarify (but if there's widespread difference in usage, the best we can probably do in a non-prescriptive dictionary is describe the conflicting uses, and I have my doubts that that in and of itself will reduce confusion).


Joe