Re: [DNSOP] kskroll-sentinel and unclear results
"Paul Hoffman" <paul.hoffman@vpnc.org> Fri, 01 June 2018 00:41 UTC
Return-Path: <paul.hoffman@vpnc.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 C3FFA124205 for <dnsop@ietfa.amsl.com>; Thu, 31 May 2018 17:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 bAdedNSBQ7yh for <dnsop@ietfa.amsl.com>; Thu, 31 May 2018 17:41:36 -0700 (PDT)
Received: from mail.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 434F21241F5 for <dnsop@ietf.org>; Thu, 31 May 2018 17:41:36 -0700 (PDT)
Received: from [10.32.60.119] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w510ebsD043484 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 31 May 2018 17:40:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [10.32.60.119]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: "Wessels, Duane" <dwessels@verisign.com>
Cc: dnsop <dnsop@ietf.org>
Date: Thu, 31 May 2018 17:41:33 -0700
X-Mailer: MailMate (1.11.2r5479)
Message-ID: <FC2E8466-4D0A-4EE4-8E90-8B04A65134CA@vpnc.org>
In-Reply-To: <B62A1B20-9318-4936-B1D1-A5EDC23FC877@verisign.com>
References: <A53AF3DD-205D-4A8D-82DF-3255287FAFB0@vpnc.org> <CAHw9_iLV3R8YxZdN1==FBhekrmSDx+xPm1_Xj8q_1qi0MJ6FGQ@mail.gmail.com> <607759DF-1039-4BA9-A48C-60CF54398BA5@vpnc.org> <B62A1B20-9318-4936-B1D1-A5EDC23FC877@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9xxpyYjQTkNhDE4VejDFa_9CXcQ>
Subject: Re: [DNSOP] kskroll-sentinel and unclear results
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 01 Jun 2018 00:41:38 -0000
On 29 May 2018, at 16:46, Wessels, Duane wrote: > I took a look at your pull request. I like the direction this is > heading, and > I like the change from "invalid" to "bogus." Great, thanks. > It leaves me with a couple > of questions though. > > Your new second paragraph of section 3 says "this entire section is > about > DNS resolution systems" and "we can classify DNS resolution systems > into > five distinct behavior types" but the subsequent descriptions of Vnew, > Vold, etc still talk about a single resolver? Now fixed. > > Similarly, in Appendix A should the text be changed so that, for > example, > instead of saying "Bob is not using a validating resolver" it says > "None > of the resolvers in Bob's DNS resolution system are validating"? > > "All of Charlie's resolvers are validating..."? > > "All of Dave's resolvers implement the sentinel method..."? I started to make this change, but it made some of the sentences quite awkward. Instead, I added a sentence at the top of the appendix that says "The examples here all assume that each person has just one resolver, or a system of resolvers that have the same properties." > Nitpick: > > "If a client directs these three queries to a DNS > resolution system where the resolvers have different propertied, > the results cannot be determined." > > Should be "properties" and I'd say "cannot be reliably determined." Now fixed. --Paul Hoffman
- [DNSOP] kskroll-sentinel and unclear results Paul Hoffman
- Re: [DNSOP] kskroll-sentinel and unclear results Warren Kumari
- Re: [DNSOP] kskroll-sentinel and unclear results Paul Hoffman
- Re: [DNSOP] kskroll-sentinel and unclear results Wessels, Duane
- Re: [DNSOP] kskroll-sentinel and unclear results Warren Kumari
- Re: [DNSOP] kskroll-sentinel and unclear results Warren Kumari
- Re: [DNSOP] kskroll-sentinel and unclear results Geoff Huston
- Re: [DNSOP] kskroll-sentinel and unclear results Paul Hoffman
- Re: [DNSOP] kskroll-sentinel and unclear results Paul Hoffman
- Re: [DNSOP] kskroll-sentinel and unclear results Geoff Huston