IETF Logo Mail Archive

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

Hal Murray <hmurray@megapathdsl.net> Mon, 02 December 2013 18:57 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 6BCE91AD687 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 2 Dec 2013 10:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 oKjtxEbaeOx0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 2 Dec 2013 10:57:08 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 46CBC1ACCDF for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 2 Dec 2013 10:57:08 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 420E086D60E for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 2 Dec 2013 18:57:06 +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 DA6EB86D422 for <ntpwg@lists.ntp.org>; Mon, 2 Dec 2013 18:56:57 +0000 (UTC)
Received: from mail223c25.carrierzone.com ([64.29.147.237]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <hmurray@megapathdsl.net>) id 1VnYfs-000Ex5-Th for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 18:56:57 +0000
X-POP-User: hmurray@megapathdsl.net
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by mail223c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id rB2IunTi027496 for <ntpwg@lists.ntp.org>; Mon, 2 Dec 2013 18:56:50 +0000
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 91031406060; Mon, 2 Dec 2013 10:56:48 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Ted Lemon <ted.lemon@nominum.com>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Ted Lemon <ted.lemon@nominum.com> of "Mon, 02 Dec 2013 00:13:17 EST." <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
Mime-Version: 1.0
Date: Mon, 02 Dec 2013 10:56:48 -0800
Message-Id: <20131202185648.91031406060@ip-64-139-1-69.sjc.megapath.net>
X-CSC: 0
X-CHA: v=2.1 cv=aKDJ99Nm c=1 sm=1 tr=0 a=OWgXOY7Tc8w5m7k7nGX6Zw==:117 a=OWgXOY7Tc8w5m7k7nGX6Zw==:17 a=Y6MaXbqoAAAA:8 a=g0qM3YM6AAAA:8 a=i5csljzfOyQA:10 a=sMgVN826qSoA:10 a=RocdOpmNmpoA:10 a=kj9zAlcOel0A:10 a=txtmwFjVAAAA:8 a=eTNsCY_WGJ8A:10 a=DGbFYnXxAAAA:8 a=KJE_JL5bt8-WbQPDp2wA:9 a=h-Le4KOJTSLWos5y:21 a=QawYSIss2mX5EQef:21 a=CjuIK1q_8ugA:10 a=bSyc6FVMW0oA:10
X-CTCH-RefID: str=0001.0A020203.529CD7F2.01C4, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules:
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-SA-Exim-Connect-IP: 64.29.147.237
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: hmurray@megapathdsl.net
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>, hmurray@megapathdsl.net, Bernie 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

ted.lemon@nominum.com said:
[Context is NTP servers next to root DNS servers.]
> History suggests otherwise.   If an IP address is hardcoded, it will get
> pummeled by devices that are too dumb to give up. 

That's why I was suggesting a crappy clock.  Can we get something that is 
crappy enough that nobody would use it for anything other than getting off 
the ground yet still good enough for DNSSEC to work?


>> Most ISPs already provide DNS servers for their customers.  How do their 
IP
>> address get setup in home routers?  Could NTP servers piggyback on that 
>> mechanism if ISPs also provided NTP servers?
> You mean DHCP?   Yes, that's what we're talking about. 

Are there two layers of DHCP?  ISP to home router and home router to PC.

If ISPs ran NTP servers, say next to their DNS servers, could DHCP provide IP 
Addresses for both DNS and NTP servers over both hops?

Is it reasonable to trust an ISP's NTP servers?


-- 
These are my opinions.  I hate spam.



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

v2.23.0 | Report a Bug | By Email