- NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 15 Jul '12

15 Jul '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:AS45177 descr: Route set advertised to AS9560 by Vibe Communications - AS45177 mp-members: 2401:7000:0:0:0:0:0:0/32^32-64, 2401:D400: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: barry(a)vibecommunications.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100830 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES6:AS45177 descr: Route set advertised to AS9560 by Vibe Communications LTD - AS45177 mp-members: 2401:7000:0:0:0:0:0:0/32^32-64, 2001:DF0:2C1:0:0:0:0:0/48^48-64, 2404:5700: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(a)vibecommunications.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120716 source: NZRR ------------------------------------------------------------

1 0

For he's a jolly good fellow...
by Andy Linton 14 Jul '12

14 Jul '12

Dean Pemberton, who some of you may know, was made a Fellow of InternetNZ last night at the AGM. Big ups to him. andy

4 3

Remote access to Data Loggers in Taharoa Mine and Rangiriri
by Bill Walker 11 Jul '12

11 Jul '12

Hey Guys, I'm looking for someone who would be interested in building a solution to give remote access to two data loggers in the North Island: Taharoa Mine 38° 9'52.40"S 174°42'48.84"E Rangiriri Interchange 37°25'41.29"S 175° 7'41.86"E Basically the solution would need to be self contained and probably solar powered. It would need to interface to both these data loggers via serial. If your interested or know someone who would be, send me your details and I'll forward them onto the engineer who has this requirement. This is something I could do but I'm on the wrong island and I doubt my wife would let me go..... Thanks, Bill

1 0

Re: [nznog] APNIC - The policy to end all policies prop-103-v001
by Dean Pemberton 10 Jul '12

10 Jul '12

That may be true for v4 (although I'm far from convinced). But I'm not at all buying it for v6 On Wednesday, July 11, 2012, wrote: > > > Actually, I think that this proposal is more than just to incite thinking, > it actually > has merit. The v4 space is functionally all assigned. Many/Most of the > existing policies > are focused on events that are no longer relevent. new policies, if any, > should ensure > accurate recording of stewardship. It would make an ISP's life -MUCH- > simpler. > > /bill > > > > > On Wed, Jul 11, 2012 at 03:53:19PM +1200, Dean Pemberton wrote: > > So let me ask a simple question. > > > > Do people think that there is a need to develop any more IP policies? Or > > are all the policies we have the moment sufficient for the future? > > > > Dean > > > > On Tuesday, July 10, 2012, Matthew Moyle-Croft wrote: > > > > > I think Randy's taking the wrong tactic with this. > > > > > > Policy needs to be a series of no-rules cage fights or, maybe, > something > > > along the line of gladiator traditions in Roman time. > > > > > > Then it could be televised, a profit made and APNIC run from that > profit > > > rather than charging for IP addresses and ASes. > > > > > > MMC > > > > > > On 09/07/2012, at 6:08 AM, Dean Pemberton wrote: > > > > > > > Morning all, > > > > > > > > Randy Bush (from IIJ in Japan) has just tabled a policy for > discussion > > > > at the August APNIC members meeting. > > > > Essentially if passed this would see the APNIC policy development > > > > process disolved. > > > > > > > > I'm interested in feedback that people on this list may have, and I'm > > > > happy to pass it along on the sig-policy list or in person at the > > > > meeting. > > > > As always, feel free to contribute to what I'm sure will be heated > > > > discussion on the APNIC sig-policy list. I'll try and summarise the > > > > happenings back here. > > > > > > > > Regards, > > > > Dean > > > > > > > > > > > > ---------- Forwarded message ---------- > > > > From: Andy Linton <asjl(a)lpnz.org> > > > > Date: Mon, Jul 9, 2012 at 5:32 AM > > > > Subject: [sig-policy] prop-103-v001: A Final IP Address Policy > Proposal > > > > To: SIG policy <sig-policy(a)apnic.net> > > > > > > > > > > > > Dear SIG members > > > > > > > > The proposal "prop-103-v001: A Final IP Address Policy Proposal" has > > > > been sent to the Policy SIG for review. > > > > > > > > It will be discussed at the Policy SIG at APNIC 34 in Phnom Penh, > > > > Cambodia, Thursday, 30 August 2012. > > > > > > > > We invite you to review and comment on the proposal on the mailing > list > > > > before the meeting. > > > > > > > > The comment period on the mailing list before an APNIC meeting is an > > > > important part of the policy development process. We encourage you to > > > > express your views on the proposal: > > > > > > > > - Do you support or oppose this proposal? > > > > - Does this proposal solve a problem you are experiencing? > If > > > > so, tell the community about your situation. > > > > - Do you see any disadvantages in this proposal? > > > > - Is there anything in the proposal that is not clear? > > > > - What changes could be made to this proposal to make it > more > > > > effective? > > > > > > > > Information about this and other policy proposals is available from: > > > > > > > > https://www.apnic.net/policy/proposals/prop-103 > > > > > > > > Andy, Skeeve, Masato > > > > > > > > > > > > ------------------------------------------------------------------- > > > > > > > > prop-103-v001: A Final IP Address Policy Proposal > > > > > > > > -------------------------------------------------------------------- > > > > > > > > Author: Randy Bush > > > > <randy(a)psg.com> > > > > > > > > > > > > 1. Introduction > > > > ------------------- > > > > > > > > IPv4 is history, with no need to add more pol> > > > NZNOG(a)list.waikato.ac.nz <javascript:;> <javascript:;> > > > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz <javascript:;> > > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

3 2

APNIC - The policy to end all policies prop-103-v001
by Dean Pemberton 10 Jul '12

10 Jul '12

Morning all, Randy Bush (from IIJ in Japan) has just tabled a policy for discussion at the August APNIC members meeting. Essentially if passed this would see the APNIC policy development process disolved. I'm interested in feedback that people on this list may have, and I'm happy to pass it along on the sig-policy list or in person at the meeting. As always, feel free to contribute to what I'm sure will be heated discussion on the APNIC sig-policy list. I'll try and summarise the happenings back here. Regards, Dean ---------- Forwarded message ---------- From: Andy Linton <asjl(a)lpnz.org> Date: Mon, Jul 9, 2012 at 5:32 AM Subject: [sig-policy] prop-103-v001: A Final IP Address Policy Proposal To: SIG policy <sig-policy(a)apnic.net> Dear SIG members The proposal "prop-103-v001: A Final IP Address Policy Proposal" has been sent to the Policy SIG for review. It will be discussed at the Policy SIG at APNIC 34 in Phnom Penh, Cambodia, Thursday, 30 August 2012. We invite you to review and comment on the proposal on the mailing list before the meeting. The comment period on the mailing list before an APNIC meeting is an important part of the policy development process. We encourage you to express your views on the proposal: - Do you support or oppose this proposal? - Does this proposal solve a problem you are experiencing? If so, tell the community about your situation. - Do you see any disadvantages in this proposal? - Is there anything in the proposal that is not clear? - What changes could be made to this proposal to make it more effective? Information about this and other policy proposals is available from: https://www.apnic.net/policy/proposals/prop-103 Andy, Skeeve, Masato ------------------------------------------------------------------- prop-103-v001: A Final IP Address Policy Proposal -------------------------------------------------------------------- Author: Randy Bush <randy(a)psg.com> 1. Introduction ------------------- IPv4 is history, with no need to add more policy. IPv6 is sufficiently plentiful that further policies are not needed. So let us agree to make no more IP address policies or proposals. 2. Summary ---------------- The APNIC community spends time and resources proposing, discussing, arguing, ... about IP address policies out of habit. The process is no longer relevant to actually coordinating the prudent and high quality operation of the internet. 3. Situation in other RIRs --------------------------------- There is an industry of policy wannabes spending inordinate time and resources making endless policy proposals about miniscule issues and baroque corner cases. This is a waste of time and other resources. 4. Details ------------- The policy proposal and decision processes should be closed and stopped after the Phnom Penh meeting. Should an emergency arise, where community consensus is needed, the EC can organize fora for forming that consensus. 5. Pros/Cons ----------------- Advantages: - We would not have to spend time discussing things of small consequence and which do not help the customer/user in any real way. Disadvantages: - It would impact the amateur careers of policy wannabes. This is a feature, not a bug. 6. Effect on APNIC ------------------------- Saves money, time, and other resources such as administrative complexity created by more complex but useless policies. 7. Effect on NIRs ----------------------- Saves money, time, and other resources such as administrative complexity created by more complex but useless policies.. * sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list sig-policy(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/sig-policy

7 10

Global IPv6 Deployment Survey Extended to 13 July
by Elly Tawhai 08 Jul '12

08 Jul '12

Hi NZNOG Community, The 2012 Global IPv6 Deployment Survey is still open for participation. Kind regards, Elly APNIC ________________________________________________________________________ Global IPv6 Deployment Survey Extended ________________________________________________________________________ The 2012 Global IPv6 Deployment Survey has been extended to Friday, 13 July. Please take a few minutes to complete the survey at: https://www.surveymonkey.com/s/GlobalIPv6survey2012 The purpose of the survey is to better understand what can be done to increase IPv6 adoption in the Asia Pacific region and worldwide. The findings from the 2012 survey will be compared to previous years to give a perspective on regional and global progress. The results will be presented and discussed widely. Please provide your name and contact information on the survey form if you wish to receive the draft survey analysis when available. Please also indicate whether you are willing to share additional data with the TNO and GNKS Consult IPv6 Deployment Monitoring team. We appreciate your time and interest in completing this survey. If you have any questions concerning the survey, please send an email to: info(a)gnksconsult.com ________________________________________________________________________ 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

Auckland Curry on Wednesday 11 July 2012 at 7:30pm
by Lin Nah 08 Jul '12

08 Jul '12

HI All, As some of you know InTAC and nethui are on in Auckland this week. There's going to be a curry dinner on Wednesday 11 July 2012 at 7:30pm. Yes TNC on a Wednesday because there's too much going on Thursday including InternetNZ AGM, and Great Blend. I'd like to invite anyone at nznog who is in Auckland to join us for dinner on Wednesday evening, whether or not you are attending Nethui. When: WEDNESDAY 11 July 2012 at 7:30pm. Venue: Raviz at 51 Hobson St, Auckland CBD Map: http://maps.google.com/maps/place?cid=13701671441809390231 http://auckland.thursdaynightcurry.com/index.cgi/Nethui_Curry http://www.facebook.com/events/460908993939232/ Usual TNC rules apply. ie Bill will be split evenly among all attendees. RSVP by email to me OR to the event on facebook. I'm collecting numbers so I can ensure we have enough seats at the restaurant. In case you don't know: There's a regular ThursdayNightCurry in both Auckland and Wellington. Wellington meets weekly at Daawat http://wellington.thursdaynightcurry.com/ Auckland meets fortnightly, location varies http://auckland.thursdaynightcurry.com/ Both start at 7:30pm. Anyone is welcome to join us. regards lin IF you have RSVP'd AND are going, please please put the relevant dates in your diary/electronic calendar/reminders. It is easy to forget.

1 0

Carrier Neutral DC
by James Kelty 05 Jul '12

05 Jul '12

Hello there, We have need to find a good carrier neutral data centre in NZ within the next couple of months. Looking for any opinions/suggestions on who to contact, or who to stay away from. One to two racks, 10 - 20 Mbit/s committed rate (possibly more). Thanks! -James

1 1

Topological map of international transit changes... ispmap
by Barry Murphy 04 Jul '12

04 Jul '12

So this list has been rather quiet of late and I've had some time on my hands to generate another ISPmap for archive... Between 22 April 2012 (http://ispmap.co.nz//work/topmap-22-Apr-2012.html) and 5th July 2012 (http://ispmap.co.nz//work/topmap-05-Jul-2012.html) it's noticeable that the following changes occurred on Tier 1 International transit providers: Telstra Clear: +2 Vocus: +2 Pacnet: -1 Odysey: -1 Global-Gateway: -2 This isn't to say I've got all providers listed, but I'm sure I'm close to it. It also doesn't represent if someone moved from global gateway to vocus and another from vocus to global gateway (swapping customer for customer), still interesting data for some :) Remember a near realtime version is available at http://ispmap.co.nz/realtime.php If I don't have you listed and you have your own ASN, please flick me an email off list and I'll add you seeing as I have a bit of time on my hands. Cheers Barry Murphy

2 1

NZ Traceroute Servers
by Jonathan Brewer 04 Jul '12

04 Jul '12

Hey Folks, I'm interested in building a picture of how NZ traffic flows to and from various Asian destinations. Unless I'm reading the results wrong, Perry's traceroute server here http://tr.meta.net.nz/tr.php appears to have only NZ networks preferring Vocus and Telstra international transit. That leaves us without a view of what the world looks like to networks who escape New Zealand via Odyssey, Pacnet, Telecom. Are there any more traceroute servers around? Am I just plain wrong and not seeing something obvious? Thanks, Jon

11 11

FW: Attn: Vodafone Mail Admin - Bouncing emails
by Regan Murphy 03 Jul '12

03 Jul '12

Trying list because postmaster bounced: 550 #5.1.0 Address rejected postmaster(a)vodafone.co.nz<mailto:postmaster(a)vodafone.co.nz> From: Regan Murphy Sent: Wednesday, 4 July 2012 3:07 p.m. To: 'postmaster(a)vodafone.co.nz' Subject: Attn: Vodafone Mail Admin - Bouncing emails Dear Vodafone Mail Admin I think you are rejecting emails relayed between two of your internal mail servers. Please check and fix. Both Sender and Reporting MTAs listed below belong to you. Thanks Regan From: mail.marshal(a)vodafone.com<mailto:mail.marshal(a)vodafone.com> [mailto:mail.marshal(a)vodafone.com]<mailto:[mailto:mail.marshal(a)vodafone.com]> Sent: Wednesday, 4 July 2012 2:52 p.m. To: OA User Subject: Undeliverable Mail: "FW: xxxxxxx" Your message: From: user(a)oasystems.co.nz<mailto:user(a)oasystems.co.nz> Subject: FW: xxxxxxx Could not be delivered because of Server refused mail at MAIL FROM - 530 5.7.1 Client was not authenticated The following recipients were affected: user(a)vodafone.com<mailto:user(a)vodafone.com> Additional Information ====================== Original Sender: <user(a)oasystems.co.nz<mailto:user(a)oasystems.co.nz>> Sender-MTA: <195.232.244.9> Reporting-MTA: <csmx01aftc.vodafone.co.nz> MessageName: <B4ff3afc60001.000000000001.0003.mml> Last-Attempt-Date: <14:51:55 Wed, 04 July 2012> Regan Murphy Microsoft Solution Architect | OA Systems Ltd | Level 1, OA Systems House, 1C/95 Ascot Ave, Remuera, Auckland 1051, New Zealand DDI +64 (9) 966 5982 | Mobile +64 (27) 566 9914 | Office +64 (9) 522 2370 | regan.murphy(a)oasystems.co.nz<mailto:regan.murphy(a)oasystems.co.nz> | http://oasystems.co.nz<http://oasystems.co.nz/> [Description: Description: cid:image001.jpg(a)01CB4AEA.58C21C30] This communication, including any attachments, may contain information which is confidential. If you are not the intended recipient: please contact the sender as soon as possible; delete all copies of this communication; and note that you are not authorised to read, copy, use or disclose any part of this communication to anyone. Thank you.

2 1

Network Measurement Lab
by Andy Linton 27 Jun '12

27 Jun '12

One of the sessions at the InTAC meeting will be Network Measurement. We'll be presenting a report that InternetNZ has recently commissioned. This report is the first phase of this work and had the following goal: "to identify the key questions and issues relating to New Zealand Internet for which evidence is required to provide a greater understanding" You can see a copy of the report and its three appendices at http://internetnz.net.nz/our-work/Lab The report is by no means the end of the process and we're keen to see active discussion at InTAC and elsewhere. Regards, andy

1 0

Global IPv6 Deployment Survey Extended
by Elly Tawhai 26 Jun '12

26 Jun '12

________________________________________________________________________ Global IPv6 Deployment Survey Extended ________________________________________________________________________ Hi NZNOG Community, The 2012 Global IPv6 Deployment Survey has been extended to Friday, 13 July. Please take a few minutes to complete the survey at: https://www.surveymonkey.com/s/GlobalIPv6survey2012 The purpose of the survey is to better understand what can be done to increase IPv6 adoption in the Asia Pacific region and worldwide. The findings from the 2012 survey will be compared to previous years to give a perspective on regional and global progress. The results will be presented and discussed widely. Please provide your name and contact information on the survey form if you wish to receive the draft survey analysis when available. Please also indicate whether you are willing to share additional data with the TNO and GNKS Consult IPv6 Deployment Monitoring team. We appreciate your time and interest in completing this survey. If you have any questions concerning the survey, please send an email to: info(a)gnksconsult.com ________________________________________________________________________ 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

NZRR Route Registry Update
by NZRR Database Notifications 25 Jun '12

25 Jun '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: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.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, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.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.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.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.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.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.21.128.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.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.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120511 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.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, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.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.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.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.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.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.21.128.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.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.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120626 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 25 Jun '12

25 Jun '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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.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, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.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.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.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.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.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.21.128.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.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.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120511 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, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.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, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.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.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.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.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.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.21.128.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.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.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120626 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 25 Jun '12

25 Jun '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: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.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, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.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.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.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.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 202.6.5.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.21.128.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.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.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120330 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, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.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, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.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.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.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.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.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.21.128.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.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.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120626 source: NZRR ------------------------------------------------------------

1 0

DNSSEC and .school.nz
by Craig Whitmore 25 Jun '12

25 Jun '12

Did something go wrong today with .school.nz being signed? And its back to insecure now? And I've noticed ac.nz, gen.nz, maori.nz are not signed yet and this problem only occurred with .school.nz as far as I can tell.. Jun 25 13:47:49 r1 named[2660]: validating @0x7f2220c555b0: school.nz DNSKEY: no valid signature found Jun 25 13:47:49 r1 named[2660]: validating @0x7f22207af970: school.nz SOA: no valid signature found Jun 25 13:47:49 r1 named[2660]: validating @0x7f2220997250: school.nz DNSKEY: no valid signature found Jun 25 13:47:49 r1 named[2660]: validating @0x7f22207af970: 3efu8lgrkhh5rbhpeeqojsqoblnvlrsf.school.nz NSEC3: no valid signature found Jun 25 13:47:49 r1 named[2660]: validating @0x7f2220d39ac0: school.nz DNSKEY: no valid signature found Jun 25 13:47:49 r1 named[2660]: validating @0x7f22207af970: eqboea4ak1cjiaoe9jcmqqadeei7u4rt.school.nz NSEC3: no valid signature found Thanks Craig – Geek..

2 1

NZRR Route Registry Update
by NZRR Database Notifications 24 Jun '12

24 Jun '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: AS24388:RS-ROUTES:AS38477 descr: advertised to AS24388 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.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 20120502 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, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.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 20120625 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 24 Jun '12

24 Jun '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:AS38477 descr: advertised to AS9439 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.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 20120502 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, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.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 20120625 source: NZRR ------------------------------------------------------------

1 0

New prefix at APE: 103.247.56.0/24
by Michael Fincham 24 Jun '12

24 Jun '12

Hi everyone, (cross-posted to NZNOG since nzix-route-announce still seems pretty much dead...) We intend to begin announcing the prefix 103.247.56.0/24 to the APE in approximately 2 weeks. This prefix will be originated from AS38477. This will bring our total set of (le 24) announced prefixes to: 114.23.96.0/22 originated from AS38477 113.130.120.0/22 originated from AS38294 path: 38477 38294 116.90.128.0/20 originated from AS38477 202.6.116.0/23 originated from AS38477 192.138.251.0/24 originated from AS38590 path: 38477 38590 182.50.160.0/22 originated from AS45641 path: 38477 45641 116.90.135.0/24 originated from AS45641 path: 38477 45641 202.37.124.0/23 originated from AS38477 131.203.133.0/24 originated from AS56102 path: 38477 56102 131.203.134.0/23 originated from AS56102 path: 38477 56102 202.44.60.0/22 originated from AS56214 path: 38477 56214 202.50.102.0/24 originated from AS38477 103.11.124.0/22 originated from AS38477 103.246.250.0/24 originated from AS38477 122.102.108.0/23 originated from AS38477 103.8.232.0/22 originated from AS132255 path: 38477 132255 103.247.56.0/24 originated from AS38477 -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250

1 0

Any spare Junipers?
by Nick Larsen 19 Jun '12

19 Jun '12

Hi all, Does anyone have any J2320's or SRX240h's for sale (in any condition, as just for a lab environment)? If so, please email nick(a)aptiv.co.nz Cheers, Nick Larsen

1 0

ARIN allows inter-RIR transfers.
by Dean Pemberton 18 Jun '12

18 Jun '12

Hi All, ARIN (the North American equivalent of APNIC) has just passed some new policy which has an impact for organisations in this region. There were three policies passed: ARIN-2011-1: ARIN Inter-RIR Transfers https://www.arin.net/policy/proposals/2011_1.html ARIN-2012-1: Clarifying requirements for IPv4 transfers https://www.arin.net/policy/proposals/2012_1.html ARIN-2012-3: ASN Transfers https://www.arin.net/policy/proposals/2012_3.html The impact for users in this regions is that APNIC members are now able to negotiate IPv4 Address Space transfers from organisations within the North American region. We have seen organisations in the ARIN region selling IP Address space in the past (Nortel selling 666k addresses to Microsoft for 7.5 million) , infact ARIN now has specific policy surrounding how to deal with a transfer in a bankruptcy scenario. The tricky part was that up until now they only allowed transfers to other members within the ARIN region. This meant that APNIC members were not able to get access to these resources and pull them into their APNIC account (and update the details around who currently holds them). This has now been changed so that as long as you can demonstrate to APNIC that you have a need for the addresses, and would have qualified for them under the old allocation scheme (ie when they still had addresses to give out), then you can transfer the numbers from the ARIN member into the APNIC region. This is generally considered a good thing. Having all users on an even footing is a step in the right direction. Anyone wanting some more clarification then feel free to post (if you think it's relevant to everyone) or mail me directly. Regards, Dean

5 5

InTAC invite
by Andy Linton 18 Jun '12

18 Jun '12

I forwarded something on this several days ago and I'm going to badger you once more about it. 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. See www.internetnz.net.nz/intac This is a chance for members of this group to meet with folks they often don't catch up with from the larger telcos and other industry players. We've got a couple of good speakers: Lev Gonick <http://www.case.edu/its/about/levgonick.html>, Chief Information Officer of Case Western Reserve University, Cleveland, USA Geoff Huston<http://www.apnic.net/publications/research-and-insights/geoff-huston>, Chief Scientist at APNIC and a chance to have some serious discussion about Technical Architecture Connectivity vs. Content UFB product specifications Technical Policy Keeping local traffic local - peering and interconnect Domestic and international IP transit

1 2

rs2.ape scheduled maintenence
by Tim Hoffman 17 Jun '12

17 Jun '12

Greetings, On Thursday 14 June Citylink will be taking rs2.ape (192.203.154.2) down for maintenance from 0800 till 0900. During this change window we will be observing a change freeze on the rest of the route servers nationwide. This is in preparation for upgrades which we are undertaking in the short to medium term. Cheers, Tim

1 1

ACL analyser
by Julian Maxwell 14 Jun '12

14 Jun '12

Hi All, I have a several-hundred-line extended ACL on a 6500, which is several years old and has had several admins over its time. As such, it is severaly (See what I did there?) ugly. I'm trying to find a tool that I can load this ACL into and it will tell me about redundant entries etc., as I have been given the envious task of moving the service it protects to a proper firewall. CiscoWorks ACL tool looks to be the business, but alas it's EOL and I can't find it anywhere. I don't want to pay hundreds/thousands for using something only once either. So what say you guys? Any suggestions on ACL managers? (Before you suggest, Gareth Evans ACL simulator won't work as you can't load ACL's into it). Cheers! Julian

3 2