Re: [DNSOP] Ben Campbell's Yes on draft-ietf-dnsop-nxdomain-cut-04: (with COMMENT)
"Ben Campbell" <ben@nostrum.com> Sun, 11 September 2016 12:51 UTC
Return-Path: <ben@nostrum.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 D660412B244; Sun, 11 Sep 2016 05:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level:
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 1mRcaxVBa_MK; Sun, 11 Sep 2016 05:51:54 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 D948612B239; Sun, 11 Sep 2016 05:51:54 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u8BCpnW1015464 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 11 Sep 2016 07:51:50 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: Ben Campbell <ben@nostrum.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date: Sun, 11 Sep 2016 07:51:45 -0500
Message-ID: <30ACBC35-CFC6-4C89-8C07-0AFCCDB47910@nostrum.com>
In-Reply-To: <20160911081619.m255yh2a7lqqibax@nic.fr>
References: <147346146854.30916.9464681523303571740.idtracker@ietfa.amsl.com> <20160911081619.m255yh2a7lqqibax@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; markup="markdown"
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1ZP1WEydqwPgzlP_xEC5lzhihmA>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop@ietf.org, draft-ietf-dnsop-nxdomain-cut@ietf.org, dnsop-chairs@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [DNSOP] Ben Campbell's Yes on draft-ietf-dnsop-nxdomain-cut-04: (with COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 11 Sep 2016 12:51:56 -0000
On 11 Sep 2016, at 3:16, Stephane Bortzmeyer wrote: > On Fri, Sep 09, 2016 at 03:51:08PM -0700, > Ben Campbell <ben@nostrum.com> wrote > a message of 25 lines which said: > >> One minor question: In section 2, paragraph 3, which behavior is >> "this behavior"? The continuing to use cached data under the cut, or >> the cached non-existence itself? > > Cached non-existence. It was clear before but the later addition of > paragraph 2 made it ambiguous. Thanks for noticing. I suggest to > replace paragraph 3 with: > > Another exception is that a validating resolver MAY decide to > implement the "NXDOMAIN cut" behaviour (described in the first > paragraph of this section) only when the NXDOMAIN response has been > validated with DNSSEC. See Section 8 for the rationale. > That works for me. Thanks! Ben.
- [DNSOP] Ben Campbell's Yes on draft-ietf-dnsop-nx… Ben Campbell
- Re: [DNSOP] Ben Campbell's Yes on draft-ietf-dnso… Stephane Bortzmeyer
- Re: [DNSOP] Ben Campbell's Yes on draft-ietf-dnso… Ben Campbell