March 2005 - NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 17 Mar '05

17 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #2103] Routing updates for WIX Route Servers (fwd) - Date: Fri, 18 Mar 2005 15:18:45 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503181518250.19063(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.36.119.0/24^24-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.78.240.0/23^23-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.36.119.0/24^24-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050318 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Mar '05

17 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #2102] Routing updates for APE Route Servers (fwd) - Date: Fri, 18 Mar 2005 15:18:10 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503181517410.19063(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.36.119.0/24^24-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.78.240.0/23^23-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.36.119.0/24^24-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050318 source: NZRR

1 0

Re: RE: [nznog] telecom planning to break VoIP over its network?
by Jonny Martin 17 Mar '05

17 Mar '05

> NZ needs some competition in the Telco market. I have to disagree with that. There is only one steady state equilibrium in a traditional telco market. We have that already. What we need are more _alternatives_ to telcos. Get out there and build some network. It's not that hard :) Cheers, Jonny.

1 0

Updating the APE and WIX route servers
by Andy Linton 17 Mar '05

17 Mar '05

Can I remind you that when you want us to make changes to the filters which control what you can announce on the exchanges you need to complete the forms at: APE http://ape.nzix.net/cgi-bin/ChangeRoutes.cgi WIX http://wix.nzix.net/cgi-bin/ChangeRoutes.cgi Please note that if you want changes at both exchanges you need to ask explicitly by completing *both* forms. We won't attempt to use telepathy as part of this process.

1 0

ICONZ Prefix list update - 2005-03-18
by John Johnston 17 Mar '05

17 Mar '05

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Hey all, For all those that peer direct with ICONZ here is an update. Current list is attached or goto http://www.iconz.net/prefix Regards John Johnston Network Engineering Manager ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: 021 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET www.iconz.net

1 0

Anycast and how it can work for you
by Barry Murphy 17 Mar '05

17 Mar '05

Hey Guys, Just wondering how many providers other than citylink adapt anycast into their network. I decided to write something here to explain to others what it is and how I've implemented it. To start, I run www.fast.co.nz which provides _free_ downloads of open source ISOs and websites. Since certain ISPs decided to depeer the ISP that was hosting my server couldn't fit the bill for this free content, even though it was saving the providers international bandwidth, thus I incorporated anycast. I have a server in Wellington connected to WIX and another on APE. Both servers advertise the IP range 202.7.6.32/29, ovcourse the Auckland server to APE and the Wellington server to WIX, Citylink then advertise the same range at a datacenter in the USA. If a users provider is connected to one of the above exchanges, they are connected to the Server closest to them, if they don't peer at either exchange they are sent to the USA server Where in my case they are forwarded to http://peer.fast.co.nz . In a commercial environment such as Trademe this could be implemented to save money. Trademe Could run it's servers in Wellington the same way they are now, and server the content to anyone That peers at the WIX, they can then advertise the same ip range in the USA and mirror the servers or maybe just an image server for the .jpg, .gif, .png images etc. How does this save money having servers in the USA, well to rent colo space and a p4 2.8gig Server in the USA costs me as little as $80 p/m for 1tb, that's right 1024Gigs worth of data And the connection is very stable. For commercial companies such as Trademe they may require a Little more bandwidth than a TB and support 24/7 etc, so they may pay tops $400 p/m, this would Be a LOT cheaper than buying additional circuits from providers in NZ. How this would effect providers that have depeered? Well lets take stuff for example, we know They push close to 25Mb/s at times, lets add Trademe and say they push 50Mb/s , well this would Mean that the providers that don't peer will be spending a couple hundred thousand $ to provide The content to their users, it would be cheaper for them to just peer. The above is just an explanation of anycast and how it could be used to serve your websites or A way to better manage your network. Any views written to the NZNog are always the view of my own And not those of my peers or employers. Regards Barry

3 2

Recovery of unused address space-implementation
by Elly Tawhai 16 Mar '05

16 Mar '05

Hi, Just forwarding this annoucement made about the Recovery of unused address space-implementation for those from NZ not subscribed to Apnic-announce mailing list. Regards, Elly APNIC * To: apnic-announce(a)apnic.net * Subject: [apnic-talk] [Apnic-announce] Recovery of unused address space -implementation * From: APNIC Secretariat <secretariat(a)apnic.net> * Date: Fri, 18 Feb 2005 11:53:47 +1000 * Cc: * List-archive: <http://www.apnic.net/mailing-lists/apnic-talk> * List-help: <mailto:apnic-talk-request(a)lists.apnic.net?subject=help> * List-id: General discussions on APNIC <apnic-talk.lists.apnic.net> * List-post: <mailto:apnic-talk(a)lists.apnic.net> * List-subscribe: <http://mailman.apnic.net/mailman/listinfo/apnic-talk>,<mailto:apnic-talk-request(a)lists.apnic.net?subject=subscribe> * List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/apnic-talk>,<mailto:apnic-talk-request(a)lists.apnic.net?subject=unsubscribe> * Reply-to: apnic-talk(a)apnic.net * Sender: apnic-announce-bounces(a)lists.apnic.net * User-agent: Mozilla Thunderbird 0.8 (Macintosh/20040913) Dear colleagues, In March 2005, the APNIC Secretariat will implement the policy, "Recovery of unused address space". The policy is described in section 5 of "Policies for historical Internet resources in the APNIC Whois Database" at: http://www.apnic.net/docs/policy/historical-resource-policies.html#5 This policy implements the consensus decision reached at APNIC 17 and endorsed by the Executive Council on 14 May in relation to proposal prop-017-v001. Details of the original proposal and links to discussions are available at: http://www.apnic.net/docs/policy/proposals/prop-017-v001.html For more information about this policy, please see the "Guide to the recovery of unused address space" at: http://www.apnic.net/docs/policy/historical-recovery-guide.html If you have questions about this policy, please contact the APNIC helpdesk at: Email: helpdesk(a)apnic.net Phone: +617 3858 3188 Fax: +617 3858 3199 Regards, ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 ----------------------------------------------------------------------

3 2

peering discussion on the radio with Russell OConnell
by Barry Murphy 16 Mar '05

16 Mar '05

Original mp3 was taken from http://www.95bfm.com/hardnews.php however I cannot locate it now: http://anycast.fast.co.nz/extras/russelloconnell-2005-03-16-bfm.mp3 (For ape or wix connected users only) Regards Barry

2 1

University of Auckland peering at the APE
by Andy Linton 15 Mar '05

15 Mar '05

Their peering session has been up now for about three hours. If you're an APE route server peer and you route to them via more expensive 'Domestic Transit Services' you may want to architect a different solution. They're announcing 130.216.0.0/16. If you are connected to the APE switch fabric and you're not peering with the route servers we'd be happy to help.

1 0

Routes from Ihug and possibly others
by Barry Murphy 14 Mar '05

14 Mar '05

Hey there, I've had a few reports from ihug customers trying to get to the following IP ranges that fall off APE: 202.7.6.32/29 - WIX Only 202.7.5.32/29 - APE Only 202.7.6.32/29 - ANYCAST (advertised at both exchanges) These ranges are provided by citylink for an APE only and anycast range, if your accepting routes from the route-servers, please check your filters and allow traffic for the above 3 ranges. These IP's pass traffic for the www.fast.co.nz project with opensource mirrors and downloads, if you want your users to be able to receive these downloads in the cheapest and quickest possible way, then fix it :) Thanks Barry

1 1