The issue of reverse DNS is the only reason for having
"unique" exchange point addressing.
The fact as I see it is that the exchange point is not
a destination. The exchange point addresses are used solely
as a transit "space", and it's nice to know what you're
hopping accross.
The only time that the exchange point as routable space
has been and issue for me is when reachability to those
network blocks is being readvertized by a peer.
There is NO reason that a service provider needs to
readvertise an exchange point network block. It's not a
destination. Eliminating this specific abuse would be a
Good Thing(tm).
Since there is no technical reason for an exchange point
to be routable, it comes down to whim. I *like* having
unique exchange point addresses for troubleshooting
purposes, for all the reasons below. That does not mean
it's not perfectly reasonable for an exchange point
operator to make it non-routable addressing, since it's
their exchange point.
If it weren't for the RA's, the ATM environment has no
need to be a shared network anyway. Might as well make the
VC's individually numbered /30's, or 10.254.254.0/24.
Why not?
Curt-