To:
<matthew.ford@bt.com>, <rdroms@cisco.com>, <mohta@necom830.hpcl.titech.ac.jp>
Cc:
<dnsop@cafax.se>
From:
"BELOEIL Luc FTRD/DMI/CAE" <luc.beloeil@francetelecom.com>
Date:
Thu, 6 Nov 2003 13:49:22 +0100
content-class:
urn:content-classes:message
Sender:
owner-dnsop@cafax.se
Thread-Index:
AcOkHDAinvfMaVSARKKRcb8D3/QuYQAIT09gAACt/bAACQvfsA==
Thread-Topic:
How IPv6 host gets DNS address
Subject:
RE: How IPv6 host gets DNS address
ok Matt, thanks for the clarification. > -----Message d'origine----- > De : matthew.ford@bt.com [mailto:matthew.ford@bt.com] > Envoye : jeudi 6 novembre 2003 09:35 > A : BELOEIL Luc FTRD/DMI/CAE; rdroms@cisco.com; > mohta@necom830.hpcl.titech.ac.jp > Cc : dnsop@cafax.se > Objet : RE: How IPv6 host gets DNS address > > > > -----Original Message----- > > From: BELOEIL Luc FTRD/DMI/CAE > [mailto:luc.beloeil@francetelecom.com] > > Sent: 06 November 2003 08:17 > > > I agree with Ralph, in some deployement model, DHCPv6 is the > > right solution to be deployed. But I also believe that some > > other deployment models would prefer other solution like a ND > > model + a simple way to discover DNS resolvers addresses > > (DHCPv6-lite, well-known addresses or RA-based solution). > > Let's not confuse matters. Ralph's statement was referring to > the use of > DHCPv6 for address assignment. The discussion about > appropriate/desirable solutions for recursive name server discovery is > unrelated to that. > > Mat > #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.