wondering if anyone from TVNZ On Demand is on this list and wouldn't
mind contacting me offlist regarding problems streaming if a user has an
IPv6 address. The helpdesk doesn't appear to know what ipv6 is so
thought I'd try an alternative.
Your views on this would be appreciated.
-------- Original Message --------
Subject: DNCL Second Level Consultation and Submissions
DNCL Second Level Consultation and Submissions
The Domain Name Commission is proposing to extend the .nz domain name
space by allowing anybody to register domain names at the
‘second level’. This has the potential to significantly
alter New Zealand’s domain name space so it’s important
we get your views.
Key features of the .nz proposals include: Registration of .nz
domain names could be at the second or third levels on an ongoing
basis. Existing second level domains (such as .co.nz) will remain
and continue to be supported. There will be no impact on any
currently registered .nz domain names. Registrations at the second
level will be on a “first come, first served” basis,
except during the Sunrise Period and where there are currently
multiple registrations of the same name in different second level
domains. The Sunrise Period will be a designated window, where
existing .nz domain name holders (registrants) can register their
domain name/s at the second level if they are the only one that has
that name at the third level. If two or more domain name holders
have the same name at the third level, no-one will be able to
register that name at the second level unless they obtain the consent
of the other third level name holders. Alternatively, if all agree,
it could become a second level domain instead. A temporary
amendment to the Dispute Resolution Service Policy to cover
sub-domains of generic domain names registered at the second level.
The above list is a very brief overview of the proposals. The
Consultation Paper at
provides more detail about what is proposed. It also includes marked
up versions of the main policies affected so that people can get an
indication of how it may be implemented.
Each section of the Consultation Paper raises specific questions.
Please respond to these questions or, more generally, to any of the
issues raised through the online response from at
Submissions can also be made by email to policies(a)dnc.org.nz, by fax
to (04) 495 2115, or by mail to P O Box 11881, Wellington. The
closing date for submissions is midday on Thursday 27 September 2012.
As submissions are received they will be published on this page.
Related documents: Consultation notice and published submissions
http://dnc.org.nz/second_level_proposal_c1 Consultation paper,
Online submission form https://www.research.net/s/dnc_consultation1
Originally published 9am, Wednesday 30 May 2012
You have received this communication because you have subscribed to the DNC website at http://www.dnc.org.nz/
If you no longer wish to receive these emails, please send an email with 'Unsubscribe' in the subject line to unsubscribe(a)dnc.org.nz
Or log into your account and turn off mail subscriptions
Dear Technical Community,
The next step towards completing the DNSSEC deployment for .nz is to
sign the second level domains, thus allowing registrants to enable
DNSSEC for their domains. We have prepared a staggered deployment
schedule for the unmoderated second level domains, which is available in
full at http://nzrs.net.nz/dns/dnssec
As a summary, geek.nz will be the first DNSSEC signed second level
domain, closely followed by ac.nz, gen.nz, maori.nz and school.nz, all
during June. In July, net.nz and org.nz will be signed, ending with
co.nz during early August.
As a reminder, the SRS has been able to receive DS records for domains
under .nz since last year, and those records will be included in their
respective zone when DNSSEC is fully enable for the second level domain.
We advise against using any of the Second Level Domains DS records as a
If you have any questions around this process, don't hesitate to contact
us at support(a)nzrs.net.nz
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 495 2337
mobile: +64 21 400535
Q: What now?
A: At the APNIC meeing in New Delhi a proposal to remove the
multihoming requirement for IPv6 portable assignments did not reach
consensus. It's likely to come back again at the meeting in August and
I'd like to explain a bit about it and get some feedback from the NZ
Q: Ok what's this one all about?
Current APNIC policy only permits portable assignments of IPv6
addresses to be made if a member is currently multihomed or plans to
be multihomed within three months.
That can mean that people feel they can't apply for IPv6 space, or
that they have to wait until they are multihomed in order to apply to
APNIC for address space.
Prop-101 looks to remove the requirement for multihoming and would let
non-multihomed APNIC members apply for a portable IPv6 assignment.
The full text is here:
Q: What is a portable assignment and why would I want one anyway?
A: A portable assignment of IPv6 addresses is independent of any
particular ISP or network provider. It means that you can take those
addresses and have them routed by anyone. Non-portable assignments
are addresses which you might get from your ISP. Those addresses are
taken from the ISPs block of IPv6 addresses and can only be used while
you are their customer. If you were using non-portable addresses and
wanted to move ISPs then you would have to renumber your network.
Q: That sounds terrible! Why would anyone want anything else?
A: Well for a lot of organisations they don't need anything else.
Think about IPv4, most people operate with addresses given to them by
their ISP just fine. Portable addresses are also only allocated by
RIR organisations like APNIC. They don't come free, there is a yearly
cost to be an APNIC member, and keep those addresses.
Q: Are there any downsides?
A: Objectors to this proposal suggest that if everyone was granted
portable address space that the routing table would grow
Q: What does everyone else in the world do?
A: APNIC is the only one for the 5 global registries which requires
multihoming for portable IPv6 assignments.
Q: So what do you want from me?
A: If you have an opinion then let me know. If you think it's
relevant to others then post it to the list. Don't hesitate to join
the APNIC policy SIG list and have your say directly.
Q: Why are you interrupting my evening?
A; I just wanted to let everyone know about a new APNIC policy which
has just passed through the Policy Development Process
A: The APNIC Executive council has just ratified a new policy called
prop-102 which will increase transparency in IPv6 allocations.
Q: Well what does it say then?
A: Well prop-102 is a hellish boring name a new APNIC proposal which
says that details of any sparse allocation
algorithm used for the allocation by APNIC of IPv6 resources be
published on their the website, and any revisions should be
communicated back to the community. You can read the full text here:
Q: Why do I care?
A: When people are allocated IP addresses, they are sometimes under
the impression that if they request more at a later date that they
will get allocated a completly different area of the address space.
That's not true. For some time now APNIC has been employing a system
called 'Sparse Allocation' to try and make sure that when you came
back, you stood a good chance of getting the IP address block just
next-door. The problem up until now has been no one knew the details
of this system. How soon did you have to come back? How large was
the block they were reserving for you? If you wanted too long did
they allocate it to someone else? All those details were hidden.
Now they will be published.
Q: What are you telling me this?
A: I'm doing my bit to keep the community across what is happening at
APNIC in a way that hopefully people can find accessible. I'll
summarise some of the other policies shortly
Q: What if I have more questions?
A: Feel free to email me and I'll try and answer any APNIC policy
related questions. Or feel free to participate in APNIC discussion
directly via their Policy SIG
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
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.
descr: advertised to AS9439 by AT&T - AS2687
changed: rpsl-admin(a)nzix.net 20120314
descr: advertised to AS9439 by at&t - AS2687
changed: rpsl-admin(a)nzix.net 20120531
---------- Forwarded message ----------
From: Campbell Gardiner <campbell(a)internetnz.net.nz>
Date: Thu, May 31, 2012 at 10:00 AM
Subject: InTAC invite (for NZNOG)
To: Andy Linton <asjl(a)lpnz.org>
Attached is the invitation for InTAC (and text below). Are you able to
send this to NZNOG please?
On Tuesday 10 July, InternetNZ is holding a one-day conference in
Auckland to discuss issues related to the technical architecture and
technical policy of ultra-fast broadband and fibre networks.
InternetNZ cordially invites yourself and colleagues to attend this
event. Please see attached for the invitation and draft programme.
Note that we are seeking further ideas for discussion topics, so
please feel free to email me with any suggestions.
What: The Internet Technical Architecture Conference (InTAC)
When: Tuesday, 10th July 2012
Where: SkyCity Convention Centre, Auckland.
Who should attend: Those involved in developing fibre policy, building
the network, and using the network to talk to one another about its
technical underpinnings. This includes people working for Local Fibre
Companies, Chorus, Retail Service Providers, Telecommunications firms,
Content Providers, Technologists, and Government.
International keynote: Lev Gonick, the Chief Information Officer of
Case Western Reserve University in Cleveland, USA
How much: $60, inclusive of GST and lunch / networking drinks.
To register: Email rsvp(a)internetnz.net.nz. Places are limited so we
suggest interested people register at the earliest.
Communications Lead, Internet New Zealand
Secretariat, New Zealand IPv6 Task Force
Web: www.internetnz.net.nz & www.ipv6.org.nz
DDI: + 64 4 495 2332
Mobile: + 64 21 506 004
Address: Level 9, Grand Arcade Tower, 16 Willis Street, Wellington 6011