(We should probably change the subject...)
>>>>> On Thu, 07 Mar 2002 14:28:40 -0500,
>>>>> Rob Austein <[EMAIL PROTECTED]> said:
> 2) While I applaud the ingenuity and enthusiasm of all the people who
> have come up with interesting ways to configure things in the IPv6
> universe without using DHCP, I have yet to see any proposals as
> simple as just using boring old DHCP for most of this stuff. We
> have a pretty good understanding of how DHCP works and what's
> required to support it (for some definition of "we" that may or may
> not include the members of this WG, a subject on which I decline to
> have a public opinion). Some of the proposals to replace DHCP, on
> the other hand, are pretty far out on either the research or kludge
> axes. While I am not in principle opposed to cool new stuff, I
> don't think it's sound engineering to do new stuff just for the
> sake of being different.
Could you be more specific about the "new stuff", please? I agree
that the "level 2 compliance" described in
draft-ietf-ipv6-dns-discovery-04 can be called a "new stuff", but the
level 1 compliance, which is now the only main part of the draft,
needs almost nothing new. In particular, if we use unicast well-known
addresses with the level 1 compliance (this will work in a small
network such as a home network or a SO-HO office), we do not need new
implementation. It's just a matter of configuration.
I admit that DHCPv6 only with information resources is also simple.
However, in order to apply DHCPv6 in the real network, we'll need
- a DHCPv6 relay agent (basically) in every subnet, or
- multicast routing when we use a well-known multicast addresses for
DHCP servers
I believe both of two can be a problem to deploy DHCPv6 which is not
easy to deal with. That's one of the key reasons why the design team
preferred the current approach to DHCPv6. (correct me if I'm wrong >
other team members.)
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
