Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt

Ralph Droms <rdroms@cisco.com> Mon, 24 February 2003 17:42 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20194 for <dhcwg-archive@odin.ietf.org>; Mon, 24 Feb 2003 12:42:33 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OHp9509881 for dhcwg-archive@odin.ietf.org; Mon, 24 Feb 2003 12:51:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OHp9p09878 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 24 Feb 2003 12:51:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20179 for <dhcwg-web-archive@ietf.org>; Mon, 24 Feb 2003 12:42:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OHnWp09796; Mon, 24 Feb 2003 12:49:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OHmPp09755 for <dhcwg@optimus.ietf.org>; Mon, 24 Feb 2003 12:48:25 -0500
Received: from rtp-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20030 for <dhcwg@ietf.org>; Mon, 24 Feb 2003 12:39:17 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h1OHh8Nh024277; Mon, 24 Feb 2003 12:43:09 -0500 (EST)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-251.cisco.com [161.44.149.251]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id MAA23894; Mon, 24 Feb 2003 12:43:08 -0500 (EST)
Message-Id: <4.3.2.7.2.20030224123058.03f484a8@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 24 Feb 2003 12:43:06 -0500
To: dhcwg@ietf.org, ipng@sunroof.eng.sun.com, namedroppers@ops.ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt
In-Reply-To: <1045912992.27180.14.camel@devil>
References: <4.3.2.7.2.20030220135524.03e6d548@funnel.cisco.com> <4.3.2.7.2.20030220135524.03e6d548@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>

Summary of discussion during WG last call on 
draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt

Pekka Savola, Tony Lindstrom, Bernie Volz and Peter Koch all responded with 
editorial suggestions.  These suggestions have been incorporated into the 
draft and will appear in next published rev.

Peter Koch and Rob Austein commented on the "Security Considerations"; 
specifically, whether DNSSEC can prevent problems caused by a search list 
supplied as part of an attack by a DHCP server.  Based on Rob's argument 
(and assuming I understood Rob correctly) that DNSSEC can guarantee that a 
host can trust the replies it receives, but DNSSEC can't guarantee that the 
host has asked the right question based on its search list, I'm inclined to 
leave the text in question unchanged.

Alain Durand raised the issue of supplying both IPv4 and IPv6 addresses for 
DNS resolvers in the DNS server option.  I judged the rough consensus in 
the responses to be that restricting the DNS server option to return only 
IPv6 addresses is acceptable.

- Ralph


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