To:
"David Meyer" <dmm@1-4-5.net>, "Rob Austein" <sra+dnsop@hactrn.net>
Cc:
"Brad Knowles" <brad.knowles@skynet.be>, "Pekka Savola" <pekkas@netcore.fi>, "Doug Barton" <DougB@DougBarton.net>, "Bob Hinden" <hinden@iprg.nokia.com>, "John Schnizlein" <jschnizl@cisco.com>, "Soohong Daniel Park" <soohong.park@samsung.com>, <dnsop@cafax.se>
From:
"BELOEIL Luc FTRD/DMI/CAE" <luc.beloeil@francetelecom.com>
Date:
Mon, 6 Oct 2003 16:32:39 +0200
content-class:
urn:content-classes:message
Sender:
owner-dnsop@cafax.se
Thread-Index:
AcOIyJqN7Xb3vRM5Q/mbtSo0Ds+jrgDR/WaQ
Thread-Topic:
How IPv6 host gets DNS address
Subject:
RE: How IPv6 host gets DNS address
As far as I understand different opinions, some do think that DNS autoconfiguration is not enough and other information are also in concern (NTP, SMTP server addresses, search path list, ...). There I admit that we need a mechanism that can at least integrate DNS discovery needs but also evolute to support other "information" discovery. There I don't think that is a work for dnsop. Some do think DNS resolver address is enough. I agree with that, when one trust its local network and/or when one just need simple Ip connectivity (see Pekka Savola example), DNS resolver addresses is the only "information" to add to stateless address autoconfiguration. There I have the feeling that DHCP-lite is still to complicated, and that well-known addresses are perhaps not appropriate cause it may involve routing policies not in the scope of local network policies. my 0.02 % Luc > -----Message d'origine----- > De : Brad Knowles [mailto:brad.knowles@skynet.be] > Envoye : jeudi 2 octobre 2003 11:03 > A : Pekka Savola > Cc : Doug Barton; Bob Hinden; John Schnizlein; Soohong Daniel Park; > dnsop@cafax.se > Objet : Re: How IPv6 host gets DNS address > > > At 8:03 AM +0300 2003/10/02, Pekka Savola wrote: > > > Why do you need a search list? I certainly don't. > > Maybe you don't, but I submit that you're not the > target typical consumer. > > > Just remember which scenarios we'd be targeting the > solution. The target > > audience would _very probably_ *not* be the enterprise network. > > One target audience would be the enterprise network. Another > would be the home user. I can see where search lists would be > important to both. > > > The one example I personally have used a couple of times > is my laptop at > > the IETF or in some other network I plug it to. I don't > care less about > > DHCP, NTP (the clock is good enough already), Windows > environments, search > > paths, etc. -- I just want the DNS and be done with it..! > > Again, I don't think you're the target typical consumer. > > -- > Brad Knowles, <brad.knowles@skynet.be> > > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > -Benjamin Franklin, Historical Review of Pennsylvania. > > GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ > !E-(---) W+++(--) N+ > !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) > X++(+++) R+(+++) > tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- > r---(+++)* z(+++) > #------------------------------------------------------------- > --------- > # To unsubscribe, send a message to <dnsop-request@cafax.se>. > #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.