>> Or to ask it a different way, (and maybe this is the >> solution) will all of the 10.x.x.x (and the other IPv4 >> private addresses) suddenly become globally broadcast?
>Please define 'global broadcast' Think of it as if they were now suddenly 1::10:x:x:x, valid on the public internet, and "routable" even though they were private before. This is what I meant by "global" probably pore phrasing, but this example should show what I was asking. > > This is a bigger problem. What will an IPv6 application or > hardware do with a ::10.x.x.x address? > >From a NetBSD's netstat -rn output (trimmed a bit): > >Internet6: >Destination Gateway Flags Refs Use Mtu Interface >::/104 ::1 UGRS 0 0 33220 lo0 => >::/96 ::1 UGRS 0 0 33220 lo0 => >::127.0.0.0/104 ::1 UGRS 0 0 33220 lo0 >::224.0.0.0/100 ::1 UGRS 0 0 33220 lo0 >::255.0.0.0/104 ::1 UGRS 0 0 33220 lo0 >::ffff:0.0.0.0/96 ::1 UGRS 0 0 33220 lo0 >2002::/24 ::1 UGRS 0 0 33220 lo0 >2002:7f00::/24 ::1 UGRS 0 0 33220 lo0 >2002:e000::/20 ::1 UGRS 0 0 33220 lo0 >2002:ff00::/24 ::1 UGRS 0 0 33220 lo0 > >In other words: nullroute those 'special' blocks. >Same goes for RFC1918 space btw. Then what you are saying is the RFC 1918 private spaces are still private? -------------------------------------------------------------------- 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] --------------------------------------------------------------------
