RE: rfc1918 ignorant

Interesting.
Did any of you note last month or so that
Sprint US came out with a notice that they
are no longer going to router /30 ptp
subnets unless the customer specifically
asks for it?

Could that be why 10.x.y.z is showing up here?

Sprint??? you out there?

According to the notice they send me on 7/1, this isn't supposed to take
effect until Aug 17th or 18th for existing customers, and they didn't
mention an option to specifically request that they not do this.
However, there was a link:

http://www.sprint.net/faq/serialip.html

That explains that you can keep using your ptp IP if you request it, but
in either case, they will no longer route their end of the IP.

By the way, doesn�t this break PMTU if the far end device has tunnels or such
which have lower MTU than on the p2p link? (because the packets would
be dropped by loose RPF external to sprintlink)

Pete

Interesting.
Did any of you note last month or so that
Sprint US came out with a notice that they
are no longer going to router /30 ptp
subnets unless the customer specifically
asks for it?

Could that be why 10.x.y.z is showing up here?

No. :slight_smile:
12 sla-bbtech-2-0.sprintlink.net (203.222.37.106) 114.207 ms 114.295 ms 114.340 ms

In this example, bbtech (the one shown in example traceroute below) uses 1918
as transit space on their network. Looks cute though with so many 1918 hops
(heh, not that i recommend it!)

-hc