- NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '10

19 Jan '10

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:AS9503 descr: Route set advertised to AS24388 by FX Networks - AS9503 members: 202.89.43.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: service(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 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.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.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, 175.111.100.0/22^22-29, 192.206.152.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, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-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.221.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.49.106.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '10

19 Jan '10

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, 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.36.218.0/23^23-29, 202.46.190.0/23^23-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.221.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.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 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 20091208 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.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.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, 175.111.100.0/22^22-29, 192.206.152.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, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-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.221.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.49.106.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '10

19 Jan '10

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.36.218.0/23^23-29, 202.46.190.0/23^23-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.221.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.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 20091106 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.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.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, 175.111.100.0/22^22-29, 192.206.152.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, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-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.221.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.49.106.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '10

19 Jan '10

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.36.218.0/23^23-29, 202.46.190.0/23^23-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.221.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.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 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 20091208 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.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.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, 192.206.152.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, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-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.221.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.49.106.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR ------------------------------------------------------------

1 0

Consultation on New Zealand Web Harvest 2010
by Gordon Paynter 19 Jan '10

19 Jan '10

Good afternoon everyone. The National Library of New Zealand is planning a second New Zealand Web Harvest in April 2010. We received a lot of feedback from NZNOG (and others) during and after New Zealand Web Harvest 2008. Following that harvest, Dean helped arrange up a meeting of interested stakeholders at the Library to discuss the various issues that were raised, and reported back to the list here: http://list.waikato.ac.nz/pipermail/nznog/2008-November/014763.html You may also recall that I spoke at the 2009 NZNOG conference about our experience with the first harvest. I will speak at the 2010 conference out our plans for the second. During the 2008 Web Harvest, members of the New Zealand internet community raised several concerns, specifically relating to: -- the notification period -- the robots policy -- the location of the harvester. For the 2010 harvest we have developed an Options Paper, detailing approaches the Library could take to address these concerns. We are circulating this Options Paper to stakeholder groups in the networking and technical communities. The feedback we receive will be built into the planning of the harvest, its public notification, and its operation. Please note that the options paper is NOT a general notification of the 2010 harvest. We will notify the wider New Zealand internet community closer to the date of the harvest when more details are known. You can find a copy of the Options Paper on the National Library website: http://bit.ly/nlnzwebharvest Submissions on the Options Paper close at 9am on Monday 8 February 2010, or you can talk to me in person at NZNOG 2010. I'll be giving a short presentation on Thursday morning, and staying on to talk to people until Friday afternoon. See you in sunny Hamilton! And by way of providing a useful service to conference attendees, and illustrating the value of web archiving, may I refer you to one of the first substantive websites about Hamilton, written by myself and my flatmates when I was at University, offering valuable advice on the city, where to eat, the University, architecture, and so on, and preserved for your benefit by the Internet Archive: If you're planning on visiting Hamilton in 1998, it's a must-read: http://web.archive.org/web/20070515122721rn_1/www.paynter.info/miscellania/… Thanks, Gordon -- Gordon Paynter Programme Manager Digitisation National Digital Library National Library of New Zealand

1 0

NZ NOG Entertainment
by Corinne Cowlishaw 19 Jan '10

19 Jan '10

Hi everyone, Would those attending have a preference for entertainment for after dinner on Thursday 28th? Also are there any particular bars that anyone could recommend in Hamilton in the city centre or near the conference? Thanks, Kind Regards, Corinne Cowlishaw Administration Assistant Level 1, 189 Miller St North Sydney, NSW 2060 T: +61 2 8999 8999 E: corinne(a)vocus.com.au W: www.vocus.com.au

1 0

NZNOG 2010 conference reminder...
by Jonny Martin 19 Jan '10

19 Jan '10

NZNOG is just a week away now. There are limited slots left in the Routing Workshop and Security Tutorial. If you want to get into these then you'll need to register on up mighty fast. Accommodation on campus needs to be finalised soon also, so same deal - register soon. Note that the registration system allows you to book just accommodation so if you've previously registered for the conference you can add another order for accommodation only should you want that. http://2010.nznog.org/register Additionally Renaissance and Brocade will be providing a Brocade (Foundry) switch/router course on the Wednesday. As a bonus they'll also be providing attendees with a complimentary exam voucher allowing for a Brocade qualification to be achieved. http://2010.nznog.org/tutorials#brocade Once more, the org team would like to thank our generous sponsors for making each and every NZNOG a reality. http://2010.nznog.org/sponsors See you in Hamilton! Jonny.

1 0

Upcoming APNIC policy implementations
by Elly Tawhai 17 Jan '10

17 Jan '10

Hi NZNOG Community, On 10 February 2009, APNIC will implement three policy proposals that reached consensus during APNIC 28 in Beijing, China in August 2009. The APNIC Executive Council (EC) endorsed the proposals during their November 2009 meeting. The three policy changes are: - Removing policy restrictions on the transfer of registration of IPv4 address allocations and IPv4 portable address assignments between current APNIC account holders. This change aims to ensure that the APNIC registry reflects the true status of IPv4 resource holdings, reducing risks to the routing and addressing infrastructure integrity of the network and providing a stronger incentive for unused IPv4 address space to return to active use during the IPv6 transition. - Providing alternative simplified criteria that allows a Member with existing IPv4 space to qualify for an appropriately sized IPv6 block under the matching IPv6 policy and request that IPv6 block through a simple online form. This change aims to encourage greater uptake of IPv6 addresses amongst APNIC Members who have IPv4 space. - Adding the ability to recover unused historical AS numbers for eventual reassignment to other APNIC account holders. This change aims to release unused AS numbers back into the unassigned pool. To view the history of these policy proposals, see: prop-050: IPv4 address transfers http://www.apnic.net/policy/proposals/prop-050 prop-073: Simplifying allocation/assignment of IPv6 to APNIC members with existing IPv4 addresses http://www.apnic.net/policy/proposals/prop-073 prop-075: Ensuring efficient use of historical AS numbers http://www.apnic.net/policy/proposals/prop-075 APNIC policies are developed by the Membership and broader Internet community. It's easy to participate in APNIC policy development. If you can't attend APNIC meetings, you can join the discussions online via the Policy SIG mailing list. To join, go to: http://www.apnic.net/community/participate/join-discussions 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

DRG Announces New Tool - The DRG Distro
by Dean Pemberton 14 Jan '10

14 Jan '10

Hi all, For the last 6 months the members of the Dragon Research Group (associated with Team Cymru https://drg.team-cymru.org/about.html) have been busy working away. We have just announced what all that work has produced. Dean ----- The Dragon Research Group (DRG) would like to announce a new tool called the DRG Distro. This new tool is at the heart of the DRG Network which provides actionable intelligence. The Dragon Research Group (DRG) Distro is a Linux-based Live CD platform. It forms the cornerstone of much of DRG's ongoing research, analysis and development efforts. The goal of the DRG Distro is to build a DRG Network of pods that can securely and anonymously help provide actionable intelligence to the Internet security community. The DRG Distro can act as a passive data collection facility for many common applications such as HTTP servers or if expressly permitted, can help actively monitor malicious Internet activity. It also includes a number of tools that when combined with the DRG Network help provide real-time, usable intelligence to the local pod partner. The entire DRG Network is designed to provide real-time actionable intelligence in the form of statistics, graphs, threat feeds and DRG Distro tool sets that will benefit the entire Internet security community. No pod partner or pod specific information is ever shared outside the core DRG team by DRG. The DRG seeks trustworthy and reliable pod partners to help build and support the growing DRG Network. All pod partners are screened by DRG to help ensure the integrity of the DRG Network. Pod runners will have some advantages over the general public. They will have full insight into their own pods and their feedback will help determine the future direction of the DRG Distro and DRG Network. To volunteer to participate in the DRG Network please send the following information in a signed PGP message to: dragon(a)drg.team-cymru.org * Real and full name * PGP public key * Proposed network and geographic location(s) of pod install * General description of pod connectivity (e.g. bandwidth available, network policy and global filter rules, special instructions) Additional feedback or questions can be directed to the email address indicated above (dragon(a)drg.team-cymru.org) or visit us on the Freenode IRC network #drg channel. Approved pod parters will receive additional info about their DRG Distro pod, including installation instructions, technical specifications and more.

1 0

Call for nominations to the APNIC Executive Council
by Elly Tawhai 14 Jan '10

14 Jan '10

_______________________________________________________________________ Call for nominations to the APNIC Executive Council _______________________________________________________________________ Three positions on the APNIC Executive Council (EC) will be opened for election at APNIC 29 in Kuala Lumpur on Friday, 5 March 2010. The Executive Council represents the APNIC Membership and acts in the best interests of the organization. The Members whose positions are up for re-election are: - Akinori Maemura - Che-Hoo Cheng - Ma Yan These three Members were all elected at APNIC 25 in Taipei, Taiwan on Friday, 29 February 2008. Nominations are due by the close of business on Wednesday, 17 February 2010 at the latest (17:30 UTC 10, Brisbane time). Nominees do not have to be representatives of APNIC Members, but only APNIC Members may nominate and vote for candidates. Nominations must be made using the online nomination form, which is available now: http://meetings.apnic.net/29/whats-on/elections/nominate If you are unable to vote online or attend APNIC 29, you can still make your vote count by appointing a proxy to represent you at the meeting. For more information on nominations received, proxy registration, current EC Members, and the role of the EC, please refer to: http://meetings.apnic.net/29/whats-on/elections Online voting will be available for this election via the MyAPNIC web site and will open soon after the nomination period closes. Nominees should note that positions on the APNIC EC are currently voluntary and that APNIC may not be able to reimburse EC Members all expenses associated with EC duties. Where possible, however, APNIC will reimburse actual expenses for attendance at APNIC meetings, providing that these fall within budget and cash flow constraints. If you have any questions, please contact the APNIC Secretariat at: helpdesk(a)apnic.net _______________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: 61 7 3858 3100 PO Box 2131 Milton, QLD 4064 Australia Fax: 61 7 3858 3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net _______________________________________________________________________

1 0

Do you have an idea for an APNIC 29 policy proposal?
by Elly Tawhai 13 Jan '10

13 Jan '10

Hi NZNOG Community Is there something in APNIC's policies that you think really needs to change? Have you tried to request resources from APNIC but didn't meet the current criteria? If so, why not propose a new policy or a change to an existing policy? To submit a proposal for discussion at APNIC 29, be sure to submit it before the proposal deadline: 27 January 2010 You can submit your proposal in two ways: 1. Use the online form at: http://www.apnic.net/policy/proposals/submit-proposal 2. Send your proposal in TEXT format to <policy(a)apnic.net>. More information ---------------- APNIC's policy development process is explained at: http://www.apnic.net/community/policy/process View current and past policy proposals at: http://www.apnic.net/policy/proposals Learn more about APNIC 29 at: http://meetings.apnic.net We look forward to seeing you in Kuala Lumpur! 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

any 2010.nznog.org webmasters?
by Thom Hooker 13 Jan '10

13 Jan '10

Could someone who runs the 2010.nznog.org web site please get in touch with me off-list? I'm having some trouble registering for the Wednesday tutorials... Thanks Thom ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smx.co.nz ______________________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 13 Jan '10

13 Jan '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.92.0.0/15^15-29, 118.148.0.0/15^15-29, 130.216.0.0/15^15-29, 58.28.0.0/16^16-29, 60.234.0.0/16^16-29, 111.69.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 121.98.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 131.203.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 138.211.0.0/16^16-29, 141.243.0.0/16^16-29, 143.96.0.0/16^16-29, 147.209.0.0/16^16-29, 150.206.0.0/16^16-29, 151.135.0.0/16^16-29, 153.111.0.0/16^16-29, 156.59.0.0/16^16-29, 156.62.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 165.205.0.0/16^16-29, 166.65.0.0/16^16-29, 166.83.0.0/16^16-29, 167.179.0.0/16^16-29, 203.97.0.0/16^16-29, 113.203.0.0/17^17-29, 115.187.128.0/17^17-29, 119.224.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 203.167.128.0/17^17-29, 203.173.128.0/17^17-29, 210.48.0.0/17^17-29, 218.101.0.0/17^17-29, 74.80.64.0/18^18-29, 112.141.0.0/18^18-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 123.100.64.0/18^18-29, 123.255.0.0/18^18-29, 124.157.64.0/18^18-29, 124.197.0.0/18^18-29, 124.198.128.0/18^18-29, 125.253.0.0/18^18-29, 202.14.0.0/18^18-29, 202.180.64.0/18^18-29, 203.60.64.0/18^18-29, 203.79.64.0/18^18-29, 203.96.0.0/18^18-29, 203.98.0.0/18^18-29, 203.110.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.184.0.0/18^18-29, 203.208.64.0/18^18-29, 203.211.64.0/18^18-29, 210.185.0.0/18^18-29, 210.246.0.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.213.160.0/19^19-29, 125.254.64.0/19^19-29, 129.223.96.0/19^19-29, 180.189.192.0/19^19-29, 202.0.32.0/19^19-29, 202.2.96.0/19^19-29, 202.46.160.0/19^19-29, 202.50.192.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.65.32.0/19^19-29, 202.74.192.0/19^19-29, 202.78.128.0/19^19-29, 202.83.32.0/19^19-29, 202.89.32.0/19^19-29, 202.89.128.0/19^19-29, 202.124.96.0/19^19-29, 202.150.96.0/19^19-29, 202.154.128.0/19^19-29, 202.169.192.0/19^19-29, 202.171.160.0/19^19-29, 202.182.96.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.89.160.0/19^19-29, 203.96.128.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.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 219.88.224.0/19^19-29, 58.84.224.0/20^20-29, 111.65.224.0/20^20-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.134.0.0/20^20-29, 114.134.160.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, 116.89.224.0/20^20-29, 116.90.128.0/20^20-29, 116.93.128.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, 119.224.128.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, 124.248.128.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, 174.128.16.0/20^20-29, 199.249.112.0/20^20-29, 202.10.80.0/20^20-29, 202.21.16.0/20^20-29, 202.22.16.0/20^20-29, 202.37.0.0/20^20-29, 202.49.16.0/20^20-29, 202.49.224.0/20^20-29, 202.50.16.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.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.160.48.0/20^20-29, 202.170.160.0/20^20-29, 202.174.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.86.192.0/20^20-29, 203.88.112.0/20^20-29, 203.100.208.0/20^20-29, 203.130.160.0/20^20-29, 203.144.32.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.160.112.0/20^20-29, 210.48.160.0/20^20-29, 210.55.16.0/20^20-29, 210.56.32.0/20^20-29, 219.88.128.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.134.176.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.90.72.0/21^21-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.53.144.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, 120.136.0.0/21^21-29, 120.136.48.0/21^21-29, 120.138.16.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.150.160.0/21^21-29, 170.9.56.0/21^21-29, 180.92.192.0/21^21-29, 180.94.232.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.20.0.0/21^21-29, 202.27.40.0/21^21-29, 202.27.48.0/21^21-29, 202.27.192.0/21^21-29, 202.27.208.0/21^21-29, 202.36.8.0/21^21-29, 202.36.16.0/21^21-29, 202.37.32.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.49.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.88.0/21^21-29, 202.49.96.0/21^21-29, 202.49.128.0/21^21-29, 202.49.152.0/21^21-29, 202.50.64.0/21^21-29, 202.56.48.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.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.169.16.0/21^21-29, 202.174.112.0/21^21-29, 202.175.128.0/21^21-29, 202.189.160.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.21.24.0/21^21-29, 203.60.8.0/21^21-29, 203.99.64.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, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 210.5.48.0/21^21-29, 210.9.136.0/21^21-29, 210.54.32.0/21^21-29, 210.54.56.0/21^21-29, 210.54.128.0/21^21-29, 210.54.152.0/21^21-29, 210.55.72.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.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.34.48.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.92.16.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 112.140.176.0/22^22-29, 113.21.224.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.59.224.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.141.104.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.102.108.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, 134.128.160.0/22^22-29, 140.200.248.0/22^22-29, 180.222.64.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.7.4.0/22^22-29, 202.8.44.0/22^22-29, 202.27.56.0/22^22-29, 202.27.76.0/22^22-29, 202.27.92.0/22^22-29, 202.27.100.0/22^22-29, 202.27.200.0/22^22-29, 202.27.216.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.36.164.0/22^22-29, 202.36.192.0/22^22-29, 202.36.224.0/22^22-29, 202.37.48.0/22^22-29, 202.37.60.0/22^22-29, 202.37.76.0/22^22-29, 202.37.92.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.45.152.0/22^22-29, 202.49.72.0/22^22-29, 202.49.172.0/22^22-29, 202.49.200.0/22^22-29, 202.49.208.0/22^22-29, 202.49.240.0/22^22-29, 202.49.252.0/22^22-29, 202.50.52.0/22^22-29, 202.50.60.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.50.188.0/22^22-29, 202.59.4.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100114 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.92.0.0/15^15-29, 118.148.0.0/15^15-29, 130.216.0.0/15^15-29, 58.28.0.0/16^16-29, 60.234.0.0/16^16-29, 111.69.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 121.98.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 131.203.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 138.211.0.0/16^16-29, 141.243.0.0/16^16-29, 143.96.0.0/16^16-29, 147.209.0.0/16^16-29, 150.206.0.0/16^16-29, 151.135.0.0/16^16-29, 153.111.0.0/16^16-29, 156.59.0.0/16^16-29, 156.62.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 165.205.0.0/16^16-29, 166.65.0.0/16^16-29, 166.83.0.0/16^16-29, 167.179.0.0/16^16-29, 203.97.0.0/16^16-29, 113.203.0.0/17^17-29, 115.187.128.0/17^17-29, 119.224.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 203.167.128.0/17^17-29, 203.173.128.0/17^17-29, 210.48.0.0/17^17-29, 218.101.0.0/17^17-29, 74.80.64.0/18^18-29, 112.141.0.0/18^18-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 123.100.64.0/18^18-29, 123.255.0.0/18^18-29, 124.157.64.0/18^18-29, 124.197.0.0/18^18-29, 124.198.128.0/18^18-29, 125.253.0.0/18^18-29, 202.14.0.0/18^18-29, 202.180.64.0/18^18-29, 203.60.64.0/18^18-29, 203.79.64.0/18^18-29, 203.96.0.0/18^18-29, 203.98.0.0/18^18-29, 203.110.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.184.0.0/18^18-29, 203.208.64.0/18^18-29, 203.211.64.0/18^18-29, 210.185.0.0/18^18-29, 210.246.0.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.213.160.0/19^19-29, 125.254.64.0/19^19-29, 129.223.96.0/19^19-29, 180.189.192.0/19^19-29, 202.0.32.0/19^19-29, 202.2.96.0/19^19-29, 202.46.160.0/19^19-29, 202.50.192.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.65.32.0/19^19-29, 202.74.192.0/19^19-29, 202.78.128.0/19^19-29, 202.83.32.0/19^19-29, 202.89.32.0/19^19-29, 202.89.128.0/19^19-29, 202.124.96.0/19^19-29, 202.150.96.0/19^19-29, 202.154.128.0/19^19-29, 202.169.192.0/19^19-29, 202.171.160.0/19^19-29, 202.182.96.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.89.160.0/19^19-29, 203.96.128.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.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 219.88.224.0/19^19-29, 58.84.224.0/20^20-29, 111.65.224.0/20^20-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.134.0.0/20^20-29, 114.134.160.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, 116.89.224.0/20^20-29, 116.90.128.0/20^20-29, 116.93.128.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, 119.224.128.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, 124.248.128.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, 174.128.16.0/20^20-29, 199.249.112.0/20^20-29, 202.10.80.0/20^20-29, 202.21.16.0/20^20-29, 202.22.16.0/20^20-29, 202.37.0.0/20^20-29, 202.49.16.0/20^20-29, 202.49.224.0/20^20-29, 202.50.16.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.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.160.48.0/20^20-29, 202.170.160.0/20^20-29, 202.174.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.86.192.0/20^20-29, 203.88.112.0/20^20-29, 203.100.208.0/20^20-29, 203.130.160.0/20^20-29, 203.144.32.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.160.112.0/20^20-29, 210.48.160.0/20^20-29, 210.55.16.0/20^20-29, 210.56.32.0/20^20-29, 219.88.128.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.134.176.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.90.72.0/21^21-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.53.144.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, 120.136.0.0/21^21-29, 120.136.48.0/21^21-29, 120.138.16.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.150.160.0/21^21-29, 170.9.56.0/21^21-29, 180.92.192.0/21^21-29, 180.94.232.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.20.0.0/21^21-29, 202.27.40.0/21^21-29, 202.27.48.0/21^21-29, 202.27.192.0/21^21-29, 202.27.208.0/21^21-29, 202.36.8.0/21^21-29, 202.36.16.0/21^21-29, 202.37.32.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.49.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.88.0/21^21-29, 202.49.96.0/21^21-29, 202.49.128.0/21^21-29, 202.49.152.0/21^21-29, 202.50.64.0/21^21-29, 202.56.48.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.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.169.16.0/21^21-29, 202.174.112.0/21^21-29, 202.175.128.0/21^21-29, 202.189.160.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.21.24.0/21^21-29, 203.60.8.0/21^21-29, 203.99.64.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, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 210.5.48.0/21^21-29, 210.9.136.0/21^21-29, 210.54.32.0/21^21-29, 210.54.56.0/21^21-29, 210.54.128.0/21^21-29, 210.54.152.0/21^21-29, 210.55.72.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.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.34.48.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.92.16.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 112.140.176.0/22^22-29, 113.21.224.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.59.224.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.141.104.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.102.108.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, 134.128.160.0/22^22-29, 140.200.248.0/22^22-29, 180.222.64.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.7.4.0/22^22-29, 202.8.44.0/22^22-29, 202.27.56.0/22^22-29, 202.27.76.0/22^22-29, 202.27.92.0/22^22-29, 202.27.100.0/22^22-29, 202.27.200.0/22^22-29, 202.27.216.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.36.164.0/22^22-29, 202.36.192.0/22^22-29, 202.36.224.0/22^22-29, 202.37.48.0/22^22-29, 202.37.60.0/22^22-29, 202.37.76.0/22^22-29, 202.37.92.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.45.152.0/22^22-29, 202.49.72.0/22^22-29, 202.49.172.0/22^22-29, 202.49.200.0/22^22-29, 202.49.208.0/22^22-29, 202.49.240.0/22^22-29, 202.49.252.0/22^22-29, 202.50.52.0/22^22-29, 202.50.60.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.50.188.0/22^22-29, 202.59.4.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100114 source: NZRR ------------------------------------------------------------

1 0

Trying to send email to sponsorship contact address on nznog website and get this error
by Robert Cotter 12 Jan '10

12 Jan '10

----- The following addresses had permanent fatal errors ----- <sponsorship(a)nznog.org<mailto:sponsorship(a)nznog.org>> (reason: 550 Unrouteable address) ----- Transcript of session follows ----- ... while talking to usenet.net.nz.: >>> DATA <<< 550 Unrouteable address 550 5.1.1 User unknown <<< 503-All RCPT commands were rejected with this error: <<< 503-Unrouteable address <<< 503 Valid RCPT command must precede DATA The email address was taken off the nznog.org website.... is this incorrect? I am trying to convince my boss that we should be a sponsor at next year's conference so need costs for budgeting etc. Oh..... beers at the vendor night if I can attend again this year. Regards Robert Cotter Sales Engineer rcotter(a)distributioncentral.co.nz<UrlBlockedError.aspx> Distribution Central NZ Unit 2, Level 1, 194 Victoria Street West, Auckland 1001, New Zealand. Mb +64 21 675550, T +64 9 309 8277, F +64 9 309 8276 www.distributioncentral.co.nz<http://www.distributioncentral.co.nz> ________________________________ This email is for the intended recipient(s) only. Be advised that if you have received this email in error that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. The sender cannot guarantee that this email or any attachment to it is free of computer viruses or other conditions which may damage or interfere with data, hardware or software with which it might be used. If you have received this email in error, please notify Distribution Central on +61 2 8986 5000 or notify sender.

2 1

Unbundled exchanges and areas
by Chris Hodgetts 12 Jan '10

12 Jan '10

Hello, Does anyone have a public map showing how much of New Zealand has been unbundled, how many Exchanges have been done, and the speeds customers are getting on unbundled exchanges... And I guess, in a given area, what ISP's are there.... After all the 'hype' of a blond CEO of a certain ISP (Any one remember the Bread stunt) about how they are going to provide New Zealanders with quicker faster cheaper Internet, I have seen no evidence of this - the cost has not dropped between an unbundled exchange and a non unbundled exchange. Last I heard in the news, less than a handfull of Auckland suburbs had been done, And I live in one of them which is good, but if I want to move, I would like to move to one that is unbundled still. The News Media has moved on to the next 'buzz word' and I guess that is what some companies were hoping for.. As LLU is now out of the public eye, and almost forgotten about. Just thought I would ask here, as I cant seem to find anything online.

4 3

NZRR Route Registry Update
by NZRR Database Notifications 11 Jan '10

11 Jan '10

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:AS24183 descr: Route set advertised to AS9560 by DTS - AS24183 members: 202.68.94.0/23^23-29, 202.20.6.0/24^24-29, 202.36.172.0/24^24-29, 202.68.82.128/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: timp(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091202 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24183 descr: advertised to AS9560 by DTS LIMITED - AS24183 members: 202.68.94.0/23^23-29, 124.150.166.0/24^24-29, 202.20.6.0/24^24-29, 202.36.172.0/24^24-29, 202.68.82.128/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: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100112 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 11 Jan '10

11 Jan '10

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:AS17492 descr: advertised to AS9560 by Vector Communications - AS17492 members: 202.126.192.0/20^20-29, 123.108.144.0/21^21-29, 202.0.151.0/24^24-29, 202.62.245.0/24^24-29, 203.30.174.0/24^24-29, 203.99.68.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: tony.wicks(a)vector.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091106 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17492 descr: advertised to AS9560 by Vector Communications - AS17492 members: 202.126.192.0/20^20-29, 115.126.128.0/21^21-29, 123.108.144.0/21^21-29, 202.162.176.0/21^21-29, 202.0.151.0/24^24-29, 202.62.245.0/24^24-29, 203.30.174.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: tony.wicks(a)vector.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100112 source: NZRR ------------------------------------------------------------

1 0

Telco Rack Linux Server
by Jonathan Brewer 09 Jan '10

09 Jan '10

Hi Folks, Anyone out there using commercial, off the shelf linux servers that happen to mount in a telco rack? Ideal would be something along the lines of 3U high and 400mm deep. 50V DC would be ideal but that's probably dreaming. I'm not too fussed about architecture but I do want something supported by a real vendor that I'm likely to be able to continue buying on a regular basis. (I'm not interested in hearing about this guy who will build me a couple for real cheap.) Cheers, Jon

2 2

NZNOG2010 is just three weeks away!
by Jonny Martin 05 Jan '10

05 Jan '10

[http://2010.nznog.org/register do it.] It's that time of year once more and the annual NZNOG conference is just three weeks away. The 2010 conference is supported by our Platinum Sponsor Vocus Communications and hosted by the WAND Group and Rural Link at Waikato University, Hamilton, Wednesday 27th - Friday 29th January 2010. The org-team have put together another cracker bunch of presentations, including: * Emergence of the video peering eco-system - Bill Norton, DrPeering.net * Signing the root - Joe Abley, ICANN * ISP scenarios for IPv6 deployment - Brian Carpenter, University of Auckland http://2010.nznog.org/full-program As usual multiple parallel tutorials on running on the Wednesday, APNIC IRME, MPLS, and a hands-on Security tutorial with Team Cymru. Additionally there will three day hands-on routing workshop taken by Philip Smith (Cisco) running Monday 25th - Wednesday 27th. This workshop has been run scores of times around the globe and is of very high quality. Full details are at http://2010.nznog.org/routing Places are limited so register early. Cost effective accommodation is being provided on campus just a short walk from the meeting rooms. $66/night gets you a room, breakfast, and internet. Rooms are limited so book early to avoid dissappointment NZNOG2010 would not be possible without the generous support of all our sponsors. Thanks Vocus Communications, WAND Group, Rural Link, Alcatel-Lucent, Renaissance, Araneo, ISPANZ, Cisco, APNIC, eintellego, Velocity Networks, Paystation, InternetNZ, and R2! Looking forward to seeing you in Hamilton, Jonny. For the 2010 org-team

1 0

New Zealand Network Operators' Group
by Donald Neal 05 Jan '10

05 Jan '10

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 25-29 January 2010 in Hamilton, hosted by The University of Waikato's WAND research group. For more information, and to register, see http://2010.nznog.org/ Did I mention you ought to register right away? 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 | It is a truth universally acknowledged | that a zombie in possession of brains High Performance Computing | must be in want of more brains. The University of Waikato | - Pride and Prejudice and Zombies

1 0

Final phase of four-byte AS number policy now active
by Elly Tawhai 04 Jan '10

04 Jan '10

_______________________________________________________________________ Final phase of four-byte AS number policy now active _______________________________________________________________________ As of 1 January 2010, APNIC no longer makes a distinction between four-byte only and two-byte only Autonomous System (AS) numbers. Instead, all AS numbers are now considered to be four-byte AS numbers. This change marks the final phase of the transition to four-byte AS numbers. For more information on the implementation phases of the four-byte AS number policy, please see "Policies for Autonomous System number management in the Asia Pacific region" section 6.3, "Timetable for moving from two-byte only AS numbers to four-byte AS numbers": http://www.apnic.net/policy/asn-policy.html#6.3 To learn more about how the transition to four-byte AS numbers may affect your network, see: http://icons.apnic.net/asn If you have any questions or need further assistance, please contact: helpdesk(a)apnic.net _______________________________________________________________________ APNIC Secretariat 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

1 0

Re: [nznog] 2010 NZNOG Conference
by Richard Naylor 23 Dec '09

23 Dec '09

At 05:50 p.m. 23/12/2009, you wrote: >There seems to be quite a few hotels in downtown >Hamilton, and it is like only 1.5km to the uni.. not that Iâd walk it. We stay at the Ventura Hotel in Hamilton. Its very nice and includes breakfast. From memory its under $100 per night or thereabouts. They're tolerant of us (or we've trained them) so running power cables out to the van doesn't completely faze them. Neither does stashing our gear under the stairs. Maybe it was the time we were there with the Police and took a new car apart.... However, they do still talk about the time we did a link from London to a pub in Wellington for an All Blacks game doing mid span EQ in the hotel room. There was only a couple of roadcases of gear in the room, honest. But it was very cool - we got to watch Sky rugby with an alternate commentary. > Iâm a little too old and entitled these days > to stay in Uni accommodation ;-) Nah - its good fun and brings back memories. However, last time I did forget the golden rule about always carrying your room key, especially when going to the loo in the middle of the night.

1 0

2007 Conference Videos
by Richard Naylor 22 Dec '09

22 Dec '09

Video of talks from the 2007 NZNOG Conference is now available at http://www.r2.co.nz/20070131/ Sorry for the delay. The talks were shot to tape, which need to be captured, edited, transcoded and finally a big web page to cover it all. Theres 30 videos covering over 24 hours (something like 20 GB of server space). I have decided that its the video you all want, so haven't made any MP3s this time. Beat me up if you want MP3s. The video is available for both streaming (2 formats) and download (1 format). Theres a flash player and windows player option. And if you ever wondered if you can have 30 embedded players in a web page - the answer is yes - they all work at the same time. If your network and CPU can handle it. Don't watch them all at once..... and let me know if you find any issues. I haven't watched them all the way thru. We just processed them. A big thanks to James at InspireNet who paid for the video guys (not R2) who shot it with some nice cameras. Richard

17 24

Re: [nznog] New Conficker Reports based on ASN and Country
by Stu Fleming 22 Dec '09

22 Dec '09

> Message: 3 > Date: Wed, 16 Dec 2009 18:48:56 -0800 > From: "Barry Raveendran Greene" <bgreene(a)senki.org> > To: <nznog(a)list.waikato.ac.nz> > Subject: [nznog] New Conficker Reports based on ASN and Country > Message-ID: <001901ca7ec3$81a8b440$84fa1cc0$@org> > Content-Type: text/plain; charset="us-ascii" > > Hello Team, > > Shadowserver has new Conficker reports. This was instigated by internal > Conficker Working Group dialog. We are now set up to really see if > remediation is effective. As you can see in the data, Conficker is still > growing (A & B). This is concerning, which some are now starting to express > ... > > > > The report also has a country level listing by ASNs. It is not perfect, but > it makes it easier to see how New Zealand is doing: > > http://www.shadowserver.org/wiki/pmwiki.php/Infections/Conficker-NZ > Just to note that stats for AS38437 (WIC NZ) are being mis-reported by this service. They are including adjacent IP netblocks (in this case 120.89.79.0) rather than just the prefixes that we originate. So while we have normal background activity (from our own tracking), Conficker C stats are showing as 3%+, which would be cause for concern (I've had 3 people contact me about this in the last couple of days), but isn't actually happening. I've sent comment to the guys at Shadowserver, but it is worth signing up for the reports, even just to check that things are being reported correctly. Regards, Stu

1 0

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

21 Dec '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:AS45280 descr: Route set advertised to AS9560 by Horizon Pacific Group Limited - AS45280 members: 114.134.160.0/24^24-29, 114.134.176.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: bryan.tabb(a)horizonpacific.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090615 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS45280 descr: advertised to AS9560 by Horizon Pacific - AS45280 members: 114.134.160.0/21^21-29, 114.134.168.0/22^22-29, 114.134.172.0/24^24-29, 123.100.106.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: bryan.tabb(a)horizonpacific.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091223 source: NZRR ------------------------------------------------------------

1 0