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

william manning <chinese.apricot@gmail.com> Fri, 06 July 2018 04:57 UTC

Return-Path: <chinese.apricot@gmail.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 120FE130E94 for <dnsop@ietfa.amsl.com>; Thu, 5 Jul 2018 21:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ZVJhmFeixwro for <dnsop@ietfa.amsl.com>; Thu, 5 Jul 2018 21:57:18 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 56969130DDA for <dnsop@ietf.org>; Thu, 5 Jul 2018 21:57:18 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id l16-v6so15470730ita.0 for <dnsop@ietf.org>; Thu, 05 Jul 2018 21:57:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=o+u0lQjkB0WOuOdcv6fm6KhxVy/ov/70nPOJ3/t3zSw=; b=XgwDq6R6Yr0yZ5aBvrmOwsteLdwvzSx5EdtT3++QRxdlnWa8apkY3Dt1FxUTKI6Fb0 M+YhXDJWScdGRn7MmdfTz/lKfaYbyGP6rCyKWmE7U8wXDxVycLZV+ryBieO/wKNhyEDc tikP6V10/oOCftotIgc+VP9BzxJT9io+aUytY2jilS/X+lK7TyLZF2hPPZPBqzTC6D4f 0GcdTanRTqlfJtIDwqDrxzUHrY/cJg584wALBBcNQN0xGU2lqRA+IEvHrPUOggPvwv31 2/9nReHxmcBjB9NLib6WqdVDIMrjvxq0eTOKg4mTaZEBSymj3aBg8lhU1pIyTcqOFEFL dgCA==
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=o+u0lQjkB0WOuOdcv6fm6KhxVy/ov/70nPOJ3/t3zSw=; b=FLo8I7zhS9YXe0bpplXty3ANqoWhKZ/Sn0ih64I7X0XRRqvXvwxHg5GUNtqxiJO6HB T6pSOgXHEM71sql6yMJlLv3ZDH/HC4UXx2EidpHnLfv/vbw0gejboagK1ImfLSNSx1yd 1NGKYAMiGdb+cmJZH+zqW3iLD21+EtnQfkzEb1bdn+VxWoRHref1uj9x+2qcUzrDdUy/ lMX9Gq9dg2aRIqwmJ2h6heoZ2NV+5cg6P2Hacp2Wj4CeR2UlBPIUlpBRKlx1rNE19FE7 T9GKUZhZka7abtP/ECawYNeALWhO78s14P2Z/YkwmCWXuxo/swYmwmzftxv21V6/FTuN gdWA==
X-Gm-Message-State: APt69E1wmnc+9BDuV6UaKAQVIP/JkW5/5BaNXrZu/g9pAEFe0yVQ0KAX Dgf0SgohUcGrvhWkE4mdfjrhB2xQTVOqxIb+s9g=
X-Google-Smtp-Source: AAOMgpdLSJtq0Hs1EKVYilV3+9YflLrVOyuYVItgY2VNgWhDG4Y8J9VhB+0BpAcVD2bsnr8uU5Bg60KD4qfl5yT2tjg=
X-Received: by 2002:a02:4f1b:: with SMTP id c27-v6mr7264919jab.39.1530853037400; Thu, 05 Jul 2018 21:57:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a6b:d40f:0:0:0:0:0 with HTTP; Thu, 5 Jul 2018 21:57:16 -0700 (PDT)
In-Reply-To: <CACfw2hgRrogP5tPU_-Bi800eZCuF4NQa=iqcCXdo8+QxrC1B7w@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> <CAKr6gn0eo=kad+uG4P_he=61=-4rZYA8oSGyUbRaKqJnQsY-BA@mail.gmail.com> <CACfw2hgRrogP5tPU_-Bi800eZCuF4NQa=iqcCXdo8+QxrC1B7w@mail.gmail.com>
From: william manning <chinese.apricot@gmail.com>
Date: Thu, 5 Jul 2018 21:57:16 -0700
Message-ID: <CACfw2hjL-tN7wK6ak95ap8NLrpyACaOJftVv4403vp206e6kuw@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007f679505704d7fc4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XHQKqFh7TZp1G034z4HicjZUnHc>
Subject: [DNSOP] Fwd: 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: Fri, 06 Jul 2018 04:57:22 -0000

---------- Forwarded message ----------
From: william manning <chinese.apricot@gmail.com>
Date: Thu, Jul 5, 2018 at 9:55 PM
Subject: Re: [DNSOP] Working Group Last Call on
draft-ietf-dnsop-terminology-bis
To: George Michaelson <ggm@algebras.org>


true enough,  there is a single, canonical dnssec signed zone which can
only be generated with explicit, auditable permission of the zone
authority.

/Wm

On Thu, Jul 5, 2018 at 4:38 PM, George Michaelson <ggm@algebras.org> wrote:

> 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
> >
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>