- NZNOG - lists.nznog.org

Web Load Balancers
by Skeeve Stevens 14 Mar '10

14 Mar '10

Hey guys, I am looking to provide a load balancing solution to a client for an online ordering system which will use SSL. I am interested in different solutions being deployed out there and any experiences with the following: - Squid reverse proxy - Cisco Content Services (CSS) Switch 11500 series - Radware AppDirector 1000 - CoyotePoint e250GX - Any others? ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

20 21

international bandwidth pricing
by James Jones 12 Mar '10

12 Mar '10

I am doing some research. What is the going rate for wholesale international bandwidth these days. -- James Jones +1-413-667-9199 james(a)freedomnet.co.nz

1 0

Re: [nznog] Web Load Balancers
by Dobbins, Roland 11 Mar '10

11 Mar '10

On Mar 12, 2010, at 10:10 AM, lenz wrote: > if you need massive HA you need more than a loadbalancer though but i > am sure you know that :-) Yes, of course - please note that I'm not the original poster, just a respondent. ;> ----------------------------------------------------------------------- Roland Dobbins <rdobbins(a)arbor.net> // <http://www.arbornetworks.com> Injustice is relatively easy to bear; what stings is justice. -- H.L. Mencken

1 0

Re: [nznog] Web Load Balancers
by lenz 11 Mar '10

11 Mar '10

how big is your load and how massive needs the system to be? i used pound for a while back in the days, nowadays my standard setup is nginx and then whatever my application needs. having nginx in front of everything makes things in general way more maintainable and the loadbalancing characteristic is good enough to call it a loadbalancer. if you need massive HA you need more than a loadbalancer though but i am sure you know that :-) cheers lenz On Fri, Mar 12, 2010 at 4:01 PM, Dobbins, Roland <rdobbins(a)arbor.net> wrote: > > On Mar 12, 2010, at 9:56 AM, Nathan Ward wrote: > >> Do Foundry no longer exist in this space? They're called Brocade now, but when I used to do this sort of thing lots they were the guys to beat. > > Yes, Foundry, you're right - the other one is called Netstream, I think? > >> Also let's not CC AusNOG or other lists with this sort of thing. When their mail server starts working there's going to be either a whole bunch of bounces, or a weird disjointed conversation over there, or more likely both. Keep it to one list yeah? > > I didn't realize there was a problem w/AusNOG. The original conversation was crossposted (generally a bad idea, I agree),a and so I thought I was doing the Right Thing by resuming it, apologies. > > ;> > > ----------------------------------------------------------------------- > Roland Dobbins <rdobbins(a)arbor.net> // <http://www.arbornetworks.com> > > Injustice is relatively easy to bear; what stings is justice. > > -- H.L. Mencken > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > -- twitter: @norbu09 current project: iWantMyName.com painless domain registration (finally) -- twitter: @norbu09 current project: iWantMyName.com painless domain registration (finally)

1 0

Anyone interested in talking about F5
by Robert Cotter 11 Mar '10

11 Mar '10

If anyone wants to talk about F5 load balances Send me an email off list or give me a call to discuss. Regards Robert Cotter Sales Engineer rcotter(a)distributioncentral.co.nz<UrlBlockedError.aspx> Distribution Central NZ Unit 2, Level 1, 194 Victoria Street West, Auckland 1001, New Zealand. Mb +64 21 675550, T +64 9 309 8277, F +64 9 309 8276 www.distributioncentral.co.nz<http://www.distributioncentral.co.nz/> Distributor of : Acronis, Avaya, Clearswift, Crossbeam, Cytrack, Extreme Networks, F5, Force10 Networks, Fortinet, Infoblox, NET, Riverbed, Tippingpoint. ________________________________ This email is for the intended recipient(s) only. Be advised that if you have received this email in error that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. The sender cannot guarantee that this email or any attachment to it is free of computer viruses or other conditions which may damage or interfere with data, hardware or software with which it might be used. If you have received this email in error, please notify Distribution Central on +61 2 8986 5000 or notify sender.

1 0

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

11 Mar '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 147.209.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 113.203.0.0/17^17-29, 180.181.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 112.141.0.0/18^18-29, 112.141.128.0/18^18-29, 114.129.128.0/18^18-29, 125.253.0.0/18^18-29, 180.200.128.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 203.208.64.0/18^18-29, 210.185.0.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 115.69.160.0/19^19-29, 118.127.0.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, 119.252.0.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.254.64.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.200.192.0/19^19-29, 180.222.0.0/19^19-29, 182.48.128.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 202.181.0.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.142.128.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 221.121.128.0/19^19-29, 58.84.224.0/20^20-29, 111.67.0.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 112.141.96.0/20^20-29, 112.141.224.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.240.208.0/20^20-29, 117.55.224.0/20^20-29, 119.10.128.0/20^20-29, 119.47.112.0/20^20-29, 119.63.208.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 125.254.96.0/20^20-29, 175.107.160.0/20^20-29, 202.3.192.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.86.96.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.174.160.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.161.128.0/20^20-29, 203.212.144.0/20^20-29, 210.56.32.0/20^20-29, 211.27.192.0/20^20-29, 110.44.24.0/21^21-29, 112.141.112.0/21^21-29, 112.141.240.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.90.128.0/21^21-29, 116.212.64.0/21^21-29, 116.240.160.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.200.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 121.200.208.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.201.72.0/21^21-29, 125.213.160.0/21^21-29, 175.107.176.0/21^21-29, 175.176.200.0/21^21-29, 180.92.192.0/21^21-29, 180.92.216.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 182.23.192.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.36.16.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.56.48.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.48.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.16.0/21^21-29, 202.169.208.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.149.80.0/21^21-29, 203.170.8.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 210.50.56.0/21^21-29, 58.179.60.0/22^22-29, 58.179.124.0/22^22-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 59.86.184.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.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 111.125.160.0/22^22-29, 111.235.140.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 114.111.144.0/22^22-29, 114.141.104.0/22^22-29, 114.142.160.0/22^22-29, 115.69.28.0/22^22-29, 116.90.72.0/22^22-29, 116.240.184.0/22^22-29, 119.15.96.0/22^22-29, 119.161.84.0/22^22-29, 119.161.92.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 124.248.140.0/22^22-29, 125.254.112.0/22^22-29, 175.107.184.0/22^22-29, 175.111.100.0/22^22-29, 180.148.24.0/22^22-29, 180.148.176.0/22^22-29, 180.189.152.0/22^22-29, 180.222.192.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.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.37.32.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.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.130.32.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.200.0/22^22-29, 202.169.216.0/22^22-29, 202.177.220.0/22^22-29, 203.0.124.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.80.60.0/22^22-29, 203.82.100.0/22^22-29, 203.83.208.0/22^22-29, 203.92.28.0/22^22-29, 203.99.132.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.156.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.188.216.0/22^22-29, 203.190.232.0/22^22-29, 203.202.132.0/22^22-29, 203.211.56.0/22^22-29, 203.212.128.0/22^22-29, 203.217.152.0/22^22-29, 210.11.144.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 59.86.170.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.76.128.0/23^23-29, 111.125.168.0/23^23-29, 114.111.148.0/23^23-29, 114.134.176.0/23^23-29, 114.141.108.0/23^23-29, 114.142.168.0/23^23-29, 115.178.6.0/23^23-29, 116.90.138.0/23^23-29, 116.90.140.0/23^23-29, 118.107.60.0/23^23-29, 119.161.80.0/23^23-29, 121.127.196.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 141.243.8.0/23^23-29, 141.243.32.0/23^23-29, 175.45.64.0/23^23-29, 180.235.104.0/23^23-29, 199.212.92.0/23^23-29, 202.4.162.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.8.44.0/23^23-29, 202.12.70.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.62.0/23^23-29, 202.14.248.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.218.0/23^23-29, 202.37.240.0/23^23-29, 202.46.176.0/23^23-29, 202.46.190.0/23^23-29, 202.49.62.0/23^23-29, 202.49.148.0/23^23-29, 202.49.164.0/23^23-29, 202.56.62.0/23^23-29, 202.61.2.0/23^23-29, 202.65.160.0/23^23-29, 202.67.118.0/23^23-29, 202.67.120.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.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.206.0/23^23-29, 202.169.220.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.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.8.18.0/23^23-29, 203.10.76.0/23^23-29, 203.11.92.0/23^23-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100309 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 147.209.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 182.154.0.0/16^16-29, 113.203.0.0/17^17-29, 180.181.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 112.141.0.0/18^18-29, 112.141.128.0/18^18-29, 114.129.128.0/18^18-29, 125.253.0.0/18^18-29, 180.200.128.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 203.208.64.0/18^18-29, 210.185.0.0/18^18-29, 58.96.128.0/19^19-29, 61.245.128.0/19^19-29, 112.141.64.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 115.69.160.0/19^19-29, 118.127.0.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, 119.252.0.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.254.64.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.200.192.0/19^19-29, 180.222.0.0/19^19-29, 182.48.128.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 202.181.0.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.142.128.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 221.121.128.0/19^19-29, 58.84.224.0/20^20-29, 111.67.0.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 112.141.96.0/20^20-29, 112.141.224.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.240.208.0/20^20-29, 117.55.224.0/20^20-29, 119.10.128.0/20^20-29, 119.47.112.0/20^20-29, 119.63.208.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 125.254.96.0/20^20-29, 175.107.160.0/20^20-29, 202.3.192.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.86.96.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.174.160.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.161.128.0/20^20-29, 203.212.144.0/20^20-29, 210.56.32.0/20^20-29, 211.27.192.0/20^20-29, 110.44.24.0/21^21-29, 112.141.112.0/21^21-29, 112.141.240.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.90.128.0/21^21-29, 116.212.64.0/21^21-29, 116.240.160.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.200.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 121.200.208.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.201.72.0/21^21-29, 125.213.160.0/21^21-29, 175.107.176.0/21^21-29, 175.176.200.0/21^21-29, 180.92.192.0/21^21-29, 180.92.216.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 182.23.192.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.36.16.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.56.48.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.48.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.16.0/21^21-29, 202.169.208.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.149.80.0/21^21-29, 203.170.8.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 210.50.56.0/21^21-29, 58.179.60.0/22^22-29, 58.179.124.0/22^22-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 59.86.184.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.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 111.125.160.0/22^22-29, 111.235.140.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 114.111.144.0/22^22-29, 114.141.104.0/22^22-29, 114.142.160.0/22^22-29, 115.69.28.0/22^22-29, 116.90.72.0/22^22-29, 116.240.184.0/22^22-29, 118.127.56.0/22^22-29, 119.15.96.0/22^22-29, 119.161.84.0/22^22-29, 119.161.92.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 124.248.140.0/22^22-29, 125.254.112.0/22^22-29, 175.107.184.0/22^22-29, 175.111.100.0/22^22-29, 180.148.24.0/22^22-29, 180.148.176.0/22^22-29, 180.189.152.0/22^22-29, 180.222.192.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.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.37.32.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.45.152.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.130.32.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.200.0/22^22-29, 202.169.216.0/22^22-29, 202.177.220.0/22^22-29, 203.0.124.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.80.60.0/22^22-29, 203.82.100.0/22^22-29, 203.83.208.0/22^22-29, 203.92.28.0/22^22-29, 203.99.132.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.156.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.188.216.0/22^22-29, 203.190.232.0/22^22-29, 203.202.132.0/22^22-29, 203.211.56.0/22^22-29, 203.212.128.0/22^22-29, 203.217.152.0/22^22-29, 210.11.144.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 59.86.170.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.76.128.0/23^23-29, 111.125.168.0/23^23-29, 114.111.148.0/23^23-29, 114.134.176.0/23^23-29, 114.141.108.0/23^23-29, 114.142.168.0/23^23-29, 115.178.6.0/23^23-29, 116.90.138.0/23^23-29, 116.90.140.0/23^23-29, 118.107.60.0/23^23-29, 119.161.80.0/23^23-29, 121.127.196.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 141.243.8.0/23^23-29, 141.243.32.0/23^23-29, 175.45.64.0/23^23-29, 180.235.104.0/23^23-29, 199.212.92.0/23^23-29, 202.4.162.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.8.44.0/23^23-29, 202.12.70.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.62.0/23^23-29, 202.14.248.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.218.0/23^23-29, 202.37.240.0/23^23-29, 202.46.176.0/23^23-29, 202.46.190.0/23^23-29, 202.49.2.0/23^23-29, 202.49.62.0/23^23-29, 202.49.148.0/23^23-29, 202.49.164.0/23^23-29, 202.56.62.0/23^23-29, 202.61.2.0/23^23-29, 202.65.160.0/23^23-29, 202.67.120.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.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.206.0/23^23-29, 202.169.220.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.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.8.18.0/23^23-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100312 source: NZRR ------------------------------------------------------------

1 0

Fwd: [members-discuss] Pacific Fibre
by John Humphrey 10 Mar '10

10 Mar '10

Just jumping in a bit - as one of the founders and looking after the tech side, some good feedback from the group - thanks. Agree with Matthew and others - we don't see the need for diversity - SX needed it because there wasn't the alternatives in 2000. Plenty of other systems now exist for diversity, especially ex Australia. We will also do bandwidth swaps on other systems to offer diversity products but most bigger players will buy their own. You might be interested in our latency forecasts. Because we will be a single hop NZ to US, our route length is lowest at 10,500 km. Latency Comparisons Pacific Fibre would have the lowest latency to the US of any existing cable system (latency estimates from other systems' web sites). Sydney to US: .. Pacific Fibre: 65 ms (via NZ) .. Endeavour: 69 ms (via Hawaii) .. Southern Cross: 70 ms (via NZ/Hawaii - landing station to landing station only) .. Southern Cross: 72 ms (via Fiji/Hawaii - landing station to landing station only) .. PPC-1: 87 ms (via Guam/Hawaii) Auckland to US: .. Pacific Fibre: 54 ms (direct to US) .. Southern Cross: 61 ms (via Hawaii - landing station to landing station only) We is designed as a POP to POP system. Re demand Timely with NBN in Australia and UFBI in NZ. We are confident of plenty of demand for Pacific Fibre. Demand is also driven by price of course so watch this space. I have a technical overview document available - mail me off list if you want a copy Cheers John Humphrey T: +64 9 522 2138 | M: +64 21 555 933 E: john(a)johnhumphrey.co.nz | Skype: kiwijohnh LinkedIn: http://www.linkedin.com/in/johnhumphrey -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Robert Larsen Sent: Thursday, March 11, 2010 4:50 PM To: nznog Subject: Re: [nznog] Fwd: [members-discuss] Pacific Fibre And some more info on GZNZ: http://www.geekzone.co.nz/juha/7143 On Thu, Mar 11, 2010 at 4:42 PM, Joel Wiramu Pauling <aenertia(a)aenertia.net> wrote: > More blogging on the topic. Interview with Mark Rushworth > > http://idealog.co.nz/blog/peter-griffin/bigger-faster-more-productive > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Fwd: [members-discuss] Pacific Fibre
by Joel Wiramu Pauling 10 Mar '10

10 Mar '10

This will interest people. Cost is estimated to be around 900 million NZ and to be operational by 2013. Not sure where it will land. -JoelW ---------- Forwarded message ---------- From: Lance Wiggs <lance(a)lancewiggs.com> Date: 11 March 2010 13:45 Subject: [members-discuss] Pacific Fibre To: pag(a)listserver.internetnz.net.nz, InternetNZ Members Discussion List <members-discuss(a)internetnz.net.nz> We are making Pacific Fibre public today. Here is the text of the press release. New Zealand businessmen propose project to build international fibre cable Aim is unlimited high speed broadband for New Zealand and Australia Pacific Fibre, an early stage international fibre venture founded by a group including New Zealand businessmen Stephen Tindall, Sam Morgan and Rod Drury, announced its plans today, aiming to break the digital divide between New Zealand, Australia and the rest of the world. Other founders include Mark Rushworth, former Vodafone Chief Marketing Officer, technology industry veteran John Humphrey, and strategy consultant and entrepreneur Lance Wiggs. Pacific Fibre is engaging in early discussions with cornerstone investors and customers. The group is looking to secure funding and build a 5.12 Terabits/sec capacity fibre cable to be ready in 2013 connecting Australia, New Zealand and the USA - the initial proposal is a cable which will deliver five times the capacity of the existing Southern Cross system. Sam Morgan commented: "We desperately need a cable that is not purely based on profit maximisation, but on delivering unconstrained international bandwidth to everybody, and so we've decided to see whether we can do it ourselves.” Stephen Tindall commented: “The New Zealand Institute identified billions of dollars in economic potential by unleashing the internet, and it is beyond time to address the issue. This is necessary and basic infrastructure – we must decrease the distance between New Zealand and the international markets. Doing so will be incredibly valuable for New Zealand and Australian businesses and consumers. If we are able to deliver on this cable this it could be as valuable to our NZ economy as the quantum leap refrigerated ships were to our export trade many years ago ” "This is a bold vision which, as realists, we know will not be easy to deliver, it will take a huge effort to complete, and has many risks. While we have completed early feasibility work it is essential for people to know we now need to determine the level of interest from potential partners before we go to the next stage of a full business case, risk assessment and proof of concept to take to investors and bankers. We realise the risks are large but are prepared to push through to the next stage. We have released this news today primarily to ensure that any parties who are interested in this space have an opportunity to speak with us during this early planning phase." Pacific Fibre's ambitious aim is to deliver the highest capacity and lowest latency international internet service to Australia and New Zealand by connecting Australia and New Zealand to the USA with 13,000 km of cable. The cable from New Zealand to the USA would be direct, substantially reducing the distance versus existing cables, and thus delivering lower latency, or lag, associated with the cable. The planned cable would also offer potential for branching units to provide connectivity to several Pacific islands. Rod Drury commented: "We are seeing a growing digital divide between New Zealand and the rest of the world. We need this infrastructure if we are serious about growing international businesses from New Zealand. “The introduction of a new cable would drive competition and capacity in the international bandwidth market, building on the success of the Southern Cross cable, which was critical for New Zealand when it was built 10 years ago. This proposed cable would provide internet service providers and large and small businesses with a major boost in capacity and speed, but also give the extra redundancy that another cable provides.” Mark Rushworth commented: “We have a lot of work to do to make this happen and I am excited by the challenge. With 90% of New Zealand internet traffic going offshore, a major boost in international capacity is needed to fix the 7pm bottleneck. The situation is bad now and only going to get worse as the New Zealand Ultra-Fast Broadband initiative and the Australian National Broadband Network start delivering fibre to the premise." “We are seeing a huge increase in demand from consumers and businesses driven by the use of video which is increasing in resolution and use. Businesses love very high resolution multi party video conferencing - all the way up to telepresence systems, while grandparents expect to be able to Skype video their grandchildren - and that too will be in HD or better. But mostly we want to unleash that creative talent New Zealand has, and be on a level footing with the rest of the world.” The current proposed cable configuration would be 13,000 km long, and have two fibre pairs with 64 wavelengths (lambdas) each at 40 Gigabits/sec per lambda. The maximum lit capacity initially would be 5.12 Terabits/sec, but would be upgradeable to over 12 Terabits/sec as the emerging 100 Gbit/sec per lambda technology becomes reality. The newer cable and repeater technology that Pacific Fibre proposes to use will be substantially more easily upgradeable than that of existing cables. Pacific Fibre will seek to work alongside existing industry players and also seek to aggregate any existing initiatives into a unified project. Mr Rushworth commented: “We are delighted by the early interest in Pacific Fibre from industry players and financial backers. We believe a unified approach to building the cable is good news for the entire telecommunications industry, including Telecom, who will finally be able to deliver innovative new services expected as normal in other countries." For more information please contact: Mark Rushworth Mark.Rushworth(a)PacificFibre.net +64 21 244 0777 www.pacificfibre.net Twitter.com/PacificFibre _______________________________________________ members-discuss mailing list members-discuss(a)internetnz.net.nz http://listserver.internetnz.net.nz/mailman/listinfo/members-discuss

6 9

A wonderful dramatic increase in IPv6 allocations
by Terry Manderson 10 Mar '10

10 Mar '10

Hi Folks, Apologies for the cross posting, but I thought many of you might find this interesting. I've bee watching the IPv6 allocation stats with some interest given the implementation of the APNIC policy proposal "prop-073: Simplifying allocation/assignment of IPv6 to APNIC members with existing IPv4 addresses" (authored by Andy Linton and myself) hit the streets in February. Pursuant to the policy recommendations APNIC have made some effort to spread the word and have badged the effort "Kickstart IPv6". Attached is a chart of the 'by month allocation count' since 2005.. You should note that there were 194 allocations/assignments made in ALL of 2009.. So far in 2010 there have been 190 allocations/assignments made.. So.. do you have your v6 allocation yet? .. and the next question, when are you going to route it and use it... I'll be happily watching the v6 routing table :-) Cheers Terry

6 5

Signing of the ARPA zone
by Joe Abley 10 Mar '10

10 Mar '10

Colleagues, This is a technical, operational announcement regarding changes to the ARPA top-level domain. Apologies in advance for duplicates received through different mailing lists. No specific action is requested of operators. This message is for your information only. The ARPA zone is about to be signed using DNSSEC. The technical parameters by which ARPA will be signed are as follows: KSK Algorithm and Size: 2048 bit RSA KSK Rollover: every 2-5 years, scheduled rollover to follow RFC 5011 KSK Signature Algorithm: SHA-256 Validity period for signatures made with KSK: 15 days; new signatures published every 10 days ZSK Algorithm and Size: 1024 bit RSA ZSK Rollover: every 3 months ZSK Signature Algorithm: SHA-256 Authenticated proof of non-existence: NSEC Validity period for signatures made with ZSK: 7 days; zone generated and re-signed twice per day The twelve root server operators [1] will begin to serve a signed ARPA zone instead of the (current) unsigned ARPA zone during a maintenance window which will open at 2010-03-15 0001 UTC and close at 2010-03-17 2359 UTC. Individual root server operators will carry out their maintenance at times within that window according to their own operational preference. The trust anchor for the ARPA zone will be published in the ITAR [2], and in the root zone in the form of a DS record once the root zone is signed. If you have any concerns or require further information, please let me know. Regards, Joe Abley Director DNS Operations, ICANN [1] <http://www.root-servers.org/> [2] <https://itar.iana.org/>

1 0