Re: [DNSOP] [Ext] Working Group Last Call for draft-ietf-dnsop-7706bis

Wes Hardaker <wjhns1@hardakers.net> Wed, 20 November 2019 10:08 UTC

Return-Path: <wjhns1@hardakers.net>
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 EDA291208DE for <dnsop@ietfa.amsl.com>; Wed, 20 Nov 2019 02:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 V9PS3nZgpJyD for <dnsop@ietfa.amsl.com>; Wed, 20 Nov 2019 02:08:43 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3B3D120827 for <dnsop@ietf.org>; Wed, 20 Nov 2019 02:08:43 -0800 (PST)
Received: from localhost (dhcp-9208.meeting.ietf.org [31.133.146.8]) by mail.hardakers.net (Postfix) with ESMTPA id DDE1328F59; Wed, 20 Nov 2019 02:08:39 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: Wes Hardaker <wjhns1@hardakers.net>, dnsop <dnsop@ietf.org>
References: <CADyWQ+EOj_G=qYSn15QCvi21nCyf=62=sB+RrvzAJKq51Xqivg@mail.gmail.com> <yblr22bcp6m.fsf@w7.hardakers.net> <47A6F985-1601-4C42-93AD-931E5B5A49BB@icann.org>
Date: Wed, 20 Nov 2019 02:08:38 -0800
In-Reply-To: <47A6F985-1601-4C42-93AD-931E5B5A49BB@icann.org> (Paul Hoffman's message of "Sat, 16 Nov 2019 09:34:12 +0000")
Message-ID: <yblmucqyi55.fsf@wu.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IKHqtz2x3W5JyfgaMGedQornFsc>
Subject: Re: [DNSOP] [Ext] Working Group Last Call for draft-ietf-dnsop-7706bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 20 Nov 2019 10:08:45 -0000

Paul Hoffman <paul.hoffman@icann.org> writes:

Hi Paul,

Thanks for the considerations and the changes made.

> > 3. Though the document has "relaxed" the specification to not require a
> >   loopback address/interface, this is still functionally a no-op since
> >   it still requires only serving data from the localhost.  That's not
> >   really relaxing it much; it just means functionally the same thing
> >   with a slightly wider view of how to implement it.
> 
> Please note that the word "localhost" no longer appears in the
> document.

True, but that's largely the semantics around the loopback.  The phrases
"same host" and "same server" appear instead, which is functionally
nearly the same thing from a logical point of view.

Anyway, I'm not suggesting it change.  So I shouldn't send this mail.

> > 10. For A.1, second paragraph about LocalRoot, can you replace with the
> >    following text (assuming you agree with it):
> > 
> >    The LocalRoot project (<https://localroot.isi.edu/>) is a service
> >    that embodies many of the ideas in this document and is operated in
> >    cooperation with USC/ISI's root server.  It distributes the root
> >    zone by AXFR, but also offers DNS NOTIFY messages when the LocalRoot
> >    system sees that the root zone has changed, providing potentially
> >    faster updates to local root implementations.  It additionally
> >    provides secured AXFR transfers, which helps defeat issues with
> >    unsigned glue records being potentially modified in transit (see
> >    Section 2).
> 
> I'm hesitant to do this because the text you give here is different
> than the text on the web site with respect to the status of the
> server, and with respect to the availability of TSIG.

Huh?  Can you clarify "with respect to the availability of TSIG"?

-- 
Wes Hardaker
USC/ISI