May 2012 - NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 30 May '12

30 May '12

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:AS17746 descr: advertised to AS9439 by Orcon - AS17746 members: 121.98.0.0/15^15-29, 60.234.0.0/16^16-29, 114.23.0.0/16^16-29, 156.62.0.0/16^16-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 180.189.192.0/19^19-29, 202.89.32.0/19^19-29, 202.150.96.0/19^19-29, 49.50.240.0/20^20-29, 112.109.64.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 112.109.80.0/21^21-29, 124.150.160.0/21^21-29, 182.23.176.0/21^21-29, 202.3.88.0/21^21-29, 202.49.64.0/21^21-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 103.3.232.0/22^22-29, 103.6.144.0/22^22-29, 110.44.16.0/22^22-29, 113.21.224.0/22^22-29, 116.193.144.0/22^22-29, 202.14.20.0/22^22-29, 202.36.8.0/22^22-29, 202.49.244.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 116.193.148.0/23^23-29, 120.138.22.0/23^23-29, 124.150.170.0/23^23-29, 143.96.2.0/23^23-29, 143.96.4.0/23^23-29, 182.236.122.0/23^23-29, 182.236.124.0/23^23-29, 202.14.82.0/23^23-29, 202.27.76.0/23^23-29, 202.36.198.0/23^23-29, 202.36.230.0/23^23-29, 202.175.142.0/23^23-29, 210.54.12.0/23^23-29, 210.54.142.0/23^23-29, 103.2.121.0/24^24-29, 103.6.212.0/24^24-29, 116.193.151.0/24^24-29, 120.138.31.0/24^24-29, 124.150.168.0/24^24-29, 124.150.172.0/24^24-29, 182.236.121.0/24^24-29, 192.88.190.0/24^24-29, 192.203.216.0/24^24-29, 202.6.5.0/24^24-29, 202.12.104.0/24^24-29, 202.14.84.0/24^24-29, 202.14.217.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.12.0/24^24-29, 202.36.70.0/24^24-29, 202.36.174.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.72.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.46.189.0/24^24-29, 202.49.59.0/24^24-29, 202.49.140.0/24^24-29, 202.49.216.0/24^24-29, 202.49.233.0/24^24-29, 202.50.164.0/24^24-29, 202.50.176.0/24^24-29, 202.50.246.0/24^24-29, 202.129.253.0/24^24-29, 202.175.137.0/24^24-29, 202.175.138.0/24^24-29, 203.6.246.0/24^24-29, 203.97.42.0/24^24-29, 210.55.5.0/24^24-29, 210.55.169.0/24^24-29, 210.55.199.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: robert.keightley(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120501 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon - AS17746 members: 121.98.0.0/15^15-29, 60.234.0.0/16^16-29, 114.23.0.0/16^16-29, 156.62.0.0/16^16-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 202.150.96.0/19^19-29, 49.50.240.0/20^20-29, 112.109.64.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 112.109.80.0/21^21-29, 182.23.176.0/21^21-29, 202.3.88.0/21^21-29, 202.49.64.0/21^21-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 103.3.232.0/22^22-29, 103.4.136.0/22^22-29, 103.6.144.0/22^22-29, 103.247.152.0/22^22-29, 113.21.224.0/22^22-29, 116.193.144.0/22^22-29, 202.14.20.0/22^22-29, 202.36.8.0/22^22-29, 202.49.244.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 116.193.148.0/23^23-29, 120.138.22.0/23^23-29, 143.96.2.0/23^23-29, 143.96.4.0/23^23-29, 202.14.82.0/23^23-29, 202.27.76.0/23^23-29, 202.36.198.0/23^23-29, 202.36.230.0/23^23-29, 202.175.142.0/23^23-29, 210.54.12.0/23^23-29, 210.54.142.0/23^23-29, 103.6.212.0/24^24-29, 116.193.151.0/24^24-29, 120.138.31.0/24^24-29, 124.150.172.0/24^24-29, 192.88.190.0/24^24-29, 192.203.216.0/24^24-29, 202.6.5.0/24^24-29, 202.12.104.0/24^24-29, 202.14.84.0/24^24-29, 202.14.217.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.12.0/24^24-29, 202.36.70.0/24^24-29, 202.36.174.0/24^24-29, 202.36.233.0/24^24-29, 202.37.72.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.46.189.0/24^24-29, 202.49.59.0/24^24-29, 202.49.140.0/24^24-29, 202.49.216.0/24^24-29, 202.49.233.0/24^24-29, 202.50.164.0/24^24-29, 202.50.176.0/24^24-29, 202.50.246.0/24^24-29, 202.175.137.0/24^24-29, 202.175.138.0/24^24-29, 203.6.246.0/24^24-29, 203.97.42.0/24^24-29, 210.55.5.0/24^24-29, 210.55.169.0/24^24-29, 210.55.199.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: robert.keightley(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR ------------------------------------------------------------

1 0

Fwd: InTAC invite (for NZNOG)
by Andy Linton 30 May '12

30 May '12

---------- 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> Hi Andy, Attached is the invitation for InTAC (and text below). Are you able to send this to NZNOG please? Thanks, C -- 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. www.internetnz.net.nz/intac 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. Regards, Campbell -- Campbell Gardiner Communications Lead, Internet New Zealand Secretariat, New Zealand IPv6 Task Force Web: www.internetnz.net.nz & www.ipv6.org.nz Email: campbell(a)internetnz.net.nz DDI: + 64 4 495 2332 Mobile: + 64 21 506 004 Address: Level 9, Grand Arcade Tower, 16 Willis Street, Wellington 6011

1 0

APNIC Survey 2012 Extended to 8 June
by Elly Tawhai 29 May '12

29 May '12

Hi NZNOG Community, The APNIC Survey is still open for participation. This your time to have your say! Kind regards, Elly APNIC ________________________________________________________________________ APNIC Survey 2012 Extended to 8 June ________________________________________________________________________ There is still time to respond to the APNIC Survey 2012 and give a direct contribution to APNIC's operational planning and future direction. You do not have to be an APNIC Member to complete the Survey, and will only be asked questions that are relevant to you. Kindly take a few minutes to fill out the Survey, which is available until 8 June at: http://www.apnic.net/survey Kind regards, ________________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 3646 South Brisbane, QLD 4101 Australia Fax: +61 7 3858 3199 6 Cordelia Street, South Brisbane, QLD http://www.apnic.net ________________________________________________________________________ * Sent by email to save paper. Print only if necessary.

1 0

Re: [nznog] Fwd: DNCL Second Level Consultation and Submissions
by Blair Harrison 29 May '12

29 May '12

Hi Folks, I have a few thoughts on this, apologies if this seems a bit conflicted, just what I'm thinking at the moment. On Wed, May 30, 2012 at 3:39 PM, Simon Green <simon(a)simongreen.net> wrote: > To me this whole things seems like a way for Internet NZ to double > their income. Most entities that have a non conflicting .co.nz domain > will also want to register their .nz domain (even if they don't use > it), just to prevent domain hijacking at a future date. And that means > two payment of domain fees. (ala ICANN allowing arbitrary top level > domains) > How about the other way around, new registrants for .nz being compelled to register .co.nz as well? An interesting thought experiment, but I think people are overall lazy, and this just won't happen unless there is someone encouraging them to do so (their registrar or web developer, most likely). Frankly though, if your business will collapse under the pressure of another $24/yr domain you're probably doing it wrong anyway. > I can't see any benefit to domain owners or the general public in > opening up to 2LD registration. I will be replying to the proposal at > some stage. > > Probably not much benefit to existing domain owners, as someone discussed earlier, most people have invested all their branding in one particular version of their domain, and that's fine. I think it does provide an "in" for new players, whose name of choice might be taken already in the 3ld space but not yet camped out in .nz I haven't really seen much confusion in the past except where people try to guess the domain of a particular company, and get it wrong, this does probably leave things open for a little confusion. As also mentioned earlier, this isn't really so much an issue any more, as if people want to find you, they just type your company name into the search box. If you're not the first hit, then you've probably done your SEO wrong - or your name is just not very unique :) Lets take a look at the distribution of .nz 2ld registrations for last month. Apologies if this doesn't display well, but the numbers are all there. 2LD Apr-12 .co 417188 .net 27229 .org 26552 .school 3285 .ac 1929 .gen 1381 .geek 1148 .govt 1117 .maori 691 .health 147 .iwi 79 .mil 34 .cri 14 .parliament 9 Total 480803 So out of 480803 total registrations in .nz, we have 417188, or 86.7% of all total registrations being .co.nz, with the next two being 5.6% and 5.5%. Seems like some extra commercial type 2ld categories might be a good idea (tourism.nz, retail.nz, trade.nz?) Lumping the bulk of domains into .co.nz has already destroyed any semblance of hierarchy, so I don't really see much reason to argue about the sanctity of the old way of doing things. It's already well and truly gone. I do think that it's worth having a discussion about whether .nz should be opened up fully, or try to find some more 2lds which might be practical - I don't think there should necessarily have to be someone apply for these, historically the process has just taken too long and only industry people really are aware of it (a-la geek.nz, a paltry 1100 registrations after several years in operation) - InternetNZ could come up with some new ones all on their own - and they're the ones with the data on existing registrations already so may be able to further split out the .co.nzregistration data into rough categories. It's probably worth having a good think about further domains to lock out at the 2ld, eg wpad.nz, and isatap.nz (which have been dealt with already in the 3ld space), I'm sure there are others. All of the supported IDN variants of the locked out domains should also be prevented from being registered. Cheers, Blair

1 0

Discussion paper on opening .nz 2ld
by Andy Linton 29 May '12

29 May '12

Just following up on my earlier posting on this. By all means discuss this on the nznog list, in pubs and clubs and anywhere else you choose but let me remind you that if you want to be sure that your opinion is taken into account don't forget the formal process described here. andy ---------- Forwarded message ---------- From: Joy Liddicoat <joy(a)liddicoatlaw.co.nz> Date: Wed, May 30, 2012 at 10:21 AM Subject: Re: [members-discuss] Discussion paper on opening .nz 2ld To: InternetNZ Members Discussion List <members-discuss(a)mailman.internetnz.net.nz> The consultation relates to a proposal being considered by the Domain Name Commission to extend the .nz domain name space by allowing registrations at the second level. This has the potential to significantly alter New Zealand's domain name space, and it is important that we hear the views of a wide variety of people and organisations. For ease of reference the Consultation Paper and some FAQ information are attached – this is also available at http://dnc.org The Consultation Paper raises a number of questions including about the creation of new second level domains within the existing .nz structure and whether or not certain names should be prohibited at the second level if registrations at the second level are permitted. I’d like to encourage all members to participate and respond with their views along with any other points you wish to raise. All comments including those of the local Internet community will form the basis of the decision on whether or not to proceed. These comments must be sent to us at the DNC. Online submissions can be made at https://www.research.net/s/dnc_consultation1 or you can email to policies(a)dnc.org.nz or post to Domain Name Commission Ltd, PO Box 11-881, Manners St, Wellington 6142. Submissions will be published online as they are received at http://dnc.org.nz/second_level_proposal_c1. If you have any questions please feel free to contact me through the Domain Name Commission at policies(a)dnc.org.nz. Yours sincerely, Joy Liddicoat Chair Domain Name Commission Limited

1 0

Xtra Mail Admin about?
by Don Gould 29 May '12

29 May '12

Can anyone tell me if I need to do anything about this problem or if it will clear? I've currently got ~100 messages sitting in my queue from one address to a bunch of xtra accounts. The messages are valid and not spam. D May 30 13:34:19 mx postfix/error[19600]: D1FB0974409: to=<$RANDOMUSER-REMOVED(a)xtra.co.nz>, relay=none, delay=487, delays=486/1.8 /0/0.02, dsn=4.7.0, status=deferred (delivery temporarily suspended: host mx2.tnz.mail.yahoo.com[124.108.96.211] refused t o talk to me: 421 4.7.0 [TS01] Messages from $MYSERVER-IP-ALSO-REMOVED temporarily deferred due to user complaints - 4.16.55.1; see htt p://postmaster.yahoo.com/421-ts01.html) -- Don Gould 31 Acheson Ave Mairehau Christchurch, New Zealand Ph: + 64 3 348 7235 Mobile: + 64 21 114 0699

6 7

Xtra Resolver issue
by Shane Langley 29 May '12

29 May '12

Hey guys, I'm trying to get hold of someone that can help with some issues using the Xtra name resolver dnsc1.xtra.co.nz - it seems we have a domain name that it refuses to accept exists and yet all other resolvers are perfectly happy with, if anyone knows who to contact it would be appreciated. Shane Langley Webtastix Internet Services 021 815 184

1 0

(no subject)
by Curtis Owings 29 May '12

29 May '12

At grave risk of email execution... I would be interested in hearing about operational experiences utilizing Chorus transport. I would also be interested in the thoughts of this group on: -Ultra Fast Broadband -VDSL2 -Voice Services The separation of Chorus allows us to consider new inputs and options. My network has to meet your needs for service and revenue. Where is Chorus failing? What do you see a need for? I don't have direct control of field forces or the NOC, but hearing about these experiences helps me decide if the ops teams have the right tools and information to support the network. I can get them more tools and better information. I don't have a problem discussing these in a public forum. However, feel free to contact me privately. Curtis Owings Principal Solution Architect T +64 4 498 9355 (extn 49355) M +64 27 655 5335 E Curtis.Owings(a)chorus.co.nz Level 3, Deloitte House, 10 Brandon Street P O Box 632, Wellington www.chorus.co.nz P Please consider the environment before printing this e-mail ________________________________ 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.

10 17

NZRR Route Registry Update
by NZRR Database Notifications 28 May '12

28 May '12

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-ROUTES6:AS9503 descr: Route set advertised to AS9439 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:DCE:0:0:0:0:0:0/32^32-64, 2001:DCE:E000:0:0:0:0:0/48^48-64, 2001:DF0:4A: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:130:0:0:0:0:0:0/32^32-64, 2403:E00:0:0:0:0:0:0/32^32-64, 2400:1200:0:0:0:0:0:0/32^32-64, 2403:C200:0:0:0:0:0:0/32^32-64, 2404:1E00:0:0:0:0:0:0/32^32-64, 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2403:7000:0:0:0:0:0:0/32^32-64, 2404:138:103:0:0:0:0:0/48^48-64, 2404:138:104:0:0:0:0:0/48^48-64, 2404:138:4000:0:0:0:0:0/48^48-64, 2404:D000:0:0:0:0:0:0/32^32-64, 2405:3A00:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:D1:0:0:0:0:0/48^48-64, 2405:2600:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64, 2001:DD8:13:0:0:0:0:0/48^48-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2404:6600:0:0:0:0:0:0/32^32-64, 2406:5A00:0:0:0:0:0:0/32^32-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2400:6900:0:0:0:0:0:0/32^32-64, 2400:BD00:0:0:0:0:0:0/32^32-64, 2001:DF0:4:0:0:0:0:0/48^48-64, 2404:139:300:0:0:0:0:0/43^43-64, 2404:139:3FF:0:0:0:0:0/56^56-64, 2406:1A00:0:0:0:0:0:0/32^32-64, 2400:E700:0:0:0:0:0:0/32^32-64, 2402:CC00:0:0:0:0:0:0/32^32-64, 2403:A00:0:0:0:0:0:0/32^32-64, 2405:B400:0:0:0:0:0:0/32^32-64, 2001:500:3:0:0:0:0:0/48^48-64, 2403:B700: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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120511 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES6:AS9503 descr: Route set advertised to AS9439 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:DCE:0:0:0:0:0:0/32^32-64, 2001:DCE:E000:0:0:0:0:0/48^48-64, 2001:DF0:4A: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:130:0:0:0:0:0:0/32^32-64, 2403:E00:0:0:0:0:0:0/32^32-64, 2400:1200:0:0:0:0:0:0/32^32-64, 2403:C200:0:0:0:0:0:0/32^32-64, 2404:1E00:0:0:0:0:0:0/32^32-64, 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2403:7000:0:0:0:0:0:0/32^32-64, 2404:138:103:0:0:0:0:0/48^48-64, 2404:138:104:0:0:0:0:0/48^48-64, 2404:138:4000:0:0:0:0:0/48^48-64, 2404:D000:0:0:0:0:0:0/32^32-64, 2405:3A00:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:D1:0:0:0:0:0/48^48-64, 2405:2600:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64, 2001:DD8:13:0:0:0:0:0/48^48-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2404:6600:0:0:0:0:0:0/32^32-64, 2406:5A00:0:0:0:0:0:0/32^32-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2400:6900:0:0:0:0:0:0/32^32-64, 2400:BD00:0:0:0:0:0:0/32^32-64, 2001:DF0:4:0:0:0:0:0/48^48-64, 2404:139:300:0:0:0:0:0/43^43-64, 2404:139:3FF:0:0:0:0:0/56^56-64, 2406:1A00:0:0:0:0:0:0/32^32-64, 2400:E700:0:0:0:0:0:0/32^32-64, 2402:CC00:0:0:0:0:0:0/32^32-64, 2403:A00:0:0:0:0:0:0/32^32-64, 2405:B400:0:0:0:0:0:0/32^32-64, 2001:500:3:0:0:0:0:0/48^48-64, 2403:B700:0:0:0:0:0:0/32^32-64, 2403:F700: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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120529 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 May '12

28 May '12

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:DCE:0:0:0:0:0:0/32^32-64, 2001:DCE:E000:0:0:0:0:0/48^48-64, 2001:DF0:4A: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:130:0:0:0:0:0:0/32^32-64, 2403:E00:0:0:0:0:0:0/32^32-64, 2400:1200:0:0:0:0:0:0/32^32-64, 2403:C200:0:0:0:0:0:0/32^32-64, 2404:1E00:0:0:0:0:0:0/32^32-64, 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2403:7000:0:0:0:0:0:0/32^32-64, 2404:138:103:0:0:0:0:0/48^48-64, 2404:138:104:0:0:0:0:0/48^48-64, 2404:138:4000:0:0:0:0:0/48^48-64, 2404:D000:0:0:0:0:0:0/32^32-64, 2405:3A00:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:D1:0:0:0:0:0/48^48-64, 2405:2600:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64, 2001:DD8:13:0:0:0:0:0/48^48-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2404:6600:0:0:0:0:0:0/32^32-64, 2406:5A00:0:0:0:0:0:0/32^32-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2400:6900:0:0:0:0:0:0/32^32-64, 2400:BD00:0:0:0:0:0:0/32^32-64, 2001:DF0:4:0:0:0:0:0/48^48-64, 2404:139:300:0:0:0:0:0/43^43-64, 2404:139:3FF:0:0:0:0:0/56^56-64, 2406:1A00:0:0:0:0:0:0/32^32-64, 2400:E700:0:0:0:0:0:0/32^32-64, 2402:CC00:0:0:0:0:0:0/32^32-64, 2403:A00:0:0:0:0:0:0/32^32-64, 2405:B400:0:0:0:0:0:0/32^32-64, 2001:500:3:0:0:0:0:0/48^48-64, 2403:B700: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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120511 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:DCE:0:0:0:0:0:0/32^32-64, 2001:DCE:E000:0:0:0:0:0/48^48-64, 2001:DF0:4A: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:130:0:0:0:0:0:0/32^32-64, 2403:E00:0:0:0:0:0:0/32^32-64, 2400:1200:0:0:0:0:0:0/32^32-64, 2403:C200:0:0:0:0:0:0/32^32-64, 2404:1E00:0:0:0:0:0:0/32^32-64, 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2403:7000:0:0:0:0:0:0/32^32-64, 2404:138:103:0:0:0:0:0/48^48-64, 2404:138:104:0:0:0:0:0/48^48-64, 2404:138:4000:0:0:0:0:0/48^48-64, 2404:D000:0:0:0:0:0:0/32^32-64, 2405:3A00:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:D1:0:0:0:0:0/48^48-64, 2405:2600:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64, 2001:DD8:13:0:0:0:0:0/48^48-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2404:6600:0:0:0:0:0:0/32^32-64, 2406:5A00:0:0:0:0:0:0/32^32-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2400:6900:0:0:0:0:0:0/32^32-64, 2400:BD00:0:0:0:0:0:0/32^32-64, 2001:DF0:4:0:0:0:0:0/48^48-64, 2404:139:300:0:0:0:0:0/43^43-64, 2404:139:3FF:0:0:0:0:0/56^56-64, 2406:1A00:0:0:0:0:0:0/32^32-64, 2400:E700:0:0:0:0:0:0/32^32-64, 2402:CC00:0:0:0:0:0:0/32^32-64, 2403:A00:0:0:0:0:0:0/32^32-64, 2405:B400:0:0:0:0:0:0/32^32-64, 2001:500:3:0:0:0:0:0/48^48-64, 2403:B700:0:0:0:0:0:0/32^32-64, 2403:F700: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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120529 source: NZRR ------------------------------------------------------------

1 0