EricLKlein wrote:
> > >> IP's should be globably unique. Which will overcome many problems
> > >> like network mergers ('oh we need to NAT now'), e2e problems etc.
> > > The new address features of IPv6 should resolve this as easily as
> > > changing
> > > providers.
> >
> > What features are those?
>
> Autoconfiguration - IPV6 allows autoconfiguration of the
> devices by either the router, DHCP server or both.
>
> This should resolve most of the problems when merging
> networks, just change the part atthe front of the /64 (or /48)
> address and leave the hosts the same.
Make that /48 as that's what every endsite should be getting at
a minimum. That's where the RFC is for.
> SHould work the same as changing the ISP.
That's what I thought too and is quite correct for a small network.
But if one is going into a larger net (>50k hosts) you will also have
the following administrativia to handle:
- dns (forward AND reverse)
- firewall configs
- router configs (though one could propagate, but how secure is that)
And then we are not even talking about telling the rest of the world
that you are changing prefixes. Eg clueing in Verisign and others
that your DNS servers changed. Seeing the fact that one can't even
clue them in to make a AAAA glue in the gtld... no comment ;)
Greets,
Jeroen
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
