Yep, just checked there myself.. apologies, it was a filter on my end :) -----Original Message----- From: Matt Brown [mailto:matt(a)mattb.net.nz] Sent: Saturday, 12 February 2005 1:19 p.m. To: Craig Spiers Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Stuff.co.nz Routing & Peering @ Wix? On Sat, 2005-02-12 at 13:12 +1300, Craig Spiers wrote:

Anyone noticed the ip block maintained by stuff.co.nz is not actually being advertised to the wix route servers?

The announcement posted to NZNog earlier in the week (although it was careful not to mention stuff.co.nz directly) indicated that a /27 is being advertised to the route servers. Checking the looking glass on wix.net.nz shows that it is most certainly being advertised to the route servers. -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

um, yeh can't get to it from ggi Simon Byrnand wrote:

At 13:19 12/02/2005, Matt Brown wrote:

...

On Sat, 2005-02-12 at 13:12 +1300, Craig Spiers wrote:

...

Anyone noticed the ip block maintained by stuff.co.nz is not actually being advertised to the wix route servers?

The announcement posted to NZNog earlier in the week (although it was careful not to mention stuff.co.nz directly) indicated that a /27 is being advertised to the route servers.

Checking the looking glass on wix.net.nz shows that it is most certainly being advertised to the route servers.

Speaking of stuff.co.nz, is anyone else having trouble reaching it in the last half hour ? And trademe ? Seems to be stopping at the hop nzlapwn1.nz.ip.att.net.

Regards, Simon

_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

[sending to NZNOG properly this time!] On Mon, 2005-02-14 at 10:53 +1300, Simon Byrnand wrote:

Speaking of stuff.co.nz, is anyone else having trouble reaching it in the last half hour ? And trademe ? Seems to be stopping at the hop nzlapwn1.nz.ip.att.net.

AT&T have an issue. Oddly the traffic is low, 20% of normal instead of the 60% the WIX-AT&T split we found before would indicate. I guess there's a bit of asymetric routing out there :| -- David Zanetti Team Leader, Systems Administration Catalyst IT Limited +64-4-8032233 +64-21-402260

Paul Adshead wrote:

A company in the US that we are trying to contact for legitimate business, is bouncing our email with the following error:

You do not have permission to send to this recipient. For assistance, contact your system administrator. ... REJECT IP Range Blocked:203 - send questions to emailhelp(a)uscompany.com>

Is there any way to find out the geographic extents of IP addresses starting 203. then they can be advised of their stupidity??

APNIC? -- Juha

At 10:30 15/02/2005, Neil Bertram wrote:

It's more likely to be a spam-related issue. Either your subnet is listed on some anti-spam list (like RBL) or that company has manually blocked subnets that lots of spam comes from. Some NZ subnets are close enough to the Asian spam subnets, I'm sure...

203.x.x.x is hardly a subnet though, its probably a large part of the world ;-) Regards, Simon

On Tue, 15 Feb 2005, Simon Byrnand wrote:

At 10:30 15/02/2005, Neil Bertram wrote:

203.x.x.x is hardly a subnet though, its probably a large part of the world ;-)

Given the number of references to "jp", "in" and "cn" in the list Joe produced, it's a not-insignificant portion of the world's population. Well over a quarter, and probably ends up at about a third once you add together the other bits. 'merkins regularly go wildly excessive in their responses to things. Last ISP I worked for had their whole /18 blocked by a company that had seen a single attempt to probe their network. Since we couldn't e-mail them, it required faxes being sent every two hours for over a day before they removed the block. Why bother? Because a number of our customers were paying for web hosting with the company. -- Matthew Poole "Don't use force. Get a bigger hammer."

Joe was too fast for me... :) Just to clarify, APNIC doesn't allocate on a per-country basis. There is no real technical benefit from doing so and it would reduce the chances of aggregation within the /8 blocks. The 203/8 spans over the whole APNIC service region. All the RIRs publish allocation data (http://www.apnic.net/info/reports/). It's mainly used for statistical analysis and research, but you can also extract country data for example as Joe has done below. For a list of all resource ranges allocated to APNIC, see: http://www.apnic.net/db/ranges.html Cheers, Nurani Nimpuno APNIC

-----Original Message----- From: Joe Abley [mailto:jabley(a)isc.org]

On 14 Feb 2005, at 16:23, Paul Adshead wrote:

...

Is there any way to find out the geographic extents of IP addresses

...

starting 203. then they can be advised of their stupidity??

$ curl -s ftp://ftp.apnic.net/apnic/dbase/data/country-ipv4.lst | \ awk -F: '/^203\./ { print $2, $3; }' 203.0/10 au 203.64/13 tw 203.72/14 tw 203.76.0/18 au 203.76.64/19 jp 203.76.96/19 bd 203.76.128/19 in 203.76.160/20 lk 203.76.176/20 in 203.76.192/18 ph 203.77.0/17 tw 203.77.128/19 hk 203.77.160/20 au 203.77.192/20 in 203.77.208/20 id 203.77.224/19 id 203.78.0/22 tw 203.78.4/24 in 203.78.5/24 hk 203.78.6/23 hk 203.78.8/21 sg 203.78.16/20 au 203.78.32/20 hk 203.78.48/20 ph 203.78.64/19 hk 203.78.96/20 th 203.78.128/19 in 203.78.160/20 np 203.78.192/20 my 203.78.224/19 jp 203.79.0/19 cn 203.79.32/20 ap 203.79.48/20 jp 203.79.64/18 nz 203.79.128/17 tw 203.80.0/22 hk 203.80.32/20 au 203.80.64/18 hk 203.80.128/22 hk 203.80.160/20 au 203.80.192/18 hk 203.81.12/22 jp 203.81.16/20 cn 203.81.32/19 sg 203.81.64/19 mm 203.81.96/20 lk 203.81.128/19 kr 203.81.160/20 mm 203.81.192/19 pk 203.81.224/20 pk 203.81.252/22 hk 203.82.0/23 hk 203.82.32/20 ph 203.82.48/20 pk 203.82.64/19 my 203.82.96/20 au 203.82.128/19 sg 203.82.160/19 au 203.82.192/20 bd 203.82.252/22 hk 203.83.0/22 hk 203.83.32/20 id 203.83.64/18 hk 203.83.128/19 kr 203.83.160/20 bd 203.83.192/19 au 203.83.252/22 hk 203.84.0/18 hk 203.84.64/18 au 203.84.128/23 hk 203.84.160/19 ph 203.84.192/19 ap 203.84.224/20 au 203.85/16 hk 203.86.0/18 cn 203.86.64/19 cn 203.86.96/19 in 203.86.128/18 hk 203.86.192/19 nz 203.86.252/22 hk 203.87.0/17 au 203.87.128/18 ph 203.87.192/20 sg 203.87.224/19 cn 203.88.0/18 cn 203.88.64/19 hk 203.88.96/20 bd 203.88.128/19 in 203.88.160/20 hk 203.88.192/19 cn 203.88.224/19 au 203.89.0/22 cn 203.89.32/19 jp 203.89.64/18 au 203.89.128/19 pk 203.89.160/19 nz 203.89.192/18 au 203.90.0/22 cn 203.90.32/19 kr 203.90.64/18 in 203.90.128/18 cn 203.90.192/19 cn 203.90.224/19 hk 203.91.0/18 cn 203.91.64/19 au 203.91.96/19 cn 203.91.128/19 hk 203.91.160/19 jp 203.91.192/19 in 203.91.224/19 au 203.92.0/22 cn 203.92.32/19 in 203.92.64/18 sg 203.92.128/19 my 203.92.160/19 cn 203.92.192/20 in 203.92.224/19 au 203.93/16 cn 203.94.0/19 cn 203.94.32/19 au 203.94.64/18 lk 203.94.128/18 au 203.94.192/18 in 203.95.0/21 cn 203.95.32/19 jp 203.95.64/19 sg 203.95.96/19 cn 203.95.128/17 tw 203.96/15 nz 203.98.0/18 nz 203.98.64/19 au 203.98.96/19 hk 203.98.128/18 hk 203.98.192/19 au 203.98.224/19 nr 203.99.0/19 nz 203.99.32/21 nz 203.99.48/20 pk 203.99.64/21 nz 203.99.96/19 id 203.99.128/18 hk 203.99.192/19 in 203.99.255/24 ws 203.100.0/19 au 203.100.32/19 cn 203.100.64/19 in 203.100.96/19 cn 203.100.128/19 hk 203.100.160/19 kr 203.100.208/20 nz 203.100.224/19 au 203.101.0/17 in 203.101.128/19 th 203.101.160/19 pk 203.101.192/19 sg 203.101.224/19 au 203.102/15 au 203.104.0/18 au 203.104.64/19 ph 203.104.96/19 jp 203.104.128/17 jp 203.105.0/17 hk 203.105.128/19 bd 203.105.224/19 tw 203.106/16 my 203.107.0/18 tw 203.107.64/18 my 203.107.128/17 th 203.108/16 au 203.109.0/19 id 203.109.64/18 in 203.109.128/17 nz 203.110.0/18 nz 203.110.64/20 la 203.110.80/20 in 203.110.128/17 au 203.111.0/17 au 203.111.128/18 au 203.111.192/20 sg 203.112.0/19 jp 203.112.64/20 id 203.112.80/20 hk 203.112.96/19 au 203.112.128/19 in 203.112.192/19 bd 203.112.224/19 my 203.113.0/17 th 203.113.128/18 vn 203.113.192/18 au 203.114.0/18 sg 203.114.64/19 ph 203.114.96/19 th 203.114.128/18 nz 203.114.224/19 th 203.115.0/18 lk 203.115.64/18 in 203.115.128/18 ph 203.115.192/18 my 203.116/15 sg 203.118.0/18 sg 203.118.64/18 th 203.118.128/18 nz 203.118.192/18 cn 203.119.0/24 au 203.119.1/24 jp 203.119.2/24 hk 203.119.3/24 tw 203.119.4/22 ph 203.119.8/22 vn 203.119.12/24 au 203.119.13/24 id 203.119.14/23 au 203.119.16/21 ap 203.119.24/21 cn 203.119.32/22 cn 203.119.36/22 vn 203.119.40/24 jp 203.119.41/24 au 203.119.42/23 au 203.119.44/22 au 203.119.48/20 au 203.119.64/18 au 203.119.128/17 au 203.120/16 sg 203.121.0/17 my 203.121.128/18 th 203.121.192/19 au 203.122.0/18 in 203.122.64/18 au 203.122.128/17 au 203.123.0/19 sg 203.123.32/20 in 203.123.64/19 au 203.123.96/20 au 203.123.128/18 in 203.123.224/19 id 203.124.0/17 sg 203.124.128/17 in 203.125/16 sg 203.126/15 sg 203.128.0/19 pk 203.128.64/19 id 203.128.128/19 cn 203.128.252/22 pk 203.129.0/22 pk 203.129.64/19 hk 203.129.128/19 au 203.129.192/18 in 203.130.0/19 pk 203.130.64/19 in 203.130.128/19 th 203.130.192/18 id 203.131.0/18 au 203.131.64/18 ph 203.131.128/18 ph 203.131.192/20 jp 203.131.224/19 hk 203.132.0/17 au 203.132.128/19 in 203.132.192/20 hk 203.132.224/19 au 203.133.0/17 tw 203.133.128/18 jp 203.133.252/22 pk 203.134.0/17 au 203.134.128/18 au 203.134.252/22 pk 203.135.0/18 pk 203.135.64/19 tw 203.135.128/19 hk 203.135.192/18 jp 203.136/14 jp 203.140/15 jp 203.142.0/18 ap 203.142.96/19 hk 203.142.128/17 au 203.143.0/18 lk 203.143.64/19 au 203.143.128/19 sg 203.143.192/18 au 203.144.0/19 au 203.144.32/20 nz 203.144.64/19 kh 203.144.96/19 in 203.144.128/17 th 203.145.0/19 th 203.145.64/19 hk 203.145.128/18 in 203.145.224/19 ap 203.146/16 th 203.147.0/18 th 203.147.112/20 ap 203.147.128/17 au 203.148.0/18 cn 203.148.64/20 ph 203.148.128/17 th 203.149.0/18 th 203.149.64/20 au 203.149.128/17 tw 203.150/15 th 203.152.0/18 sg 203.152.96/19 nz 203.152.128/19 in 203.152.224/19 au 203.153.0/22 id 203.153.64/20 hk 203.153.128/20 th 203.153.224/19 au 203.154/15 th 203.156.0/17 th 203.156.128/18 th 203.156.192/18 cn 203.157/16 th 203.158/15 th 203.160.0/23 vn 203.160.32/19 hk 203.160.64/19 hk 203.160.96/20 vn 203.160.128/20 lk 203.160.160/19 ph 203.160.192/19 ph 203.160.224/19 tw 203.161.0/22 vn 203.161.64/18 au 203.161.128/18 au 203.161.224/19 hk 203.162/16 vn 203.163.0/17 ap 203.163.128/18 in 203.163.192/19 tw 203.164/16 au 203.165/16 jp 203.166.0/17 au 203.166.128/19 sg 203.166.224/19 au 203.167.0/17 ph 203.167.128/17 nz 203.168.0/19 ph 203.168.64/18 jp 203.168.128/17 hk 203.169.0/22 ph 203.169.32/20 hk 203.169.64/18 sg 203.169.128/17 hk 203.170.0/20 ph 203.170.64/20 pk 203.170.128/17 th 203.171.0/22 ph 203.171.64/18 au 203.171.128/19 ap 203.171.252/22 in 203.172.0/19 ph 203.172.32/19 th 203.172.64/18 th 203.172.128/17 th 203.173.0/18 au 203.173.64/20 jp 203.173.128/17 nz 203.174.0/22 ph 203.174.64/20 jp 203.174.128/18 au 203.174.192/18 jp 203.175.0/22 ph 203.175.64/19 pk 203.175.96/20 pk 203.175.128/17 cn 203.176.0/18 ph 203.176.64/19 ph 203.176.128/17 hk 203.177/16 ph 203.178/15 jp 203.180/14 jp 203.184.0/18 nz 203.184.64/20 au 203.184.128/17 hk 203.185.0/18 hk 203.185.64/18 th 203.185.128/19 th 203.185.192/18 au 203.186/16 hk 203.187.0/17 tw 203.187.128/18 cn 203.187.192/18 in 203.188.0/18 th 203.188.64/18 hk 203.188.128/19 au 203.188.160/19 bd 203.188.192/18 bd 203.189.0/23 bd 203.189.64/20 lk 203.189.128/19 kh 203.189.160/20 hk 203.189.224/19 bd 203.190.0/19 bd 203.190.32/22 bd 203.190.64/19 ph 203.190.128/19 in 203.190.160/20 vn 203.190.192/20 au 203.190.254/23 bd 203.191.0/19 bd 203.191.32/23 bd 203.191.64/18 cn 203.191.128/22 bd 203.191.160/19 au 203.191.192/20 au 203.192.0/19 cn 203.192.32/19 th 203.192.96/19 jp 203.192.128/18 jp 203.192.192/18 in 203.193.0/17 hk 203.193.128/18 in 203.193.192/18 au 203.194.0/18 au 203.194.64/19 jp 203.194.96/20 in 203.194.128/17 hk 203.195.0/18 hk 203.195.64/19 hk 203.195.96/20 th 203.195.128/17 in 203.196.0/21 cn 203.196.64/20 in 203.196.96/19 jp 203.196.128/17 in 203.197/16 in 203.198/16 hk 203.199/16 in 203.200/16 in 203.201.0/17 au 203.201.128/18 au 203.201.192/18 in 203.202.0/17 au 203.202.128/18 au 203.202.192/18 jp 203.203/16 tw 203.204/16 tw 203.205/16 jp 203.206/16 au 203.207.0/20 tw 203.207.64/18 cn 203.207.128/17 cn 203.208.0/20 cn 203.208.16/22 cn 203.208.64/18 au 203.208.128/17 sg 203.209.0/17 th 203.209.128/20 hk 203.209.192/18 au 203.210.0/20 hk 203.210.96/19 au 203.210.128/17 vn 203.211.0/19 tw 203.211.64/18 nz 203.211.128/19 sg 203.211.160/19 jp 203.211.192/18 jp 203.212.0/20 cn 203.212.64/20 in 203.212.128/19 au 203.212.192/18 in 203.213.0/17 au 203.213.128/19 au 203.213.192/18 ph 203.214/16 au 203.215.0/19 au 203.215.64/18 ph 203.215.128/19 au 203.215.160/19 pk 203.215.240/20 hk 203.216/16 jp 203.217.0/18 au 203.217.64/19 au 203.217.96/19 tw 203.217.128/18 tw 203.217.192/18 hk 203.218/16 hk 203.219/16 au 203.220/15 au 203.222.0/19 tw 203.222.32/19 au 203.222.64/18 au 203.222.128/18 au 203.222.192/18 cn 203.223.0/20 cn 203.223.32/20 kh 203.223.64/20 jp 203.223.128/19 my 203.223.192/18 hk 203.224/11 kr $

_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nzno>g

'A Place' its that island Bill Gates bought a few years back? kidding, Maybe its grouped into 'Asia Pacific' as part of APNIC? Dan Scott Weeks wrote:

On Mon, 14 Feb 2005, Joe Abley wrote:

: 203.79.32/20 ap : 203.84.192/19 ap : 203.142.0/18 ap

What country is ap? I can't find it at http://www.iana.org/cctld/cctld-whois.htm or in a search and traceroutes to addresses in these three stop in at least 3 different countries. (I didn't want to try more than three...)

scott

_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

On Wed, 16 Feb 2005, Chad Wilson wrote: : From the ISO's site: : http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/iso_... : : AP : African Regional Industrial Property Organization WIPO ST.3 not used at : present stage : : Still bizarre. :-o That can't be right. All other countries are in the AP region. scott : : On Wed, 16 Feb 2005 08:02:18 +1300, Dan Clark wrote: : : > 'A Place' : > its that island Bill Gates bought a few years back? : > kidding, Maybe its grouped into 'Asia Pacific' as part of APNIC? : > : > Dan : > : > Scott Weeks wrote: : > : >> On Mon, 14 Feb 2005, Joe Abley wrote: : >> : >> : 203.79.32/20 ap : >> : 203.84.192/19 ap : >> : 203.142.0/18 ap : >> : >> : >> What country is ap? I can't find it at : >> http://www.iana.org/cctld/cctld-whois.htm or in a search and : >> traceroutes to addresses in these three stop in at least 3 different : >> countries. (I didn't want to try more than three...) :

On 15 Feb 2005, at 13:58, Scott Weeks wrote:

On Mon, 14 Feb 2005, Joe Abley wrote:

: 203.79.32/20 ap : 203.84.192/19 ap : 203.142.0/18 ap

What country is ap? I can't find it at http://www.iana.org/cctld/cctld-whois.htm or in a search and traceroutes to addresses in these three stop in at least 3 different countries. (I didn't want to try more than three...)

I believe it's "Asia Pacific", and that it's used when there is no clear single country to tag a resource to. Joe

See if you address is listed on http://www.moensted.dk/spam/ If you are only listed on country specific lists, complain to the company. Some misguided US companies will block spam from Korea by blocking all APNIC addresses. (the 203.0.0.0/8 is dedicated to APNIC) jfp. ------------------------------------------------------------------------ Jean-Francois Pirus Senior Software Engineer Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------

Hi Richard and all,

-----Original Message----- From: Richard Cox [mailto:lists(a)mandarin.co.nz] <snip>

Gordon Smith commented:

...

Unfortunately there are some in the U.S. that do block all APNIC space, mainly due to the amount of spam originating from China and Korea.

That, plus APNIC's reluctance to accept responsibility for legacy errors in their database.

Well, this is not quite true. APNIC has actually focused a fair bit on improving data integrity in whois over the last few years. To name a few: General improvement of whois data integrity - Clean up of un-referenced objects - Removal of objects unrelated to actual resource info (mar-03) - Removal of resource info not in APNIC range (mar-03) - Modify records that are not RPSL compliant (mar-03) - Reduce amount of inaccurate / out of date records Improving security of whois - Protection of un-maintained objects (sep-02) - Deprecation of 'NONE' and 'MAIL-FROM' (sep-02) - Secure authentication methods (PGP, MD5) - Stop unauthorised changes of records Over the last years, the RIRs have coordinated efforts to transfer the management of early registrations (pre-RIR) from ARIN to the RIR appropriate to the region in which the resource holders reside (http://www.apnic.net/db/erx/). This has resulted in an increase of historical registrations in the APNIC whois over the years - many which have incomplete contact details. In order to prevent anyone to go in and modify these records at their whim, APNIC has locked the records with an APNIC maintainer. We have also implemented processes to handle updates of historical records in a proper manner. In addition to this, after endorsement from the community, efforts are starting this year, to recover unused historical address space. (Many of the early allocations made are no longer in use and are simply left in whois with outdated details.) This will also hopfully reduce the amount of address space hijacking as well as improving the quality of the data in whois. Finally, there are efforts to establishing direct relationships with all resource holders in the APNIC region. This to meet an increased need for a secure manner to validate resource custodianship (which in the future could mean issuing of routing certificates). Again, one of the aims of this apart from clarifying the custodianships is to improve the integrity of the database for allocations made by the RIR as well as for historical allocations. On a general note, it is also worth pointing out that whenever the APNIC hostmasters are contacted about inaccurate contact details in the whois database, they try to look for updated contact details and in some cases contact the resource holders for the correct contact details. (Although this is somewhat difficult if it is legacy space with no internal records available.) If there are other efforts you would like to see APNIC take on, you are encouraged to voice your opinion on the APNIC mailing list. There is a Special Interest Group (SIG) that discussed the whois Database which you can subscribe to here: http://www.apnic.net/community/lists/ You do not have to be an APNIC member to participate in the decision making process. Anyone in the Internet community can express their opinion or put forward a proposal. An archive of all previous policy proposals (including the ones I mention above) can be found here: http://www.apnic.net/docs/policy/proposals/archive.html All current proposals are here: http://www.apnic.net/docs/policy/proposals/ We really do welcome some more participation from New Zealand, so I hope more of you will get involved! Cheers, Nurani ---------------------------------------------------------------------- Nurani Nimpuno Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 ---------------------------------------------------------------------- See you at APNIC-19 Kyoto, Japan, 21 to 25 Feb 2005 and APRICOT 2005 http://www.apnic.net/meetings ---------------------------------------------------------------------- * ASIAN TSUNAMI & EARTHQUAKE RELIEF APPEAL Links to tsunami and earthquake disaster relief programs are available on our home page at http://www.apnic.net. ______________________________________________________________________