- NZNOG - lists.nznog.org

A very rough overview of current state of NZ IPv6 deployment.
by Dean Pemberton 11 Jan '09

11 Jan '09

I'm not cross-posting I swear =) The following information was just posted to the IPv6 Steering Group TechSIG list and as it's got network operational content I'm posting it here as well. http://www.geek.nz/ipv6/ It's a quick stab (not complete by any means at all) at a survey of the state of IPv6 deployment within New Zealand. Discussion around this is in full flight on the TechSIG list. For those of you who missed what list I'm talking about. Here is the the invitation again. Dean ---------------------------- A workshop at held at InternetNZ on the 28 November in Wellington saw the formation of a New Zealand IPv6 Steering Group. This group includes representatives from telecommunications carriers, internet service providers, ICT vendors, and industry and user associations. The members of this steering group consist of invited senior representatives from the following organisations: InternetNZ TUANZ ISPANZ Telecommunications Carriers Forum Digital Development Forum Telecom TelstraClear WorldXChange Orcon FX Networks REANNZ Canterbury Development Corporation Kordia Cisco Vodafone Juniper Networks Alcatel Lucent Braintrust Prophecy Networks This steering group will primarily be concerned with high level discussion regarding the deployment of IPv6 within New Zealand. The steering group will not necessarily be a place where technical discussion takes place. As with so many things these days, a combination of business and technical expertise must be bought together to solve a given problem. To this end at the same workshop a Technical Special Interest Group (TechSIG) was also established. The goals of this group are: . To act as a central point for IPv6 technical discussion within the New Zealand Internet community. . To identify to the IPv6 Steering Group any business related barriers to IPv6 deployment which have been identified by the SIG's technical contributors. . To comment and provide potential solutions to technical related barriers identified by members of the IPv6 Steering Group. . To stimulate the production of relevant technical documentation. The co-conveners of this group are Andy Linton Nathan Ward Brian Carpenter Dean Pemberton A mailing list has been created and membership is open to all interested parties. Subscription details can be found at the link below; http://listserver.internetnz.net.nz/mailman/listinfo/ipv6-techsig I would encourage anyone who has an interest in the deployment and growth of IPv6 to join and contribute to the list. Please do not feel that this is a 'Networking Specialist Only' list. The deployment of IPv6 (and depletion of IPv4) has just as significant an impact on system administrators and content/application providers as it does on network administrators. I welcome all technical viewpoints onto the list. Thank you for your time. Dean Pemberton (Co-convener, IPv6 Steering Group Technical SIG)

2 2

Re: [nznog] NZNOG 2009 Network Management Miniconf
by Ewen McNeill 11 Jan '09

11 Jan '09

In message <20081220012229.F382C112733(a)wat.la.naos.co.nz>, Ewen McNeill writes: >If you've registered for NZNOG 2009 (http://2009.nznog.org/register) >you will have seen that we are holding another network administrators >miniconf on the Wednesday tutorial day. One more reminder to send us (a) topics you'd like to see discussed, and (b) offers to introduce a specific topic. This is your chance to talk with your peers about layer 7 issues which are of relevance to you. To date we have had suggested: - configuration automation (puppet, cfengine, and friends) - scaling network monitoring (eg, distributed nagios) - virtualisation (VMWare ESX, etc) No one showed any interest in talking about ENUM (either having it as a topic, or giving an intro talk), so perhaps that topic is too last week. We'd be happy to host it if there is still interest, particularly if those trying to get the 4.6.e164 delegation are willing to turn up and talk about it. Please send additional topics (and ideally offers to present for 5-15 minutes as an intro to the topic) to: <talks09(a)nznog.miniconf.org> Simon Lyall and Ewen McNeill Network Administrators Miniconf

1 0

[Fwd: Re: NZNOG list as NZNOC list.....]
by Gerard Creamer 11 Jan '09

11 Jan '09

On 12/01/2009 2:27 p.m., Andy Linton wrote: > > > And of course that page is already there. Doh! > > It's at http://www.nznog.org/?page_id=6 And this thread has prompted quite a few updates to the NOC list, which is fantastic. If there are any more changes or alterations please send them to info (at) nznog.org and I'll do them all at the same time. Cheers, Gerard

1 0

Compass Networks Email Servers IP addresses on RBL List again
by Robert Cotter 11 Jan '09

11 Jan '09

It looks like Compass have got one of their email servers IP addresses on a RBL IP list . 203.152.112.39 The tester i am using is http://www.fortiguardcenter.com/antispam/antispam.html#spamlookup Could some body let them know please, so I stop getting complaints from my partner about the stupid anti-spam system flagging legitimate emails wrong. Regards Robert Cotter ________________________________ 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.

8 12

Re: [nznog] FW: The Cidr Report
by jamie baddeley 10 Jan '09

10 Jan '09

> -----Original Message----- > From: cidr-report(a)potaroo.net [mailto:cidr-report(a)potaroo.net] > Sent: Saturday, 10 January 2009 12:00 a.m. > To: cidr-report(a)potaroo.net > Cc: apops(a)apops.net; afnog(a)afnog.org; nanog(a)merit.edu; eof-list(a)ripe.net; routing-wg(a)ripe.net > Subject: The Cidr Report > > This report has been generated at Fri Jan 9 21:13:41 2009 AEST. > The report analyses the BGP Routing Table of AS2.0 router and generates a report on aggregation potential within the table. > > Check http://www.cidr-report.org for a current version of this report. > 8<---SNIP--------------- > > Possible Bogus Routes > > 151.135.0.0/16 AS4768 CLIX-NZ TelstraClear Ltd Folks, Any reason why our friends at TCL are announcing (what appears to be) an unallocated block? Jamie

3 2

Informational - Vocus Outage at APE - 12/01/2009
by McDonald Richards 08 Jan '09

08 Jan '09

Date: 12/1/2009 2:00 AM AEDT to 12/1/2009 4:00 AM AEDT Advisory Type: Informational Services: Data Service Affecting: APE Connectivity Advisory Notes: Due to planned works on Monday the 12th of January commencing at 2:00AM AEDT the Vocus ASN 4826 peering session at APE will be down for a brief period. Please address any questions or concerns to noc(a)vocus.com.au. Regards, Vocus NOC

1 0

NZNOG09 not too far away now...
by Jonny Martin 07 Jan '09

07 Jan '09

Hi All, NZNOG09 is now less than three weeks away. Please register now if you haven't already! Please don't leave it until the last week as so many of you tend to do :). http://2009.nznog.org/ The NZNOG block booking at the Mount Richmond Hotel for NZNOG09 has now completely sold out. Given that we block booked virtually the entire hotel you'll find it hard to get accommodation there for the duration of the conference if you haven't already booked it. We have a great list of speakers again this year, as well as not one, but two social functions which are at no additional cost thanks to our generous sponsors. Thanks, and look forward to seeing you in Auckland, City of Sales... Jonny. For the NZNOG09 org team.

1 0

Re: [nznog] enum
by Michael Sutton 06 Jan '09

06 Jan '09

This is my third email on the subject of ENUM. (on a diet) Firstly; I would appreciate and hope that experts including members of NZNOG do not argue to justify why USER ENUM should NOT be implemented in New Zealand. It is not up to individuals to quantify how it will be used or the value of it to end users and application developers in the fullness of time. It is instead up to our community to actively promote and facilitate the use of any reasonable protocol on the Internet. The truly unique fact about 4.6.e164.arpa is that it is an officially sanctioned/moderated top level domain using the stable DNS ENUM services. ENUM (the protocol) is operational around the world and also in New Zealand via DNS client USER ENUM enquiries made both to countries already actively using e164.arpa as well as other registries such as e164.org TLD's. For myself I see this as a real issue of my personal Internet usage rights in New Zealand. Imagine if we were still considering whether New Zealand should have its own CC TLD. That is the situation we are in with respect to USER ENUM 4.6.e164.arpa. I cannot opt-in to register my New Zealand telephone number and all my associated communication services while ~50 countries can. Imagine if each internet protocol had to be approved by local entities such as the MED, TCF and InternetNZ. Eg. email or http/https web or skype or h323 - such a scenario is impossible to countenance. Yet User ENUM 4.6.e164.arpa delegation has been "frozen" for years by agreements between the MED (TCF and InternetNZ). 4.6.e164.arpa delegation must be approved by the MED and as such I recommend that the MED delegate it to themselves and fast track operation and policy implementation. New Zealand Telco companies who are members of the TCF already use PROVIDER ENUM as a backroom routing protocol. There is nothing they need from USER ENUM 4.6.e164.arpa but they do need to co-operate with the authentication process for establishing USER ENUM registrations. The political issue here of USER ENUM is why New Zealanders are being 'prevented' from using this service. We need a least cost, least capture USER ENUM Registry to be established which puts ENUM client users as well as application developers interests as the prime consideration. Issues concerning +1 delegation: Previous emails suggested that the United States +1 delegation was lapsed as there was no demand - This is not the situation. It is useful to appreciate that +1 represents a number of Caribbean countries as well as Canada and the United States and the complications that this fact originally had. +1 had been registered delegated for trial to "CC1 ENUM LLC" (a private company Country Code 1 ENUM Limited Liability Company). This Company's shareholders include AT&T, Sprint-Nextel, and Verizon etc - Board Papers show the stake-holder were/are not in themselves interested in supporting USER ENUM instead their primary goal was PROVIDER ENUM with delegation of 1.e164.arpa to the Company. The US State Department however "refused" to renew the +1 registration to CC1 ENUM LLC in February 2008 as the Company does not need the delegation to operate PROVIDER ENUM. Indeed the Company is proceeding with PROVIDER ENUM using 1.e164.us. (which is not a sanctioned ITU ENUM). Then in May of 2008, positively supported by United States Representatives, the ITU SG adopted "new" guidelines to cover delegation of numbers such as +1 which represent multiple countries. Therefore Canada and the other Caribbean countries are also supporting this guideline. What appears to have happened is that because CC1 ENUM LLC was only really interested in routing optimization, the US Government has pulled the plug on it because it was making no plan for USER ENUM and rather than letting the LLC remain as the Delegee the U.S.G. decided to prevent capture by this entity. This situation closely mirrors that in New Zealand - the networks want PROVIDER ENUM but eschew USER ENUM. The actions of the US Government in May 2008 (Geneva) show that they are very keen for USER ENUM to be enabled for the 1.e164.arpa countries. My advice to the Minister: On the 19th December 2008 I wrote to Ministers of the NZ Government requesting (in one part) that implementation of USER ENUM be expedited and set as a KPI of the relevant Ministry. I was completely unaware at the time of the application that was to be made on the 23rd of December by Mr. Jones for delegation of 4.6.e164.arpra. Unless the ITU receives a letter from the MED within 60 days of Mr. Jones' application the ITU will refuse the application. This notice of refusal will then be communicated by the email list to every international subscriber to the list (private/corporate/government) and will show New Zealand, I suggest, in a disorganized and poor light. (No criticism of Mr. Jones) Should this ENUM 4.6.e164.arpa registration situation then be repeated again and again and again then Kiwis will look like Thanksgiving turkeys. Best regards Michael Sutton ( Previously InternetNZ's ENUM Task Force Chairperson.) http://www.awacs.co.nz (NZNOG conference timing provides conflicts with my current schedule :( ) I suggest Andrew Ruthven and Don Christie from Catalyst be invited to attend any panel session NZNOG has)

3 2

108/8 and 184/8 allocated to ARIN
by Leo Vegoda 04 Jan '09

04 Jan '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 ARIN in December 2008: 108/8 and 184/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.9.0.397 wj8DBQFJYcuzvBLymJnAzRwRAiHoAJ9ElxHBdXiQEYcWTE+QMKIA4+0rpwCgmbTy w5fYf3la3xtY5SjT5w+dS/w= =xUKB -----END PGP SIGNATURE-----

1 0

Call for Nominations to the APNIC Executive Council
by Sunny 04 Jan '09

04 Jan '09

_______________________________________________________________________ Call for Nominations to the APNIC Executive Council _______________________________________________________________________ Four positions on the APNIC Executive Council (EC) will be opened for election at APNIC 27 in Manila on Friday, 27 February 2009. The members whose positions are up for reelection are Kuo Wei Wu, Kusumba Sridhar, Mao Wei, and Ming-Cheng Liang, who were all elected at APNIC 24 in Bali on 2 March 2007. Nominations are due by the close of business on Tuesday, 13 February 2009 at the latest (17:30 UTC+10 Brisbane time). Nominees do not have to be representatives of members, but only APNIC members may nominate and vote for candidates. Nominations must be made using the online nomination form which will be available from 5 January 2009: http://meetings.apnic.net/elections/nominate.html If you are unable to vote online or attend APNIC 27, you can still make your vote count by appointing a proxy to represent you at the meeting. Proxy forms are available at: http://www.apnic.net/meetings/proxy.html For more information on nominations received, proxy registration, current EC members, and the role of the EC, please refer to: http://meetings.apnic.net/elections/about/index.html Online voting will be available for this election via the MyAPNIC web site and will open soon after the nomination period closes. Nominees should note that positions on the APNIC EC are currently voluntary and that APNIC may not be able to reimburse EC members all expenses associated with EC duties. Where possible, however, APNIC will reimburse actual expenses for attendance at APNIC meetings, providing that these fall within budget and cash flow constraints. If you have any questions, please contact the APNIC Secretariat at: secretariat(a)apnic.net. Regards, _______________________________________________________________________ APNIC Secretariat email: secretariat(a)apnic.net http://www.apnic.net sip: info(a)voip.apnic.net phone: +61 7 3858 3100 _______________________________________________________________________

1 0