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

George Michaelson <ggm@algebras.org> Thu, 05 July 2018 23:38 UTC

Return-Path: <ggm@algebras.org>
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 A4C94130E21 for <dnsop@ietfa.amsl.com>; Thu, 5 Jul 2018 16:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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=algebras-org.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 pJCUdemP8jWw for <dnsop@ietfa.amsl.com>; Thu, 5 Jul 2018 16:38:42 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 73EEC130E13 for <dnsop@ietf.org>; Thu, 5 Jul 2018 16:38:42 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id p11-v6so12740347wmc.4 for <dnsop@ietf.org>; Thu, 05 Jul 2018 16:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kIfdME99ol17VHa+yZamt03NE4oRz5ErlR32Qg/92ds=; b=J4IhNSmYIOpeN8DicbgEw1sQ2+M+j0MmcDPfZrLBaBvViFGvL4152BKsM6QA6P/+uV e+OeZGsFCGkISjwjyyRB+C7JzVGna52pWdF96YkMmatqnSKaIr4KBSCO8XfHQZqj7UsI OLHEXeo7zyYeI279DfTjmdLbjxTOFS7E/98i03IM5Q3Rapg4ksscWoxbyitHH81qi82P 6eJ7DnKehiwB10++bOfQ/8uHvkdxSZ97esb8e4tHE309sQES1UmM143kZK48X67buYd1 UJsheEup6SOj4INHV2pcenU9WX+wjk1ZaQMTZxNr8PvAAepH5sDjFFqyzoYVSpVviDP/ tI+Q==
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:cc; bh=kIfdME99ol17VHa+yZamt03NE4oRz5ErlR32Qg/92ds=; b=oHkgF2IeA/gYNV6qFf6AJhyKsq5RU0XQZaEczBmHPIDR9oskk6ElW/cLEe7GO3qhtL HfYy1Lndv4k+a0ej0Q3ONkTDFvh15uU6OMW2NmSBSLV+KyzpkSJ/gzbNAxnDOynCusUa Fp79mutk0y9dRrMLGkkuaN8PmwjH2YB0mN0rwBvHS0ZKOIBDn129liUPVaIhEw5dL9yp TPTiwWF4ZdWrde3hQPmWepxQ5rS6uIcWTrFGsrESR0OSyovc9OvA9uvTbIlm9KkqURrc tdCmvdHK72kJHNn4hane32qTl8N9s+fHbqPZsAJ8qp+PwMo7iB8x3Tn5C/JgITDsPUOF yr4g==
X-Gm-Message-State: APt69E2MXjawy2NzUpsVKr09QAt0PaeS7WDbqbl7Y8I7AoHeAF6YmywR 5MdkhlhVMrQIPfXdwPRrnQTYF5l+H4GxYHJlSSwzdQ==
X-Google-Smtp-Source: AAOMgpdlAwnog2UQ5MDTu8O88PMF6lNT0xp82ugeKC1CHsIkp8Pa89FmYQhfUAnDUT2ULfdWe3rtBYBjvEA4OUGDDoA=
X-Received: by 2002:a1c:8c08:: with SMTP id o8-v6mr4765985wmd.60.1530833920866; Thu, 05 Jul 2018 16:38:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a1c:12cb:0:0:0:0:0 with HTTP; Thu, 5 Jul 2018 16:38:40 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:29e3:df9:526:dcf9]
In-Reply-To: <CAKW6Ri7sxmosXq+m8iCmQwLXTvB8cgobOKcxsbB5r7P2_jgcsw@mail.gmail.com>
References: <17A1E6A9-E43F-41AB-B24D-4B29F17FCC07@gmail.com> <CAAiTEH-7bqUZJZbfPSP+2+r6fswixKsFdaNeMLzEQd6YfHpCsw@mail.gmail.com> <4B65C153-BF80-4266-A800-6B6DD6E1C6D6@hopcount.ca> <CAKW6Ri7sxmosXq+m8iCmQwLXTvB8cgobOKcxsbB5r7P2_jgcsw@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
Date: Fri, 6 Jul 2018 09:38:40 +1000
Message-ID: <CAKr6gn0eo=kad+uG4P_he=61=-4rZYA8oSGyUbRaKqJnQsY-BA@mail.gmail.com>
To: Dick Franks <rwfranks@acm.org>
Cc: IETF DNSOP WG <dnsop@ietf.org>, Matthew Pounsett <matt@conundrum.com>, Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SR-mx89NDsggvP8WJsoqODhBR_U>
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: Thu, 05 Jul 2018 23:38:46 -0000

Only the zone authority can publish a DNSSEC signed zone.

Anyone can claim to publish a view of a non-DNSSEC signed zone.

On Thu, Jul 5, 2018 at 7:11 PM, Dick Franks <rwfranks@acm.org> wrote:
>
> On 3 July 2018 at 16:40, Joe Abley <jabley@hopcount.ca> wrote:
>>
>> 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.
>
>
> 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.
>
>
> Dick
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>