IETF Logo Mail Archive

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-root-loopback

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 04 June 2015 23:49 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 971B31ACD57 for <dnsop@ietfa.amsl.com>; Thu, 4 Jun 2015 16:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=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 XZqsXyq_4Dpk for <dnsop@ietfa.amsl.com>; Thu, 4 Jun 2015 16:49:04 -0700 (PDT)
Received: from proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 415131ACD5C for <dnsop@ietf.org>; Thu, 4 Jun 2015 16:49:04 -0700 (PDT)
Received: from [10.20.30.109] (142-254-17-100.dsl.dynamic.fusionbroadband.com [142.254.17.100]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t54NmSDt080866 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jun 2015 16:48:29 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 142-254-17-100.dsl.dynamic.fusionbroadband.com [142.254.17.100] claimed to be [10.20.30.109]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <alpine.LSU.2.00.1506042353420.30373@hermes-1.csi.cam.ac.uk>
Date: Thu, 04 Jun 2015 16:48:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8AAA0137-32F5-4844-97A8-BCF6B507D2FE@vpnc.org>
References: <5570CA65.90304@gmail.com> <alpine.LSU.2.00.1506042353420.30373@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/jL9jjlCR_L2u8fDdX7dtc8B1Et4>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-root-loopback
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 04 Jun 2015 23:49:05 -0000

On Jun 4, 2015, at 4:05 PM, Tony Finch <dot@dotat.at> wrote:
> Are there any implementations of this draft?

Assuming you mean "is anyone deploying the ideas in this draft, particularly those in Appendix B", that would be good information for the authors to have.

> If resolvers are encouraged to use NSEC records to synthesize NXDOMAIN
> responses, would there still be any point to this draft?

Yes. No one has written up a document on using NSEC records to synthesize NXDOMAIN for the root, and if they do, there will certainly be operational considerations for that that are different than the operational considerations for this draft. I'm not saying one would be better than the other, but I suspect that the operational description of this draft would be easier for an operator to understand.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email