> I don't like taking into account money in technical matters. > Welcome to the eral world, not the lab or academic world. > > BTW: let me note that I know of a certain hospital with a /16 IPv4 > and all their heartmonitoring and other surveilance apparatus > are using IP's out of that /16. With one big, good configured, > firewall at the gate and ofcourse nice VLAN's which don't even > allow packets from those VLAN's to come even close to the internet. > Now I quickly hear a "why do they have a public /16", because it's > globally unique and they can easily merge with another hospital > or organization and don't have to 'fear/uncertainty/doubt' that > their address spaces will ever collide. Oh and for the question > of how much v6 they would need: a single /48 would suffice as > it would allow 65535 networks or quite possibly VLAN's. And yes > they could receive that from their current upstream which also > delivers the /16 to their doorstep. > Your explination seems to take into account the pre IPv6 autoconfigure options which are supposed to make this merger or provider change eaiser to handle. They used the IPv4 space as they did because there was nothing better, but what we are supposed to be doing is providing this bigger better plan.
-------------------------------------------------------------------- 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] --------------------------------------------------------------------
