IETF Logo Mail Archive

Re: [DNSOP] draft-ietf-dnsop-kskroll-sentinel-10 and AD

"Paul Hoffman" <paul.hoffman@vpnc.org> Tue, 03 April 2018 13:42 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 6C4731275AB for <dnsop@ietfa.amsl.com>; Tue, 3 Apr 2018 06:42:11 -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 yZamqu4E2pRl for <dnsop@ietfa.amsl.com>; Tue, 3 Apr 2018 06:42:10 -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 38D35126BF7 for <dnsop@ietf.org>; Tue, 3 Apr 2018 06:42:10 -0700 (PDT)
Received: from [10.32.60.77] (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 w33DfTwQ032495 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Apr 2018 06:41:30 -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.77]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Geoff Huston <gih902@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Date: Tue, 03 Apr 2018 06:42:05 -0700
X-Mailer: MailMate (1.11r5462)
Message-ID: <6D617FAC-D981-4AE1-8943-4F0D12C46397@vpnc.org>
In-Reply-To: <2F103A8E-72F6-4159-900D-B7006D0AC647@gmail.com>
References: <039408B0-89EE-4038-B9C9-CBCC35EC24EC@isc.org> <64816369-700A-4413-B1F0-160FB145EE6C@gmail.com> <BF3E4F4D-027C-4A2B-8026-14AF3FBA4603@isc.org> <2F103A8E-72F6-4159-900D-B7006D0AC647@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/89c-BZ84HjQqaVXNdmWTN_3HRbs>
Subject: Re: [DNSOP] draft-ietf-dnsop-kskroll-sentinel-10 and AD
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: Tue, 03 Apr 2018 13:42:11 -0000

On 3 Apr 2018, at 1:34, Geoff Huston wrote:

> I’ll remove the condition then.

Will you re-instate what Petr asked for, namely some wording that 
indicates that the resolver has to do DNSSEC validation on what it gets 
back from the authoritative server *regardless* of whether the 
originating client requests it? Without that, it is unclear what a 
resolver should do.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email