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

Matthew Pounsett <matt@conundrum.com> Tue, 03 July 2018 13:11 UTC

Return-Path: <matt@conundrum.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 85C23130E02 for <dnsop@ietfa.amsl.com>; Tue, 3 Jul 2018 06:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.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 xorOfCRCQx5E for <dnsop@ietfa.amsl.com>; Tue, 3 Jul 2018 06:11:39 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 48E08130DF7 for <dnsop@ietf.org>; Tue, 3 Jul 2018 06:11:39 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id o5-v6so3022171itc.1 for <dnsop@ietf.org>; Tue, 03 Jul 2018 06:11:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=BvFTUv8LWsbGnMgH4Wf4wAdXSR8ccmdrdxiH1ewJgn0=; b=ma82nk9SNVyo1hZH6NaEvwXwPJvIpYvv4d/o8PHDpxjxBvSdPskh8KSWyPeGxo2ijS iTDrElEAY9+WI61o0WhmbTHQNKh1KI+yLZG/zGhyL0VsxpDov4FJVJUSw4PZcbbq15t7 LpXPMarfThjhK9zgf/rye0WtCA9W0xmO2jeJ0ahc8DawvG4mp3p7GMselIVJng9Stb2O goCj2elrN/Bo9kfS653p0QBLjxjd2vBgPrZ6C31Vg3vO+lDQ2N+7539DBx1eZ6ZFJjzx 9klZM+C1fQmCvcbeMEBTq/q67iEZOb9ljzNktCGfp5JNP75kG1eabv0UqHCuF4sXQP+8 qYFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=BvFTUv8LWsbGnMgH4Wf4wAdXSR8ccmdrdxiH1ewJgn0=; b=Bblxy0MJsS21gnRCW766H6tWbDQCz8NpCtAQZJsBXSLShGTYffmlsB62Rxyi6Vl74D GqN+KK8L7N0KPytWoQk/eR1N+fbkGB8r1bH6YYt2nIhZ60myICqROL4dBgncsuPpkACG DbJzX+c+ApaEIyi9ds6rrnXg/MxnIDHLTs6u9oyY/eymk9d7dLSCyREnHon7+Ec79HjN SvCTTbJHg/ZQgSehzoOGFKEpGhUSogKZG2fihzpqbDFemmKdFWjF6qtCZGX88B7TEtMQ JCg7jK5kdVK2xzgEtwEjIakn10LJpwmNNChbXoBrKaEEb1sgrbhk13eN5DCsipHrxHI1 uA8A==
X-Gm-Message-State: APt69E2WYHgaoBDwURoPevbSRfKhpIC9tLME/Y6m8+Nv6TAJuisC0CWh yf98GnRwBa0F7YTMG+PxjB+GTGyXxDDOrlecMk8aJ61iQgc=
X-Google-Smtp-Source: AAOMgpcLqNvhZq+yaScJFkiHRGba/Y7f7u9PuFPqDg/XngSBWFui3WFleVN0MsfJ0JhemkgrpEc4MFaMsPQcqaLv3No=
X-Received: by 2002:a24:1049:: with SMTP id 70-v6mr9482207ity.115.1530623498203; Tue, 03 Jul 2018 06:11:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a02:350b:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 06:11:37 -0700 (PDT)
In-Reply-To: <17A1E6A9-E43F-41AB-B24D-4B29F17FCC07@gmail.com>
References: <17A1E6A9-E43F-41AB-B24D-4B29F17FCC07@gmail.com>
From: Matthew Pounsett <matt@conundrum.com>
Date: Tue, 03 Jul 2018 09:11:37 -0400
Message-ID: <CAAiTEH-7bqUZJZbfPSP+2+r6fswixKsFdaNeMLzEQd6YfHpCsw@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e54d0c0570180df1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mT47pos_Xi3ldu88hrVWnu_uKxM>
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 13:11:42 -0000

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.

However, using such a broad definition of "publishing" seems, to me, to
introduce confusion in that it removes a clear distinction between the
steps of generating data, distributing those data, and then making them
available to be queried.  To draw a comparison, one might look to the steps
of writing, publishing, distributing, and selling a book (although I'm not
sure how the first two would map differently to publishing DNS data.. they
seem like the same step to me in this context).