There are absolutely zero reasons I've seen so far (I'd be interested to hear abstruse ones? "I thought who cares" isn't one) to avoid using one of the private ranges.
10.0.0.0/8 isn't even noticeably harder to remember or type, really.
There are absolutely zero reasons I've seen so far (I'd be interested to hear abstruse ones? "I thought who cares" isn't one) to avoid using one of the private ranges.
10.0.0.0/8 isn't even noticeably harder to remember or type, really.
APnic is not blameless here. They knew the issues with this space when it was assigned to them as a research network. For quite awhile they allowed Google to advertise the space and collect data on it's usage. I assume Google no longer was providing the infrastructure to do so and APnic saw an opportunity to have someone collect data for them for free.
Collecting data on traffic sent to this ip range is one thing but approving its use for a service available to the public knowing the accompanying issues much of the public would have accesssing it is in my opinion not responsible use of a research network.
There are better options though. Why not the class E reserved addresses, or just using some address space you actually own?
Though apparently an RFC from... 2012... has a solution. 100.64.0.0/10 is for internal ISP use.