October 2008 - NZNOG - lists.nznog.org

Vodafone peering cleanup
by Pshem Kowalczyk 12 Oct '08

12 Oct '08

Hi All, I would like everyone know that Vodafone now peers at CHIX (with old ihug AS#). We've also embarked on a journey to de-pollute our advertisements. Still some way to go, but watch this space ;-) kind regards Pshem

1 0

JANOG's English Page Updated
by Masaru AKAI 11 Oct '08

11 Oct '08

Dear NZNOG Colleagues, We have updated JANOG (Japan Network Operators' Group) English wiki page. Recent additions include presentation titles and abstracts for the JANOG22 meeting, which was held July 2008. You can view the contents via the link below. http://www.janog.gr.jp/en/index.php?JANOG22%20Programs For us to bring better content, your comments and feedbacks are greatly appreciated. Regards, Masaru AKAI, for JANOG i18n Team

1 0

Submarine cable exposed by erosion on Murawai Beach
by Tony Wicks 10 Oct '08

10 Oct '08

Hi all, while doing a bit of off roading at Murawai Yesterday, I came across this exposed submarine cable. It could be one of the older Pacrim or Tasman cables but I suspect it may be the Southern Cross Western cable. I would hope the appropriate people might be on this list to recognize the cable and initiate remedy action as the cable is in a very public and exposed position. http://tonyw.com/cable-2.htm There are some Telecom cable warning signs further back in line with the cable, and next stop from Murawai in the direction the cable is going is Australia. Cheers, beer on

5 8

NZRR Route Registry Update
by NZRR Database Notifications 09 Oct '08

09 Oct '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia Ltd - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.128.0/21^21-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.6.116.0/23^23-29, 202.27.88.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: praneel.prasad(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080729 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.128.0/21^21-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.6.116.0/23^23-29, 202.27.88.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081010 source: NZRR ------------------------------------------------------------

1 0

APNIC at IGF 2008 and APNIC Fellowships
by Srinivas Chendi 05 Oct '08

05 Oct '08

To remove yourself from this email list go to https://apnic.insightfulcrm.com:443//removeme.php?identifier=ddec4293-e7e9-…

1 0

Auckland datacenters
by Nathan Ward 05 Oct '08

05 Oct '08

Hi all. I'm looking for somewhere to put servers and stuff in Auckland. Central is better, but I'm open to alternatives. I've talked to a few places, but they are adverse to more than 10A per rack and other silly things. Attempting to work through it, but.. yeah. Any recommendations (offlist) would be nice. If desired, I can summarise back to the list. I'm more interested in neutral places than anywhere run by an ISP, mainly because I don't want to have to move gear, or be treated like a lower class citizen if I move away from their transit. Not saying it would happen, but independence is healthy. The possibility for caged space is also nice. There's one or two obvious places, but bear in mind that I'm thinking about 5 racks immediately, maybe 10 within 12 months, maybe more. The obvious places aren't big enough. Alternatively, if anyone has a need for something like this then let me know and we can collaborate. -- Nathan Ward

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Oct '08

05 Oct '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9834 descr: Route set advertised to AS9560 by Trade Me Limited - AS9834 members: 202.21.128.0/24^24-29, 203.57.145.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: allister(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080626 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9834 descr: advertised to AS9560 by Trade Me Limited - AS9834 members: 202.162.72.0/23^23-29, 202.21.128.0/24^24-29, 203.57.145.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081006 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Oct '08

05 Oct '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24078 descr: Route set advertised to AS9560 by TradeMe - AS24078 members: 202.21.128.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050408 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24078 descr: advertised to AS9560 by Trade Me Limited - AS24078 members: 202.162.72.0/23^23-29, 202.21.128.0/24^24-29, 203.57.145.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081006 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Oct '08

05 Oct '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24078 descr: advertised to AS9439 by Trade Me Limited - AS24078 members: 202.21.128.0/24^24-29, 203.57.145.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080626 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24078 descr: advertised to AS9439 by Trade Me Limited - AS24078 members: 202.162.72.0/23^23-29, 202.21.128.0/24^24-29, 203.57.145.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081006 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Oct '08

05 Oct '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9834 descr: advertised to AS9439 by Trade Me Limited - AS9834 members: 203.57.145.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080626 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9834 descr: advertised to AS9439 by Trade Me Limited - AS9834 members: 202.162.72.0/23^23-29, 202.21.128.0/24^24-29, 203.57.145.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081006 source: NZRR ------------------------------------------------------------

1 0