IETF Logo Mail Archive

Re: [DNSOP] Simplified Updates of DNS Security Trust Anchors, for rolling the root key

Paul Wouters <paul@nohats.ca> Wed, 01 July 2015 22:36 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB35A1B2AF6 for <dnsop@ietfa.amsl.com>; Wed, 1 Jul 2015 15:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qY-Riwws6PQk for <dnsop@ietfa.amsl.com>; Wed, 1 Jul 2015 15:36:46 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AE391B2AE9 for <dnsop@ietf.org>; Wed, 1 Jul 2015 15:36:46 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3mMHV46lRPzCmS; Thu, 2 Jul 2015 00:36:44 +0200 (CEST)
Authentication-Results: mx.nohats.ca; dkim=pass (1024-bit key) header.d=nohats.ca header.i=@nohats.ca header.b=Hu4HSmxz
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id VtyMQ3ULxXxr; Thu, 2 Jul 2015 00:36:42 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 2 Jul 2015 00:36:42 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 597D580058; Wed, 1 Jul 2015 18:36:41 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1435790201; bh=im0oO+vB8pmuqd5wXpVGh8D2NlRWd7c6DejWbR4SyNs=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Hu4HSmxz9qTwh3JkUVS14js1n3pME+Tu5BB2whx0LA2SshQ+WAp+fpjB+IlaY8vR6 +b7wJvmtTNGO7fFEe5lllwuBGn4R2hcGRcnNlRQsKTM+WoDDiSL9TJg7tD1QrN37p8 IBAtkHizanbyQCNaQ2V7WR7MXc0y1Na5UcSyNTkA=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.15.1/8.15.1/Submit) with ESMTP id t61Maeuc009003; Wed, 1 Jul 2015 18:36:40 -0400
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Wed, 01 Jul 2015 18:36:40 -0400
From: Paul Wouters <paul@nohats.ca>
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAHw9_i+BRPXCdNLE4UCHDMzx0zcDfm8SbjLF1BGanGGL9VSCoA@mail.gmail.com>
Message-ID: <alpine.LFD.2.11.1507011833370.8321@bofh.nohats.ca>
References: <CAHw9_iKmhA+f8QyuLkWeXQDfwprydVaGkR+LVJACGtsTB0+Pfw@mail.gmail.com> <55929AE2.50105@sinodun.com> <CAHw9_i+BRPXCdNLE4UCHDMzx0zcDfm8SbjLF1BGanGGL9VSCoA@mail.gmail.com>
User-Agent: Alpine 2.11 (LFD 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/EGeQ13J_uhQECd2Ucu9EdtMTW-o>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Simplified Updates of DNS Security Trust Anchors, for rolling the root key
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 01 Jul 2015 22:36:47 -0000

On Tue, 30 Jun 2015, Warren Kumari wrote:

>> I have been planning to write a draft to address 1 by having validators send
>> the DS of known TA's in an edns0 option code. This info, could then be
>> logged by the authoritative nameservers.
>
> Inserting it in edns0 implies (I think) that all of the queries will
> contain this, which seems like a fairly big query size / efficiency
> hit. I guess you could just do it every N queries, or M time, or
> something. Very similar idea though...

Why? You would only add it to the question for DNSKEY of the root.
Maybe only after you determined a validation failure, so you clearly
have the wrong trust anchor.

It seems in general, having some special record signed by only the
new key seems a nicer solution, as it allows for large network
monitors (eg atlas) to use unmodified dns servers. But it will require
some kind of legal/contractual change :(

Paul

v2.23.0 | Report a Bug | By Email