There is a different argument, other than collision rate, for having a
registry. Whois and reverse DNS.
I have debugged numerous networks where there are leaks of RFC1918 addresses
from other places. Given a flat multi-city L2 "WAN", it's very difficult to
debug unless you have homogenous equipent with all of that vendor's
management stuff. Yes, SNMP ought to work, and sometimes it does.
The first time that I was called to debug this, it was because we had just
put one institution on the internet (I'm talking 1994 here). The default
route injected into the WAN attracted all sorts of packets with wrong source
addresses. But, it was early, and RFC1918^WRFC1597 wasn't as ubiquitous,
and whois identified the other class Bs that we were seeing.
{how did this happen back in 1994? common subcontractor ran all those networks on the
same set of T1s, charging each customer for the full fare. Yes, there was
a lot of embarassed people}
While ULAs and privacy enhanced addresses have important uses for individual
privacy, when it comes to non-moving business/enterprise infrastructure,
audit and accountability is much more important, and ULA-R does not satisfy
that.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
Attachment:
signature.asc
Description: PGP signature
