IETF Logo Mail Archive

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

"TS Glassey" <tglassey@earthlink.net> Mon, 26 November 2007 00:49 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 1IwSAK-0003Th-Ii; Sun, 25 Nov 2007 19:49:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwSAI-0003Sl-QG for dhcwg@ietf.org; Sun, 25 Nov 2007 19:49:34 -0500
Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwSAE-0004Pv-EQ for dhcwg@ietf.org; Sun, 25 Nov 2007 19:49:34 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=HqyViIhdE8wj5XD2Bg0kl82TqwWqIJGun2rcn+EYqJ5j1mCp1oveErXm45JvgUeR; 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-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IwSAC-0006T4-3l; Sun, 25 Nov 2007 19:49:28 -0500
Message-ID: <014701c82fc6$32c17b30$6401a8c0@tsg1>
From: TS Glassey <tglassey@earthlink.net>
To: Ted Lemon <mellon@fugue.com>
References: <20071121052610.DD3EF39E3F@mail1.ntp.org> <4748DAB1.2030506@ntp.org> <6EDC6595-CD66-490F-90FD-A730E4BF3360@fugue.com> <4748F4C4.1090407@ntp.org> <47496F73.8040206@sun.com> <000701c82f6e$03795350$6401a8c0@tsg1> <4749D28D.8090505@sun.com> <00af01c82fa5$8a9acfd0$6401a8c0@tsg1> <4749E7F6.8010709@sun.com> <00f101c82fb9$beaad0e0$6401a8c0@tsg1> <93DCBBAA-5FB3-4187-B8A3-67DDC0AF3519@fugue.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Optionsfor DHCPv6
Date: Sun, 25 Nov 2007 16:48:03 -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: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79ebf4c825155ed1a11519a0363fa21942350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: ntpwg@lists.ntp.org, dhcwg@ietf.org, Brian Utterback <Brian.Utterback@Sun.COM>, "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

----- Original Message ----- 
From: "Ted Lemon" <mellon@fugue.com>
To: "TS Glassey" <tglassey@earthlink.net>
Cc: "Brian Utterback" <Brian.Utterback@Sun.COM>; <ntpwg@lists.ntp.org>; 
"Richard Gayraud (rgayraud)" <rgayraud@cisco.com>; <dhcwg@ietf.org>
Sent: Sunday, November 25, 2007 4:16 PM
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Optionsfor 
DHCPv6


> On Nov 25, 2007, at 5:20 PM, TS Glassey wrote:
>> You mean the DHCP lease? True unless the connection is forced to be 
>> renewed.
>> Otherwise, as long as the connection is in place one would think its 
>> proper
>> to have the service address remain the same.
>
> This is a very frustrating discussion.   Do you guys ever actually use 
> DHCP in operation?

Yes all the time.

>  Connections aren't "forced to be renewed."   DHCP  clients renew their 
> leases periodically.

Sorry Ted... they most assuredly do expire and if the user wants to continue 
to use those services the transport MUST renew its lease to have an IP 
address. That's what 'forces' the lease renegotiation

> It's possible to set up a  DHCP server to give out a lease that doesn't 
> need to be renewed, but  nobody ever does that.

Uh yes they do and its one of the problems with this type of system too.

> Even if some random person at one site  somewhere does it, they're not 
> going to have enough clients to cause  you trouble - it's only a large 
> site that will cause you trouble, and  trust me, they can't operate their 
> network without regular lease  renewals.

Ted, here again this is a policy issue.

>
> So in practice, for any significant source of NTP traffic, you are  going 
> to have DHCP lease renewals.   There aren't going to be any  exceptions to 
> this.
>
> Furthermore, for clients that only do the lightweight DHCP protocol, 
> there is a required refresh interval.   So again, this simply isn't a 
> problem.

Ted - this is about auditing and what's needed for digital evidence.  So we 
disagree here. NTP will not be run on platforms constrained by those issues 
if we are not careful and properly setup NTP so that the trust factor's it 
operates off of are secured as well.

Todd

> 


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

v2.23.0 | Report a Bug | By Email