It's the other way round: SPRINT should tell his customers he can't guarantee 100% global Internet connectivity because he disagrees with the current address allocation policy of the IANA/InterNIC/RIPE NCC/AP-NIC. They might want to look for a different transit provider...
Regards,
Miguel
say what you will about this policy, but someone (sean?) thought long and hard about it's implications. i didn't like the abrupt manner in which it was implemented, but it does take guts and it is pretty elegant: it's everyone else's 206 customers who can't reach sprint's customers. even though it's the packets from sprint's customer's that can't make it back to everyone else. that's the beauty of it. sprint announces networks in the 206 space to us and to everyone else. we accept the announcements if they are larger than /24: *> 206.12.94.0 192.41.177.241 128 80 0 1239 3602 ? *> 206.12.187.0 192.41.177.241 128 80 0 1239 1794 ? *> 206.13.159.0 192.41.177.241 128 80 0 1239 1791 3064 i * 206.24.100.0/23 192.41.177.241 128 80 0 1239 1792 3563 i *> 206.40.99.0 192.41.177.241 128 80 0 1239 3663 i *> 206.40.100.0 192.41.177.241 128 80 0 1239 3663 i *> 206.40.101.0 192.41.177.241 128 80 0 1239 3663 i *> 206.40.102.0 192.41.177.241 128 80 0 1239 3663 i *> 206.40.103.0 192.41.177.241 128 80 0 1239 3663 i * 206.40.128.0/19 192.41.177.241 128 80 0 1239 4534 i so if i'm a customer of sprint in a 206+ network that is announced as a /24, i have a route to the world. the real message is if you have a 206+ address, make sure that your provider can put it into an aggregation block for you (or go to sprint). nobody said it would be boring. :-) Jeff Young young@mci.net