- NZNOG - lists.nznog.org

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