Re: [DNSOP] New draft: Algorithm Negotiation in DNSSEC

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 20 July 2017 07:57 UTC

Return-Path: <bortzmeyer@nic.fr>
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 F235D126557 for <dnsop@ietfa.amsl.com>; Thu, 20 Jul 2017 00:57:24 -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 U-HtN7XwjLOy for <dnsop@ietfa.amsl.com>; Thu, 20 Jul 2017 00:57:24 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (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 8D56E129A96 for <dnsop@ietf.org>; Thu, 20 Jul 2017 00:57:21 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id A3B7C31CE6; Thu, 20 Jul 2017 09:57:18 +0200 (CEST)
Received: by godin (Postfix, from userid 1000) id B0E75EC0B75; Thu, 20 Jul 2017 09:51:45 +0200 (CEST)
Date: Thu, 20 Jul 2017 09:51:45 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Shumon Huque <shuque@gmail.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-ID: <20170720075145.GA970@laperouse.bortzmeyer.org>
References: <CAHPuVdUVQqvFZJFV4D88cg4fGfFqxnzAwj1VRr6oK7Y1n9hDUw@mail.gmail.com> <20170719084942.GA18413@laperouse.bortzmeyer.org> <CAHPuVdUNJ7VeJBAYqEzdt3hBa5screuoJHB7WHMzHPgOgmf-Fg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHPuVdUNJ7VeJBAYqEzdt3hBa5screuoJHB7WHMzHPgOgmf-Fg@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/BRAmjGd5oGZREtHhUemnvOpO2W8>
Subject: Re: [DNSOP] New draft: Algorithm Negotiation in DNSSEC
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: Thu, 20 Jul 2017 07:57:25 -0000

On Wed, Jul 19, 2017 at 02:28:37PM +0200,
 Shumon Huque <shuque@gmail.com> wrote 
 a message of 153 lines which said:

> > Suppose I send the list ECDSA;RSA, and I receive only ECDSA
> > signatures. How the resolver/cache would now if it was a complete
> > list?
> 
> The response contains the EDNS0 option if the responder executed
> this protocol. In which case, the cache would tag this response as a
> subset.

Sorry, I still do not understand. The EDNS0 option does not indicate
if the set is a subset or not. Or do you assume that, if the response
indicates that the responder executes this protocol, an answer is
always a subset (even if it's not)?

> When the resolver queries the DNSKEY RRset for the zone, it knows
> which algorithms are supported for the zone.

You can have keys which are not used for signing (such as in the root
today).