Re: [dnsext] DNSSEC, robustness, and several DS records

Francis Dupont <Francis.Dupont@fdupont.fr> Thu, 12 May 2011 22:18 UTC

Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE499E07E9 for <dnsext@ietfa.amsl.com>; Thu, 12 May 2011 15:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tk-Z1QVmAdj4 for <dnsext@ietfa.amsl.com>; Thu, 12 May 2011 15:18:42 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id A7109E075A for <dnsext@ietf.org>; Thu, 12 May 2011 15:18:36 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p4CMIUBq006069; Fri, 13 May 2011 00:18:30 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201105122218.p4CMIUBq006069@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Doug Barton <dougb@dougbarton.us>
In-reply-to: Your message of Wed, 11 May 2011 17:47:59 PDT. <4DCB2E3F.4030701@dougbarton.us>
Date: Fri, 13 May 2011 00:18:30 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: dnsext@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [dnsext] DNSSEC, robustness, and several DS records
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2011 22:18:42 -0000

 In your previous mail you wrote:

   A) Insert obligatory rant about why "should" and "may" should never be 
   used in standards documents.

=> I don't follow your idea...

   B) I don't think it takes even the smallest leap of imagination to say 
   that if the SHA-256 DS is invalid, and the SHA-1 DS is valid, the SHA-1 
   should be used and the SHA-256 should be ignored.
   
=> it is not a problem of imagination: either you implement what the
spec says or you implement something else. And IMHO the first option
is never a "bug".

   I think we could have a fine "angels-on-the-head-of-a-pin" debate about 
   what "present" means in the RFC text

=> present == is an element of the set

   but I have a hard time believing that the intent of the text is
   that if you have something that works it should be ignored in favor
   of something that doesn't.
   
=> but it is the intent: this is why I wrote there is no "valid"
in the spec (where my "valid" means your "works").

So I don't expect to see bind or unbound to change their behavior
unless/until a new rfc is published with another spec.

Regards

Francis.Dupont@fdupont.fr