- NZNOG - lists.nznog.org

WTB: Packet Shaping Appliance
by Craig Spiers 21 Oct '09

21 Oct '09

Hi Guys, Anyone got an old packeteer 6500 or similar they're wanting to move on? We're currently looking for one J Cheers Craig Spiers | Network Manager Solarix Networks Limited DDI: +64 9 974 4753 | Mob: +64 21 857 183 | Office: +64 9 974 4750 | FAX: +64 9 974 4760 Email: craig.spiers(a)solarix.co.nz | Web: www.solarix.net.nz CAUTION: This email is confidential. If it is not intended for you please do not read, distribute or copy it or any attachments. Please notify the sender by return email and delete the original message and any attachments.Any views expressed in this email may be those of the individual sender and may not necessarily reflect the views of Solarix Networks Limited. Please consider the environment before printing this email! Disclaimer added by CodeTwo Exchange Rules http://www.codetwo.com

1 0

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

21 Oct '09

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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 121.79.224.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091022 source: NZRR ------------------------------------------------------------

1 0

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

21 Oct '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.46.176.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.201.0/24^24-29, 202.169.202.0/24^24-29, 202.169.205.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090929 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.32.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.46.176.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.99.134.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 114.134.173.0/24^24-29, 114.134.174.0/24^24-29, 192.88.85.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.36.0/24^24-29, 202.37.38.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.201.0/24^24-29, 202.169.202.0/24^24-29, 202.169.205.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.99.133.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091022 source: NZRR ------------------------------------------------------------

1 0

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

21 Oct '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091007 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 121.79.224.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091022 source: NZRR ------------------------------------------------------------

1 0

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

21 Oct '09

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:AS17705 descr: advertised to AS9439 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 140.200.248.0/22^22-29, 192.138.251.0/24^24-29, 203.92.25.0/24^24-29, 203.174.26.0/24^24-29, 210.7.46.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080724 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17705 descr: advertised to AS9439 by Inspire Net Ltd - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 121.79.224.0/21^21-29, 140.200.248.0/22^22-29, 192.138.251.0/24^24-29, 203.92.25.0/24^24-29, 203.174.26.0/24^24-29, 210.7.46.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: ops(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091022 source: NZRR ------------------------------------------------------------

1 0

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

21 Oct '09

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091007 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 121.79.224.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091022 source: NZRR ------------------------------------------------------------

1 0

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

21 Oct '09

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:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.46.176.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.201.0/24^24-29, 202.169.202.0/24^24-29, 202.169.205.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090929 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.32.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.46.176.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.99.134.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 114.134.173.0/24^24-29, 114.134.174.0/24^24-29, 192.88.85.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.36.0/24^24-29, 202.37.38.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.201.0/24^24-29, 202.169.202.0/24^24-29, 202.169.205.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.99.133.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091022 source: NZRR ------------------------------------------------------------

1 0

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

18 Oct '09

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:AS17746 descr: advertised to AS9439 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090722 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 120.138.16.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 110.34.48.0/22^22-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.62.245.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091019 source: NZRR ------------------------------------------------------------

1 0

OT: ISP deployment scenarios for IPv6
by Brian E Carpenter 15 Oct '09

15 Oct '09

I'm working on a new draft about ISP scenarios for IPv6, along with Sheng Jiang of Huawei Research. We will soon be soliciting input so that we can fill in the blanks in http://tools.ietf.org/id/draft-carpenter-v6ops-isp-scenarios One reason we're doing this is that translation scenarios seem much more important now than they did a few years ago. I'd love to hear (off list) from any provider willing to spend some time filling in our (gulp, sorry) questionnaire. In case there's any interest in beer related to this, I do plan to be at NZNOG in January. Brian Carpenter

1 0

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

14 Oct '09

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:AS131187 descr: Route set advertised to AS9439 by Teritary Education Commission aka Education Commons Network - AS131187 members: 203.217.140.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: andrew.frazer(a)thenetworks.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090915 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS131187 descr: advertised to AS9439 by Tertiary Education Commission - AS131187 members: 203.217.142.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dylan(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091015 source: NZRR ------------------------------------------------------------

1 0

APRICOT 2010 Call for Papers
by Jonny Martin 12 Oct '09

12 Oct '09

[Apologies for duplicates] Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) 23 February - 5 March 2010, Kuala Lumpur, Malaysia http://www.apricot2010.net CALL FOR PAPERS =============== The APRICOT 2010 Programme Committee is now seeking contributions for Presentations and Tutorials for APRICOT 2010. We are looking for people and proposals that would: - Offer a technical tutorial on an appropriate topic; and/or - Participate in the technical conference sessions as a speaker; and/or - Convene and chair a Birds of a Feather (BOF) session. Please submit proposals on-line at http://submission.apricot.net/paper/user/login.php?event=22 CONFERENCE MILESTONES --------------------- Call for Papers Opens: 12 October 2009 First Deadline for Submissions: 30 November 2009 First Draft Programme Published: 7 December 2009 Final Deadline for Submissions: 14 February 2010 Final Programme Published: 15 February 2010 Final Slides Received: 19 February 2010 PROGRAM MATERIAL ---------------- The APRICOT Programme is organised in three parts, including workshops, tutorials and the conference. The APNIC Policy SIG and Annual Members Meeting will be held during the APRICOT conference. Topics for tutorials and conference would include amongst others relevant to Internet Operations and Technologies: - IPv4 / IPv6 Routing and operations - IPv4 address runout / IPv6 deployment and transition technologies - Backbone operations - ISP and Carrier services - Network security issues (NSP-SEC, DDoS Anti-Spam, Anti-Malware) - Peering / IXPs - Internet policy (Security, Regulation, Content Management, Addressing, etc) - Access and Transport Technologies, including broadband deployment, Cable/DSL, wireless, WiMax, metro ethernet, fiber network, MPLS - Content & Service Delivery (Multicast, Voice, Video, "telepresence", Gaming) CFP SUBMISSION -------------- Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions otherwise the Programme Committee will be unable to review the submission. For work in progress, the most current information available at time of submission is acceptable. Final slides are to be provided by the specified deadline for publication on the APRICOT website. While the majority of speaking slots will be filled by the first submission deadline, a limited number of slots may be available up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Please submit on-line at http://submission.apricot.net/paper/user/login.php?event=22 Any questions or concerns should be addressed to the Programme Committee by e-mail. We look forward to receiving your presentation proposals. Jonny Martin & Philip Smith Co-Chairs, APRICOT Programme Committee program(a)apricot.net

1 0

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

06 Oct '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091007 source: NZRR ------------------------------------------------------------

1 0

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

06 Oct '09

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091007 source: NZRR ------------------------------------------------------------

1 0

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

06 Oct '09

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:AS38477 descr: Route set advertised to AS9439 by Unleash Computers Ltd - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 202.6.116.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: support(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS38477 descr: advertised to AS9439 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 202.6.116.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: michael(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091007 source: NZRR ------------------------------------------------------------

1 0

seeking Florent Bouron
by Brislen, Paul, VF-NZ 05 Oct '09

05 Oct '09

Apologies and beer but... Florent, you emailed me about a network issue and the network team is keen to make contact but can't get hold of you... Can you drop me a line. Sorry all. Cheers Paul Paul Brislen External Communications Manager Vodafone New Zealand 021 721 337 ----------------------------------------------------------------------------------------------- Unless otherwise stated, any views or opinions expressed are solely those of the author and do not represent those of Vodafone New Zealand Limited.

1 0

More DoS attacks
by David Robb 05 Oct '09

05 Oct '09

Hi all, Just FYI, any slowness on the TCL network yesterday around 14:36, 19:53 and 20:48 were probably attributable to yet more DoS attacks against the network. Although we did get them blocked upstream as swiftly as possible, there may've been some short periods of congestion Mostly they seem to be originating from China. --David

1 0

Sysadmin Miniconf LCA2010: CFP extended
by Simon Lyall 03 Oct '09

03 Oct '09

Due to and extended deadline by the Linux.conf.au organising committee the deadline for proposals has been extended to the 15th of October. We have received a number of of excellent proposals already but have space for additional ones, especially shorter and lightning talks. Our Call for Presentations is below: CFP: LCA 2010 Systems Administration Miniconf As part of the linux.conf.au conference in Wellington, New Zealand in January 2010 we will be holding a 1 day mini conference orientated to Linux Systems Administration. Please see our website at http://sysadmin.miniconf.org/ for details. The organisers of the Systems Administration Miniconf would like to invite proposals for presentations to be delivered at the Miniconf. Presentation Topics =================== Topics for presentations could include (but are not limited to) Systems Administration, Backups, Security, Troubleshooting, Buying Decisions, Virtualisation, Enterprise Monitoring and Management, Identity Management, Web and Email management, Wiki, Clustering and High Availability, Log Management, Spam and Virus Filtering, VOIP, Ticketing systems, Bootstrapping and automated installation, Configuration Management and packaging. We strongly welcome topics on best practice, new developments in systems administration and cutting edge techniques to better manage Linux hosts and environments. Presentations should be of a technical nature and speakers should assume that members of the audience have at least a couple of years experience in Unix/Linux administration. Format of Presentations ======================= We are now seeking proposals for presentations at the mini-conference. We have openings for: - 45 minute double-length presentations - 20 minute full presentations - 10-15 minute "How we do things" presentations - 5-10 minute "lightning talks" Please note, due to the single day available, we expect the vast majority of available timeslots to be 25 minutes long or less. The 10-15 minute "How we do things" presentations are intended for people to talk about their sites. Information could include: Servers, talks, tools, people and roles, experiences, software, operating systems, monitoring, alerting, provisioning etc. The intent is to give other attendees a picture of what is happening in the "real world" and some understanding of how other sites work. Submitting talks ================ Please note that in order to give a presentation or attend the miniconf you must be signed up for the main linux.conf.au conference. Presenting at the Miniconf does not entitle you to discounted or free registration at the main conference nor priority with registration. Unfortunately the Miniconf has no budget for sponsorship of speakers (but welcomes offers of sponsorship). Please see the Call for Presentations web page at: http://sysadmin.miniconf.org/cfp10.html the site contains the information required for submissions. Submissions should be made via: http://sysadmin.miniconf.org/proposal10.html Questions should be sent to: lca10 @ sysadmin.miniconf.org. Dates and Deadlines =================== To encourage early submissions priority ( both of inclusion and scheduling ) will be given to presentations submitted before the 7th of September. 2009-09-07 - Deadline for early submissions 2009-10-15 - Deadline for submissions 2009-10-21 - Final programme confirmation. 2010-01-18 - Start of conference. Contact and Questions ===================== Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf and presenting at it. If you have any questions please feel free to email the organisers at: lca10 @ sysadmin.miniconf.org

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 Sep '09

30 Sep '09

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:AS38037 descr: Route set advertised to AS9439 by Internet NZ - AS38037 members: 202.46.176.0/24^24-29, 202.46.183.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: Tim.Hoffman(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS38037 descr: advertised to AS9439 by InternetNZ - AS38037 members: 202.46.176.0/22^22-29, 202.46.183.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091001 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Sep '09

28 Sep '09

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:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.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.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.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.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090929 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Sep '09

28 Sep '09

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:AS4770 descr: advertised to AS9560 by ICONZ LTD - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.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.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ Ltd - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.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.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090929 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Sep '09

28 Sep '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090911 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.46.176.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.201.0/24^24-29, 202.169.202.0/24^24-29, 202.169.205.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090929 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Sep '09

28 Sep '09

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:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090917 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.46.176.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.201.0/24^24-29, 202.169.202.0/24^24-29, 202.169.205.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090929 source: NZRR ------------------------------------------------------------

1 0

Request for Participation - Arbor 2009 Infrastructure Security Report.
by Roland Dobbins 27 Sep '09

27 Sep '09

We're in the process of collecting feedback for the 2009 Infrastructure Security Report; this is the Fifth Edition of the report, and would really be grateful for some .nz responses in order to ensure more complete regional representation in the report. The 2009 Infrastructure Security Survey is up and available for input. You can register to complete the survey at this URL: <https://www.tcb.net/survey/index.php?sid=98557&lang=en> We've again added many questions this time from past participants of the survey, this should be evidenced throughout. Feedback collection will end as soon as we've reached the desired number of respondents (ideally, 80+). We hope to make the results available by November 2009 at the latest. Also, please recall that NO personally- (or organizationally-) identifiable information will be shared in any manner. The 2008 edition of the survey is available here: <http://www.tcb.net/ISR2008_US.pdf> Or on the Arbor web site (reg required): <http://www.arbornetworks.com/report> Thanks in advance for your participation! ----------------------------------------------------------------------- Roland Dobbins <rdobbins(a)arbor.net> // <http://www.arbornetworks.com> Sorry, sometimes I mistake your existential crises for technical insights. -- xkcd #625

1 0

NZRR Route Registry Update
by NZRR Database Notifications 24 Sep '09

24 Sep '09

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: AS24388:RS-ROUTES:AS38477 descr: advertised to AS24388 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 202.6.116.0/23^23-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)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090407 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS38477 descr: advertised to AS24388 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 202.6.116.0/23^23-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)unleash.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090925 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Sep '09

23 Sep '09

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090922 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Sep '09

23 Sep '09

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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090923 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Sep '09

23 Sep '09

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: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Sep '09

23 Sep '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090922 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Sep '09

23 Sep '09

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:AS24006 descr: advertised to AS9439 by Knossos Networks Ltd - AS24006 members: 202.160.48.0/20^20-29, 161.29.192.160/29, 161.29.193.80/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24006 descr: advertised to AS9439 by Knossos Networks Limited - AS24006 members: 114.134.160.0/20^20-29, 202.160.48.0/20^20-29, 161.29.192.160/29, 161.29.193.80/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090924 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 22 Sep '09

22 Sep '09

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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090824 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090923 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 22 Sep '09

22 Sep '09

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-ROUTES6:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2002:0:0:0:0:0:0:0/16^16-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES6:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2404:3800:0:0:0:0:0:0/32^32-64, 2001:0dce:0:0:0:0:0:0/48^48-64, 2001:0dce:e000:0:0:0:0:0/48^48-64, 2001:0df0:004a:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090923 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 Sep '09

21 Sep '09

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090824 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090922 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 Sep '09

21 Sep '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090824 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090922 source: NZRR ------------------------------------------------------------

1 0

WorldxChange IPv6 over xDSL Trial
by Callum Barr 21 Sep '09

21 Sep '09

[cross posted from the ipv6-techsig list incase anyone is interested.] Hi All, WorldxChange is about to start a IPv6 trial over xDSL and was wondering if anyone here would like to participate. At this stage it will be a closed trial limited to 10 or so users. It will be offered over a standard xDSL link dual-stacked using DHCPv6 for address assignment, so, you will need a router that is capable of DHCPv6. So far we have tested with the Cisco 837 & 877 (for which we have example configs), but if you think you can make it work, then you are welcome to try. We will be assigning a /56 prefix to each user, and it can either be static or dynamic, upto you :) Prerequisites; An xnet adsl account A capable router (see above) A willingness to provide feedback on how we can improve the service To sign up for the trial, have a look at http://wxnz.net/ipv6-trial/ Note: The helpdesk will not be supporting IPv6 at this stage in time, support will be via a forum setup on the wxnz.net site. Cheers, Callum Barr Network Engineer WorldxChange Communications Ltd @: cbarr(a)wxc.co.nz d: +64 9 950 1322 c: +64 27 567 2746

1 0

2/8 and 46/8 allocated to the RIPE NCC
by Leo Vegoda 20 Sep '09

20 Sep '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to the RIPE NCC in September 2009: 2/8 and 46/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. The IANA free pool contains 26 unallocated unicast IPv4 /8s. Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFKt6AdvBLymJnAzRwRAiscAKDaqyQYv8YLcXsg/tubUBe1THTNIACfQ0iP 23SVpODdlrWi0qEuEHVbi5c= =DVak -----END PGP SIGNATURE-----

1 0

Re: [nznog] NZNOG Digest, Vol 81, Issue 12
by Alan Maher 18 Sep '09

18 Sep '09

7 9

Re: [nznog] fx connection issues {was some digest}
by Tom 16 Sep '09

16 Sep '09

Seems they have been inundated with DoS attacks of late. See thread "DoS against TCL last night" Alan Maher wrote: > with Xtra, but it came (briefly), then died again. > Strange but true. > All else works just fine, which suggests something at their end > > Tom wrote: >> Loads ok here, on orcon. You with TCL? >> >> Alan Maher wrote: >>> My apologies for this (my first) post. >>> As a former Sys Admin, I retain an interest in this area >>> for purely personal & academic reasons. >>> After observing the post, I attempted to access http://www.fx.net.nz/ >>> and it timed out. >>> And is doing so again this evening. >>> Your thoughts? >>> All else is functioning fine. ( I run PClos linux on my desktop & use >>> Open DNS) >>> Alan Maher >>> >>> nznog-request(a)list.waikato.ac.nz wrote: >>>> Send NZNOG mailing list submissions to >>>> nznog(a)list.waikato.ac.nz >>>> >>>> To subscribe or unsubscribe via the World Wide Web, visit >>>> http://list.waikato.ac.nz/mailman/listinfo/nznog >>>> or, via email, send a message with subject or body 'help' to >>>> nznog-request(a)list.waikato.ac.nz >>>> >>>> You can reach the person managing the list at >>>> nznog-owner(a)list.waikato.ac.nz >>>> >>>> When replying, please edit your Subject line so it is more specific >>>> than "Re: Contents of NZNOG digest..." >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> Today's Topics: >>>> >>>> 1. Re: DoS against TCL last night (David Robb) >>>> 2. Re: DoS against TCL last night (Nathan Ward) >>>> 3. Re: DoS against TCL last night (Neil Fenemor) >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> Subject: >>>> Re: [nznog] DoS against TCL last night >>>> From: >>>> David Robb <ender(a)paradise.gen.nz> >>>> Date: >>>> Wed, 16 Sep 2009 15:54:06 +1200 >>>> To: >>>> nznog(a)list.waikato.ac.nz >>>> >>>> To: >>>> nznog(a)list.waikato.ac.nz >>>> >>>> >>>> On Mon, 14 Sep 2009 09:52:34 David Robb wrote: >>>> >>>>> Hi all, >>>>> >>>>> In case anyone noticed/was wondering why things were running a bit >>>>> slowly >>>>> through TCL last night, we were receiving somewhere >1Gbit of DoS >>>>> traffic >>>>> (mostly large TCP, random ports) across a couple of links which got >>>>> a bit >>>>> saturated. >>>>> >>>> >>>> And it's back again, even bigger this time. Filters are in place, >>>> but if anyone notices things being a little slow, this is probably why. >>>> >>>> --David >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> Subject: >>>> Re: [nznog] DoS against TCL last night >>>> From: >>>> Nathan Ward <nznog(a)daork.net> >>>> Date: >>>> Wed, 16 Sep 2009 16:07:46 +1200 >>>> To: >>>> nznog(a)list.waikato.ac.nz >>>> >>>> To: >>>> nznog(a)list.waikato.ac.nz >>>> >>>> >>>> On 16/09/2009, at 3:54 PM, David Robb wrote: >>>> >>>>> On Mon, 14 Sep 2009 09:52:34 David Robb wrote: >>>>>> Hi all, >>>>>> >>>>>> In case anyone noticed/was wondering why things were running a bit >>>>>> slowly >>>>>> through TCL last night, we were receiving somewhere >1Gbit of DoS >>>>>> traffic >>>>>> (mostly large TCP, random ports) across a couple of links which >>>>>> got a bit >>>>>> saturated. >>>>> >>>>> And it's back again, even bigger this time. Filters are in place, >>>>> but if >>>>> anyone notices things being a little slow, this is probably why. >>>> >>>> Appreciate the updates David - it's good to see people sharing this >>>> sort of stuff. >>>> >>>> -- >>>> Nathan Ward >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> Subject: >>>> Re: [nznog] DoS against TCL last night >>>> From: >>>> Neil Fenemor <neil(a)underground.geek.nz> >>>> Date: >>>> Wed, 16 Sep 2009 22:20:32 +1200 >>>> To: >>>> nznog(a)list.waikato.ac.nz >>>> >>>> To: >>>> nznog(a)list.waikato.ac.nz >>>> >>>> >>>> 2009/9/16 David Robb <ender(a)paradise.gen.nz >>>> <mailto:ender(a)paradise.gen.nz>> >>>> >>>> On Mon, 14 Sep 2009 09:52:34 David Robb wrote: >>>> > In case anyone noticed/was wondering why things were running a >>>> bit slowly >>>> > through TCL last night, we were receiving somewhere >1Gbit of >>>> DoS traffic >>>> > (mostly large TCP, random ports) across a couple of links which >>>> got a bit >>>> > saturated. >>>> >>>> And it's back again, even bigger this time. Filters are in place, >>>> but if >>>> anyone notices things being a little slow, this is probably why. >>>> >>>> >>>> Yeah, we've (FX Networks) been hit by a couple over the last few >>>> days. Tonights one was particularly bad. And I have heard of another >>>> couple of ISPs that have been targeted as well (well, customers >>>> thereof). >>>> Anyone else? Is this a bit of a trend starting? >>>> >>>> --David >>>> >>>> >>>> Cheers, >>>> >>>> neil >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> NZNOG mailing list >>>> NZNOG(a)list.waikato.ac.nz >>>> http://list.waikato.ac.nz/mailman/listinfo/nznog >>>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> NZNOG mailing list >>> NZNOG(a)list.waikato.ac.nz >>> http://list.waikato.ac.nz/mailman/listinfo/nznog >>

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Sep '09

16 Sep '09

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:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 110.34.48.0/22^22-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.62.245.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090917 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 120.138.16.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 110.34.48.0/22^22-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.62.245.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090917 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Sep '09

16 Sep '09

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:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 110.34.48.0/22^22-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090817 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 110.34.48.0/22^22-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.62.245.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090917 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Sep '09

16 Sep '09

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:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090826 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090917 source: NZRR ------------------------------------------------------------

1 0

DoS against TCL last night
by David Robb 15 Sep '09

15 Sep '09

Hi all, In case anyone noticed/was wondering why things were running a bit slowly through TCL last night, we were receiving somewhere >1Gbit of DoS traffic (mostly large TCP, random ports) across a couple of links which got a bit saturated. As soon as it was brought to the network team's attention, the target (a poor DSL customer, I don't think DSL supports 1Gbit yet!) was null routed. --David Robb

3 3

NEWS: Government broadband proposal announced
by Matthew Poole 15 Sep '09

15 Sep '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dark fibre features heavily, no government investment in fibre companies that have a shareholder that has retail telecomm's operations, and various other goodness. The central/local holding companies model will be followed. http://computerworld.co.nz/news.nsf/netw/B9DE9FBAF33A6A1ACC257632007699A6 Looks like a pretty good result, all things considered. - -- Matthew Poole "Don't use force. Get a bigger hammer." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkqwGvsACgkQTdEtTmUCdpwv4gCdHNIzzIu9V9MzR75nRXB4tFqc /m8AnR/eoIBosjEgY4FWaLUv3cRnW8Ls =WmUm -----END PGP SIGNATURE-----

1 0

IPv6 Deployment Monitoring Survey
by Elly Tawhai 14 Sep '09

14 Sep '09

Hi there! APNIC is now conducting our "IPv6 Deployment Monitoring Survey". It'd be great if you could spend about 15 minutes to complete the survey. The survey closes on 28 September 2009. Survey results will be presented at RIPE59 in October 2009. We will also publish the survey analysis and results as soon as they become available on the APNIC website. We also intend to present it at APNIC 29 in February 2010. Let's find out about the global status of IPv6 deployment! Please visit: http://www.surveymonkey.com/s.aspx?sm=YahORYFZHoqKo2Kc8R1R4Q_3d_3d Apologies if you have received more than one copy of this email. Thank you! Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ------------------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Sep '09

10 Sep '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090826 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090911 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Sep '09

10 Sep '09

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:AS23755 descr: advertised to AS9439 by Citylink - AS23755 members: 202.7.4.0/22^22-29, 202.8.44.208/28^28-29, 202.8.47.64/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dylan(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080804 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by StreamingNET - AS23755 members: 202.7.4.0/22^22-29, 192.33.14.0/24^24-29, 192.58.128.0/24^24-29, 202.8.44.208/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dylan(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090911 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Orcon Network Speeds
by andrew＠borg.co.nz 08 Sep '09

08 Sep '09

Neil: We have only seen this issue with out own link but are now getting reports from others stating they have been having similar issues for the past couple of months. Brett: Apparently we are really close to the cabinet, I am not sure but suspect it is the one about 150M down the road. Mode: G.DMT Type: Interleave Line Coding: Trellis On Status: No Defect Link Power State: L0 Downstream Upstream SNR Margin (dB): 14.4 12.0 Attenuation (dB): 4.0 3.0 Output Power (dBm): 7.8 11.9 Attainable Rate (Kbps): 9184 936 Rate (Kbps): 7616 768 K (number of bytes in DMT frame): 239 25 R (number of check bytes in RS code word): 16 16 S (RS code word size in DMT frame): 1 8 D (interleaver depth): 64 8 Delay (msec): 16 16 Super Frames: 105395061 105395059 Super Frame Errors: 2 110 RS Words: 2871896918 358987089 RS Correctable Errors: 764 170 RS Uncorrectable Errors: 28 N/A HEC Errors: 2 110 OCD Errors: 0 0 LCD Errors: 0 0 Total Cells: 2118506566 0 Data Cells: 862336822 0 Bit Errors: 0 0 Total ES: 1 0 Total SES: 0 0 Total UAS: 16 0

20 20

Re: [nznog] ADMIN: Re: Orcon Network Speeds
by Farhan Sattar 08 Sep '09

08 Sep '09

On 9/09/2009 10:37 a.m., Andy Linton wrote: > You're all clearly asking 'cat' to do things it wasn't designed for - > see: > > http://harmful.cat-v.org/cat-v/unix_prog_design.pdf Maybe we need a few pigeons among the cats...help reduce international bandwidth costs http://www.faqs.org/rfcs/rfc1149.html Farhan Sattar NZNet - business grade internet services Tel +64 9 280 4876 | Mobile +64 21 1266500 | Fax +64 9 914 0040 C1-5 Douglas Alexander Pde, Albany, PO Box 101-069 NSMC, Auckland, NZ Visit us at www.nznet.co.nz

1 0

Block of AS Numbers allocated to APNIC
by Leo Vegoda 07 Sep '09

07 Sep '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA AS Numbers registry has been updated to reflect the allocation of a block of AS Numbers to APNIC. 55296-56319 Assigned by APNIC whois.apnic.net 2009-09-02 The registry can be found at: http://www.iana.org/assignments/as-numbers/as-numbers.xml http://www.iana.org/assignments/as-numbers/as-numbers.xhtml http://www.iana.org/assignments/as-numbers/as-numbers.txt Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj4DBQFKpohJvBLymJnAzRwRAncHAJiRWENmmK+qwpvAZIaPrs/urIa/AJ9f1A05 PM9TJWxzbAxpSiXyIgzvfA== =MGZ2 -----END PGP SIGNATURE-----

1 0

Orcon Network Speeds
by andrew＠borg.co.nz 07 Sep '09

07 Sep '09

For the last 3 months or so we have been having issues with Orcon's DSL network and as Orcon have chosen not to bother communicating over this issue and ignoring requests to resolve this matter in a timely manner I would like to know if there are any others who are having similar issues or can throw some light on to what the problem may be. Firstly around 7PM most nights up until 10PM our DSL started dropping 50% of its packets and any extern web services became unusable. We were prompted by Orcon to reset our router and did so but the issue persisted. They then suggested it was the router so we replace this with a new one and still the problem persisted. Using the new router we were able to ping the Orcon DNS server but still getting the packet loss. Orcon then turned off Interleave and the problem was still not resolved however apparently the issue was handed up to Telecom and eventually after about 2 months there was an improvement and the packet loss seems to no longer be an issue. However during these times the speeds have dropped to a level where some services are almost unusable, we have a server on a fiber tail connected to APE and from the DSL speeds to that server and any adjacent server seem to drop out or are reduced to a point where they are unusable. We seem to also be having issues with VoIP service where as what appears to be a micro outage drops calls intermittently doe no reason and the same goes for some RDP sessions. We are nearing month 4 and the issue persists and there has been little communications from Orcon as to how the issue is to be resolved other than the comment that Internet service is not a guaranteed service. Any suggestions would be welcomed as I would like to resolve this one way or another. Regards Andrew Hooper.

3 2

Re: [nznog] Orcon Network Speeds
by andrew＠borg.co.nz 07 Sep '09

07 Sep '09

Thanks for the responses. Ticket numbers are as follows. FPI-934198 PDT-333835 BVP-710368 KGL-788789 I have not over the last few days to conduct some tests while the issue is visible however these are a couple from a few days ago as well as a previous one. (Attached at end of email) Changing providers is all fine and dandy BUT if the issue is with the scalability of the infrastructure or the owner of the infrastructure then this is not likely to resolve anything I believe that in this instance Telecom is the owner of the DSL infrastructure. AFAIK we are on the normal DSL network and not on the Orcon+ network Although I partly agree that this may not be the forum to bring such a matter to light the fact is that it is not a residential service it is a business service I pay for and use it as a management port to the rest of the network. Criggie: I am starting to get the feeling that DSL is really not a scalable solution. May just have to crawl back in my hole and stick with my wireless world. Tracing route to ***.***.***.177 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.254 2 1 ms 1 ms 1 ms 192.168.90.253 3 125 ms 50 ms 48 ms lo1.erx2.nct.orcon.net.nz [60.234.8.18] 4 47 ms 49 ms 79 ms 121.98.9.21 5 48 ms 49 ms 50 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13] 6 49 ms 49 ms 49 ms ge-0-3-0-0.cre1.sky.orcon.net.nz [121.98.9.10] 7 49 ms 50 ms 48 ms gigabit.fx1.ape.net.nz [192.203.154.115] 8 47 ms 49 ms 51 ms ***.***.***.177 Tracing route to ***.***.***.190 over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.254 2 <1 ms 1 ms <1 ms 192.168.90.253 3 47 ms 49 ms 50 ms lo1.erx2.nct.orcon.net.nz [60.234.8.18] 4 49 ms 50 ms 48 ms 121.98.9.21 5 49 ms 48 ms 52 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13] 6 49 ms 49 ms 49 ms ge-0-3-0-0.cre1.sky.orcon.net.nz [121.98.9.10] 7 143 ms 641 ms 600 ms gigabit.fx1.ape.net.nz [192.203.154.115] 8 53 ms 50 ms 49 ms bushwireless.fx.net.nz [131.203.253.78] 9 60 ms 54 ms 59 ms ***.***.***.190 Tracing route to ns1.orcon.net.nz [210.55.12.1]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.254 2 1 ms <1 ms 1 ms 192.168.90.253 3 62 ms * * lo1.erx2.nct.orcon.net.nz [60.234.8.18] 4 62 ms 60 ms * 121.98.9.21 5 * * * Request timed out. 6 62 ms 60 ms * ns1.orcon.net.nz [210.55.12.1] 7 62 ms 60 ms 59 ms ns1.orcon.net.nz [210.55.12.1] Pinging 210.55.12.1 with 32 bytes of data: Request timed out. Request timed out. Reply from 210.55.12.1: bytes=32 time=61ms TTL=59 Reply from 210.55.12.1: bytes=32 time=60ms TTL=59 Ping statistics for 210.55.12.1: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 60ms, Maximum = 61ms, Average = 60ms

2 1

NZRR Route Registry Update
by NZRR Database Notifications 03 Sep '09

03 Sep '09

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:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090408 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 124.150.160.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090904 source: NZRR ------------------------------------------------------------

1 0

The New Zealand Network Operators' Group
by Donald Neal 03 Sep '09

03 Sep '09

The New Zealand Network Operators' Group The NZNOG mailing list exists to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. The NZNOG Trust is registered as a charitable entity under the Charities Act. The trust exists to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. Other than the trustees, the NZNOG does not have a formal membership. Conference NZNOG holds New Zealand's only annual technical networking conference. The next conference is scheduled to be held on 27-29 January 2010 in Hamilton, hosted by The University of Waikato's WAND research group. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has around 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of APN Online, Citylink, and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

Re: [nznog] NZ prefix list
by Richard Hulse 02 Sep '09

02 Sep '09

>>> Matthew Moyle-Croft <mmc(a)internode.com.au> 3/09/2009 15:36:41 >>> > We'll be rich. > (Don't fall into the mistake of taking me seriously here). Someone will... Time for beer.

1 0

NZ prefix list
by Donald Gordon 02 Sep '09

02 Sep '09

Hi I'm in need of a view of what IP prefixes are local to NZ (ideally, what FX considers domestic, but I'm not too picky) for a personal project. My upstream can't provide me with a BGP feed, alas. Is there anyone here who could provide me with a multihop BGP view of their domestic routing table, or a looking glass I could screen-scrape? thanks (and beer?) in advance donald

6 6

FWD: Programme for IEEE NZ Wireless Workshop 2009 - Friday 4 September
by Clark Mills 01 Sep '09

01 Sep '09

Hi all. Forwarded message FYI. Might be of interest to someone out there. Kind regards... Clark ===================================================== *Subject:* Programme for IEEE NZ Wireless Workshop 2009 - (4 September) Dear colleagues This is a reminder that the *2009 IEEE New Zealand Wireless Workshop* is to be held 9:30am - 5pm, Friday, 4 September, 2009 Conference Centre Auditorium The University of Auckland 24 Symonds Street Auckland Registration: None (This is a free-of-charge event) *The programme for the Wireless Workshop is now on-line at: *http://www.ece.auckland.ac.nz/~pgrad/ieeenzwws.pdf <http://www.ece.auckland.ac.nz/%7Epgrad/ieeenzwws.pdf> The Conference Centre Auditorium on Symonds Street is physically connected to the Engineering School on Level 4 (street level). Car parking is available (for a fee) in a large university public access carpark under the huge new Business School on Grafton Road, near the intersection with Symonds Street). http://www.auckland.ac.nz/uoa/home/tm-visitor-parking There is also pay-and-display parking on the surrounding streets (but not on Symonds Street). Attached is a City Campus map showing the locations of the Conference Centre and the public parking building. Thank you to those who have already indicated your attendance (or otherwise). Planning was assisted by your responses. Please note that there is no requirement to register for this event. You are welcome to attend as much, or as little, of the day as suits you. IEEE membership is not a requirement. Best regards Kevin Sowerby IEEE ComSoc NZ Chapter

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '09

31 Aug '09

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:AS9245 descr: advertised to AS9560 by COMPASS NZ - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 120.136.0.0/21^21-29, 123.108.144.0/21^21-29, 202.174.6.0/23^23-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080702 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9245 descr: advertised to AS9560 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 202.174.6.0/23^23-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.198.0/24^24-29, 202.37.234.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: antonio.pavletich(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090901 source: NZRR ------------------------------------------------------------

1 0

[AusNOG] Future IPv6 allocation policies
by Andy Linton 28 Aug '09

28 Aug '09

Hi All, I thought I would post to the list and highlight something that I think you will find important regarding IPv6 future deployment. This week at the APNIC Open Policy Meeting in Beijing (which concluded yesterday) the policy proposal "prop-073-v004: Simplifying allocation/ assignment of IPv6 to APNIC members with existing IPv4 addresses" reached consensus in both the policy SIG (Special Interest Group) and the APNIC Member Meeting. Provided this proposal makes it through the 8 week comment period with consensus intact and the APNIC Executive Council deems the proposal has reached community consensus it will be endorsed, this policy change means: * Any APNIC member organisation that has IPv4, requires no further justification to receive IPv6. - A member that has an IPv4 allocation would be eligible for an IPv6 /32 - A member that has an IPv4 assignment would be eligible for an IPv6 /48 * The APNIC secretariat is directed to implement a simple online request for IPv6 resources under this policy * The policy proposal authors recommend that the APNIC Secretariat communicate to members and others that the criteria for receiving an initial IPv6 block has been reduced and that the process of obtaining IPv6 address space has been made simpler to show that there is no effective barrier to members obtaining IPv6 addresses. Details can be found here: http://www.apnic.net/policy/proposals/prop-073 I'm sure we all recognise that there are many barriers and issues on the road to IPv6 deployment, this policy proposal makes that first step, of getting IPv6 address space, as easy as possible especially in the APNIC region. Cheers, Andy (Prop-073 Co-Author)

1 0

APNIC 28 meeting report
by Srinivas (Sunny) Chendi 27 Aug '09

27 Aug '09

________________________________________________________________________ APNIC 28 25-28 August 2009, Beijing, China ________________________________________________________________________ Thank you to everyone who contributed to APNIC 28. The preliminary event participation statistics are: Total number of delegates 272 Delegates at APNIC Member Meeting: 101 Economies represented: 25 APNIC member organizations represented: 51 APNIC held remote participation events via video conference in Kuala Lumpur, Malaysia and Dhaka, Bangaladesh. Attendance figures for these events were: Kuala Lumpur, Malaysia 12 Dhaka, Bangaladesh 86 (TBC) Web-based online participation options included a choice of video, audio and text chat. Participation figures for online remote delegates based on unique IP address were: Online remote participation feeds 288 To read, watch or listen to archives from the meeting, go to: http://meetings.apnic.net/28 Elections --------- During the APNIC Member Meeting (AMM) in Beijing on Friday, 28 August 2009, the following candidate was elected to the NRO NC. - Dr Kenny Huang Elections were held for NIR SIG Chair positions NIR SIG Chair - Izumi Okutani NIR SIG Co-chair - Wei Zhao An election was held for Policy SIG Co-Chair Policy SIG Co-chair - Terence Zhang Congratulations to the successful candidates: Election details are available at: http://meetings.apnic.net/28/elections Meeting decisions ----------------- Policy SIG Seven policy proposals were discussed. The following proposals reached consensus: prop-050: IPv4 address transfers prop-073: Simplifying allocation/assignment of IPv6 to APNIC members with existing IPv4 addresses prop-074: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries prop-075: Ensuring efficient use of historical AS numbers The following proposal was returned to the mailing list for further discussion: prop-076: Requiring aggregation for IPv6 subsequent allocations The following proposals were returned to their authors for further consideration: prop-077: Proposal to supplement transfer policy of historical IPv4 addresses prop-078: Reserving /10 IPv4 address space to facilitate IPv6 deployment http://www.apnic.net/policy/proposals MoU Signed ----------- APNIC signed a Memorandum of Understanding with the following organization: CNNIC (China Internet Network Information Center) Meeting sponsors ---------------- APNIC offers its deepest thanks to the sponsors of APNIC 28, whose invaluable contributions allowed APNIC to offer a meeting program of a very high standard: http://meetings.apnic.net/28/sponsorship Upcoming APNIC meetings ----------------------- APNIC 29 1-5 March 2010 Kuala Lumpur, Malaysia (with APRICOT 2010) http://meetings.apnic.net/29 APNIC 30 Four Seasons Hotel, Bangkok 23-27 August 2010 Bangkok, Thailand Thanks Sunny -- -------------------------------------------------------------------- Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3189/99 ____________________________________________________________________

1 0

Report on APNIC 28 policy proposals
by Elly Tawhai 27 Aug '09

27 Aug '09

Hi NZNOG Community, Below is a summary report of the status of policy proposals following discussion at APNIC 28. The following proposals reached consensus: prop-050: IPv4 address transfers prop-073: Simplifying allocation/assignment of IPv6 to APNIC members with existing IPv4 addresses prop-074: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries prop-075: Ensuring efficient use of historical AS numbers The following proposal was returned to mailing list for further discussion: prop-076: Requiring aggregation for IPv6 subsequent allocations The following proposals were returned to their authors for further consideration: prop-077: Proposal to supplement transfer policy of historical IPv4 addresses prop-078: Reserving /10 IPv4 address space to facilitate IPv6 deployment Next steps ---------- 1. Proposals that reached consensus will be returned to the Policy SIG mailing list for an eight-week comment period. 2. If no substantial objections are received during the final comment period, the proposals are deemed to have reached consensus at each stage of the policy development process. At this point, the SIG Chairs forward the proposals to the APNIC Executive Council (EC) for endorsement. 3. If the APNIC EC endorses the proposals, the APNIC Secretariat begins work on implementation of the proposals. Implementation usually takes a minimum of three months, but may take more depending on the implementation complexity. For more information on the proposals, please see: http://www.apnic.net/policy/proposals For more information on the APNIC policy development process, see: http://www.apnic.net/community/policy/process Kind regards, Elly APNIC

1 0

NZRR Route Registry Update
by NZRR Database Notifications 27 Aug '09

27 Aug '09

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:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.60.128.0/17^17-29, 112.141.0.0/18^18-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.208.64.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 122.129.128.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.201.128.0/19^19-29, 112.141.96.0/20^20-29, 113.20.0.0/20^20-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 117.55.224.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.68.160.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.93.160.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 112.141.112.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.102.96.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.213.160.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 202.4.232.0/21^21-29, 202.46.136.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.169.16.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.170.8.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 116.90.72.0/22^22-29, 119.15.96.0/22^22-29, 119.63.208.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 110.76.128.0/23^23-29, 114.111.130.0/23^23-29, 114.111.142.0/23^23-29, 114.141.108.0/23^23-29, 115.42.0.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 118.107.60.0/23^23-29, 119.161.80.0/23^23-29, 119.161.84.0/23^23-29, 121.127.196.0/23^23-29, 122.100.0.0/23^23-29, 122.100.10.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.14.248.0/23^23-29, 202.21.136.0/23^23-29, 202.45.152.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.220.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.10.76.0/23^23-29, 203.16.60.0/23^23-29, 203.17.112.0/23^23-29, 203.18.102.0/23^23-29, 203.21.76.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.30.98.0/23^23-29, 203.32.86.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.120.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.60.4.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 220.157.74.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 115.42.5.0/24^24-29, 115.42.6.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.235.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.93.0/24^24-29, 119.161.94.0/24^24-29, 121.127.198.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.136.0/24^24-29, 141.243.60.0/24^24-29, 168.134.2.0/24^24-29, 192.65.182.0/24^24-29, 192.88.85.0/24^24-29, 192.102.239.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.124.13.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 198.22.61.0/24^24-29, 202.0.151.0/24^24-29, 202.6.91.0/24^24-29, 202.14.63.0/24^24-29, 202.14.247.0/24^24-29, 202.14.250.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090623 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus - AS4826 members: 118.92.0.0/15^15-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 141.243.0.0/16^16-29, 147.209.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 113.203.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 112.141.0.0/18^18-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 203.208.64.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 113.192.0.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 122.129.128.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.254.64.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 210.56.224.0/19^19-29, 111.67.0.0/20^20-29, 112.109.64.0/20^20-29, 112.141.96.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 117.55.224.0/20^20-29, 119.10.128.0/20^20-29, 119.47.112.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 125.254.96.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.86.96.0/20^20-29, 202.93.160.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 110.44.24.0/21^21-29, 112.109.80.0/21^21-29, 112.141.112.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.200.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.102.96.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 124.248.136.0/21^21-29, 125.213.160.0/21^21-29, 180.92.192.0/21^21-29, 180.94.232.0/21^21-29, 202.4.232.0/21^21-29, 202.27.192.0/21^21-29, 202.36.16.0/21^21-29, 202.46.136.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.169.16.0/21^21-29, 202.169.208.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.170.8.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 111.118.208.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 114.141.104.0/22^22-29, 116.90.72.0/22^22-29, 119.15.96.0/22^22-29, 119.63.208.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 124.248.132.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.27.200.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.130.32.0/22^22-29, 202.153.64.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.216.0/22^22-29, 202.177.220.0/22^22-29, 203.0.124.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.60.4.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.147.92.0/22^22-29, 203.161.128.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.211.56.0/22^22-29, 203.217.152.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 110.76.128.0/23^23-29, 114.111.144.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 116.90.138.0/23^23-29, 118.107.60.0/23^23-29, 119.161.80.0/23^23-29, 119.161.84.0/23^23-29, 119.161.92.0/23^23-29, 121.127.196.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 123.255.222.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.14.248.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.49.164.0/23^23-29, 202.56.62.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.206.0/23^23-29, 202.169.220.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.10.76.0/23^23-29, 203.16.60.0/23^23-29, 203.17.112.0/23^23-29, 203.18.102.0/23^23-29, 203.21.76.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.30.98.0/23^23-29, 203.32.86.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.34.140.0/23^23-29, 203.55.120.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.56.218.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.87.34.0/23^23-29, 220.157.74.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 111.125.160.0/24^24-29, 113.197.64.0/24^24-29, 113.212.98.0/24^24-29, 115.42.0.0/24^24-29, 115.42.5.0/24^24-29, 115.42.6.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.136.0/24^24-29, 116.90.140.0/24^24-29, 117.18.235.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.94.0/24^24-29, 121.127.198.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 168.134.2.0/24^24-29, 192.65.182.0/24^24-29, 192.88.85.0/24^24-29, 192.102.239.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.124.13.0/24^24-29, 192.133.31.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090828 source: NZRR ------------------------------------------------------------

1 0

Remote participation in APNIC 28
by Elly Tawhai 26 Aug '09

26 Aug '09

Hi NZNOG Community, You may be aware that APNIC 28 is currently taking place, and the Policy SIG has started. Don't forget you can participate remotely in discussions, ask the presenter questions, and voice your opinion. For more information on webcast, Jabber chat, and live transcript services please see: http://meetings.apnic.net/28 Some of the policy proposals up for discussion this time are: * prop-050: IPv4 address transfers * prop-073: Automatic allocation/assignment of IPv6 * prop-074: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries * prop-075: Ensuring efficient use of historical AS number * prop-076: Requiring the aggregation of IPv6 subsequent allocations * prop-077: Proposal to supplement transfer policy of historical IPv4 addresses * prop-078: Reserving /10 IPv4 address space to facilitate IPv6 deployment Kind regards, Elly APNIC

1 0

Email losses to Xtra and Actrix
by Phonenet 26 Aug '09

26 Aug '09

Wondering if anyone else has noted this... Had several enquiries over the last 5 days from subscribers who are receiving questions re why they have not replied to emails. Initial email replies are sent from local domains, follow ups have been sent from alternative Ihug and Paradise addresses, all are to do with TradeMe sales/purchases. Subscribers report no bounces yet emails do not appear to be getting to the destination inbox (and are not appearing in the spam/junk mailbox for the recipient). Responses off list might be most appropriate... Ian Cousins

2 1

NZRR Route Registry Update
by NZRR Database Notifications 25 Aug '09

25 Aug '09

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:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090817 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090826 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 25 Aug '09

25 Aug '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090817 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090826 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Aug '09

23 Aug '09

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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090824 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Aug '09

23 Aug '09

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090806 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090824 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Aug '09

23 Aug '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090806 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090824 source: NZRR ------------------------------------------------------------

1 0

Linux.conf.au 2010 Sysadmin Miniconf : Call for Presentations
by Simon Lyall 21 Aug '09

21 Aug '09

CFP: LCA 2010 Systems Administration Miniconf As part of the linux.conf.au conference in Wellington, New Zealand in January 2010 we will be holding a 1 day mini conference orientated to Linux Systems Administration. Please see our website at http://sysadmin.miniconf.org/ for details. The organisers of the Systems Administration Miniconf would like to invite proposals for presentations to be delivered at the Miniconf. Presentation Topics =================== Topics for presentations could include (but are not limited to) Systems Administration, Backups, Security, Troubleshooting, Buying Decisions, Virtualisation, Enterprise Monitoring and Management, Identity Management, Web and Email management, Wiki, Clustering and High Availability, Log Management, Spam and Virus Filtering, VOIP, Ticketing systems, Bootstrapping and automated installation, Configuration Management and packaging. We strongly welcome topics on best practice, new developments in systems administration and cutting edge techniques to better manage Linux hosts and environments. Presentations should be of a technical nature and speakers should assume that members of the audience have at least a couple of years experience in Unix/Linux administration. Format of Presentations ======================= We are now seeking proposals for presentations at the mini-conference. We have openings for: - 45 minute double-length presentations - 20 minute full presentations - 10-15 minute "How we do things" presentations - 5-10 minute "lightning talks" Please note, due to the single day available, we expect the vast majority of available timeslots to be 25 minutes long or less. The 10-15 minute "How we do things" presentations are intended for people to talk about their sites. Information could include: Servers, talks, tools, people and roles, experiences, software, operating systems, monitoring, alerting, provisioning etc. The intent is to give other attendees a picture of what is happening in the "real world" and some understanding of how other sites work. Submitting talks ================ Please note that in order to give a presentation or attend the miniconf you must be signed up for the main linux.conf.au conference. Presenting at the Miniconf does not entitle you to discounted or free registration at the main conference nor priority with registration. Unfortunately the Miniconf has no budget for sponsorship of speakers (but welcomes offers of sponsorship). Please see the Call for Presentations web page at: http://sysadmin.miniconf.org/cfp10.html the site contains the information required for submissions. Submissions should be made via: http://sysadmin.miniconf.org/proposal10.html Questions should be sent to: lca10 @ sysadmin.miniconf.org. Dates and Deadlines =================== To encourage early submissions priority ( both of inclusion and scheduling ) will be given to presentations submitted before the 7th of September. 2009-09-07 - Deadline for early submissions 2009-09-21 - Deadline for submissions 2009-10-01 - Final programme confirmation. 2010-01-18 - Start of conference. Contact and Questions ===================== Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf and presenting at it. If you have any questions please feel free to email the organisers at: lca10 @ sysadmin.miniconf.org

1 0

Re: [nznog] Problem with Telstra DNS
by Richard Hulse 20 Aug '09

20 Aug '09

Hi Mauricio, In some cases yes, it appears. And yes we are hosting with ICONZ, but no we are not using a CDN. cheers Richard >>> "Mauricio Freitas" <freitasm(a)geekzone.co.nz> 21/08/2009 12:47:34 >>> Are the people complaining about it using a third party DNS (OpenDNS for example)? Are you hosting with ICONZ? Or are you using a CDN? Mauricio Freitas http://www.geekzone.co.nz http://www.geekzone.co.nz/freitasm http://www.twitter.com/freitasm -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Richard Hulse Sent: Friday, 21 August 2009 12:36 p.m. To: nznog <nznog(a)list.waikato.ac.nz Subject: [nznog] Problem with Telstra DNS We are serving some of our static web content off a different domain to main site - static.radionz.net.nz. The main site is at www.radionz.co.nz Some TelstraClear customers cannot access this address at all, meaning they don't get any images or style sheets. We have two complaints from businesses now as well as a few residential complaints. Doing a dig on my own Paradise/Telstra cable connection at home returns the correct information. I am asking this on the list because the Telstra help desk would not accept the fault because we do not have a residential account that has the fault. Can people with TCL connections please send me a dig (off list) It'd be great if someone from Telstra could also contact me. regards, Richard Hulse _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] Problem with Telstra DNS - an update
by Richard Hulse 20 Aug '09

20 Aug '09

Thanks for all the digs. The problem has now been traced to random time-outs on the seconday DNS server at freeparking. They are looking into it. Odd that it should affect only some people on one ISP. cheers, Richard

1 0

Problem with Telstra DNS
by Richard Hulse 20 Aug '09

20 Aug '09

We are serving some of our static web content off a different domain to main site - static.radionz.net.nz. The main site is at www.radionz.co.nz Some TelstraClear customers cannot access this address at all, meaning they don't get any images or style sheets. We have two complaints from businesses now as well as a few residential complaints. Doing a dig on my own Paradise/Telstra cable connection at home returns the correct information. I am asking this on the list because the Telstra help desk would not accept the fault because we do not have a residential account that has the fault. Can people with TCL connections please send me a dig (off list) It'd be great if someone from Telstra could also contact me. regards, Richard Hulse

2 1

NZNOG 2010 Conference announcement and the NZNOG Trust / org team
by Dave Mill 19 Aug '09

19 Aug '09

Hi all First of all, the important stuff... We're proud to announce that we're holding our 2010 conference at Waikato University, Hamilton hosted by the WAND group. The conference tutorial day will be held on Wednesday 27 January and the main conference will be held from Thursday 28 January to Friday 29 January. NZNOG 2010 : Jan 27 - Jan 29 Hamilton, New Zealand We're currently working on having an additional co-host who will provide some other useful services. In the near future we should have a CFP and further announcements regarding the conference. Expect conference fees to be similar to last year with slightly cheaper accommodation. Read on for some more information regarding how NZNOG conferences ran/run... I'm a very infrequent poster to the main NZNOG list, but as many of you know I've been fairly involved in the running of the NZNOG conferences for the past 4 years. Our conferences have always been successful, if anything too successful. NZNOG has ended up with some assets, which is a bit of a problem for an organisation that doesn't actually exist. The decision was made to establish an entity that holds NZNOG assets and makes sure that a conference happens regularly. At any time in the past, our various hosts could have walked away with a reasonable amount of money, or could have made a financial loss. What we have done is to create a structure to stop that potential disaster from happening anytime in the foreseeable future. With some generous support and legal assistance from InternetNZ we deemed that forming a Trust seemed right for our various reasons. We then briefly ran this by the attendees of NZNOG 09 on Friday afternoon. There were no serious objections raised so it has been done. So, we now have a NZNOG Trust. The initial Trustees are: Joe Abley Donald Neal Andy Linton We have collectively selected trustees that are well established and trusted in the NZNOG community but aren't the actual "do-ers" when it comes to the conferences. Their role is that of oversight. If you want any further official information on this trust then I'm sure many of you are capable of finding this online. Then each year the NZNOG Trust will appoint the org team to actually run the conference. This year an eight man team has been appointed. The org team was somewhat unilaterally selected in consultation with the Trustees based on the core of previous years to allow for a smooth transition into the new structure. From next year onwards a call for volunteers will go out before selection with the intention of much wider participation. As always, there will be additional help required closer to the conference. The NZNOG 10 org team is: Dave Mill Dean Pemberton Sam Sargeant Gerard Creamer Alastair Johnson Neil Fenemor Jonny Martin Richard Nelson - representing WAND The Trust oversees the budget, whilst the org team have the delegated authority to spend the Trust's money and to ensure that the conference happens and is well run. I hope all of this makes sense and that people agree that what we've done is a move in the right direction for the NZNOG community. I'm happy to answer questions off-list, or will answer questions on-list if I believe they're appropriate for an on-list reply. Cheers Dave For the NZNOG10 Org Team

1 0

ESP based Denial of Service
by Philip D'Ath 18 Aug '09

18 Aug '09

This is a bit of a long shot, but is anyone in NZ observing an attempted DOS attack using ESP traffic (in particular IP protocol 50)?

3 2

NZRR Route Registry Update
by NZRR Database Notifications 17 Aug '09

17 Aug '09

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:AS45459 descr: advertised to AS9560 by Web Drive Limited - AS45459 members: 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29, 123.100.98.48/28^28-29, 123.100.98.160/28^28-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)webhost.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090729 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS45459 descr: advertised to AS9560 by Web Drive Limited - AS45459 members: 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-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)webhost.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090818 source: NZRR ------------------------------------------------------------

1 0

BoF for APNIC 28 in Beijing - IPv6 Promotion
by Skeeve Stevens 16 Aug '09

16 Aug '09

Greeting all that will be attending APNIC 28 in Beijing, While we are in China at APNIC 28, and as per the spirit of 1.3 of http://www.apnic.net/__data/assets/pdf_file/0012/3117/sig-guidelines.pdf I am proposing that we hold a BoF for the purpose of seeing if there are enough interested parties to get together to discuss the issue of IPv6 promotion in the APNIC region with the 'maybe' end of it becoming a SIG. I am asking for some leeway in this request as this region is a complex one with a very broad range of cultural differences and language barriers that that don't always translate across the entire membership. For example, the way we might want to accomplish something in Australia could be very different to the way it would be done in say Japan, China or India. IPv6 promotion is something that APNIC has been doing for quite a while now, with some degree of success. But given the timeframes in which we have till things get very painful for many organisations, I do not believe that APNIC has sufficient resources (whether that be man-power, financial, etc) to effectively promote it across all the economic communities that it represents. I would like the hold a BoF to gauge the interest on how members themselves can be more involved in their region, what they would/could be prepared to do, and to discuss the challenges that we are having, developing new ideas and focusing on specific ways to promote IPv6 - without all the technical mumbo-jumbo. I am suggesting a much less technical perspective needs to take shape. I realise that a very large percentage of us are technical people, but there are many business minded people who I am sure have many great ideas... and if there isn't that many... let's get them involved somehow. Many members in the APNIC region have their own NIR (JPNIC, CNNIC, etc) to assist in these kinds of matters (I assume), but in Australia and NZ specifically speaking for my area of focus, we deal directly with APNIC... so I don't know how appropriate having people who deal with their NIR directly on these matters, but the more the merrier. There is no suggestion in this proposal that the many people who talk at conferences about IPv6, or APNIC themselves have not done a good job... My suggestion is that we can do more, and time is of the essence. I am inspired to bring this about by my own passion regarding IPv6 adoption, and I am willing to put (and already have put) the resources and passion of me and my company behind efforts to help finding new ways to foster IPv6 adoption in this region. There seems to be an issue of room availability at APNIC28, but if I have to put up some $$ myself and we go take over the local McDonalds, I am willing to do so to try and help make this BoF happen. I think timing is important... and I think now is the time we need to start discussing these things. Big machines like APNIC move rather slowly, and I am willing to try to do what it takes to try and push things along. So, if you're going to be in Beijing, and you really are passionate about IPv6 adoption, please come and see me - the big bald aussie-guy - and let's get something happening. I will be looking at the schedule to see where we can fit a couple of hours to chat. Also, you might be approached by myself or others who are also interested in making this happen. All I can ask is to please be involved, and DO - rather than talk about it. -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Aug '09

16 Aug '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090724 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090817 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Aug '09

16 Aug '09

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:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090724 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090817 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Aug '09

16 Aug '09

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:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090721 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 110.34.48.0/22^22-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090817 source: NZRR ------------------------------------------------------------

1 0

Telstraclear international proxy?
by Jethro Carr 13 Aug '09

13 Aug '09

hi all, I am seeing an unusual problem with accessing international sites which I believe is being caused by a proxy on international HTTP access for Telstraclear cable internet users. I was attempting to setup virtualhosts on a new webserver (US based) and added entries to /etc/hosts in order to test the sites before I updated the DNS records. However, any access attempt to the new server on port 80 would just return the current production site, which was running on a different server (also in the US). Confirmed with tcpdump that my packets were leaving my computer for the correct IP. There is no proxy in place on my network. I believe there is some kind of proxy/cache for international traffic from Telstraclear's cable network. The proxy is set up in such a way, it ignores the destination IP address being requested and instead takes the requested hostname, resolves it via DNS and fetches the page from the resolved server IP. DEMONSTRATION If I take an international IP and use it for my browser's proxy settings, I find that I can use that IP as a proxy to access any other international website (but not domestic). eg: 74.125.67.100 (google.com) 212.58.254.252 (bbc.com) Using either IP as a proxy will allow me to reach any other international site, but will not allow access to domestic sites (returns blank page). ASSISTANCE Has anyone seen this problem before or know of any caching being taken place by Telstraclear? Would also be good to know if it's specific to Telstraclear cable customers, or other Telstraclear customers as well. Any advice on how I might be able to query the proxy to identify it's owner would be appreciated. thanks, jethro -- Jethro Carr www.jethrocarr.com/index.php?cms=blog www.amberdms.com

11 16

What is more important? - ipv4 vs. routing table size
by Skeeve Stevens 13 Aug '09

13 Aug '09

Hey all, I'd like to stimulate some discussion regarding IPv4 conservation vs. The size of the routing table. I'd like to hear what people think is more important - and why - which it is more important - or a miz? IPv4 conservation - possibly allocating smaller default allocations - or making it easier (/24, /23) vs. The size or the routing table. If by a more conservative allocation above was done, and the world table jumped to 400, 500 thousands or more routes - what implications would this have on routers and so on. APNIC's minimum is a /22 (was a /19 in 2000) (4 * /24's) ARIN is a /20 to ISPs (16 * /24's) RIPE is a /21 (8 * /24's) LANIC is a /21 (I think) AFRINIC is a /22 (4 * /24's) There are smaller hosting companies out there (here in ANZ at least) that want to be on, hosting, multi-homed, but only need a /24 or /23, but they're given the minimum allocation on a /22 - whether they need it or not. Thoughts? -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

5 5

KIWICON ]|[ - 2009 - Call For Papers
by Kiwicon <3 12 Aug '09

12 Aug '09

A wise deadite captain once yelled "Cry Havoc and let loose the Dogs of War!". Quite frankly, we couldn't have said it better ourselves: ~~ ~~ || || @@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@\___ @@@@@@@@@@@@@@@@@@ \ @@@@@@@@@@@@@@@@@ X___/ \/ KIWICON ]|[ 28TH & 29TH NOVEMBER 2009 With a current record of three arrests, seven conceptions and one committal Kiwicon is back for 2k9. The time has come to fake up an abstract and submit it to the Kiwicon Crue for judgement. In the coming months, we predict you will spend more time dreaming of kudos and UID 0 than actually working on your slides, since you'll be doing them the night before anyway. It's not New Zealand's only security conference, but it is the one where you're more likely to get a standing ovation for scanning an entire country than pointed questions regarding whether you were, perhaps, a little reckless in accessing systems without authorisation. _ _-(")- `%%%%% `KIWICON` // \\ The Crue holds a special place in their bowels for those who are aggravated that Kiwicon is held on a weekend so they don't get time off work. It is a gathering for those who are passionate about security. It has been hacked together by the .nz security scene for the .nz security community. Following in the tradition of previous cons, the atmosphere is extremely laid back; even the feds don't wear suits. Kiwicon is about sharing information. It's about intersections and cross-pollination and dissemination and other nouns disturbing reminiscent of a pre-AIDs key party. Sure, you could bring your RFID readers, your lockpicks or even your back track DVD but mostly you just need to bring yourself and the willingness to learn. For a little con down under we don't do too bad. Previously, Kiwicon has featured: the Crackstation, iKat (last seen at a airport near you), layer two telco shenanigans, a video montage of boardrooms across Japan, old school phreaking on new school kit, exposure of RIM's failure to hide their snooping capabilities, fun with the SCADA systems, making Microsoft look like turkeys, nuking various heap protections from space, and of course fucking up the certificate chain of your new passport. _ _-(")- `%%%%% // \\ `THE VENUE` The Crue is aware that location is everything, so once again we will be invading the Pipitea Campus which is surrounded by prestigious Wellington buildings such as Parliament house, the (partly renovated and badly secured) High Court, Ministry of Defence and various telecommunication hubs. All services are handy to the venue as well (train station, taxi rank, burger caravan, police cells / court etc). Caffeination will be provided by the lovely folks at Sweet Fanny-Anne's. _ _-(")- `%%%%% // \\ `THE PRICE` A recession-proof fifty bucks for the employed. Students and those otherwise supported by our precious taxpayer dollars (this does not include Members of Parliament) will pay $30. GST receipts will be available on request. The Crue will endeavour to leverage its synergies to architect a compelling ROI solution. _ _-(")- `%%%%% // \\ `THE TOPICS` Social networking/automated stalking, Cellular Networks (GSM,2degrees, openbts), State-sponsored surveillance, Malware (Viruses, Botnets), The Scam of EAL Certification, Industrial Espionage, Reverse Engineering, The Failwhale Rider, Virtualisation, Flash mobs, WebApps, 0hday The schedule will be made up as we go, so fifteen minutes or thirty minutes worth of material should be submitted as fifteen or thirty minutes worth of talk. We do place an upper limit of an hour (including questions), as anything longer than that can continue at the pub. _ _-(")- `%%%%% // \\ `SUBMISSIONS` These need to be in by the Witching Hour of the 31st October (NZST). Expats and wanna-be Kiwis will want to get their submissions in by 10th October, when we're going to be announcing the first round of Interesting Stuff. To submit a presentation to Kiwicon2k9, send an email to cfp(a)kiwicon.org with the following information: * Name or Handle: * Country of Residence: * Employer (if applicable): * Presentation Title: * Presentation Length: * Presentation Synopsis: * Brief Bio: If you do not provide a bio, one will be provided for you. _ _-(")- `%%%%% // \\ `BOTTOM LINE` The Crue want you to submit your talk to Kiwicon or the cute little header sheep gets it. _ -(")- `%%%%% // \\ `CONTACT` Email us: kiwicon(a)kiwicon.org Check the site: https://www.kiwicon.org/ Drop by silc: silc.kiwicon.org:2706/kiwicon Join the list: hackers-subscribe(a)kiwicon.org CFP online at https://kiwicon.org/cfp2k9.txt

1 0

Cable cuts in Asia
by Juha Saarinen 12 Aug '09

12 Aug '09

Reading in Commsday and Computerworld Singapore that APCN2, APCN, EAC and SMW3 near Taiwan have developed faults, possibly due to typhoon Morakot. Anyone in NZ noticing the effect of that? -- Juha

2 1

175/8 and 182/8 allocated to APNIC
by Leo Vegoda 11 Aug '09

11 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in August 2009: 175/8 and 182/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFKguZyvBLymJnAzRwRAmDCAKCCnxLNmk32v+sm786x5RyVLnLBDACcCu5I zCs7FdAdkIZRnfNtuVyVB0s= =6huK -----END PGP SIGNATURE-----

1 0

Re: [nznog] Telecom International HTTP Caching
by Paul Tinson 11 Aug '09

11 Aug '09

As a general rule if the content is in a page that gets retrieved by the cache it will be cached and served from the cache to subsequent requests. This includes mp3 files if they are an embedded object. If the mp3 is a single file then I would not expect it to be cached in parts, so it should not be missing pieces. If it's a streaming mp3 that may be different and if you supply an example URL I can check this. If you don't want it cached or want to control the time we keep it in cache then you can use cache control directives and expiry meta tags in the page. At this point in time we have not enabled caching of streaming media. If you have a specific example URL please send it to me and I can double check though. If we have cached it I will look into why. I am happy to look into specific examples of issues, but if you have a wider service effecting issues please continue to use the helpdesk as this will result in calls being handled correctly and not left unattended on the list. Hope this answers your questions. Regards Paul -----Original Message----- From: Richard Hulse [mailto:Richard.Hulse(a)radionz.co.nz] Sent: Wednesday, 12 August 2009 9:00 a.m. To: nznog; Paul Tinson Subject: Re: [nznog] Telecom International HTTP Caching Hi Paul, I'll ask this on the list, as there are quite a few (other) audio and video content providers here... How will the cache handle MP3s that are served via HTTP? Is this content you want to cache? Should we be setting some sort of header to make it work better? Willl you also be caching on-demand Windows Media content? I ask because I have noticed that some of our visitors complain of Mp3 audio that is truncated or has bits missing out of the middle. It seems to clear itself after a few hours. cheers, Richard Hulse Webmaster Radio NZ

5 5

Re: [nznog] Telecom International HTTP Caching
by Richard Hulse 11 Aug '09

11 Aug '09

Hi Paul, I'll ask this on the list, as there are quite a few (other) audio and video content providers here... How will the cache handle MP3s that are served via HTTP? Is this content you want to cache? Should we be setting some sort of header to make it work better? Willl you also be caching on-demand Windows Media content? I ask because I have noticed that some of our visitors complain of Mp3 audio that is truncated or has bits missing out of the middle. It seems to clear itself after a few hours. cheers, Richard Hulse Webmaster Radio NZ

1 0

Telecom International HTTP Caching
by Paul Tinson 11 Aug '09

11 Aug '09

Good Morning, Telecom would like to advise that over the coming weeks we will be extending our international http caching service. This work should go unnoticed but if you or your customers do experience a loss of international browsing then please contact the Broadband Helpdesk on: adsl_helpdesk(a)xtra.co.nz Please make sure the subject has "HTTP Caching" included so that the Helpdesk can filter on these issues. If you would like to talk to the Helpdesk then please phone: 0800 22 55 98 Please state that you believe this to be an http caching issue when raising the case so that it will be routed to the correct resources. NB. Please note that the service is only in place for Telecom Broadband Customers and "International" in this case is based on the international routing tables, as such some domestic sites may appear to Telecom as international content. If you have any specific questions about the service then please feel free to post the questions on this mailing list and as time allows they will be answered. Regards Paul Tinson Senior Specialist Web App Services Shared & Other IS Operations E paul.tinson(a)telecom.co.nz <mailto:paul.tinson(a)telecom.co.nz> W www.telecom.co.nz <http://www.telecom.co.nz> Level 9, 31 Airedale Street Auckland ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

3 4

Re: [nznog] Telstraclear international proxy?
by Anton Smith 10 Aug '09

10 Aug '09

> Message: 12 > Date: Tue, 11 Aug 2009 10:31:53 +1200 > From: Dean Pemberton <nznog(a)deanpemberton.com> > Subject: Re: [nznog] Telstraclear international proxy? > To: nznog(a)list.waikato.ac.nz > Message-ID: <4A809FD9.3040700(a)deanpemberton.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 11/08/09 12:31 AM, Anton Smith wrote: > > In the beginning when diagnosing the problem, an engineer might not > > even know that the problem lies with Telstra, and we have seen people > > posting http headers and so on in the past wondering what was going > > on. > > > > I don't believe that was the case in this instance. It was not a > general query about a general problem. It was a specific technical > issue with a specific ISP. In that case a trouble ticket should be > logged with the ISP first, then post to the list. I'd even accept if > these were both done at the same time. > > To not give the ISP involved a chance to address the issue through > normal customer support channels is not giving them a fair go. > Some ISPs are not very good at customer support, but if you don't log > the call, then how can you expect anything of them. > > I'll explain some more why this is so important; > In years gone by, NZNOG was seen by the major Telcos and some ISPs as a > bunch of troublemakers. I know this for a fact because I've worked for > them while they held this opinion. They viewed NZNOG as a group of > individuals constantly waiting to bash them at any opportunity. The > minute that someone found a bug, or a technical issue, they would post > it first to NZNOG and everyone would hang the associated ISP/Telco out > to dry. > > As such, no one from those organisations joined NZNOG, contributed to > NZNOG, attended the NZNOG conference, etc etc etc. > > Over time we have worked very hard to re-engage with the ISPs and > Telcos, making NZNOG a place where they can derive benefit from > contributing to. Just today we see Paul Tinson posting about Telecom's > cache changes. I doubt anyone would disagree that this is the sort of > involvement that we want. > > Do you think that TelstraClear are going to engage with NZNOG if just > the week previously an NZNOG member was posting publically about > technical issues on their network before giving them a chance to address > them? > > It's a bit like someone buying a shirt at a store, being unhappy with > it, and doing a spot on Campbell Live before going back to the shop and > asking for a refund. Now sure, Campbell Live has its place. It even > has a place for long running retail disputes, but it shouldn't be the > first port of call. And neither should NZNOG. > > We work hard with the Telcos to keep them engaged (the benefits of which > can be seen in Telecoms post this morning), please keep this in mind > when posting. Just make sure you've worked with them first. If you > have and they did a bad job, then by all means post and all bets are off =) > > > Dean > Hi Dean, Given the general difficulties in resolving problems with various ISP/Carriers it is sometimes a fact that the only place you can learn what you need to is here. I'm very heartened by the Telecom post about their caching, and being very specific about the path to follow if there are issues encountered. That is exactly what I believe is missing from Telstra. Perhaps our discussions here (that may be deemed off topic in which case I shall raise the virtues of beer later) are actually constructive in that they can help highlight to carriers how a proactive approach might be used. I do however completely agree with you that it is important to foster a greater sense of community that includes the carriers, ISPs and NZNOG. It is important that NZNOG is not just seen as a bashing list. However, I did not really see that the original post about the caching was negative, and far from "bashing".. so I hardly think that the relationship between NZNOG and Telstra would have been damaged. Maybe my own post had a disgruntled tone, for which I apologise - I shouldn't have done that. I do believe that proactive approaches from the bigger players towards the list (like the Telecom post) are brilliant, and I encourage others (Telstra) to do something similar. Regards, Anton

2 1

Re: [nznog] NZNOG Digest, Vol 80, Issue 9
by Anton Smith 10 Aug '09

10 Aug '09

Hi Dean, While I agree with the general notion that people should go to the ISP directly first, in the Telstra case with their transparent proxy I think it is okay posting here. Mainly because most people on this list know it is there, while most people on the ISPs desk probably don't. Telstra could make this a bit better for themselves by being more verbose about the proxies presence, rather than getting various levels of brokenness complaints. In the beginning when diagnosing the problem, an engineer might not even know that the problem lies with Telstra, and we have seen people posting http headers and so on in the past wondering what was going on. I just think that this kind of thing is a natural side effect of an ill publicised (and some would argue, annoying) network feature, and if Telstra are not proactive about letting people know they have it and the problems that may arise, then they deserve the occasional mail list post. Regards, Anton Disclaimer: I have run into their proxy before due to asymmetric routing + transparent proxy unhappiness (resulted in what looked like a black hole). On Mon, Aug 10, 2009 at 2:00 AM, <nznog-request(a)list.waikato.ac.nz> wrote: > From: Dean Pemberton <nznog(a)deanpemberton.com> > Subject: Re: [nznog] Telstraclear international proxy? > To: nznog <nznog(a)list.waikato.ac.nz> > Message-ID: <4A7F6257.9080104(a)deanpemberton.com> > Content-Type: text/plain; charset=ISO-8859-1 > > > I'd like to take this opportunity to remind people that the appropriate > way to handle situations like this is to log a support call with the > ISPs helpdesk before posting support questions to this list. > > If you believe that it is a problem which effects the NZ Operator > community as a whole and you have exhausted your options (including > escalations) with the ISP concerned then it is maybe appropriate to post. > > This is to eliminate the situation where an ISP finds its name/helpdesk > practices used in vain throughout a mailing list without being given a > chance to put the matter right in private first. > > > Thanks > Dean

5 4

Re: [nznog] Telstraclear international proxy?
by Philip D'Ath 09 Aug '09

09 Aug '09

I can see that becoming urban slang. -----Original Message----- From: Steve Phillips Sent: Mon 10/08/2009 15:15 To: nznog Subject: Re: [nznog] Telstraclear international proxy? Sorry for the completely pointless empty post. My cat did it ! -- Steve. Steve Phillips wrote: > Gordon Smith wrote: >> The bulk of the caching issues service providers are asked to deal >> with come about because people don't know how to configure web servers. >> >> Meta tags and expires are actually useful, but it seems that there are >> always a few people that don't use them, even though their content is >> dynamic.

2 1

Re: [nznog] Microsoft xbox spam ?
by Ian Batterbee 09 Aug '09

09 Aug '09

Just to head off further replies on this thread - I believe the problem was that I was forced to register with microsoft's games for windows (or some such name) when I installed GTA4 many months ago, and it seems that Microsoft have emailed everyone on there, rather than just xbox platform owners. So although unwanted, it was probably legit and just an oversight on their part. Ian Batterbee wrote: > >> Has anyone else received spam from Microsoft about an XBox service update >> ? >> >>

1 0

Google Wave
by James Jones 09 Aug '09

09 Aug '09

I am just curious if anyone else on NZNOG is play with Wave Federation Server? James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

2 1

Microsoft xbox spam ?
by Ian Batterbee 07 Aug '09

07 Aug '09

Has anyone else received spam from Microsoft about an XBox service update ? The message claims that I received it as part of my XBox Live subscription, but since I don't have such a subscription, and don't even own an xbox, I think they're telling porkies.

1 0

APNIC training August 2009
by Elly Tawhai 06 Aug '09

06 Aug '09

________________________________________________________________________ APNIC training and hostmaster consultations in Wellington and Auckland, New Zealand, 3-4/5-6 August 2009 ________________________________________________________________________ Dear All, APNIC is pleased to invite you to attend the following training courses and hostmaster consultation sessions in New Zealand: Course: IRM (Internet Resource Management) and APNIC update Date: 3 August 2009 Location: Wellington, New Zealand Venue: InternetNZ Level 10 Exchange Place 5 - 7 Willeston Street Course: IRM (Internet Resource Management) Date: 5 August 2009 Location: Auckland, New Zealand Venue: CallPlus Level 4, Qantas House 191 Queen Street Event: Hostmaster individual consultations Date: 4 August 2009 Location: Wellington, New Zealand Venue: InternetNZ Level 10 Exchange Place 5 - 7 Willeston Street Event: Hostmaster individual consultations Date: 6 August 2009 Location: Auckland, New Zealand Venue: CallPlus Level 4, Qantas House 191 Queen Street Fees: Fees are for training only. There is no charge for the consultation sessions Pay onsite (cash only) Pay online (credit card) ----------------------- ------------------------ APNIC members: NZD 100 AUD 65 Others: NZD 130 AUD 85 (The online fee is charged in Australian dollars and includes a 20% discount) Notes: ------ - The Hostmaster consultations and training sessions are two distinct events with separate registration processes. - Training courses run from 09:00 to 17:00. - Hostmaster consultations fun from 09:30 to 13:00. - Lunch, refreshments, and training materials are provided. - Seats are limited and the registration is on a 'first come-first served' basis with priority given to APNIC members. To register for the Wellington training, please go to: http://www.apnic.net/events/whats-on/training-events/calendar/events/2009/n… To register for the Auckland training, please go to: http://www.apnic.net/events/whats-on/training-events/calendar/events/2009/n… For course information please go to: http://www.apnic.net/services/services-apnic-provides/training/courses/core… If you have problems registering please contact stella(a)apnic.net Hostmaster consultations ------------------------ APNIC is offering free, individual Hostmaster consultation sessions. At these sessions you can ask about: - How to request IPv4, IPv6, and AS numbers from APNIC - How APNIC hostmasters will evaluate your resource request - Current policies for IP and AS number management in the APNIC region - How to maintain and update your resource registration record in the APNIC Whois Database - Any individual issues you might have To register for the Hostmaster consultations, please email: elly(a)apnic.net Best regards, APNIC training team ________________________________________________________________________ APNIC Training training(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 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ________________________________________________________________________

2 1

FW: Content again - legality question
by Skeeve Stevens 06 Aug '09

06 Aug '09

Again, any thoughts on the NZ situation (legally) regarding this? -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Friday, 7 August 2009 12:59 AM To: ausnog(a)ausnog.net Subject: [AusNOG] Content again - legality question Hey all, Content question again - but this time a legal question. For any content that is 'freely available on the web' - what is the legality of acquiring this content and delivering it locally? For example.. many TV stations are uploading full episodes onto their websites after the show has aired. YouTube would be another example. I am only talking about free content - which is not paid for, but freely downloadable from websites. I guess I am talking about a 'pre-caching' kind of situation. Also, does anyone know at what point music becomes legally free to use in Australia?... like books after 50years after the authors death (in the US it is 20). ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

8 9

FW: Content - Music, Movies, TV
by Skeeve Stevens 05 Aug '09

05 Aug '09

Hey all, Any comments on the NZ situation regarding this? -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Friday, 7 August 2009 12:55 AM To: ausnog(a)ausnog.net Subject: [AusNOG] Content - Music, Movies, TV Hey all, I have multiple clients who are wanting to sell content to their customers. There are multiple scenarios: - ISP's to their users - Hotspots in accommodation locations wanting to sell it to visitors - similar to in-room entertainment in big hotels - Providers of in building connectivity who want to delivery triple-play to their residents Does anyone know of any aggregators of this kind of content with the studios and so on? ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Aug '09

05 Aug '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090806 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Aug '09

05 Aug '09

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090806 source: NZRR ------------------------------------------------------------

1 0