IETF Logo Mail Archive

Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6

"TS Glassey" <tglassey@earthlink.net> Mon, 26 November 2007 02:54 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwU72-00019f-Az; Sun, 25 Nov 2007 21:54:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwU70-00019L-V7 for dhcwg@ietf.org; Sun, 25 Nov 2007 21:54:18 -0500
Received: from elasmtp-banded.atl.sa.earthlink.net ([209.86.89.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwU6x-0007YL-0t for dhcwg@ietf.org; Sun, 25 Nov 2007 21:54:18 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=tF5mS6VXCH9TDW8wmpHNU/Q5bgBA5DtIEMJ+wtM4db7vHX8LZhwfUwnPTgGhbQYZ; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [24.23.176.93] (helo=tsg1) by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IwU6u-0007lp-OE; Sun, 25 Nov 2007 21:54:12 -0500
Message-ID: <018501c82fd7$9ff707e0$6401a8c0@tsg1>
From: TS Glassey <tglassey@earthlink.net>
To: Ted Lemon <mellon@fugue.com>
References: <200711260009.lAQ092va059077@drugs.dv.isc.org> <EF06E977-C3D9-4EDF-A126-6CD888BA8F36@fugue.com> <014d01c82fc6$6b1ecd70$6401a8c0@tsg1> <5C093633-A256-4059-AA10-1800F62F522A@fugue.com> <017901c82fd4$9cad3b70$6401a8c0@tsg1> <E0F01D6C-3FB6-4150-9722-32CFF3079327@fugue.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Date: Sun, 25 Nov 2007 18:54:08 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec799f52d4d967dc6d0c206ceb10b18cadc2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ntpwg@lists.ntp.org, dhcwg@ietf.org, Mark Andrews <Mark_Andrews@isc.org>, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ted :-)

----- Original Message ----- 
From: "Ted Lemon" <mellon@fugue.com>
To: "TS Glassey" <tglassey@earthlink.net>
Cc: <ntpwg@lists.ntp.org>; <dhcwg@ietf.org>; "Mark Andrews" 
<Mark_Andrews@isc.org>; "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>
Sent: Sunday, November 25, 2007 6:43 PM
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) 
OptionsforDHCPv6


> On Nov 25, 2007, at 8:32 PM, TS Glassey wrote:
>> Which makes the Network Administrator liable for screw-up's and the 
>> damages
>> therein... Sorry this one is a no-sale IMHO.
>
> Why?   Network administrators are already responsible for all the  other 
> fields in the DHCP server - why is the NTP server address special?
>

Ted there are issues with the Old-School methods and if you believe that 
they are the right way to operate your network nothing I can say from either 
someone who has written subpicosecond event capture code as well as auditing 
profiles for securing and making the evidence believable.

So lets just agree to disagree about this. The addition of NTP servers in 
this instance opens more liabilities than it solves problems for whether 
anyone likes that or not. Sorry, but your neat fix here opens new security 
issues and allows NTP servers to become also impacted by DHCP security 
issues.

Sorry but reality is what it is, and adding this support to DHCP opens more 
problems than it solves.

Todd 


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email