IETF Logo Mail Archive

Re: Practical issues deploying DNSSEC into the home.

SM <sm@resistor.net> Tue, 10 September 2013 16:45 UTC

Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 023DA21E815E for <ietf@ietfa.amsl.com>; Tue, 10 Sep 2013 09:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TvL7iDII8JN for <ietf@ietfa.amsl.com>; Tue, 10 Sep 2013 09:45:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A770821E8172 for <ietf@ietf.org>; Tue, 10 Sep 2013 09:45:04 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r8AGivSl023682; Tue, 10 Sep 2013 09:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1378831503; bh=HMUe1NqQMA1WiBW8SCywtcFqcKxZlIvqYZUXczeg+Vw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Dqpm1HGG85QBrxqzHVVxU+MaeaEYtRwXugNX0c6sYPeKs4lw4B5jf8dHK0AUJ4MWU O3WlrWtn4EJTNcmRNK72THYWTuvIzULlN383VXV48HBeuaoYYwo2kJDaOsGO1cKZlj lq2qy4xkKkXH/NsQUBeAzqCNk+3e8x9ZRDo6dlKI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1378831503; i=@resistor.net; bh=HMUe1NqQMA1WiBW8SCywtcFqcKxZlIvqYZUXczeg+Vw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4u71gWnpaSnW0Sbhh/k7wS0NdHJdOSAmN+KnBZb/w4XUvMZisVuJk27gRxHcL7s5T bqUbDRNwmjVucNyRnn1wUVAF+sur4HvUe0zpdNP4M02Ed9wKgAAfnCi8tvbtPnuWzH 0ZBt3PKc0cCQmMzes3mssXB7d0fZ3MMhyCRO1faM=
Message-Id: <6.2.5.6.2.20130910090500.0c3b29a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 10 Sep 2013 09:44:05 -0700
To: Jim Gettys <jg@freedesktop.org>
From: SM <sm@resistor.net>
Subject: Re: Practical issues deploying DNSSEC into the home.
In-Reply-To: <CAGhGL2APj-XfuMUHgLsELnZRbRNCLrjMBxFBtcg4zx+5SG7Bag@mail.g mail.com>
References: <CAGhGL2APj-XfuMUHgLsELnZRbRNCLrjMBxFBtcg4zx+5SG7Bag@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ietf@ietf.org, dns-security@lists.tislabs.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 16:45:08 -0000

Hi Jim,
At 08:55 10-09-2013, Jim Gettys wrote:
>We uncovered two practical problems, both of which need to be solved 
>to enable full DNSSEC deployment into the home:
>
>1) DNSSEC needs to have the time within one hour.  But these devices 
>do not have TOY clocks (and arguably, never will, nor even probably 
>should ever have them).
>
>So how do you get the time after you power on the device?  The usual 
>answer is "use ntp".  Except you can't do a DNS resolve when your 
>time is incorrect.  You have a chicken and egg problem to 
>resolve/hack around :-(.

That problem has been bothering me for a while.  There can be a leap 
of faith at startup to get the correct time.  DNSSEC can be done after that.

Regards,
-sm

v2.23.0 | Report a Bug | By Email