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

Dick Franks <> Thu, 05 July 2018 09:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5B261130EA1 for <>; Thu, 5 Jul 2018 02:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SlgeejBYslab for <>; Thu, 5 Jul 2018 02:12:20 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EC5DC126DBF for <>; Thu, 5 Jul 2018 02:12:19 -0700 (PDT)
Received: by with SMTP id b188-v6so9861146wme.3 for <>; Thu, 05 Jul 2018 02:12:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=+KJHtCIPPPF2bjLpkhpCzWSijCusf6UhvQmKNzANV7Q=; b=awmkn2GXut+45TH83lvjJGcurVUQQ+OeF8xSCrEXB+40GBTsr1DcqkxySyeM06HPJ2 67A5M5sYa/baYqps4ellaLMUNk3Qvu+InvPLDvlD9xaA4Ilcr0arbnDp/7XvR4Sl4B/1 D7dK/P3nnnV1Y8Gl0f0M97dfmtEjxGzHkEeoHaqN8hyadpLmlLXW1rwpG27r78SBe+eZ 6IjHhvasnHljyXOax6G/0EhVyoq7HL6M0EfQeSU7ZbRcwWoJGMMZlUr061iqgCtKSHlJ e1GEUT4TDnNRzW17Kxlb9jRaD3422Za3fZlPOLTlwyWePR0S6S9uBJEX/vZcUfCSKrQ6 +Zsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=+KJHtCIPPPF2bjLpkhpCzWSijCusf6UhvQmKNzANV7Q=; b=Zn5sw2Y+yk525kotJ53crZAXqEmwYW+e2lh1Mf6krtPqeIpmHj7lrln/mvi+OybweN ydh5YfPiYOmJE11QtuY3CZ2bHrhZsSU8CAvWMeFwT9IRfB+2g+Ec03CKcTSv8W3lyBYX z02BjTgK5Nzv+D1wgYxuQ9+rBSgJpc5vA/Hr05Q6bg8jPs23uqEGv8+AP0ouKYB+WE8v NDalR/UxyqaSzfS2i+lUA94HSGRIZyQkQGqcOYwcJ2QuSlsRpN0AzJyXsdHsEKv534tt xNpJJnmTGhumCm40OlkGEh8zbpJPMv86KYZiNJLKWslNsyLeWhh58Y7NY8IL0dttLJoK tsBQ==
X-Gm-Message-State: APt69E2sP0PlDOJ4rFAug8onT2m0UqbQggGtcu0g7dUj57GS79LYYBIS w4i1ayeYfYl7rrNa5R+Xev2tEyIeu92n8ul4jJg=
X-Google-Smtp-Source: AAOMgpepPxm9mZx3YvVkiFvDcwlI8mA3bVqfkG5j6wxx4e3OSKlGrzulE6EEcOP/lYGJtKWsirMSNrQlQ1ZX/Cq/JFw=
X-Received: by 2002:a1c:2dc8:: with SMTP id t191-v6mr3733022wmt.94.1530781938286; Thu, 05 Jul 2018 02:12:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:adf:c7c4:0:0:0:0:0 with HTTP; Thu, 5 Jul 2018 02:11:37 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
From: Dick Franks <>
Date: Thu, 5 Jul 2018 10:11:37 +0100
X-Google-Sender-Auth: T3ye-nDRDYnBmpCm6q7H-7ghZjw
Message-ID: <>
Cc: Matthew Pounsett <>, Joe Abley <>
Content-Type: multipart/alternative; boundary="000000000000a9048d05703cf12b"
Archived-At: <>
Subject: Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-terminology-bis
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 Jul 2018 09:12:22 -0000

On 3 July 2018 at 16:40, Joe Abley <> wrote:

> On 3 Jul 2018, at 09:11, Matthew Pounsett <> 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.

agree, the word carries the usual dictionary meaning:

 publish  v.t. to make public; to divulge; to announce; to proclaim; to set
forth to the public;
   to put forth and offer for sale orig. any article, now books,
newspapers, etc.;
   to put into circulation.

zone generation without the "setting forth" does not appear to qualify.