IETF Logo Mail Archive

Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt

Kurt Roeckx <kurt@roeckx.be> Tue, 03 December 2013 12:27 UTC

Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469DA1AE12C for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 3 Dec 2013 04:27:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 PoIHhR2MgspK for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 3 Dec 2013 04:27:54 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0DDAD1AE128 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 3 Dec 2013 04:27:54 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id BED8E86DADD for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 3 Dec 2013 12:27:51 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 124AD86D422 for <ntpwg@lists.ntp.org>; Tue, 3 Dec 2013 12:27:31 +0000 (UTC)
Received: from juliette.telenet-ops.be ([195.130.137.74]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kurt@roeckx.be>) id 1Vnp4b-000Pi5-Iw for ntpwg@lists.ntp.org; Tue, 03 Dec 2013 12:27:31 +0000
Received: from intrepid.roeckx.be ([94.226.199.45]) by juliette.telenet-ops.be with bizsmtp id x0TR1m00R0zFtyu060TRSQ; Tue, 03 Dec 2013 13:27:26 +0100
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id 5B30F1FE0213; Tue, 3 Dec 2013 13:27:25 +0100 (CET)
Date: Tue, 03 Dec 2013 13:27:25 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Danny Mayer <mayer@ntp.org>
Message-ID: <20131203122725.GD2329@roeckx.be>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <529BD4CF.6000408@ntp.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: 195.130.137.74
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: kurt@roeckx.be
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Sun, Dec 01, 2013 at 07:31:11PM -0500, Danny Mayer wrote:
> I think we need to figure out how to get around the Catch-22 situation
> of DNSSEC requiring relatively good time and NTP wanting to be able to
> use DNS to find valid NTP servers.

If the box doesn't have an rtc, and so maybe starts in 1970, and
doesn't have anything it can trust there is no way out of it.  You
first need _something_ you can trust be it time or some
certificate.

I do not trust my ISP, so I don't see how I can get that started
and be sure that both my time are correct and dnssec validates
properly.  The only way I see around this is that someone manually
checks that the time is correct.


Kurt

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

v2.23.0 | Report a Bug | By Email