IETF Logo Mail Archive

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

TGLASSEY <tglassey@earthlink.net> Tue, 14 January 2014 06:31 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 230B01ADF0E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 13 Jan 2014 22:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level:
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538] 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 8AaKcvOiIdU1 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 13 Jan 2014 22:31:13 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 236AA1AD672 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 13 Jan 2014 22:31:13 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 2EBE286D77E for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Jan 2014 06:31:02 +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 5FB4186D422 for <ntpwg@lists.ntp.org>; Tue, 14 Jan 2014 06:30:53 +0000 (UTC)
Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <tglassey@earthlink.net>) id 1W2xWV-000FB5-1q for ntpwg@lists.ntp.org; Tue, 14 Jan 2014 06:30:53 +0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=S78UBiLBpcHeObyU60MXqcwp6Ou3TO3s60JkUEZOKQWcvrjtU5O5289VD5M1BTQV; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.134.155] (helo=[192.168.0.4]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1W2xWO-0003xr-Ea for ntpwg@lists.ntp.org; Tue, 14 Jan 2014 01:30:44 -0500
Message-ID: <52D4D9A5.60506@earthlink.net>
Date: Mon, 13 Jan 2014 22:31:01 -0800
From: TGLASSEY <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ntpwg@lists.ntp.org
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
In-Reply-To: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79d6626f808e9dfa9c941186d1955dd8b3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.134.155
X-SA-Exim-Connect-IP: 209.86.89.65
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: tglassey@earthlink.net
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
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 12/1/2013 8:47 PM, Hal Murray wrote:
> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just
> a generic didn't-work?
It will depend on the implementation.
>
> How close does the time have to be for DNSSEC to work?

Again it will depend on the implementation. Kerberos tickets for cross 
mounting a microsoft file system can be made to expire in a short enough 
time frame that this could cause issues.
>
> Could this problem be solved by setting up a bank of NTP servers at well
> known IP Addresses?  Say, one next to each root DNS server.
This is why a NTP proxy would be a good tool.
> If you tried to
> do that, I'd expect a serious problem would be overload because idiots would
> try to use them for normal NTP use rather than just getting off the ground.
You guys host one right? So you know... We see insane levels of use. 
Most all of us in the ITS program do.
> It might be possible to discourage that by making them return crappy time.
No - that's not really an acceptable trust thing.
>
>
> ted.lemon@nominum.com said:
>> As for the home router use model, it may be that what you really want is for
>> the home router to query for an FQDN-only DHCP option from the ISP DHCP
>> server, and then resolve that FQDN and respond to DHCP clients on the
>> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
>> address is (one hopes) resolved either at query time or when its TTL
>> expires, this ought to prevent a repeat of the firmware burn-in incident.
> Most ISPs already provide DNS servers for their customers.  How do their IP
> address get setup in home routers?

DHCP in most instances.
>   Could NTP servers piggyback on that
> mechanism if ISPs also provided NTP servers?
>
Sure and from the perspective of the Cable or provider who does control 
the last mile they just run their own perimeter or edge based services 
and configure them in with DHCP. Again the client never sees it.
>
>
>

-- 
-------------

Personal Email - Disclaimers Apply

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

v2.23.0 | Report a Bug | By Email