IETF Logo Mail Archive

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

Ralph Droms <rdroms@cisco.com> Mon, 19 November 2007 23:41 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 1IuGFV-0008Os-RA; Mon, 19 Nov 2007 18:41:53 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuGFV-0008On-4G for dhcwg@ietf.org; Mon, 19 Nov 2007 18:41:53 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuGFU-0007PY-Pd for dhcwg@ietf.org; Mon, 19 Nov 2007 18:41:53 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Nov 2007 18:41:52 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lAJNfqt6007836; Mon, 19 Nov 2007 18:41:52 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAJNflwr026621; Mon, 19 Nov 2007 23:41:48 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Nov 2007 18:41:05 -0500
Received: from [192.168.1.102] ([10.86.240.146]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Nov 2007 18:41:05 -0500
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <20071119225643.GI14750@isc.org>
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> <20071119225643.GI14750@isc.org>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <6DD46BAB-2F5F-4DFB-A4CC-BCA325DDFDA8@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Options for DHCPv6
Date: Mon, 19 Nov 2007 18:41:18 -0500
To: DHC WG <dhcwg@ietf.org>, ntpwg@lists.ntp.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 19 Nov 2007 23:41:05.0526 (UTC) FILETIME=[A6EA4160:01C82B05]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15554.002
X-TM-AS-Result: No--18.416600-8.000000-31
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=1233; t=1195515712; x=1196379712; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Re=3A=20[ntpwg]=20Network=20Time=20Protocol =20(NTP)=20Options=20for=09DHCPv6 |Sender:=20 |To:=20DHC=20WG=20<dhcwg@ietf.org>,=20ntpwg@lists.ntp.org; bh=rzWFrobBo/AFISrcr/eEXgigCgkUD8uRLh2ipiZEPsw=; b=bZZVxtr/aTMvJe3fsp9iDl/qEIgvee8x1/B1z4sZSMk+olIdAH3KKEdc2a4LIObLeoRNLqmc DwSJTt8+D3gqApahClvkjMP3cnGdL3pe2397k1DTWnFNGSq1qNM0PJoQ;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc:
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

draft-droms-dhc-container-opt-01.txt defines container options for  
both DHCPv4 and DHCPv6.

- Ralph

On Nov 19, 2007, at Nov 19, 2007,5:56 PM, David W. Hankins wrote:
> [...]
> I would also like to suggest that some of these concerns may be
> mitigated by tracking Ralph Drom's recent 'container option' draft,
> wherein a SOHO router may dynamically receive from an 'upstream'
> DHCPv6 server the configuration values it should give 'downstream'
> DHCPv6 clients.
>
> I'm not aware of an equivalent for DHCPv4 however.
>
>
> So cautioned, I personally leave it up to the NTP community to
> prove to us exactly to what extent it is genuinely useful to have
> such intermediaries as DNS (or even DHCP, even if I consider that
> a given) involved.
>
> -- 
> Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
> Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
> -- 
> David W. Hankins	"If you don't do it right the first time,
> Software Engineer		     you'll just have to do it again."
> Internet Systems Consortium, Inc.		-- Jack T. Hankins
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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

v2.23.0 | Report a Bug | By Email