Hello,
As many of you all might known, LACNIC has been allocated the block 201/8 from IANA back in April/2003:
Based on this, we would like to ask to network administrators in general to revise their router configuration to make sure they are not filtering valid routes, like networks into 201/8 block.
Thank you. Hostmaster // Registration Service ---------------------------------- Latin America and Caribbean Region Internet Addresses Registry http://www.lacnic.net ----------------------------------
Some folks (like me) verify assignments based on published data from the RIRs. Checking your FTP site for delegated prefixes as they show up in the DNS, I see this in the zones directory: -rw-r--r-- 1 ftp ftp 653 Dec 23 11:58 170-LACNIC -rw-r--r-- 1 ftp ftp 187 Dec 23 11:58 170-LACNIC.asc -rw-r--r-- 1 ftp ftp 52 Dec 23 11:58 170-LACNIC.md5 -rw-r--r-- 1 ftp ftp 214 Dec 23 11:58 199-LACNIC -rw-r--r-- 1 ftp ftp 187 Dec 23 11:58 199-LACNIC.asc -rw-r--r-- 1 ftp ftp 52 Dec 23 11:58 199-LACNIC.md5 -rw-r--r-- 1 ftp ftp 1478 Dec 23 11:58 204-LACNIC -rw-r--r-- 1 ftp ftp 187 Dec 23 11:58 204-LACNIC.asc -rw-r--r-- 1 ftp ftp 52 Dec 23 11:58 204-LACNIC.md5 -rw-r--r-- 1 ftp ftp 108 Dec 23 11:58 205-LACNIC -rw-r--r-- 1 ftp ftp 187 Dec 23 11:58 205-LACNIC.asc -rw-r--r-- 1 ftp ftp 52 Dec 23 11:58 205-LACNIC.md5 e.g. no zone data for 201.0.0.0/8 - so at least from here, we will filter 201.0.0.0/8 until we see valid DNS data. --bill