[atlas] All-Probe Traceroute + detect RFC1918 addresses

Gert Doering <gert at space.net> writes:

> "What happens inside your network happens inside your network" (and
> the RFC explicitly permits that, of course), but we do not want to 
> see it on someone else's network.

Exactly my point.  My traceroute example is all in "my" network if you
include the mobile access endpoint.  The usage of RFC1918 for PGW pools
and links is co-ordinated.  There is no reason you should not see
RFC1918 adresses as source here.

>> > Given the age of the document, the language used to be less STRONG
>> > back then.
>> 
>> Sure. Assigning RFC1918 addresses to customers was also unheard of, and
>> didn't even need to be mentioned.
>
> If that is CGN'ed, it's not violating the RFC.

Of course it's not.  But you'll have to define the customer endpoint as
part of the RFC1918 "enterprise" network.

> Leaking packets from addresse that do not belong to you does.

Yes.  And the point is that you cannot tell if there is a leakage unless
you are able to detect the network borders.  Which you can't by counting
traceroute hops.


Bjørn