On 05/02/2011, at 8:29 PM, Gaurab Raj Upadhaya wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2/5/11 8:13 AM, Geoff Huston wrote:
Given that's the address that appears to have been hijacked by cisco for its wifi gear, its a bit later to be attempting to pull that one back from the abyss.
Agree.! it's down the abyss, and other then the research value, there isn't much value to it. But I'd believe, listing them formally in an RFC as Bogons is different from it being not so useful.
As far as IANA would be concerned, it's allocated to APNIC, and they are done with it. APNIC has to willingly give up it's ability to further delegate those blocks for them to be listed in that I-D. Would APNIC be able to formally ask IANA/Leo to categorize it as Bogon ?
If the incoming traffic to these prefixes drops to levels that are within a similar order to traffic to other addresses APNIC will return them to the allocation pool.
or may be Cisco can pay the APNIC membership and justify the /24 for internal use :-).
Or maybe Cisco can do the Right Thing and correct this in all their deployed equipment. Geoff