IPv4 Exhaustion - the Endgame begins

[Fairlight]

Confusious (Jay Ashworth) say:
> IANA -- or what's left of it -- issued it's last 5 reserved /8 IP address
> blocks to the 5 regional Internet Registries; there are no more unassigned
> class A blocks.

Maybe if they revoked Mercedes-Benz's (or was it BMW's?) class A, they'd
have more.  I'm sure there are more out there that ARIN didn't revoke.

> If you maintain any filePro apps which store IP addresses as decimal 
> dotted-quads, remember that you'll shortly need to expand those to 
> accept hex-and-colons IPv6 addresses as well.

I wonder how well fP Sockets deals with IPv6 issues...  Is it going to be
able to handle things properly, or is it going to become outmoded like the
HTML stuff did when the standard evolved?

> If you maintain any filePro apps *accessed* from the Internet, remember
> that IPv4 is about to commence it's long, slow slide into obscurity;
> you'll need to make those apps accessible by IPv6 fairly soon.

What are you on about?  Anything on the IPv4 segment of the net should be
able to reach any other part of the IPv4 segment of the net.  Anything with
an IPv6-enabled stack -should- be transparently able to deal with inbound
IPv6 traffic in terms of gethostbyaddr() calls and the like.

Are you seeing something to change in terms of a current IPv4 web server
application, other than making sure IPv6 is enabled in the TCP/IP stack?

> Comcast is, for example, about to roll out native IPv6 to cablemodem 
> customers.

I was told by a network engineer a week and a half ago that the day to
watch is something like June 18th or 21st...can't remember, somewhere right
around there, all the carriers are supposed to take IPv6 "live".

mark->
-- 
Audio panton, cogito singularis.