IETF Logo Mail Archive

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

"Benoit Lourdelet (blourdel)" <blourdel@cisco.com> Mon, 19 November 2007 16:42 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 1Iu9hZ-0003gm-HO; Mon, 19 Nov 2007 11:42:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu9hX-0003ge-Vi for dhcwg@ietf.org; Mon, 19 Nov 2007 11:42:23 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iu9hU-0007nf-Iy for dhcwg@ietf.org; Mon, 19 Nov 2007 11:42:23 -0500
X-IronPort-AV: E=Sophos;i="4.21,437,1188770400"; d="scan'208";a="158164569"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 19 Nov 2007 17:42:20 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lAJGgJ8p004718; Mon, 19 Nov 2007 17:42:19 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAJGg6Um023019; Mon, 19 Nov 2007 16:42:11 GMT
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Nov 2007 17:42:06 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Optionsfor DHCPv6
Date: Mon, 19 Nov 2007 17:43:17 +0100
Message-ID: <A05118C6DF9320488C77F3D5459B17B706443BB8@xmb-ams-333.emea.cisco.com>
In-Reply-To: <1195484306.9159.13.camel@uma>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Optionsfor DHCPv6
Thread-Index: AcgqvKhi+fNjIHtPQSikkuqS+aEQ3QADk33Q
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <4733482A.7020302@sun.com> <A05118C6DF9320488C77F3D5459B17B70634E4E5@xmb-ams-333.emea.cisco.com> <473D0C34.4030507@ntp.org> <1195185173.26090.4.camel@uma> <474114E3.9040309@ntp.org> <474198BA.3000109@sun.com> <1195484306.9159.13.camel@uma>
From: "Benoit Lourdelet (blourdel)" <blourdel@cisco.com>
To: Ted Lemon <mellon@fugue.com>, Brian Utterback <brian.utterback@sun.com>
X-OriginalArrivalTime: 19 Nov 2007 16:42:06.0295 (UTC) FILETIME=[1EC40670:01C82ACB]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15554.001
X-TM-AS-Result: No--16.596200-8.000000-2
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1566; t=1195490539; x=1196354539; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=blourdel@cisco.com; z=From:=20=22Benoit=20Lourdelet=20(blourdel)=22=20<blourdel@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Re=3A=20[ntpwg]=20Network=20Time=20Protocol =20(NTP)=20Optionsfor=09DHCPv6 |Sender:=20; bh=YkdvBSPWBSk891w/XoD6fZQp++xOys2I/WOtNlRMCyk=; b=KRnbf4CtOzrDWiZQbfk+Dl+YHmTY1I2gSfWZ6MhBEjyV64hQcb8ia3SoxhgqL7apA7QaTlZd PhCh3Y41vlyDLwRGnU1Zjk+O68XvYckhv6dLfxxRVJE19gAbCw8wc33U;
Authentication-Results: ams-dkim-1; header.From=blourdel@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ntpwg@lists.ntp.org, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>, dhcwg@ietf.org
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

The beauty of offering IP address instead of FQDN is that you totally
control your client.
You don't let any room for interpretation of the result of the
subsequent DNS query in the DHCP Client.

Benoit 

> -----Original Message-----
> From: Ted Lemon [mailto:mellon@fugue.com] 
> Sent: Monday, November 19, 2007 3:58 PM
> To: Brian Utterback
> Cc: Danny Mayer; Benoit Lourdelet (blourdel); 
> ntpwg@lists.ntp.org; dhcwg@ietf.org; Richard Gayraud (rgayraud)
> Subject: Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) 
> Optionsfor DHCPv6
> 
> On Mon, 2007-11-19 at 09:07 -0500, Brian Utterback wrote:
> > That having been said, I would like to see a way to pass a 
> FQDN as an 
> > option, perhaps passing both. Then you could have logic 
> like "Here's 
> > both, use the name if you can, and use the address if you must."
> 
> An option in a protocol that produces no different behavior 
> is just an opportunity for interoperability problems.
> 
> This is actually an old discussion.   Danny's position isn't 
> unheard of,
> but the fact is that there's really no way in which this 
> option is different from the other fifty options that tell 
> DHCP clients how to contact servers.
> 
> There's no reason why this option should use FQDNs while the 
> other fifty use IP addresses, and there are a number of good 
> reasons not to send FQDNs, the first and most obvious of 
> which is that they take up more space in the packet, and 
> space in the packet is very limited.
> 

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

v2.23.0 | Report a Bug | By Email