Re: [DNSOP] I-D Action: draft-ietf-dnsop-extended-error-04.txt

Wes Hardaker <wjhns1@hardakers.net> Mon, 11 March 2019 22:15 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 91DA31279B1 for <dnsop@ietfa.amsl.com>; Mon, 11 Mar 2019 15:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 Ofd7fQD58O0V for <dnsop@ietfa.amsl.com>; Mon, 11 Mar 2019 15:15:44 -0700 (PDT)
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 6AC19128664 for <dnsop@ietf.org>; Mon, 11 Mar 2019 15:15:44 -0700 (PDT)
Received: from localhost (pc5.it-anacpk1-unet.ocn.ne.jp [153.150.27.29]) by mail.hardakers.net (Postfix) with ESMTPA id 3756E23FDC; Mon, 11 Mar 2019 15:15:32 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "Michael J. Sheldon" <msheldon@godaddy.com>, Brian Dickson <brian.peter.dickson@gmail.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "dnsop\@ietf.org" <dnsop@ietf.org>
References: <154689301066.32204.17312124670782800354@ietfa.amsl.com> <20190214195125.nwbazwpk3rgrgxkf@sources.org> <3f0fde90-5a64-6bda-7800-a63311557e2a@godaddy.com>
Date: Mon, 11 Mar 2019 15:15:31 -0700
In-Reply-To: <3f0fde90-5a64-6bda-7800-a63311557e2a@godaddy.com> (Michael J. Sheldon's message of "Thu, 14 Feb 2019 20:12:15 +0000")
Message-ID: <yblftrt6osc.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/NmjFmtUZ4II3UJz1XQSKnRp9_uw>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-extended-error-04.txt
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: Mon, 11 Mar 2019 22:15:45 -0000

"Michael J. Sheldon" <msheldon@godaddy.com> writes:

Brian and Michael both,

> > Rationale : the current text seems to imply this code is only when
> > there is no DNSKEY at all.

>  I disagree. There are going to be cases where DS and DNSKEY are not
> fully in sync due to key rollovers, prestaging, etc. This is not a fatal
> error.

[and Brian agreed elsewhere]

Thanks for your comments on the draft and this discussion.  You can read
the results of this particular point in my response to Petr under bullet
6.4 in that message.
-- 
Wes Hardaker
USC/ISI