- NZNOG - lists.nznog.org

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

06 May '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.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.129.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, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.90.128.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.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, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 202.169.176.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.78.128.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 218.100.52.0/23^23-29, 220.233.4.0/23^23-29, 58.87.6.0/24^24-29, 58.96.0.0/24^24-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-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.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.5.127.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.15.243.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.187.0/24^24-29, 203.18.197.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.79.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090409 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 112.141.0.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.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.129.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, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 118.127.176.0/20^20-29, 119.161.64.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, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 118.127.168.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.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.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.136.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 117.18.238.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.100.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 110.76.128.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.232.0/24^24-29, 117.18.235.0/24^24-29, 117.18.237.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.84.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.140.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.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.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090507 source: NZRR ------------------------------------------------------------

1 0

Wholesale DSL Opportunity
by Ben Cornish 05 May '09

05 May '09

All, We are looking at expanding our national Australian network into New Zealand, and as such we are looking for a partner to assist us with this. In the short term, we are looking for Transit and also access to Telecom NZ DSL tails(to be handed off as L2TP sessions over Ethernet preferably). Handoff location would be Sky Tower. Is there anyone interested in this opportunity - please contact me off list Thanks Ben Cornish National Network Manager Direct 07 3234 9302 Direct: 02 8235 3520 Mobile 0417 617 204 Email mailto:benc(a)brennanit.com.au Web http://www.brennanit.com.au/ http://www.brennanit.com.au/

1 0

Re: [nznog] 922Mhz SRD Link
by Brislen, Paul, VF-NZ 01 May '09

01 May '09

Hi all. We can't make any public statement about this interference until after the court hearing, early next week, but after that I'm happy to get one of the network guys to come in and chat about it with you if a: that would help, b: that's of interest and c: they're not already here under their own steam. Cheers Paul -------------------------------------------------------------------- This message was sent from my BlackBerry Wireless Handheld from Vodafone ________________________________ From: nznog-bounces(a)list.waikato.ac.nz To: NZNOG(a)list.waikato.ac.nz Sent: Sat May 02 08:55:23 2009 Subject: Re: [nznog] 922Mhz SRD Link Thanks Ian, Yes I believe that this is likely to be the same problem and the issue is not just causing problems for Vodafone but also smaller operators. The fact that MED have confirmed that they are operating within the allowable channels is of some concern as this would mean there is little that can be done however using equipment legal or not that can squash competition is surely an anticompetitive act. That aside I have completed another can of the area and was wrong on the power levels received from a 3rd cell phone operator, it was just over 2V/m and I’m pretty sure a signal this strong is really not healthy. This was obtained from 150/200m away. Not trying to get up in anyone’s face here but I wonder if in fact Telecom are being blamed for something that is being caused by other vendors networks as well. Have MED created some of the issues by slicing the available channels too fine as was the case with out tests of the WiMAX gear recently. And If MED has and is allowing the deployment of equipment that is making the public spectrum un-usable and they can not force the vendors to clean up their act then maybe they need to look at opening up some more USABLE public spectrum rather than just putting it up for auction where again only the big players have the funds available to purchase these ranges (and associated equipment). Regards Andrew -----Original Message----- From: Ian Batterbee [mailto:ibatterb(a)gmail.com] Sent: Friday, May 01, 2009 10:01 PM To: andrew(a)borg.co.nz Subject: Re: [nznog] 922Mhz SRD Link http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5&objectid=10569… relevant maybe ? andrew(a)borg.co.nz wrote, On Fri 01/05/2009 19:06: Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew ________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ----------------------------------------------------------------------------------------------- Unless otherwise stated, any views or opinions expressed are solely those of the author and do not represent those of Vodafone New Zealand Limited.

3 2

Re: [nznog] 922Mhz SRD Link
by andrew＠borg.co.nz 01 May '09

01 May '09

Thanks Ian, Yes I believe that this is likely to be the same problem and the issue is not just causing problems for Vodafone but also smaller operators. The fact that MED have confirmed that they are operating within the allowable channels is of some concern as this would mean there is little that can be done however using equipment legal or not that can squash competition is surely an anticompetitive act. That aside I have completed another can of the area and was wrong on the power levels received from a 3rd cell phone operator, it was just over 2V/m and I'm pretty sure a signal this strong is really not healthy. This was obtained from 150/200m away. Not trying to get up in anyone's face here but I wonder if in fact Telecom are being blamed for something that is being caused by other vendors networks as well. Have MED created some of the issues by slicing the available channels too fine as was the case with out tests of the WiMAX gear recently. And If MED has and is allowing the deployment of equipment that is making the public spectrum un-usable and they can not force the vendors to clean up their act then maybe they need to look at opening up some more USABLE public spectrum rather than just putting it up for auction where again only the big players have the funds available to purchase these ranges (and associated equipment). Regards Andrew -----Original Message----- From: Ian Batterbee [mailto:ibatterb(a)gmail.com] Sent: Friday, May 01, 2009 10:01 PM To: andrew(a)borg.co.nz Subject: Re: [nznog] 922Mhz SRD Link http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5 <http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5&objectid=1 0569875> &objectid=10569875 relevant maybe ? andrew(a)borg.co.nz wrote, On Fri 01/05/2009 19:06: Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew _____ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] The Internet is in the news!
by Yun Huang Yong 01 May '09

01 May '09

I think this is the Onion piece: http://preview.tinyurl.com/d5h8np At 09:23 AM 1/05/2009, Ian Batterbee wrote: >That was so bad I thought I was reading an article from the onion! > >Ruh roh. We'd better all upgrade to Internet 2. -- (__) Share what you know. Yun Huang Yong `\------(oo) Learn what you don't. gumby(a)mooh.org || (__) --' goosmurf(a)yahoo.com \|/ ||w--|| \|/ --

12 12

922Mhz SRD Link
by andrew＠borg.co.nz 30 Apr '09

30 Apr '09

Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew

1 0

Re: [nznog] The Internet is in the news!
by Scott Weeks 30 Apr '09

30 Apr '09

> >So would you trust a guy in a pink Hawaiian shirt to analyse and > >recommend the future of the internet? Being from Hawaii no, I wouldn't... ;-) Try something like these instead. http://www.alohashirtshop.com/docs/view_image.php?id=11361&width=608 http://www.hawaiian-shirt.net/paradise_found/pf08/bamboo_embroidery_bk_pf.j… ---------- bmanning(a)vacation.karoshi.com wrote: -------------- From: bmanning(a)vacation.karoshi.com pragmatically, WTF are folks going to do when you can't get more IPv4 space from APNIC? Pick the best answer(s): ) IPv6 ) NATs all the way down ) hijack space from others ) find a new line of work as a beer-bottle washer -------------------------------------------------------------- Ipv6 and whatever the new name for NAT-PT is. Then LISP? http://www.1-4-5.net/~dmm/lisp scott ------------------- ------------------- -------------------

1 0

Re: [nznog] The Internet is in the news!
by Scott Weeks 30 Apr '09

30 Apr '09

At 09:23 AM 1/05/2009, Ian Batterbee wrote: >That was so bad I thought I was reading an article from the onion! > >Ruh roh. We'd better all upgrade to Internet 2. -------- gumby_lists(a)mooh.org wrote: -------- From: Yun Huang Yong <gumby_lists(a)mooh.org> I think this is the Onion piece: http://preview.tinyurl.com/d5h8np ------------------------------------------------- That's just about the silliest thing I have seen! "The internet has been up for 5000 days, about 13 years, and hasn't broken down once." According to that the internet was 'started' in 1996! (See RFC 1 by Steve Crocker April 1969) I wonder what the hell I was on in 1987! Surely they wouldn't want to know about the introduction section of RFC 1254: A large number of widely dispersed Internet sites experienced simultaneous slowdown or cessation of networking services for prolonged periods... "youtube transmits more data than the internet." Wow, I didn't know youtube was out of band... ;-) I think the pink aloha shirt was affecting the brain of "sunrise gadget guy". That thing is worse that the old Magnum PI shirts! http://www.mokuman.com/images/magnumpi-shirt_header534.jpg scott ------------------- -------------------- --------------------

2 1

Re: [nznog] The Internet is in the news!
by Stu Fleming 30 Apr '09

30 Apr '09

Isn't a "brown-out" what an "ohnosecond" used to be called, being the approximate period of time between making a live config change and discovering the device non-responsive as a result? Brown-out being more expressive as it also describes the effect on the operator succinctly.

1 0

The Internet is in the news!
by Nathan Ward 30 Apr '09

30 Apr '09

http://technology.timesonline.co.uk/tol/news/tech_and_web/the_web/article61… "Internet users face regular "brownouts" that will freeze their computers as capacity runs out in cyberspace, according to research to be published later this year." Ruh roh. We'd better all upgrade to Internet 2. That beer Jamie made me try last night was pretty good. I forget what it was called. Phew. -- Nathan Ward

5 4

180/8 and 183/8 allocated to APNIC
by Leo Vegoda 30 Apr '09

30 Apr '09

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

1 0

The New Zealand Network Operators' Group
by Donald Neal 30 Apr '09

30 Apr '09

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

1 0

Two /8s allocated to APNIC from IANA (180/8, 183/8)
by Elly Tawhai 30 Apr '09

30 Apr '09

_______________________________________________________________________ Two /8s allocated to APNIC from IANA (180/8, 183/8) _______________________________________________________________________ Hi NZNOG Community, The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in April 2009 and will be making allocations from these ranges in the near future: 180/8 183/8 Reachability and routability testing of the new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html 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

Re: [nznog] CallPlus Routing
by Stu Fleming 29 Apr '09

29 Apr '09

> > On 30/04/2009, at 12:17 AM, Bradley Scarisbrick wrote: >> > It appears fears of an outbreak were unfounded, CP NOC is alive and >> > well, >> > and with a top notch sense of humor for the late shift ... >> > > > Graveyard shift, perhaps When the WHO downgraded the Mexican flu death toll from 152 to 7 the other day, my first thought was a re-enactment of "From Dusk till Dawn"...145 zombies wandering around looking for networking jobs...

1 0

Re: [nznog] CallPlus Routing
by Stephen Barker 28 Apr '09

28 Apr '09

Will oinkment help? Sorry, I'll crawl back under my rock now. Steve > -----Original Message----- > From: Bradley Scarisbrick [mailto:bradleys(a)republic.net.nz] > Sent: Thursday, 30 April 2009 12:18 a.m. > To: NZNOG(a)list.waikato.ac.nz > Subject: Re: [nznog] CallPlus Routing > > It appears fears of an outbreak were unfounded, CP NOC is > alive and well, > and with a top notch sense of humor for the late shift ... > > > On Wed, 29 Apr 2009 20:31:17 +1000, "Sean K. Finn" > <Sean.Finn(a)ozservers.com.au> wrote: > > Maybe the swine virus is really a Zombie virus in disguise. Uh oh. > > > > -----Original Message----- > > From: nznog-bounces(a)list.waikato.ac.nz > > [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Dean > Pemberton > > Sent: Wednesday, 29 April 2009 7:50 PM > > To: Bradley Scarisbrick > > Cc: NZNOG(a)list.waikato.ac.nz > > Subject: Re: [nznog] CallPlus Routing > > > > Zombie NOC...... Coooooool! > > > > =P > > Dean > > > > Bradley Scarisbrick wrote: > >> Could someone from CallPlus please contact me regarding an > issue with > >> routing to/from that network, CallPlus noc appears lifeless :) > >> > >> Thanks > >> --- > >> > >> Bradley Scarisbrick > >> > >> > >> _______________________________________________ > >> 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 > > -- > --- > > Bradley Scarisbrick > Creative ">P: +64 9 523 5620 > F: +64 9 523 5621 > M: +64 21 545 960 > W: http://www.republic.net.nz > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.12.3/2076 - Release > Date: 04/28/09 18:02:00 > >

1 0

CallPlus Routing
by Bradley Scarisbrick 28 Apr '09

28 Apr '09

Could someone from CallPlus please contact me regarding an issue with routing to/from that network, CallPlus noc appears lifeless :) Thanks --- Bradley Scarisbrick

5 5

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

28 Apr '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:AS23958 descr: advertised to AS9560 by DTS Ltd - AS23958 members: 202.68.94.0/23^23-29, 202.174.178.0/23^23-29, 202.174.190.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070907 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23958 descr: advertised to AS9560 by DTS - AS23958 members: 210.48.160.0/20^20-29, 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: technical(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090429 source: NZRR ------------------------------------------------------------

1 0

Domain Propagation
by Thomas Rowley 27 Apr '09

27 Apr '09

Lately I've had a lot of issues with domain nameserver changes taking *ages*to propagate in NZ. They seem to propogate really quickly everywhere else in the world from what i can tell. Do some NZ ISP's take longer to update their DNS records for some reason? Anyone else experienced this? Cheers Thomas

18 27

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

27 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081124 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR ------------------------------------------------------------

1 0

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

27 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081203 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ LTD - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR ------------------------------------------------------------

1 0

Website
by Richard Nelson 27 Apr '09

27 Apr '09

Who is maintaining the NZNOG website at the moment? I'm trying to find some slides that were presented at NZNOG'08 but the links to the slides archives now redirect to the NZNOG'09 page. I was wondering if those slide sets are still available? Thanks, Richard.

3 2

APNIC 28 fellowships - apply now
by Srinivas (Sunny) Chendi 25 Apr '09

25 Apr '09

________________________________________________________________________ The APNIC 28 fellowship program ________________________________________________________________________ Dear At APNIC, we understand that it may be difficult for our members from developing economies to attend APNIC meetings. In response, APNIC provides the fellowship awards to enable people from these developing economies to attend the APNIC meeting free of charge. As an APNIC fellow, you can: ---------------------------- - Acquire hands-on experience in IPv6 transition and deployment strategies - Attend all workshops and tutorials at APNIC 28 - Participate in policy discussions that will affect how your organization accesses Internet number resources - Meet a wide range of people in the Internet industry from around the world For more information about the fellowship award packages, selection process, and submitting an application, please visit our website: http://meetings.apnic.net/28/fellowship Deadline -------- The deadline for submissions is Thursday, 21 May 2009. Sincerely, ________________________________________________________________________ Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3189 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

Telstra IP: 218.101.59.4
by Simon Lyall 23 Apr '09

23 Apr '09

Could whoever is in charge of this Proxy/Spider/whatever please contact me ASAP. I've blocked you for now after I unsuccessfully tried to contact you yesterday and had problems again today. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 1

Two blocks of AS Numbers allocated
by Leo Vegoda 22 Apr '09

22 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA AS Numbers registry has been updated to reflect the allocation of two blocks of AS Numbers recently. 53248-54271 Assigned by ARIN whois.arin.net 2009-04-21 54272-55295 Assigned by ARIN whois.arin.net 2009-04-21 The registry can be found at: http://www.iana.org/assignments/as-numbers/as-numbers.xml Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFJ78q5vBLymJnAzRwRAsxhAKCvxeFIPNw/gZnUDnH0Q51wWR7fiACeMKe+ XnUY36jXeaFRj2Ecn+4ZgFE= =cnqY -----END PGP SIGNATURE-----

1 0

What happens when someone attacks your fibre networks?
by Matthew Poole 22 Apr '09

22 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://perens.com/works/articles/MorganHill/ "The city of Morgan Hill and parts of three counties lost 911 service, cellular mobile telephone communications, land-line telephone, DSL internet and private networks, central station fire and burglar alarms, ATMs, credit card terminals, and monitoring of critical utilities. In addition, resources that should not have failed, like the local hospital's internal computer network, proved to be dependent on external resources, leaving the hospital with a "paper system" for the day." (continues in the article). To summarise, it's all very well having redundant systems but if someone takes to the telco infrastructure you still need something that's entirely distinct. Otherwise you end up in a wee bit of a pickle. It's a good case, as if further ones were needed, against BPL. If the power's up but the telco networks are down, interference with ham radio is a "bad thing"[tm]. - -- Matthew Poole "Don't use force. Get a bigger hammer." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ78f8TdEtTmUCdpwRAtuHAJ9ytrxlD9yY7sTN1ScPldX5qo4ynwCeK4YM HHa8f1TryqH5jpfTbspTXfM= =QKQe -----END PGP SIGNATURE-----

2 1