- NZNOG - lists.nznog.org

Server Hosting...
by Don Gould 04 Apr '06

04 Apr '06

Hi All, I'm looking for pricing to colocate a 1ru server. Need to have access to data from more than one network. Needs to have a fixed price for 150gb of data in a month with price advised for additional data. Need to know speed of up stream links. Need to have 12 - 16 public IPs Responses off list please (don't think the nog list needs filling with quotes today :) don(a)bowenvale.co.nz Thanks in advance. Cheers Don -- Don Gould

5 5

Notification of NZRR Database changes
by NZRR Database Notifications 02 Apr '06

02 Apr '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.173.63.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050808 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by ihug - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 198.32.71.0/24^24-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.173.63.0/24^24-29, 210.55.184.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050808 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 Apr '06

02 Apr '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS23883 as-name: NZRR-AS23883 descr: Shane Cole Ltd descr: WIX peering at '202.7.0.157' descr: see Citylink RT job #4963 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23883 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: shane.mobile(a)paradise.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23883 descr: Route set advertised to AS9439 by Shane Cole Ltd - AS23883 members: 203.128.224.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: shane.mobile(a)paradise.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR

1 0

OT - Reply from Cunliffe
by Ian Cousins 31 Mar '06

31 Mar '06

Anyone else get this type of reply from Cunliffe's office recently?... as if I'm going to open an attachment in an email with the subject header "Attached image data". I'm assuming its a reply of some sort to the "Better broadband" letter I sent them. Ian Cousins, Wellington -------- Original Message -------- Subject: Attached image data. Date: Fri, 31 Mar 2006 10:16:03 +1200 From: Sandra Wilson <Sandra.Wilson(a)parliament.govt.nz> To: lyncus(a)ihug.co.nz Sandra Wilson Ministerial Secretary Hon David Cunliffe Phone: 04 470 6667 Fax: 04 471 2360 Email: Sandra.Wilson(a)parliament.govt.nz ----- Forwarded by Sandra Wilson/minserv on 31/03/2006 10:15 am ----- GoschePhotocopier(a)minist ers.govt.nz To: SANDRA.WILSON(a)PARLIAMENT.GOVT.NZ cc: 31/03/2006 10:21 am Fax to: Subject: Attached image data. This is image data from the scanner.(See attached file: Scan24.pdf) No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.3/298 - Release Date: 30/03/2006

2 1

Re: [nznog] OT - Reply from Cunliffe
by Phonenet 31 Mar '06

31 Mar '06

This doesn't appear to have gone out properly first time so here it is again... > Mark Foster wrote: > >Its a PDF. Theyre generally safe, arent they? > I know its a pdf but it was the manner in which it was sent that got to me - no real header/subject and everyone knows NOT to open attachments sent from unknown persons that you aren't expecting.... and as for this reply from Justin Cook: > Looks like your standard network scanner/photocopier email. I don't > think it's in response to anything, although it could always be a > virus pretending to be a photocopier. > > If you wrote them a physical letter then it seems likely it was > scanned and was meant to be sent to the MP in question but someone > sent it to you instead. Go on, open it! :D > > > *Justin Cook* > Developer > http://www.skull.co.nz/ > I wonder if we really want our systems developed by someone with this sort of appraoch..... BTW it wasn't a physical letter I sent - the "Better Broadband" leeter was a form ;letter that I rewrote to cover the points I wanted to make as an individual and as a business owner. Ian

1 0

NZCERT-discuss mailing list.
by Brendan Murray 29 Mar '06

29 Mar '06

Last time I steal your bandwidth for this. NZCERT-discuss A mailing list to discuss the establishment of an NZ CERT ========================================================= The issue of creating an NZ Computer Emergency Response Team has been around for years. There are a bunch of ways that it can be done, a lot of people that can be involved and ultimately a lot of dollars required to make it work. We raised the idea on behalf of the InternetNZ NZCERT task force on the NZNOG and InternetNZ members-discuss lists last year. There was some support for the idea, as well as some suggestions for the creation of a local nsp-discuss like mailing list. While the nsp idea is a good one, it doesn't address the issue of a NZ based Computer Emergency Response Team (CERT) In the recent MED discussion paper "A Strategic Consideration of ICT Security and Confidence in New Zealand" on page 33 they state: "1.Areas for further work would appear to include the following: - Reviewing the need for the establishment of a national computer emergency response team (CERT) and a mechanism for anonymous reporting of security incidents;" InternetNZ has created a NZCERT-discuss mailing list as one step in the process of evaluating the need and way forward for a NZ based CERT. A separate mailing list was created to allow those that were interested to take part, and to stop using the bandwidth of the NZNOG, members-discuss and other lists. You are invited to join the NZCERT-discuss list by sending email to NZCERT-discuss-subscribe(a)internetnz.net.nz -- Brendan Murray brendan(a)wolfhoundsecurity.com The Observation Post www.wolfhoundsecurity.com 14 Centre Road Phone: +64-3-4543282 RD 2 Ocean Grove Fax: +64-3-4543285 Dunedin, New Zealand Mobile: +64-21-1153290

1 0

NZNOG06 redux
by Simon Blake 28 Mar '06

28 Mar '06

A few thoughts on the future of NZNOG that came to me after the meeting closed on Friday. There is no direct operational content here. First up, a big thank you to everybody who participated, the sponsers and speakers, the many volunteers, and especially Lin, Peter, Mark, Joe and Donald for organising an excellent show. With my sponsers hat on, I can say that I think it was money well spent, even with Jonny hogging the limelight :-). 1) where were the small Wellington ISP's? GlobeNet, Actrix, DTS, Xtreme, LinuxNet, NZWireless - did you have staff there? If not, why not? What would make you come along next time? 2) the content I made the comment at the time that I wouldn't want to see more vendor content. I realised afterwards that that wasn't strictly fair - we're all vendors in one way or another, and some of the vendor presentations were amongst the most interesting at the conference. I think what I was driving at was "I don't want to watch vendors present regurgitations of the whitepapers on their website", rather than "vendors are evil, get behind me Satan". This conference will remain relevant if you get information in it that you can't get anywhere else. 3) "is it technical enough?" People who have interesting things to say or viewpoints to push (think Paul Vixie and Geoff Huston in previous years, and Hamish Macewan this year) are often the folks who leave a lasting impression, regardless of their technical merit (or more often, lack thereof). Conversely, it'd be a sorry conference if the occasional paper didn't sneak in that needed more than high school math to understand - it's always good to have a few papers that make you go "Huh? WTF is s/he talking about?". So I'd like to make a case for "papers from people who know and care about what they're talking about, regardless of whether they are technical or not". Having said that, I wouldn't want the conference to be any less technical, since the easiest way of meeting the above criteria is to have reasonably technical presentations. 4) should we have a sysadmin stream? If you want to run an SA stream to get more punters through the door, then don't bother, it feels about the right size now. So a stream that was concerned with Oracle DBA'ing, or virus scanning on desktop machines, and which was clearly aimed at a different target user group than the current attendees seems a little pointless. Of course, it is naive to suggest that system administration and network operations are somehow foreign to each other - most of us do elements of both. So if there was a stream that was "system administration for network operators" that could attract some interesting papers on (for eg) nagios, or snmp daemons, or LDAP, or cool radius hacks, or asterisk, or spam handling, or similar then I think I'd be all for it. 5) should we align with another conference/body? If it makes it easier to run the gig by getting some support from the likes of InternetNZ, then I'd be calm with that, it'd be a shame to see this fail because of the burden on volunteers. However, this is now clearly a successful and vibrant conference in its own right - I'm not sure that running the conference in conjunction with something like Govis would achieve anything positive. 6) should we publish proceedings? Seems like a good idea if you want students/academics to participate (something I think we should encourage), but it's yet another job for a volunteer, to apply for the ISSN number, and put such a document together. Cheers Si

3 2

(Fwd) Re: ICANN Wellington
by Nick Wallingford 28 Mar '06

28 Mar '06

------- Forwarded message follows ------- Sorry - I did follow up with a posting that got rejected and I'd left office by then. It does need Real Player or equivalent, as the audio/video is coming straight from ICANN, their encoding, their format... Nick On 29 Mar 2006 at 8:45, Juha Saarinen wrote: > Nick Wallingford wrote: > > There's a page with an IRC channel and the streaming audio/video of > > the events in the Illot Theatre, where some of the activities of the > > ICANN conference are happening. > > Hmm... need more coffee, or a bigger font. Read that as "... the events > in the Idiot Theatre". > > > I'm hoping that the channel will be monitored through today's > > sessions to take remote questions. > > > > http://www.icann.org.nz/irc.htm > > Needs RealPlayer? > > -- > Juha ------- End of forwarded message -------

1 0

ICANN Wellington
by Nick Wallingford 28 Mar '06

28 Mar '06

There's a page with an IRC channel and the streaming audio/video of the events in the Illot Theatre, where some of the activities of the ICANN conference are happening. I'm hoping that the channel will be monitored through today's sessions to take remote questions. http://www.icann.org.nz/irc.htm Nick Wallingford

2 2

.nz Whois Unavailable
by David Zanetti 27 Mar '06

27 Mar '06

Announcing on behalf NZRS: Due to a failure in one of the SRS sites, whois.srs.net.nz had to be switched from one site to another. While DNS propogates, you may find problems talking to whois.srs.net.nz. Some registrar sites may be okay, depending on exactly how they query whois (XML or using a name other than whois.srs.net.nz). Should be all resolved in a few hours (since that's the TTL :) ) -- David Zanetti <david.zanetti(a)catalyst.net.nz> Team Leader, Systems Administration Catalyst IT Limited +64-4-8032233 +64-21-402260

1 0