- NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 26 Apr '10

26 Apr '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-ROUTES6:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2404:3800:0:0:0:0:0:0/32^32-64, 2001:0dce:0:0:0:0:0:0/32^32-64, 2001:0dce:e000:0:0:0:0:0/48^48-64, 2001:0df0:004a:0:0:0:0:0/48^48-64, 2404:1800:0:0:0:0:0:0/32^32-64, 2001:4530:0:0:0:0:0:0/32^32-64, 2400:b400:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100307 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES6:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2404:3800:0:0:0:0:0:0/32^32-64, 2001:0dce:0:0:0:0:0:0/32^32-64, 2001:0dce:e000:0:0:0:0:0/48^48-64, 2001:0df0:004a:0:0:0:0:0/48^48-64, 2404:1800:0:0:0:0:0:0/32^32-64, 2001:4530:0:0:0:0:0:0/32^32-64, 2400:b400:0:0:0:0:0:0/32^32-64, 2404:0130:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig.wallace(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100427 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Apr '10

26 Apr '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 121.79.224.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 116.90.129.0/24^24-29, 116.90.138.0/24^24-29, 116.90.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.221.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 210.7.46.0/24^24-29, 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig.wallace(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100421 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 121.79.224.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 116.90.129.0/24^24-29, 116.90.138.0/24^24-29, 116.90.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.221.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 210.7.46.0/24^24-29, 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lee.carter(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100427 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Apr '10

26 Apr '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 121.79.224.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 116.90.129.0/24^24-29, 116.90.138.0/24^24-29, 116.90.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.221.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 210.7.46.0/24^24-29, 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig.wallace(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100421 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 121.79.224.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 116.90.129.0/24^24-29, 116.90.138.0/24^24-29, 116.90.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.221.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 210.7.46.0/24^24-29, 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lee.carter(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100427 source: NZRR ------------------------------------------------------------

1 0

DNSSEC Talk Invitation (Wellington)
by Paul McKitrick 25 Apr '10

25 Apr '10

Hi All, I thought that this community may be interested in attending a talk this week on DNSSEC. What: Wellington ISIG Chapter Monthly Meeting (http://isig.org.nz/) Where: Confidential Bar, 65 The Terrace, Wellington (http://bit.ly/9iOvYS - the entrance is a standalone doorway opening to stairs leading down) When: 6pm Thursday 29 April 2010 Bio: Jay Daley is the CEO of .nz Registry Services, who operate the .nz top level domain and are aiming to implement DNSSEC later this year. Jay was previously the CTO of .uk and has only been moderately deskilled by management so should be able to deliver a presentation on DNSSEC that is roughly right. Synopsis: The talk will cover the basics of DNSSEC, including - what problems it solves, with particular reference to the Great Firewall of China incident - how the keys and signatures work, the role of hashing and the chain of trust (with pretty diagrams!) - operational impact, size, key management and timings - tools and architecture - applications that are now unleashed because of DNSSEC If there is time then Jay may also rant about how root X.509 certificates are a confidence trick and how DNSSEC will finally give us a PKI. Regards, Paul. Paul McKitrick (ITCP) Manager Compliance and Security Domain Name Commission Email: mcs(a)dnc.org.nz Fax: +64 4 495 2115 PO Box 11-881, Wellington, 6142 New Zealand

1 0

Re: [nznog] NZNOG Digest, Vol 88, Issue 15
by chris＠amuri.net 23 Apr '10

23 Apr '10

-original message- Subject: NZNOG Digest, Vol 88, Issue 15 From: nznog-request(a)list.waikato.ac.nz Date: 24/04/2010 12:00 pm Send NZNOG mailing list submissions to nznog(a)list.waikato.ac.nz To subscribe or unsubscribe via the World Wide Web, visit http://list.waikato.ac.nz/mailman/listinfo/nznog or, via email, send a message with subject or body 'help' to nznog-request(a)list.waikato.ac.nz You can reach the person managing the list at nznog-owner(a)list.waikato.ac.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of NZNOG digest..." Today's Topics: 1. NZRR Route Registry Update (NZRR Database Notifications) 2. Xtra BBA Issue with Cisco 877 (Terry Wilson) 3. Re: Xtra BBA Issue with Cisco 877 (Philip D'Ath) 4. Re: Request for Information from anyone providing V6 services in NZ (Joel Wiramu Pauling) 5. Re: Xtra BBA Issue with Cisco 877 (Terry Wilson) ---------------------------------------------------------------------- Message: 1 Date: Fri, 23 Apr 2010 12:03:29 +1200 From: NZRR Database Notifications <rpsl-admin(a)nzix.net> To: nznog(a)list.waikato.ac.nz Subject: [nznog] NZRR Route Registry Update Message-ID: <E1O56Mj-0004w8-I7(a)totti.citylink.co.nz> 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: AS9281:RS-ROUTES:AS38477 descr: Route set advertised to AS9281 by Unleash - AS38477 members: 113.130.120.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: michael(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100415 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS38477 descr: advertised to AS9281 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 131.203.133.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100423 source: NZRR ------------------------------------------------------------ ------------------------------ Message: 2 Date: Fri, 23 Apr 2010 12:30:20 +1200 From: "Terry Wilson" <terry(a)pds-dn.co.nz> To: <NZNOG(a)list.waikato.ac.nz> Subject: [nznog] Xtra BBA Issue with Cisco 877 Message-ID: <8C5232314BEE4D43A980918BD0EE1B7C7ED5F3(a)pds-mail02.PDS> Content-Type: text/plain; charset="us-ascii" Afternoon, I'm struggling with an issue that I'm hoping someone might be able to shed some light on for us. New connection in Queenstown (new phone + data) with ADSL enabled on line. Had some issues initially with the connection going down while the IP address was assigned, Telecom have resolved this and the 2Wire modem now reports that it is up and connected. Trying to connect a Cisco 877 into the same line, we get ATM to come up (CD light is on) but PPP will not come up; talking user through it but everything looks ok. I have had the router sent back down here and it tests fine on our existing Telecom ADSL test connection, back on site and it still won't get an IP or authenticate. T3G coverage is pretty rubbish so I can't remote control from here; may need to find a competent tech in Queenstown to go over and have a look for us. Any suggestions would be appreciated; been working on this with Telecom for four days now and as far as they are concerned it's a Cisco issue. Thanks, Terry ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

1 0

Xtra BBA Issue with Cisco 877
by Terry Wilson 22 Apr '10

22 Apr '10

Afternoon, I'm struggling with an issue that I'm hoping someone might be able to shed some light on for us. New connection in Queenstown (new phone + data) with ADSL enabled on line. Had some issues initially with the connection going down while the IP address was assigned, Telecom have resolved this and the 2Wire modem now reports that it is up and connected. Trying to connect a Cisco 877 into the same line, we get ATM to come up (CD light is on) but PPP will not come up; talking user through it but everything looks ok. I have had the router sent back down here and it tests fine on our existing Telecom ADSL test connection, back on site and it still won't get an IP or authenticate. T3G coverage is pretty rubbish so I can't remote control from here; may need to find a competent tech in Queenstown to go over and have a look for us. Any suggestions would be appreciated; been working on this with Telecom for four days now and as far as they are concerned it's a Cisco issue. Thanks, Terry ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

2 2

Request for Information from anyone providing V6 services in NZ
by Joel Wiramu Pauling 22 Apr '10

22 Apr '10

Hi all, I am after information regarding state of play around V6 deployment, I understand some of this may not be publicly sharable but would appreciate any info, especially in written form. Primarily interested in things like: * Is your company offering V6 services a) Residential - To the greater v6 internet. b) Corporate Wan - Are you delivering a v6 WAN services, and if able to disclose, who has been asking for it? * Are you providing V6 content services (WebSites, DNS etc) for clients? * Where have you seen demand, and who is asking for it? * Are the RFP's you are seeing including V6 as a component? * Are you designing V6 centric services Any info appreciated Kind regards -JoelW

2 2

NZRR Route Registry Update
by NZRR Database Notifications 22 Apr '10

22 Apr '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: AS9281:RS-ROUTES:AS38477 descr: Route set advertised to AS9281 by Unleash - AS38477 members: 113.130.120.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: michael(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100415 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS38477 descr: advertised to AS9281 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 131.203.133.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100423 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] sorry for the spam
by Bigalownz 21 Apr '10

21 Apr '10

nope this one http://www.pcworld.com/businesscenter/article/194635/drugdealing_spammers_h… and my password was random numbers and letters i never use words ----- Original Message ----- From: "Jay Daley" <jay(a)nzrs.net.nz> To: "Bigalownz" <bigalownz(a)gmail.com> Sent: Thursday, April 22, 2010 12:52 AM Subject: Re: [nznog] sorry for the spam On 21/04/2010, at 12:23 PM, Bigalownz wrote: > my gmail account got hacked and sent out spam > so the email was not from me Out of curiosity, two questions: 1. Is your password easily guessable? 2. Did you log into your gmail account during this incident? http://www.computerworld.com/s/article/9175081/A_Chinese_ISP_momentarily_hi… regards Jay > > thanks > Sean > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog -- Jay Daley Chief Executive .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 931 6977 mobile: +64 21 678840

1 0

sorry for the spam
by Bigalownz 20 Apr '10

20 Apr '10

my gmail account got hacked and sent out spam so the email was not from me thanks Sean

1 0