- NZNOG - lists.nznog.org

Telecom HTTP Cache
by Paul Tinson 16 May '10

16 May '10

Telecom NZ would like to advise that there will be planned work undertaken on the Telecom Broad Band HTTP Cache farm on Thursday the 20th of May. The planned work has a window of 3 am to 6 am. If the date of the work changes there will be an update sent out. There should be little to no impact on international browsing as a bypass will be put in place prior to the work starting. Details ======= Planned Start Date: 20th May 2010 03:00 Planned Finish Date: 20th May 2010 06:00 Expected Impact: Minimal to None due to Cache Bypass If you have any specific questions about this work then please feel free to post the questions on this mailing list/forum and as time allows they will be answered. NB. Please note that the service is only in place for Telecom Broadband Customers and "International" in this case is based on the international routing tables, as such some domestic sites may appear to Telecom as international content. Regards Paul Tinson Senior Specialist Level 9, Mayoral Dr Bldg, 31 Airedale Street Auckland www.telecom.co.nz ________________________________ This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

1 0

ERX(s) wanted
by Sam Deller - Airnet NZ 06 May '10

06 May '10

Understandably this list is not Trademe. But its the only hope in hell of quickly finding a couple of DC gigether flavoured baby Juniper ERX's... Please contact (or flame me) off list if anyone knows of any -Sam

1 0

More .nz domain statistical stuff
by Blair Harrison 06 May '10

06 May '10

Hi Guys, I have been a little slack making pretty graphs lately, but came up with this tonight. Just a correlation between growth in .nz domains, and growth in .nz population from 1994-2009. Interesting to note there are a couple of years where growth in domains outstripped growth in population. 2000/2001 and 2007/2008. Pretty PDF version here: http://jedi.school.nz/nzdg/popvsdomains.pdf And an Excel version here, along with all the usual full dataset of domain info. Interesting effects created by Numbers when exporting to xls in that the graph is all backwards. http://jedi.school.nz/nzdg/nzdomaingrowth-fromnov93-mar10.xls As usual, comments welcome. Cheers, Blair

3 2

Root Zone DNSSEC Deployment Technical Status Update
by Joe Abley 05 May '10

05 May '10

Root Zone DNSSEC Deployment Technical Status Update 2010-05-05 This is the sixth of a series of technical status updates intended to inform a technical audience on progress in signing the root zone of the DNS. ** The final transition to a signed root zone took place today ** on J-Root, between 1700--1900 UTC. ** ** All root servers are now serving a signed root zone. ** ** All root servers will now generate larger responses to DNS ** queries that request DNSSEC information. ** ** If you experience technical problems or need to contact ** technical project staff, please send e-mail to rootsign(a)icann.org ** or call the ICANN DNS NOC at +1 310 301 5817, e-mail preferred ** if possible. ** ** See below for more details. RESOURCES Details of the project, including documentation published to date, can be found at <http://www.root-dnssec.org/>. We'd like to hear from you. If you have feedback for us, please send it to rootsign(a)icann.org. DEPLOYMENT STATUS The incremental deployment of DNSSEC in the Root Zone is being carried out first by serving a Deliberately Unvalidatable Root Zone (DURZ), and subsequently by a conventionally signed root zone. Discussion of the approach can be found in the document "DNSSEC Deployment for the Root Zone", as well as in the technical presentations delivered at RIPE, NANOG, IETF and ICANN meetings. All of the thirteen root servers have now made the transition to the to the DURZ. No harmful effects have been identified. The final root server to make the transition, J-Root, started serving the DURZ in a maintenance window between 1700--1900 UTC on 2010-05-05. Initial observations relating to this transition will be presented and discussed at the DNS Working Group meeting at RIPE 60 in Prague on 2010-05-06. PLANNED DEPLOYMENT SCHEDULE Already completed: 2010-01-27: L starts to serve DURZ 2010-02-10: A starts to serve DURZ 2010-03-03: M, I start to serve DURZ 2010-03-24: D, K, E start to serve DURZ 2010-04-14: B, H, C, G, F start to serve DURZ 2010-05-05: J starts to serve DURZ To come: 2010-07-01: Distribution of validatable, production, signed root zone; publication of root zone trust anchor (Please note that this schedule is tentative and subject to change based on testing results or other unforeseen factors.)

1 0

Looking for historical Data on V6
by Joel Wiramu Pauling 04 May '10

04 May '10

Apologies to those cross-posted on the V6 Tech list: Hi all, I am just putting together a couple of graphs (see attached spreadsheet). comparing historical V4 deployment (currently looking at number of published A records as my metric) to the current v6 deployment. Rather than make a direct comparison of v6 vs v4 AS's etc as in Geoff Hustons reports, I am looking to show that the size of the v6 Internet is roughly equivalent to the size of X historical point in time of the v4 Internet. Currently using the DNS A/AAAA record metrics it looks like the current size of V6 Internet is around the same size of the historical 1998 V4 internet. I know using A/AAAA records isn't the greatest of metrics, but with the point in mind of showing historical comparative sizings is I think useful for showing the need to be engaged actively in deploying V6. Any further suggested approaches and especially data sources for furnishing this investigation appreciated. Kind regards -JoelW

2 2

Any Soekris net4501's for sale?
by Nick Larsen 04 May '10

04 May '10

Just wondering if anyone has a Soekris net4501 for sale? I have something I'd like to test, but don't want to wait for shipping if I can help it. Cheers, Nick Larsen Network Technician DDI +64.4.471.4447 Freephone 0800 ZEROONE Ph +64.4.499.0018 Fax +64.4.499.0019 Address Level 4, United Building. 107 Customhouse Quay, Wellington, New Zealand

1 1

New Zealand Network Operators' Group
by Donald Neal 03 May '10

03 May '10

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 is registered as a charitable entity under the Charities Act. The 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. Other than the trustees, the NZNOG does not have a formal membership. Conference NZNOG holds New Zealand's only annual technical networking conference. See http://drpeering.net/a/Ask_DrPeering/Entries/2010/2/1_NZNOG_2010.html or http://2010.nznog.org/ to see what you missed. 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 1100 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 | I don't approve of gambling. I'll just | spend my time in the bar. High Performance Computing | - NZNOG 2010 attendee The University of Waikato |

1 0

NZRR Route Registry Update
by NZRR Database Notifications 03 May '10

03 May '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: 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 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, 192.138.251.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 20100504 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 03 May '10

03 May '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:AS38477 descr: advertised to AS24388 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 202.6.116.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: noc(a)unleash.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090925 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS38477 descr: advertised to AS24388 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, 192.138.251.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 20100504 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 03 May '10

03 May '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: AS9439:RS-ROUTES:AS38477 descr: advertised to AS9439 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 20100326 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS38477 descr: advertised to AS9439 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, 192.138.251.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 20100504 source: NZRR ------------------------------------------------------------

1 0