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

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Mon, 24 February 2003 19:33 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 OAA23818 for <dhcwg-archive@odin.ietf.org>; Mon, 24 Feb 2003 14:33:58 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OJgb418253 for dhcwg-archive@odin.ietf.org; Mon, 24 Feb 2003 14:42:37 -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 h1OJgbp18250 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 24 Feb 2003 14:42:37 -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 OAA23807 for <dhcwg-web-archive@ietf.org>; Mon, 24 Feb 2003 14:33:26 -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 h1OJf2p18143; Mon, 24 Feb 2003 14:41:02 -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 h1OJeTp18108 for <dhcwg@optimus.ietf.org>; Mon, 24 Feb 2003 14:40:29 -0500
Received: from imr1.ericy.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23716 for <dhcwg@ietf.org>; Mon, 24 Feb 2003 14:31:18 -0500 (EST)
Received: from mr5.exu.ericsson.se (mr5u3.ericy.com [208.237.135.124]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id h1OJZ7d15014; Mon, 24 Feb 2003 13:35:08 -0600 (CST)
Received: from eamrcnt761.exu.ericsson.se (eamrcnt761.exu.ericsson.se [138.85.133.39]) by mr5.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id h1OJZ7Z11540; Mon, 24 Feb 2003 13:35:08 -0600 (CST)
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <W7X99WWB>; Mon, 24 Feb 2003 13:35:07 -0600
Message-ID: <A1DDC8E21094D511821C00805F6F706B05552E70@eamrcnt715.exu.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: 'Ralph Droms' <rdroms@cisco.com>, dhcwg@ietf.org, ipng@sunroof.eng.sun.com, namedroppers@ops.ietf.org
Subject: RE: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconf ig-02.txt
Date: Mon, 24 Feb 2003 13:33:27 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2DC3B.9AC3CE60"
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>

Isn't it possible for the DHCPv6 server to return IPv4 addresses as per
RFC 2373, section 2.5.4 (IPv6 Addresses with Embedded IPv4 Addresses),
in particular:

   A second type of IPv6 address which holds an embedded IPv4 address is
   also defined.  This address is used to represent the addresses of
   IPv4-only nodes (those that *do not* support IPv6) as IPv6 addresses.
   This type of address is termed an "IPv4-mapped IPv6 address" and has
   the format:

   |                80 bits               | 16 |      32 bits        |
   +--------------------------------------+--------------------------+
   |0000..............................0000|FFFF|    IPv4 address     |
   +--------------------------------------+----+---------------------+

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Monday, February 24, 2003 12:43 PM
To: dhcwg@ietf.org; ipng@sunroof.eng.sun.com; namedroppers@ops.ietf.org
Subject: Re: [dhcwg] Re: WG last call on
draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt


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