Someones being naughty again...

Sat Mar 14 09:06:29 UTC 1998

> Offhand, I can't think of any other problems but I really discourage
> people from using internal address space for this purpose because it:
> 
> 	- breaks stuff like path MTU discovery, etc. when filtered.

You also discourage people from filtering the ICMP packets this uses.
Right?

> 	- prevents easy identification of links, whose they are, etc.
> 	  because you can't have reverse DNS and the addresses don't
> 	  belong to you.

Not a problem if it is entirely inside an enterprise, as valid addresses
before and after it would be the same enterprise.  But as links between
I would see a problem.

> 	- causes confusion when multiple networks that are using such
> 	  addresses are merged or interconnected in the wrong (right)
> 	  way.

Private addressing is not the ideal solution, but when networks are built
with lots of links to lots of places, address allocating authorities
prefer you to use private addresses where feasible.  It maybe be a gray
and fuzzy line determining that, but many cases clear work fine with
such addresses (for example having a consisent MTU).

> I like the idea behind why you would do it, but... can't justify it.

I don't have so many links that I can't get them all in a /24.  But much
beyond that and I will be using private addresses.  I do run some private
address LANs, but they end in private addresses and you should never see
them (but if you are my customer you will be able to).

-- 
Phil Howard | stop8810 at spammer6.net stop6589 at spammer3.net no1way64 at no3where.edu
  phil      | no3spam1 at noplace4.edu no3spam5 at anywhere.com crash431 at s8p1a7m3.com
    at      | blow2me8 at no83ads9.org stop7363 at dumb7ads.edu suck6it9 at no1place.net
  milepost  | end8it30 at noplace0.com no2spam5 at anyplace.org a1b5c1d8 at s3p3a5m0.edu
    dot     | no52ads8 at no97ads7.com die9spam at noplace0.org end0it22 at spam9mer.edu
  com       | stop3424 at no2place.net eat38me1 at lame9ads.org end2ads8 at nowhere8.org