- NZNOG - lists.nznog.org

Telstraclear international proxy?
by Jethro Carr 13 Aug '09

13 Aug '09

hi all, I am seeing an unusual problem with accessing international sites which I believe is being caused by a proxy on international HTTP access for Telstraclear cable internet users. I was attempting to setup virtualhosts on a new webserver (US based) and added entries to /etc/hosts in order to test the sites before I updated the DNS records. However, any access attempt to the new server on port 80 would just return the current production site, which was running on a different server (also in the US). Confirmed with tcpdump that my packets were leaving my computer for the correct IP. There is no proxy in place on my network. I believe there is some kind of proxy/cache for international traffic from Telstraclear's cable network. The proxy is set up in such a way, it ignores the destination IP address being requested and instead takes the requested hostname, resolves it via DNS and fetches the page from the resolved server IP. DEMONSTRATION If I take an international IP and use it for my browser's proxy settings, I find that I can use that IP as a proxy to access any other international website (but not domestic). eg: 74.125.67.100 (google.com) 212.58.254.252 (bbc.com) Using either IP as a proxy will allow me to reach any other international site, but will not allow access to domestic sites (returns blank page). ASSISTANCE Has anyone seen this problem before or know of any caching being taken place by Telstraclear? Would also be good to know if it's specific to Telstraclear cable customers, or other Telstraclear customers as well. Any advice on how I might be able to query the proxy to identify it's owner would be appreciated. thanks, jethro -- Jethro Carr www.jethrocarr.com/index.php?cms=blog www.amberdms.com

11 16

What is more important? - ipv4 vs. routing table size
by Skeeve Stevens 13 Aug '09

13 Aug '09

Hey all, I'd like to stimulate some discussion regarding IPv4 conservation vs. The size of the routing table. I'd like to hear what people think is more important - and why - which it is more important - or a miz? IPv4 conservation - possibly allocating smaller default allocations - or making it easier (/24, /23) vs. The size or the routing table. If by a more conservative allocation above was done, and the world table jumped to 400, 500 thousands or more routes - what implications would this have on routers and so on. APNIC's minimum is a /22 (was a /19 in 2000) (4 * /24's) ARIN is a /20 to ISPs (16 * /24's) RIPE is a /21 (8 * /24's) LANIC is a /21 (I think) AFRINIC is a /22 (4 * /24's) There are smaller hosting companies out there (here in ANZ at least) that want to be on, hosting, multi-homed, but only need a /24 or /23, but they're given the minimum allocation on a /22 - whether they need it or not. Thoughts? -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

5 5

KIWICON ]|[ - 2009 - Call For Papers
by Kiwicon <3 12 Aug '09

12 Aug '09

A wise deadite captain once yelled "Cry Havoc and let loose the Dogs of War!". Quite frankly, we couldn't have said it better ourselves: ~~ ~~ || || @@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@\___ @@@@@@@@@@@@@@@@@@ \ @@@@@@@@@@@@@@@@@ X___/ \/ KIWICON ]|[ 28TH & 29TH NOVEMBER 2009 With a current record of three arrests, seven conceptions and one committal Kiwicon is back for 2k9. The time has come to fake up an abstract and submit it to the Kiwicon Crue for judgement. In the coming months, we predict you will spend more time dreaming of kudos and UID 0 than actually working on your slides, since you'll be doing them the night before anyway. It's not New Zealand's only security conference, but it is the one where you're more likely to get a standing ovation for scanning an entire country than pointed questions regarding whether you were, perhaps, a little reckless in accessing systems without authorisation. _ _-(")- `%%%%% `KIWICON` // \\ The Crue holds a special place in their bowels for those who are aggravated that Kiwicon is held on a weekend so they don't get time off work. It is a gathering for those who are passionate about security. It has been hacked together by the .nz security scene for the .nz security community. Following in the tradition of previous cons, the atmosphere is extremely laid back; even the feds don't wear suits. Kiwicon is about sharing information. It's about intersections and cross-pollination and dissemination and other nouns disturbing reminiscent of a pre-AIDs key party. Sure, you could bring your RFID readers, your lockpicks or even your back track DVD but mostly you just need to bring yourself and the willingness to learn. For a little con down under we don't do too bad. Previously, Kiwicon has featured: the Crackstation, iKat (last seen at a airport near you), layer two telco shenanigans, a video montage of boardrooms across Japan, old school phreaking on new school kit, exposure of RIM's failure to hide their snooping capabilities, fun with the SCADA systems, making Microsoft look like turkeys, nuking various heap protections from space, and of course fucking up the certificate chain of your new passport. _ _-(")- `%%%%% // \\ `THE VENUE` The Crue is aware that location is everything, so once again we will be invading the Pipitea Campus which is surrounded by prestigious Wellington buildings such as Parliament house, the (partly renovated and badly secured) High Court, Ministry of Defence and various telecommunication hubs. All services are handy to the venue as well (train station, taxi rank, burger caravan, police cells / court etc). Caffeination will be provided by the lovely folks at Sweet Fanny-Anne's. _ _-(")- `%%%%% // \\ `THE PRICE` A recession-proof fifty bucks for the employed. Students and those otherwise supported by our precious taxpayer dollars (this does not include Members of Parliament) will pay $30. GST receipts will be available on request. The Crue will endeavour to leverage its synergies to architect a compelling ROI solution. _ _-(")- `%%%%% // \\ `THE TOPICS` Social networking/automated stalking, Cellular Networks (GSM,2degrees, openbts), State-sponsored surveillance, Malware (Viruses, Botnets), The Scam of EAL Certification, Industrial Espionage, Reverse Engineering, The Failwhale Rider, Virtualisation, Flash mobs, WebApps, 0hday The schedule will be made up as we go, so fifteen minutes or thirty minutes worth of material should be submitted as fifteen or thirty minutes worth of talk. We do place an upper limit of an hour (including questions), as anything longer than that can continue at the pub. _ _-(")- `%%%%% // \\ `SUBMISSIONS` These need to be in by the Witching Hour of the 31st October (NZST). Expats and wanna-be Kiwis will want to get their submissions in by 10th October, when we're going to be announcing the first round of Interesting Stuff. To submit a presentation to Kiwicon2k9, send an email to cfp(a)kiwicon.org with the following information: * Name or Handle: * Country of Residence: * Employer (if applicable): * Presentation Title: * Presentation Length: * Presentation Synopsis: * Brief Bio: If you do not provide a bio, one will be provided for you. _ _-(")- `%%%%% // \\ `BOTTOM LINE` The Crue want you to submit your talk to Kiwicon or the cute little header sheep gets it. _ -(")- `%%%%% // \\ `CONTACT` Email us: kiwicon(a)kiwicon.org Check the site: https://www.kiwicon.org/ Drop by silc: silc.kiwicon.org:2706/kiwicon Join the list: hackers-subscribe(a)kiwicon.org CFP online at https://kiwicon.org/cfp2k9.txt

1 0

Cable cuts in Asia
by Juha Saarinen 12 Aug '09

12 Aug '09

Reading in Commsday and Computerworld Singapore that APCN2, APCN, EAC and SMW3 near Taiwan have developed faults, possibly due to typhoon Morakot. Anyone in NZ noticing the effect of that? -- Juha

2 1

175/8 and 182/8 allocated to APNIC
by Leo Vegoda 11 Aug '09

11 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in August 2009: 175/8 and 182/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFKguZyvBLymJnAzRwRAmDCAKCCnxLNmk32v+sm786x5RyVLnLBDACcCu5I zCs7FdAdkIZRnfNtuVyVB0s= =6huK -----END PGP SIGNATURE-----

1 0

Re: [nznog] Telecom International HTTP Caching
by Paul Tinson 11 Aug '09

11 Aug '09

As a general rule if the content is in a page that gets retrieved by the cache it will be cached and served from the cache to subsequent requests. This includes mp3 files if they are an embedded object. If the mp3 is a single file then I would not expect it to be cached in parts, so it should not be missing pieces. If it's a streaming mp3 that may be different and if you supply an example URL I can check this. If you don't want it cached or want to control the time we keep it in cache then you can use cache control directives and expiry meta tags in the page. At this point in time we have not enabled caching of streaming media. If you have a specific example URL please send it to me and I can double check though. If we have cached it I will look into why. I am happy to look into specific examples of issues, but if you have a wider service effecting issues please continue to use the helpdesk as this will result in calls being handled correctly and not left unattended on the list. Hope this answers your questions. Regards Paul -----Original Message----- From: Richard Hulse [mailto:Richard.Hulse(a)radionz.co.nz] Sent: Wednesday, 12 August 2009 9:00 a.m. To: nznog; Paul Tinson Subject: Re: [nznog] Telecom International HTTP Caching Hi Paul, I'll ask this on the list, as there are quite a few (other) audio and video content providers here... How will the cache handle MP3s that are served via HTTP? Is this content you want to cache? Should we be setting some sort of header to make it work better? Willl you also be caching on-demand Windows Media content? I ask because I have noticed that some of our visitors complain of Mp3 audio that is truncated or has bits missing out of the middle. It seems to clear itself after a few hours. cheers, Richard Hulse Webmaster Radio NZ

5 5

Re: [nznog] Telecom International HTTP Caching
by Richard Hulse 11 Aug '09

11 Aug '09

Hi Paul, I'll ask this on the list, as there are quite a few (other) audio and video content providers here... How will the cache handle MP3s that are served via HTTP? Is this content you want to cache? Should we be setting some sort of header to make it work better? Willl you also be caching on-demand Windows Media content? I ask because I have noticed that some of our visitors complain of Mp3 audio that is truncated or has bits missing out of the middle. It seems to clear itself after a few hours. cheers, Richard Hulse Webmaster Radio NZ

1 0

Telecom International HTTP Caching
by Paul Tinson 10 Aug '09

10 Aug '09

Good Morning, Telecom would like to advise that over the coming weeks we will be extending our international http caching service. This work should go unnoticed but if you or your customers do experience a loss of international browsing then please contact the Broadband Helpdesk on: adsl_helpdesk(a)xtra.co.nz Please make sure the subject has "HTTP Caching" included so that the Helpdesk can filter on these issues. If you would like to talk to the Helpdesk then please phone: 0800 22 55 98 Please state that you believe this to be an http caching issue when raising the case so that it will be routed to the correct resources. NB. Please note that the service is only in place for Telecom Broadband Customers and "International" in this case is based on the international routing tables, as such some domestic sites may appear to Telecom as international content. If you have any specific questions about the service then please feel free to post the questions on this mailing list and as time allows they will be answered. Regards Paul Tinson Senior Specialist Web App Services Shared & Other IS Operations E paul.tinson(a)telecom.co.nz <mailto:paul.tinson(a)telecom.co.nz> W www.telecom.co.nz <http://www.telecom.co.nz> Level 9, 31 Airedale Street Auckland ________________________________ "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."

3 4

Re: [nznog] Telstraclear international proxy?
by Anton Smith 10 Aug '09

10 Aug '09

> Message: 12 > Date: Tue, 11 Aug 2009 10:31:53 +1200 > From: Dean Pemberton <nznog(a)deanpemberton.com> > Subject: Re: [nznog] Telstraclear international proxy? > To: nznog(a)list.waikato.ac.nz > Message-ID: <4A809FD9.3040700(a)deanpemberton.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 11/08/09 12:31 AM, Anton Smith wrote: > > In the beginning when diagnosing the problem, an engineer might not > > even know that the problem lies with Telstra, and we have seen people > > posting http headers and so on in the past wondering what was going > > on. > > > > I don't believe that was the case in this instance. It was not a > general query about a general problem. It was a specific technical > issue with a specific ISP. In that case a trouble ticket should be > logged with the ISP first, then post to the list. I'd even accept if > these were both done at the same time. > > To not give the ISP involved a chance to address the issue through > normal customer support channels is not giving them a fair go. > Some ISPs are not very good at customer support, but if you don't log > the call, then how can you expect anything of them. > > I'll explain some more why this is so important; > In years gone by, NZNOG was seen by the major Telcos and some ISPs as a > bunch of troublemakers. I know this for a fact because I've worked for > them while they held this opinion. They viewed NZNOG as a group of > individuals constantly waiting to bash them at any opportunity. The > minute that someone found a bug, or a technical issue, they would post > it first to NZNOG and everyone would hang the associated ISP/Telco out > to dry. > > As such, no one from those organisations joined NZNOG, contributed to > NZNOG, attended the NZNOG conference, etc etc etc. > > Over time we have worked very hard to re-engage with the ISPs and > Telcos, making NZNOG a place where they can derive benefit from > contributing to. Just today we see Paul Tinson posting about Telecom's > cache changes. I doubt anyone would disagree that this is the sort of > involvement that we want. > > Do you think that TelstraClear are going to engage with NZNOG if just > the week previously an NZNOG member was posting publically about > technical issues on their network before giving them a chance to address > them? > > It's a bit like someone buying a shirt at a store, being unhappy with > it, and doing a spot on Campbell Live before going back to the shop and > asking for a refund. Now sure, Campbell Live has its place. It even > has a place for long running retail disputes, but it shouldn't be the > first port of call. And neither should NZNOG. > > We work hard with the Telcos to keep them engaged (the benefits of which > can be seen in Telecoms post this morning), please keep this in mind > when posting. Just make sure you've worked with them first. If you > have and they did a bad job, then by all means post and all bets are off =) > > > Dean > Hi Dean, Given the general difficulties in resolving problems with various ISP/Carriers it is sometimes a fact that the only place you can learn what you need to is here. I'm very heartened by the Telecom post about their caching, and being very specific about the path to follow if there are issues encountered. That is exactly what I believe is missing from Telstra. Perhaps our discussions here (that may be deemed off topic in which case I shall raise the virtues of beer later) are actually constructive in that they can help highlight to carriers how a proactive approach might be used. I do however completely agree with you that it is important to foster a greater sense of community that includes the carriers, ISPs and NZNOG. It is important that NZNOG is not just seen as a bashing list. However, I did not really see that the original post about the caching was negative, and far from "bashing".. so I hardly think that the relationship between NZNOG and Telstra would have been damaged. Maybe my own post had a disgruntled tone, for which I apologise - I shouldn't have done that. I do believe that proactive approaches from the bigger players towards the list (like the Telecom post) are brilliant, and I encourage others (Telstra) to do something similar. Regards, Anton

2 1

Re: [nznog] NZNOG Digest, Vol 80, Issue 9
by Anton Smith 10 Aug '09

10 Aug '09

Hi Dean, While I agree with the general notion that people should go to the ISP directly first, in the Telstra case with their transparent proxy I think it is okay posting here. Mainly because most people on this list know it is there, while most people on the ISPs desk probably don't. Telstra could make this a bit better for themselves by being more verbose about the proxies presence, rather than getting various levels of brokenness complaints. In the beginning when diagnosing the problem, an engineer might not even know that the problem lies with Telstra, and we have seen people posting http headers and so on in the past wondering what was going on. I just think that this kind of thing is a natural side effect of an ill publicised (and some would argue, annoying) network feature, and if Telstra are not proactive about letting people know they have it and the problems that may arise, then they deserve the occasional mail list post. Regards, Anton Disclaimer: I have run into their proxy before due to asymmetric routing + transparent proxy unhappiness (resulted in what looked like a black hole). On Mon, Aug 10, 2009 at 2:00 AM, <nznog-request(a)list.waikato.ac.nz> wrote: > From: Dean Pemberton <nznog(a)deanpemberton.com> > Subject: Re: [nznog] Telstraclear international proxy? > To: nznog <nznog(a)list.waikato.ac.nz> > Message-ID: <4A7F6257.9080104(a)deanpemberton.com> > Content-Type: text/plain; charset=ISO-8859-1 > > > I'd like to take this opportunity to remind people that the appropriate > way to handle situations like this is to log a support call with the > ISPs helpdesk before posting support questions to this list. > > If you believe that it is a problem which effects the NZ Operator > community as a whole and you have exhausted your options (including > escalations) with the ISP concerned then it is maybe appropriate to post. > > This is to eliminate the situation where an ISP finds its name/helpdesk > practices used in vain throughout a mailing list without being given a > chance to put the matter right in private first. > > > Thanks > Dean

5 4

Re: [nznog] Telstraclear international proxy?
by Philip D'Ath 09 Aug '09

09 Aug '09

I can see that becoming urban slang. -----Original Message----- From: Steve Phillips Sent: Mon 10/08/2009 15:15 To: nznog Subject: Re: [nznog] Telstraclear international proxy? Sorry for the completely pointless empty post. My cat did it ! -- Steve. Steve Phillips wrote: > Gordon Smith wrote: >> The bulk of the caching issues service providers are asked to deal >> with come about because people don't know how to configure web servers. >> >> Meta tags and expires are actually useful, but it seems that there are >> always a few people that don't use them, even though their content is >> dynamic.

2 1

Re: [nznog] Microsoft xbox spam ?
by Ian Batterbee 09 Aug '09

09 Aug '09

Just to head off further replies on this thread - I believe the problem was that I was forced to register with microsoft's games for windows (or some such name) when I installed GTA4 many months ago, and it seems that Microsoft have emailed everyone on there, rather than just xbox platform owners. So although unwanted, it was probably legit and just an oversight on their part. Ian Batterbee wrote: > >> Has anyone else received spam from Microsoft about an XBox service update >> ? >> >>

1 0

Google Wave
by James Jones 09 Aug '09

09 Aug '09

I am just curious if anyone else on NZNOG is play with Wave Federation Server? James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

2 1

Microsoft xbox spam ?
by Ian Batterbee 07 Aug '09

07 Aug '09

Has anyone else received spam from Microsoft about an XBox service update ? The message claims that I received it as part of my XBox Live subscription, but since I don't have such a subscription, and don't even own an xbox, I think they're telling porkies.

1 0

APNIC training August 2009
by Elly Tawhai 06 Aug '09

06 Aug '09

________________________________________________________________________ APNIC training and hostmaster consultations in Wellington and Auckland, New Zealand, 3-4/5-6 August 2009 ________________________________________________________________________ Dear All, APNIC is pleased to invite you to attend the following training courses and hostmaster consultation sessions in New Zealand: Course: IRM (Internet Resource Management) and APNIC update Date: 3 August 2009 Location: Wellington, New Zealand Venue: InternetNZ Level 10 Exchange Place 5 - 7 Willeston Street Course: IRM (Internet Resource Management) Date: 5 August 2009 Location: Auckland, New Zealand Venue: CallPlus Level 4, Qantas House 191 Queen Street Event: Hostmaster individual consultations Date: 4 August 2009 Location: Wellington, New Zealand Venue: InternetNZ Level 10 Exchange Place 5 - 7 Willeston Street Event: Hostmaster individual consultations Date: 6 August 2009 Location: Auckland, New Zealand Venue: CallPlus Level 4, Qantas House 191 Queen Street Fees: Fees are for training only. There is no charge for the consultation sessions Pay onsite (cash only) Pay online (credit card) ----------------------- ------------------------ APNIC members: NZD 100 AUD 65 Others: NZD 130 AUD 85 (The online fee is charged in Australian dollars and includes a 20% discount) Notes: ------ - The Hostmaster consultations and training sessions are two distinct events with separate registration processes. - Training courses run from 09:00 to 17:00. - Hostmaster consultations fun from 09:30 to 13:00. - Lunch, refreshments, and training materials are provided. - Seats are limited and the registration is on a 'first come-first served' basis with priority given to APNIC members. To register for the Wellington training, please go to: http://www.apnic.net/events/whats-on/training-events/calendar/events/2009/n… To register for the Auckland training, please go to: http://www.apnic.net/events/whats-on/training-events/calendar/events/2009/n… For course information please go to: http://www.apnic.net/services/services-apnic-provides/training/courses/core… If you have problems registering please contact stella(a)apnic.net Hostmaster consultations ------------------------ APNIC is offering free, individual Hostmaster consultation sessions. At these sessions you can ask about: - How to request IPv4, IPv6, and AS numbers from APNIC - How APNIC hostmasters will evaluate your resource request - Current policies for IP and AS number management in the APNIC region - How to maintain and update your resource registration record in the APNIC Whois Database - Any individual issues you might have To register for the Hostmaster consultations, please email: elly(a)apnic.net Best regards, APNIC training team ________________________________________________________________________ APNIC Training training(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61 7 3858 3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ________________________________________________________________________

2 1

FW: Content again - legality question
by Skeeve Stevens 06 Aug '09

06 Aug '09

Again, any thoughts on the NZ situation (legally) regarding this? -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Friday, 7 August 2009 12:59 AM To: ausnog(a)ausnog.net Subject: [AusNOG] Content again - legality question Hey all, Content question again - but this time a legal question. For any content that is 'freely available on the web' - what is the legality of acquiring this content and delivering it locally? For example.. many TV stations are uploading full episodes onto their websites after the show has aired. YouTube would be another example. I am only talking about free content - which is not paid for, but freely downloadable from websites. I guess I am talking about a 'pre-caching' kind of situation. Also, does anyone know at what point music becomes legally free to use in Australia?... like books after 50years after the authors death (in the US it is 20). ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

8 9

FW: Content - Music, Movies, TV
by Skeeve Stevens 05 Aug '09

05 Aug '09

Hey all, Any comments on the NZ situation regarding this? -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Friday, 7 August 2009 12:55 AM To: ausnog(a)ausnog.net Subject: [AusNOG] Content - Music, Movies, TV Hey all, I have multiple clients who are wanting to sell content to their customers. There are multiple scenarios: - ISP's to their users - Hotspots in accommodation locations wanting to sell it to visitors - similar to in-room entertainment in big hotels - Providers of in building connectivity who want to delivery triple-play to their residents Does anyone know of any aggregators of this kind of content with the studios and so on? ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Aug '09

05 Aug '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090806 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Aug '09

05 Aug '09

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-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090806 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] [AusNOG] APNIC Policy SIG Co-Chair
by Skeeve Stevens 05 Aug '09

05 Aug '09

Hey there Andy, I've actually put myself down as well.... nowhere near as much experience as you clearly... just trying to get some ANZ representation. Will you need a co-chair-assistant lacky? ;-) Well, if you win, awesome... maybe next time for me! Clearly CN will have the votes.... I wonder how many from ANZ are going to Beijing? ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? > -----Original Message----- > From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog- > bounces(a)lists.ausnog.net] On Behalf Of Andy Linton > Sent: Wednesday, 5 August 2009 12:41 PM > To: ausnog(a)lists.ausnog.net > Subject: [AusNOG] APNIC Policy SIG Co-Chair > > This is a bit cheeky of me - join the AusNOG list and post off topic > immediateley but... > > There was a recent announcement on the APNIC sig-policy mailing list > seeking candidates for this role. You can see the announcement at: > > http://mailman.apnic.net/mailing-lists/sig- > policy/archive/2009/08/msg00005.html > > I have submitted a response to this (http://notnil.org/) and I'd like > to > ask for your support if we get to the point where there is an election > process. If I get the nod I will buy beer but you'll need to be in > Beijing for the APNIC meeting. > > I'd also encourage you to consider the proposals that are being > discussed on the sig-policy list and which will be on the agenda at > the Beijing meeting. A number of these could have an impact on > operations over the next year or so. See > http://www.apnic.net/community/policy/proposals > _______________________________________________ > AusNOG mailing list > AusNOG(a)lists.ausnog.net > http://lists.ausnog.net/mailman/listinfo/ausnog

3 3

Web Base Connectivity
by Dan Clark 04 Aug '09

04 Aug '09

Gidday, has anyone else got connectivity issues through to www.webabse.co.nz ? Connecting from XTRA/Telecom doesn't seem to get past MaxNet but connecting from via APE its fine?? Regards Dan Clark

9 9

Re: [nznog] Web Base Connectivity
by jamie baddeley 04 Aug '09

04 Aug '09

I thought of that too, but sadly it measures in a single dimension. And AFAIK it's not distributed. Happy to be proved wrong. jamie On Tue, 2009-08-04 at 21:21 +1200, Nathan Ward wrote: > Also, http://downforeveryoneorjustme.com/ > > On 4/08/2009, at 8:03 PM, jamie baddeley wrote: > > > I think something like this within NZ is quite good. > > > > http://internethealthreport.com/ > > > > Would help with operational problems like this. > > > > Surely WAND could do that thing? I think there's real value we could > > all > > add to that idea. > > > > It's nice to be able to go to a place which basically gives a > > dashboard > > display. Maybe an iPhone app or something for all you Beret wearing > > Apple folks out there ;-) > > > > Who's going to LCA Next year? > > > > cheers, > > > > jamie > > > > On Tue, 2009-08-04 at 18:58 +1200, Gerard Creamer wrote: > >> And OK from my TelstraClear cable connection: > >> > >> | > >> ------------------------------------------------------------------------------------------| > >> | WinMTR > >> statistics | > >> | Host - % | Sent | Recv | > >> Best | > >> Avrg | Wrst | Last | > >> | > >> ------------------------------------------------| > >> ------|------|------|------|------|------| > >> | 192.168.9.1 - 0 | 64 | 64 | 0 > >> | 1 | 93 | 0 | > >> | 121-73-66-1.cable.telstraclear.net - 0 | 64 | 64 | 0 > >> | 26 | 360 | 15 | > >> |ge-2-0-0-874-ie2-internet.telstraclear.net - 0 | 64 | 63 > >> | 15 > >> | 23 | 62 | 31 | > >> |ge-2-0-0-874-ie1-internet.telstraclear.net - 0 | 64 | 64 > >> | 15 > >> | 20 | 46 | 15 | > >> | 203.167.232.174 - 0 | 64 | 64 | 15 > >> | 28 | 203 | 31 | > >> | gi6-1.hsa2.alb.maxnet.net.nz - 0 | 64 | 64 | 15 > >> | 31 | 250 | 31 | > >> | gi3-819.akmn1-br2.webhost.co.nz - 0 | 64 | 64 | 15 > >> | 20 | 78 | 15 | > >> | gi1-9.akmn1-csw2.webhost.co.nz - 0 | 63 | 63 | 15 > >> | 22 | 62 | 31 | > >> | webbase.co.nz - 0 | 63 | 63 | 15 > >> | 26 | 125 | 31 | > >> |________________________________________________|______|______| > >> ______|______|______|______| > >> WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( > >> stanimir(a)cr.nivis.com ) > >> > >> Cheers, > >> Gerard > >> > >> > >> Lindsay Druett wrote: > >>> Now, did you mean www.webbase.co.nz <http://www.webbase.co.nz> ? > >>> > >>> lindsay(a)alcyone:~$ traceroute webbase.co.nz > >>> traceroute to webbase.co.nz (203.89.178.165), 30 hops max, 60 byte > >>> packets > >>> 1 tehlinzathome-14.fx.net.nz (131.203.124.14) 19.036 ms 19.381 ms > >>> 19.732 ms > >>> 2 GigabitEthernet0-3-200.akkin-rt2.fx.net.nz (131.203.80.254) > >>> 8.232 > >>> ms 9.912 ms 11.120 ms > >>> 3 131.203.252.130 (131.203.252.130) 12.144 ms 13.428 ms 14.687 > >>> ms > >>> 4 gi1-8.akmn1-csw2.webhost.co.nz (119.47.119.142) 15.706 ms > >>> 16.710 > >>> ms 17.737 ms > >>> 5 webbase.co.nz (203.89.178.165) 19.917 ms 20.276 ms 21.200 ms > >>> > >>> > >>> On Tue, 2009-08-04 at 18:28 +1200, Dan Clark wrote: > >>>> Gidday, has anyone else got connectivity issues through to > >>>> www.webabse.co.nz <http://www.webabse.co.nz>? > >>>> Connecting from XTRA/Telecom doesn't seem to get past MaxNet but > >>>> connecting from via APE its fine?? > >>>> > >>>> Regards > >>>> Dan Clark > >>>> > >>>> -- > >>>> This message has been scanned for viruses and > >>>> dangerous content by *MailScanner <http://www.mailscanner.info/>*, > >>>> and is > >>>> believed to be clean. > >>>> _______________________________________________ > >>>> NZNOG mailing list > >>>> NZNOG(a)list.waikato.ac.nz <mailto:NZNOG(a)list.waikato.ac.nz> > >>>> http://list.waikato.ac.nz/mailman/listinfo/nznog > >>>> > >>> > >>> -- > >>> This message has been scanned for viruses and > >>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, > >>> and is > >>> believed to be clean. > >>> ------------------------------------------------------------------------ > >>> > >>> _______________________________________________ > >>> NZNOG mailing list > >>> NZNOG(a)list.waikato.ac.nz > >>> http://list.waikato.ac.nz/mailman/listinfo/nznog > >>> > >> _______________________________________________ > >> NZNOG mailing list > >> NZNOG(a)list.waikato.ac.nz > >> http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > !DSPAM:22,4a77eb4773596020614038! > > > > > > -- > Nathan Ward

4 4

APNIC Policy SIG Co-Chair
by Andy Linton 04 Aug '09

04 Aug '09

There was a recent announcement on the APNIC sig-policy mailing list seeking candidates for this role. You can see the announcement at: http://mailman.apnic.net/mailing-lists/sig-policy/archive/2009/08/msg00005.… I have submitted a response to this and I'd like to ask for your support if we get to the point where there is an election process. If I get the nod I will buy beer but you'll need to be in Beijing for the APNIC meeting. I'd also encourage you to consider the proposals that are being discussed on the sig-policy list and which will be on the agenda at the Beijing meeting. A number of these could have an impact on operations over the next year or so. See http://www.apnic.net/community/policy/proposals

1 0

Cisco.com Outage FYI
by Skeeve Stevens 03 Aug '09

03 Aug '09

Cisco.com outage http://blogs.cisco.com/news/comments/final_update_ciscocom_outage/ -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 1

Two new /8s allocated to APNIC from IANA (175/8 and 182/8)
by Srinivas (Sunny) Chendi 03 Aug '09

03 Aug '09

_______________________________________________________________________ Two /8s allocated to APNIC from IANA (175/8 and 182/8) _______________________________________________________________________ Dear colleagues The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in August 2009 and will be making allocations from these ranges in the near future: 175/8 182/8 Reachability and routability testing of the new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html Please be aware, there are now just twenty-eight /8s remaining in IANA's unallocated IPv4 address pool. Kind regards, Srinivas (Sunny) External Relations Manager APNIC

1 0

NZRR Route Registry Update
by NZRR Database Notifications 03 Aug '09

03 Aug '09

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-ROUTES:AS17492 descr: advertised to AS9560 by Vector Communications - AS17492 members: 202.126.192.0/20^20-29, 123.108.144.0/21^21-29, 202.0.151.0/24^24-29, 203.30.174.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: matt.oram(a)vector.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080618 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17492 descr: advertised to AS9560 by Vector Communications LTD. (Tangent LTD) - AS17492 members: 202.126.192.0/20^20-29, 123.108.144.0/21^21-29, 202.0.151.0/24^24-29, 202.62.245.0/24^24-29, 203.30.174.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: matt.oram(a)vector.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090804 source: NZRR ------------------------------------------------------------

1 0

Fwd: [INZ Media Release] Media Release: InternetNZ announces Council election results
by Juha Saarinen 02 Aug '09

02 Aug '09

Seeing that there was some interest on the list before about the INZ council election results, here they are: Begin forwarded message: > InternetNZ announces Council election results > > Media Release > 3 August 2009 > > InternetNZ (Internet New Zealand Inc) announces official results in > this year's InternetNZ Council elections. > > Interim results were announced at the Society’s Annual General > Meeting last Friday, with final results now confirmed. There were 21 > nominations for six vacancies on Council. Official results are as > follows: > > Frank March has been elected President of InternetNZ, succeeding > Pete Macaulay. Jamie Baddeley has been elected Vice President. Both > will serve a three-year term. > > Hamish MacEwan, Michael Foley, Judy Speight and Liz Butterfield have > been re-elected to their Councillor positions. MacEwan and Foley > will each serve a three-year term. Speight and Butterfield will each > serve a one-year term. > > The election of Baddeley to the Vice President’s position has > created a vacant seat on Council. The details of a by-election to > fill this seat will be announced by Friday 7 August. > > New President Frank March says this year was one of the most keenly > contested InternetNZ elections, with a pool of excellent candidates > putting their names forward. > > “I warmly congratulate the successful candidates. They all have > strong Internet-related track records and a passion for the goals of > InternetNZ. I look forward to working and deliberating with them on > Council.” > > March also acknowledges the valuable contribution made to the > Society by outgoing Council member Stewart Fleming, who failed to > secure re-election. > > “Stewart has provided valuable contributions to the work of the > InternetNZ Council. I thank him for his efforts and hope that he > will continue to be involved in other roles.” > > The new-look InternetNZ Council is: > > President: > Frank March > > Vice President: > Jamie Baddeley > > Councillors: > Chris Streatfield > Donald Clark > Hamish MacEwan > Jonny Martin > Judy Speight > Liz Butterfield > Michael Foley > Michael Wallmannsberger > Neil James > > For more information contact: > > Frank March > President > InternetNZ > 021 494 165 > president(a)internetnz.net.nz -- Juha Saarinen juha(a)saarinen.org twitter: juhasaarinen http://www.geekzone.co.nz/juha | http://www.techsploder.com

2 1

The New Zealand Network Operators' Group
by Donald Neal 02 Aug '09

02 Aug '09

The New Zealand Network Operators' Group The NZNOG mailing list exists to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. The NZNOG Trust exists to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. Other than the trustees, the NZNOG does not have a formal membership. Conference In the NZNOG conference, the people are represented by two separate yet equally important groups. The trust, which is responsible for where the money goes, and the organising committee who do most of the actual work. See http://2009.nznog.org/ for details of this year's conference. Details of next year's conference should begin to emerge in the near future. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has around 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of APN Online, Citylink, and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

FW: Bind 9 vulnerability
by Simon Allard 28 Jul '09

28 Jul '09

I am sure everyone has seen this by now, but thought I would pass it on for those who haven't. -----Original Message----- From: John Martinez [mailto:jmartinez(a)zero11.com] Sent: Wednesday, 29 July 2009 12:50 p.m. To: nanog(a)nanog.org Subject: Bind 9 vulnerability https://www.isc.org/node/474

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Jul '09

28 Jul '09

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-ROUTES:AS45459 descr: Route set advertised to AS9560 by Web Drive - AS45459 members: 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-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)webhost.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090618 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS45459 descr: advertised to AS9560 by Web Drive Limited - AS45459 members: 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29, 123.100.98.48/28^28-29, 123.100.98.160/28^28-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)webhost.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090729 source: NZRR ------------------------------------------------------------

1 0

FYI - New pro-forma invoice scam
by Mark Harris 27 Jul '09

27 Jul '09

Apologies if you know about this. Just received a pro-forma invoice from Domain Renewal Group which states "This notice is not a bill" but says theat my .com domain is "due to expire in the next few months" (1/10/10? I don't think so) and has a handy credit card detail piece.www.domainrenewalgroup.com Just in case you get calls. Cheers ~mark

1 0

CCIP ALERT: Microsoft to Release Out of Band Security Bulletins
by Paul McKitrick 26 Jul '09

26 Jul '09

Good Afternoon, You may be aware that Microsoft have made an announcement regarding an out of band update release scheduled for this week. Microsoft has informed CCIP that when they release an update which is outside of its regular monthly scheduled, an 'out-of-band' release, that it is significant and this why CCIP is bringing this to your attention. CCIP advise you to evaluate and apply the applicable updates at your earliest opportunity. Please note that the Tuesday referred to is US time and therefore Wednesday the 29th in New Zealand. The following was released by Microsoft: ---BEGIN QUOTE--- This is an advance notification of two Out-of-Band security bulletins that Microsoft is intending to release on July 28, 2009. One bulletin will be for the Microsoft Visual Studio product line; application developers should be aware of updates available affecting certain types of applications. The second bulletin contains defense-in-depth changes to Internet Explorer to mitigate future attacks related to the Visual Studio bulletin, as well as fixes for vulnerabilities rated Critical that are not currently under active attack. The full version of this Microsoft Security Bulletin Advance Notification can be found at http://www.microsoft.com/technet/security/bulletin/ms09-jul-ans.mspx. ================================= NEW BULLETIN SUMMARY ================================= Bulletin ID: Visual Studio Maximum Severity Rating: Moderate Vulnerability Impact: Remote Code Execution Restart Requirement: Requires restart Affected Software: Microsoft Visual Studio .NET 2003, Microsoft Visual Studio 2005, Microsoft Visual Studio 2008, Microsoft Visual C++ 2005, and Microsoft Visual C++ 2008 ================================= Bulletin ID: Internet Explorer Maximum Severity Rating: Critical Vulnerability Impact: Remote Code Execution Restart Requirement: Requires restart Affected Software: Internet Explorer on Windows 2000, Windows XP, Windows Server 2003, Windows Vista and Windows Server 2008 ================================= Disclaimer on Possible Changes ================================= Although we do not anticipate any changes, the information provided in this summary is subject to change until the release. At this time, no additional information on this bulletin such as details regarding severity or details regarding the vulnerability will be made available until the bulletin is published. ====================================== Microsoft is hosting two webcasts to address customer questions on these bulletins on July 28, 2009, at 1:00 PM Pacific Time (US & Canada) and at 4:00 PM Pacific Time (US & Canada). Register now for the July 28, 1:00 PM Webcast and the July 28, 4:00 PM Webcast. Afterwards, these webcasts are available on-demand. For more information, see Microsoft Security Bulletin Summaries and Webcasts. ---END QUOTE--- CCIP are not proposing to alert on this issue further unless new information or issues come to light. Please refer to the Microsoft bulletin for routine updates. Many thanks, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz ===================================================================== If you would like to subscribe or unsubscribe from CCIP Vulnerability Alerts, Advisories, and e-Bulletins, Please send an email with either 'Subscribe' or 'Unsubscribe' in the subject line to publications(a)ccip.govt.nz ===================================================================== --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Jul '09

26 Jul '09

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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Jul '09

26 Jul '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Jul '09

26 Jul '09

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-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Jul '09

26 Jul '09

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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090727 source: NZRR ------------------------------------------------------------

1 0

Australian Net Filter Gets One Step Closer
by Jeffrey A. Williams 25 Jul '09

25 Jul '09

All, Hard to see how this represents good governance... Should ISP's or other types of service providers be acting as Internet Police for their respective governments? I don't think so... I wonder how the majority of NZ'ers feel about this? See: http://tech.slashdot.org/comments.pl?sid=09/07/25/0049217 Condobolin sends in an update to the Australian government's ongoing efforts to implement ISP-level filtering. One of the hurdles they had to overcome was to build a system that would allow them to filter content without impairing other internet usage. http://www.arnnet.com.au/article/312354/isps_give_clean_feed_filter_technic… A trial of the system has just concluded, and the results are positive at least, for the government. Quoting: "More than half of the Internet service providers (ISPs) taking part in the Federal Government's ISP filtering trial have reported minimal speed disruptions or technology problems. Of the nine participating ISPs, iPrimus, Netforce, Webshield, Nelson Bay Online and OMNIconnect told ARN they had seen no slowdowns in Internet speeds or problems with the filtering solutions in place. Of the remaining four ISPs, Tech2U and Highway1 were unable to respond by time of publication while Unwired and Optus refused to comment. ... 'From a technical perspective we're more than confident that if the government decided to roll out a mandatory Internet filter based on or around an Australian Communications and Media Authority blacklist or subset thereof, then it can be done without any impact whatsoever to the speed of the Internet,' [said Webshield managing director Anthony Pillion]." Regards, Spokesman for INEGroup LLA. - (Over 284k members/stakeholders strong!) "Obedience of the law is the greatest freedom" - Abraham Lincoln "YES WE CAN!" Barack ( Berry ) Obama "Credit should go with the performance of duty and not with what is very often the accident of glory" - Theodore Roosevelt "If the probability be called P; the injury, L; and the burden, B; liability depends upon whether B is less than L multiplied by P: i.e., whether B is less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947] =============================================================== Updated 1/26/04 CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of Information Network Eng. INEG. INC. ABA member in good standing member ID 01257402 E-Mail jwkckid1(a)ix.netcom.com My Phone: 214-244-4827

2 2

WLG Power Instabilities
by Jonathan Brewer 25 Jul '09

25 Jul '09

Hi Folks, FYI the power grid in Wellington took a hit around 16:10 this afternoon. I saw subscriber units all over Te Aro and the CBD fringes reboot. Regards, Jon

1 0

linux.conf.au 2010: extension of CFP deadline to 31 July
by Andrew Ruthven 24 Jul '09

24 Jul '09

Hi everyone: The linux.conf.au deadline is now on the 31 July at 0500 UTC (1700 New Zealand time). Other times around the world can be found at http://tinyurl.com/lca10cfp ----------- Announcement from http://www.lca2010.org.nz/media/news/65 WELLINGTON, New Zealand – Friday 24 July 2009 – The LCA2010 Organising Committee have been overwhelmed by the numbers and quality of the papers submitted to linux.conf.au so far! The success of the papers so far has put us in a generous mood. So we've decided to give all you slackers out there an extension on the Call for Papers by one week! Call for Papers Now Closing: Friday 31 July 2009 at 17:00 NZST Remember, to increase your chances of acceptance, check out the Papers Info[1] page on our website before submitting your paper. [1] http://www.lca2010.org.nz/programme/papers_info -- Andrew Ruthven Wellington, New Zealand At home: andrew(a)etc.gen.nz | linux.conf.au 2010 | Follow the signs. Visit Wellington! | http://www.lca2010.org.nz

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Jul '09

23 Jul '09

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-ROUTES:AS2687 descr: advertised to AS9560 by ATT - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090715 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090724 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Jul '09

23 Jul '09

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:AS2687 descr: advertised to AS9439 by ATT - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090715 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090724 source: NZRR ------------------------------------------------------------

1 0

CCIP ALERT: New Adobe Vulnerability Being Actively Exploited
by Paul McKitrick 22 Jul '09

22 Jul '09

Good Afternoon, CCIP would like to bring to your attention a new vulnerability in Adobe Flash player (versions 9 and 10) as well as Adobe Reader and Acrobat (version 9) that is being actively exploited. We have received reports of this exploit being used within attacks experienced in New Zealand. MITIGATION Until a fix is made available from Adobe CCIP encourages the following workarounds: -Disable the Flash plugin in your browser or disallow by default. -Disable Flash within Adobe reader. -Consider enabling Data Execution Prevention (DEP)in Windows (Set DEP to opt out). The US CERT have released a vulnerability note: http://www.kb.cert.org/vuls/id/259425 1. Disabling the the Flash plugin or disallowing Flash by default: An example of disallowing by default for Firefox is to use the extension NoScript. 2. Disabling Flash within Reader: ---BEGIN QUOTE--- Flash and 3D & Multmedia support are implemented as plugin libraries in Adobe Reader. Disabling Flash in Adobe Reader will only mitigate attacks using a SWF embedded in a PDF file. Disabling 3D & Multimedia support does not directly address the vulnerability, but does provide additional mitigation and results in a more user-friendly error message instead of a crash. To disable Flash and 3D & Multimedia support in Adobe Reader 9 on Microsoft Windows, delete or rename these files: "%ProgramFiles%\Adobe\Reader 9.0\Reader\authplay.dll" "%ProgramFiles%\Adobe\Reader 9.0\Reader\rt3d.dll" For Apple Mac OS X, delete or rename these files: "/Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/AuthPlayLib.bundle" "/Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/Adobe3D.framework" For GNU/Linux delete or rename these files (locations may vary among distributions): "/opt/Adobe/Reader9/Reader/intellinux/lib/libauthplay.so" "/opt/Adobe/Reader9/Reader/intellinux/lib/librt3d.so" File locations may be different for Adobe Acrobat or other Adobe products that include Flash and 3D & Multimedia support. Disabling these plugins will reduce functionality, and will not protect against SWF files hosted on web sites. ---END QUOTE-- 3. Enabling DEP in Microsoft Windows: ---BEGIN QUOTE--- Users should consider enabling Data Execution Prevention (DEP) in supported versions of Windows. DEP should not be considered a complete workaround but can mitigate the execution of attacker-supplied code in some cases. Microsoft has published detailed technical information about DEP in Security Research & Defense blog posts "Understanding DEP as a mitigation technology" part 1 and part 2. Use of DEP should be considered in conjunction with the application of patches or other mitigations described in this document. ---END QUOTE--- Adobe are working on a fix and have released the following advisory: http://www.adobe.com/support/security/advisories/apsa09-03.html Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz ===================================================================== If you would like to unsubscribe from CCIP Vulnerability Alerts, Advisories, e-Bulletins, Monthly Reports and Information Notes, Please send an email with 'Unsubscribe' in the subject line to publications(a)ccip.govt.nz ===================================================================== --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 Jul '09

21 Jul '09

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 Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090722 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 Jul '09

21 Jul '09

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: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 14.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 46.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 179.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 185.0.0.0/8^+, 223.0.0.0/8^+} admin-c: Rob Thomas RTH32-ARIN tech-c: Rob Thomas RTH32-ARIN remarks: For the complete set of bogons, please see:
fltr-martian - special use and reserved prefixes.
fltr-bogons - fltr-unallocated + fltr-martian.
http://www.cymru.com/Documents/bogon-list.html notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)cymru.com mnt-by: MAINT-BOGON-FILTERS changed: radb(a)cymru.com 20021229 changed: radb(a)cymru.com 20021230 changed: radb(a)cymru.com 20030213 changed: radb(a)cymru.com 20030404 changed: radb(a)cymru.com 20030406 changed: radb(a)cymru.com 20030408 changed: radb(a)cymru.com 20030606 changed: radb(a)cymru.com 20031117 #16:08:32(UTC) changed: radb(a)cymru.com 20040116 #07:17:57(UTC) changed: radb(a)cymru.com 20040401 #22:29:46(UTC) changed: radb(a)cymru.com 20040428 #18:27:34(UTC) changed: radb(a)cymru.com 20040803 #05:43:18(UTC) changed: radb(a)cymru.com 20050129 #11:48:46(UTC) changed: radb(a)cymru.com 20050330 #23:14:55(UTC) changed: radb(a)cymru.com 20050413 #06:12:46(UTC) changed: radb(a)cymru.com 20050618 #04:07:01(UTC) changed: radb(a)cymru.com 20050701 #06:18:28(UTC) changed: radb(a)cymru.com 20060105 #20:45:57(UTC) changed: radb(a)cymru.com 20061013 #18:41:19(UTC) changed: radb(a)cymru.com 20061122 #14:51:27(UTC) changed: radb(a)cymru.com 20061227 #03:31:18(UTC) changed: radb(a)cymru.com 20070128 #22:04:23(UTC) changed: radb(a)cymru.com 20070411 #18:20:12(UTC) changed: radb(a)cymru.com 20070603 #04:48:23(UTC) changed: radb(a)cymru.com 20070726 #15:53:57(UTC) changed: radb(a)cymru.com 20071002 #15:48:55(UTC) changed: radb(a)cymru.com 20071002 #16:45:21(UTC) changed: radb(a)cymru.com 20071029 #16:50:49(UTC) changed: radb(a)cymru.com 20071105 #23:37:09(UTC) changed: radb(a)cymru.com 20071105 #23:44:41(UTC) changed: radb(a)cymru.com 20080125 #18:37:51(UTC) changed: radb(a)cymru.com 20080214 #20:21:40(UTC) changed: radb(a)cymru.com 20080527 #23:12:28Z changed: noc(a)cymru.com 20080529 #15:52:05Z changed: irr-admin(a)nic.ad.jp 20090501 #APNIC 180/8 183/8 changed: rpsl-admin(a)nzix.net 20090722 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 14.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 46.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 179.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 185.0.0.0/8^+, 223.0.0.0/8^+} admin-c: Rob Thomas RT624 tech-c: Rob Thomas RT624 remarks: For the complete set of bogons, please see: fltr-martian - special use and reserved prefixes. fltr-bogons - fltr-unallocated + fltr-martian. http://www.cymru.com/Documents/bogon-list.html notify: noc(a)cymru.com mnt-by: MAINT-BOGON-FILTERS changed: noc(a)cymru.com 20090518 #20:08:04Z changed: rpsl-admin(a)nzix.net 20090722 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 Jul '09

21 Jul '09

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: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 14.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 46.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} admin-c: Rob Thomas RTH32-ARIN tech-c: Rob Thomas RTH32-ARIN remarks: For the complete set of bogons, please see:
fltr-martian - special use and reserved prefixes.
fltr-bogons - fltr-unallocated + fltr-martian.
http://www.cymru.com/Documents/bogon-list.html notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)cymru.com mnt-by: MAINT-BOGON-FILTERS changed: radb(a)cymru.com 20021229 changed: radb(a)cymru.com 20021230 changed: radb(a)cymru.com 20030213 changed: radb(a)cymru.com 20030404 changed: radb(a)cymru.com 20030406 changed: radb(a)cymru.com 20030408 changed: radb(a)cymru.com 20030606 changed: radb(a)cymru.com 20031117 #16:08:32(UTC) changed: radb(a)cymru.com 20040116 #07:17:57(UTC) changed: radb(a)cymru.com 20040401 #22:29:46(UTC) changed: radb(a)cymru.com 20040428 #18:27:34(UTC) changed: radb(a)cymru.com 20040803 #05:43:18(UTC) changed: radb(a)cymru.com 20050129 #11:48:46(UTC) changed: radb(a)cymru.com 20050330 #23:14:55(UTC) changed: radb(a)cymru.com 20050413 #06:12:46(UTC) changed: radb(a)cymru.com 20050618 #04:07:01(UTC) changed: radb(a)cymru.com 20050701 #06:18:28(UTC) changed: radb(a)cymru.com 20060105 #20:45:57(UTC) changed: radb(a)cymru.com 20061013 #18:41:19(UTC) changed: radb(a)cymru.com 20061122 #14:51:27(UTC) changed: radb(a)cymru.com 20061227 #03:31:18(UTC) changed: radb(a)cymru.com 20070128 #22:04:23(UTC) changed: radb(a)cymru.com 20070411 #18:20:12(UTC) changed: radb(a)cymru.com 20070603 #04:48:23(UTC) changed: radb(a)cymru.com 20070726 #15:53:57(UTC) changed: radb(a)cymru.com 20071002 #15:48:55(UTC) changed: radb(a)cymru.com 20071002 #16:45:21(UTC) changed: radb(a)cymru.com 20071029 #16:50:49(UTC) changed: radb(a)cymru.com 20071105 #23:37:09(UTC) changed: radb(a)cymru.com 20071105 #23:44:41(UTC) changed: radb(a)cymru.com 20080125 #18:37:51(UTC) changed: radb(a)cymru.com 20080214 #20:21:40(UTC) changed: radb(a)cymru.com 20080527 #23:12:28Z changed: noc(a)cymru.com 20080529 #15:52:05Z source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 14.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 46.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 179.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 185.0.0.0/8^+, 223.0.0.0/8^+} admin-c: Rob Thomas RTH32-ARIN tech-c: Rob Thomas RTH32-ARIN remarks: For the complete set of bogons, please see:
fltr-martian - special use and reserved prefixes.
fltr-bogons - fltr-unallocated + fltr-martian.
http://www.cymru.com/Documents/bogon-list.html notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)cymru.com mnt-by: MAINT-BOGON-FILTERS changed: radb(a)cymru.com 20021229 changed: radb(a)cymru.com 20021230 changed: radb(a)cymru.com 20030213 changed: radb(a)cymru.com 20030404 changed: radb(a)cymru.com 20030406 changed: radb(a)cymru.com 20030408 changed: radb(a)cymru.com 20030606 changed: radb(a)cymru.com 20031117 #16:08:32(UTC) changed: radb(a)cymru.com 20040116 #07:17:57(UTC) changed: radb(a)cymru.com 20040401 #22:29:46(UTC) changed: radb(a)cymru.com 20040428 #18:27:34(UTC) changed: radb(a)cymru.com 20040803 #05:43:18(UTC) changed: radb(a)cymru.com 20050129 #11:48:46(UTC) changed: radb(a)cymru.com 20050330 #23:14:55(UTC) changed: radb(a)cymru.com 20050413 #06:12:46(UTC) changed: radb(a)cymru.com 20050618 #04:07:01(UTC) changed: radb(a)cymru.com 20050701 #06:18:28(UTC) changed: radb(a)cymru.com 20060105 #20:45:57(UTC) changed: radb(a)cymru.com 20061013 #18:41:19(UTC) changed: radb(a)cymru.com 20061122 #14:51:27(UTC) changed: radb(a)cymru.com 20061227 #03:31:18(UTC) changed: radb(a)cymru.com 20070128 #22:04:23(UTC) changed: radb(a)cymru.com 20070411 #18:20:12(UTC) changed: radb(a)cymru.com 20070603 #04:48:23(UTC) changed: radb(a)cymru.com 20070726 #15:53:57(UTC) changed: radb(a)cymru.com 20071002 #15:48:55(UTC) changed: radb(a)cymru.com 20071002 #16:45:21(UTC) changed: radb(a)cymru.com 20071029 #16:50:49(UTC) changed: radb(a)cymru.com 20071105 #23:37:09(UTC) changed: radb(a)cymru.com 20071105 #23:44:41(UTC) changed: radb(a)cymru.com 20080125 #18:37:51(UTC) changed: radb(a)cymru.com 20080214 #20:21:40(UTC) changed: radb(a)cymru.com 20080527 #23:12:28Z changed: noc(a)cymru.com 20080529 #15:52:05Z changed: irr-admin(a)nic.ad.jp 20090501 #APNIC 180/8 183/8 changed: rpsl-admin(a)nzix.net 20090722 source: NZRR ------------------------------------------------------------

1 0

Have your say on APNIC proposals now
by Elly Tawhai 20 Jul '09

20 Jul '09

Hi NZNOG Community, This is a reminder to have your say via the APNIC Policy SIG mailing list on policy proposals that will be presented at APNIC 28 in Beijing, 25-28 August 2009. It is important to discuss the proposals on the mailing list before the meeting so any major issues you raise can be considered by the proposal authors in time for the meeting. In particular, the IPv4 transfer proposal (prop-050) is currently being developed by the community on the Policy SIG mailing list. If you want to contribute to what goes into the final proposal text, please send your comments to the Policy SIG mailing list by the close of business this Friday, 23 July 2009. APNIC SIG-Policy Mailing list can be subscribed from: http://www.apnic.net/community/participate/join-discussions Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ------------------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Jul '09

20 Jul '09

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-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.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, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-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, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.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, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090721 source: NZRR ------------------------------------------------------------

1 0

4-byte AS numbers
by Andy Linton 19 Jul '09

19 Jul '09

Given that APNIC are now assigning 4-byte AS numbers by default, I wondered what the state of play was among members of this list. You can still get 2-byte AS numbers: "Two-byte AS numbers will only be assigned if the applicant can demonstrate that a four-byte only AS number is unsuitable." but come January 2010 numbers will be assigned without distinction. Is anyone out there ready for this?

9 10

DSLAM Advice
by Skeeve Stevens 16 Jul '09

16 Jul '09

Hey all, I figure that these are the best possible two lists for information for this region relating to DSLAM's and I am sure people have already have some experience in this area. We're doing a lot of in building 'Multi-Dwelling' installations, most are based on Ethernet, but some buildings it is not cost effective to deploy UTP and the copper is already in place, so DSLAM's become the best option. VDSL/VDSL2 are the only options worth considering due to the speed ability over ADSL technologies. We've been looking at the Zyxel 5005 IP DSLAM with VDSL2 cards. I'd like to know if anyone else has some good/bad things to say about * Zyxel DSLAM's, * other vendor options which are price competitive * Know whether the Zyxel DSLAM's support multi-PVC services so we can deliver different services which are contended/rate-limited differently * CPE options worth considering (wired and wireless options) * I understand VDSL2 is 100mb/45mb speeds... at what distance do these speeds go down, and any other considerations which may affect it? If anyone has any other ideas (apart from Powerline Communications - just not interested). ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

2 1

Re: [nznog] DSLAM Advice
by Richard Naylor 16 Jul '09

16 Jul '09

At 07:56 p.m. 17/07/2009, you wrote: > Were doing a lot of in > building Multi-Dwelling installations, most > are based on Ethernet, but some buildings it is > not cost effective to deploy UTP and the copper > is already in place, so DSLAMs become the best option. Good luck. At my previous job we gave up on apartments. Where we had our own UTP it was madness. Contractors for the incumbent stole pairs or even sheaths with wild disregard of ownership. The clients have a reluctance to pay and frequently do a runner. Make sure you have a fella called "Big Ted" who is a cross between King Kong and Wurzel Gumidge, wears a tool belt with bloody big side cutters and picks his teeth with a screwdriver. He visits clients frequently and in his limited vocabulary says, "you gonna pay ?". They do. In between client visits, Big Ted "educates" installation contractors on "the rules" about using other folks cables and gives them "First Aid" lessons. Based on my experience with electricity in apartments, and a guy called Ted Grace. He taught me how to be a linesman. > If anyone has any other ideas (apart from > Powerline Communications just not interested). Well I have powerline that has been working fine since 1977, but it only signals at 1bps and does require a 10KW amplifier injecting at 33KV. Its called ripple control. Turns the street lights on pretty reliably in Wellington. The amp sounds like a locomotive when its running and does rather dim the lights. I use Planet and MicroNet gear in our OB stuff. Its VDSL 1.0 and gives us 20Mbps symmetric for 1KM. We tend to use it point to point and not with big DSLAMs. It works on audio way-lines in stadiums, museums etc, wet string in old buildings and is pretty useful. Its also good in newer buildings where you have over 25 floor to traverse (allow 4 m per floor). We dropped a cable down 25+ floors the other day with a total run of 250m. No issues at all. Both Planet and Micronet make multi-way switches with it, but we don't have that need yet. It just works and has been great for us. We do have some modern powerline stuff and it does work in high rise buildings, but you need to understand how higher (than 50Hz) propagates on the mains network. Its great in corporates where you aren't allowed to run any cables thru the office, but you need to avoid any coils such as found in meters, CTs, etc. so would be crap in a multi-dwelling building. Ripple and DC inject work a treat tho, and reverse signalling at 100 to 300KHz is also very good. Lower freqs go thru transformers fine. LEB used to read meters that way. R

1 0

InternetNZ Council Elections
by Andy Linton 16 Jul '09

16 Jul '09

I've been looking at the candidates for the InternetNZ Council elections with some concern at the lack of candidates from this community. See http://internetnz.net.nz/about/council/2008-2009/2009-election I know many of you are not what you see as political animals but there is a need for a strong voice in that forum from the technical community. I see many of the current list of candidates as coming from a purely business background with little or no Internet history. This community had to galvanise itself once before to ensure that InternetNZ represented the ideals that many of us hold about how InternetNZ should be organised and you may want to ask yourself is it time to get involved. My position as a Director of the Domain Name Commission precludes me from standing. I'm happy to discuss with anyone who might be interested and lend my support if you think it's useful andy

7 7

NZRR Route Registry Update
by NZRR Database Notifications 16 Jul '09

16 Jul '09

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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Jul '09

16 Jul '09

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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Jul '09

16 Jul '09

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-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Jul '09

16 Jul '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090717 source: NZRR ------------------------------------------------------------

1 0

NZ public OpenPGP Keyserver
by Jay Daley 14 Jul '09

14 Jul '09

Just to let you all know that we have just established a public OpenPGP keyserver in NZ, which we believe is the first such keyserver in NZ. You can access it at: http://pgp.net.nz (for the info pages) http://pgp.net.nz:11371 (for the hkp:// and x-hkp:// interfaces) This server is operated by .nz Registry Services, part of the InternetNZ group, as a public service to the NZ Internet community. kind regards Jay -- Jay Daley Chief Executive .nz Registry Services desk: +64 4 931 6977 mobile: +64 21 678840

2 2

NZRR Route Registry Update
by NZRR Database Notifications 14 Jul '09

14 Jul '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090708 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by ATT - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090715 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Jul '09

14 Jul '09

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-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090708 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by ATT - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090715 source: NZRR ------------------------------------------------------------

1 0

CCIP ALERT: Unpatched Microsoft Office Web Components vulnerability is being actively exploited
by Paul McKitrick 13 Jul '09

13 Jul '09

Good Evening, For those of you who are not already aware, CCIP would like to bring your attention the the Microsoft Security Advisory 973472 that was released today: http://www.microsoft.com/technet/security/advisory/973472.mspx CCIP is bringing this to your attention as this vulnerability has been reported as being actively exploited in the wild. Microsoft have announced a vulnerability in Microsoft Office Web Components Control that allows remote code execution. This is reported to affect the following software: Microsoft Office XP Service Pack 3 Microsoft Office 2003 Service Pack 3 Microsoft Office XP Web Components Service Pack 3 Microsoft Office 2003 Web Components Service Pack 3 Microsoft Office 2003 Web Components for the 2007 Microsoft Office System Service Pack 1 Microsoft Internet Security and Acceleration Server 2004 Standard Edition Service Pack 3 Microsoft Internet Security and Acceleration Server 2004 Enterprise Edition Service Pack 3 Microsoft Internet Security and Acceleration Server 2006 Internet Security and Acceleration Server 2006 Supportability Update Microsoft Internet Security and Acceleration Server 2006 Service Pack 1 Microsoft Office Small Business Accounting 2006 MITIGATION Microsoft is working on a security update for this, however until it is released administrators are advised to take the following mitigation steps immediately. There is currently no patch to correct this issue. However you can set the kill-bit to mitigate this vulnerability. Microsoft have provided a way to automatically implement the workaround by following the instructions under "Fix It For Me" in the following Knowledge Base article: http://support.microsoft.com/kb/973472 Alternatively the following quoted text can be included in a .REG file and imported into your registry. ---BEGIN QUOTE--- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0002E541-0000-0000-C000-000000000046}] "Compatibility Flags"=dword:00000400 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0002E559-0000-0000-C000-000000000046}] "Compatibility Flags"=dword:00000400 ---END QUOTE--- The following article describes how to deploy the fix using Active Directory: http://technet.microsoft.com/en-us/library/bb457006.aspx There is also a writeup on Microsoft's Security Response Centre Blog: http://blogs.technet.com/msrc/archive/2009/07/13/microsoft-security-advisor… Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz ===================================================================== If you would like to unsubscribe from CCIP Vulnerability Alerts, Advisories, e-Bulletins, Please send an email with 'Unsubscribe' in the subject line to publications(a)ccip.govt.nz ===================================================================== --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

Re: [nznog] InternetNZ elections - no free beer involved
by Drew Calcott 12 Jul '09

12 Jul '09

Steven Heath wrote: > > The first to say it on NZNOG perhaps. > Which is exactly my point. I'm guessing quite a few people on here are in my position and really don't know what is going on with INZ at all... so it would be nice if people are going to go soliciting votes if they could spell out what they believe the problems are. INZ things may not be directly NZNOG related, but the list is currently dead quiet otherwise, so now that the issue has been raised, how about you come in for a discussion over a cup of tea, rather than just standing outside on the lawn holding a sign with your name on it? Regards, -- ---- Drew Calcott Linux Systems Administrator Science IT University of Auckland e: drew.calcott(a)auckland.ac.nz p: +64-9-373 7599, ext#: 84269

7 8

stuff.co.nz
by Leon Strong 12 Jul '09

12 Jul '09

Could someone from stuff.co.nz please contact me offlist please if anyone at stuff reads the nog? :) -- *Leon Strong *| Technical Engineer *DDI:* +64 9 950 2203 *Fax:* +64 9 302 0518 *Mobile:* +64 21 0202 8870 *Freephone:* 0800 SMX SMX (769 769) Level 11, 290 Queen Street, Auckland, New Zealand | SMX Ltd | smx.co.nz <http://smx.co.nz> SMX | Business Email Specialists The information contained in this email and any attachments is confidential. If you are not the intended recipient then you must not use, disseminate, distribute or copy any information contained in this email or any attachments. If you have received this email in error or you are not the originally intended recipient please contact SMX immediately and destroy this email.

1 0

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

12 Jul '09

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: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 source: NZRR ------------------------------------------------------------

1 0

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

12 Jul '09

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: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 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, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 source: NZRR ------------------------------------------------------------

1 0

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

12 Jul '09

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-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090415 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 source: NZRR ------------------------------------------------------------

1 0

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

12 Jul '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090415 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29, 123.100.117.192/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090713 source: NZRR ------------------------------------------------------------

1 0

Enabling Telecom XT Handsets for Email delivery
by Ted Grenfell 09 Jul '09

09 Jul '09

Telecom wishes to advise Mail administrators of the IP ranges assigned to XT handsets on our WCDMA network. If you administer an SMTP service likely to be accessed via handsets on Telecom's XT network then you might like to update your SMTP ACL's to enable the following IP ranges :- internet.telecom.co.nz 122.56.192.0/20 (16 /24's) 122.56.208.0/21 (8 /24's) direct.telecom.co.nz 122.56.216.0/22 (4 /24's) 122.56.220.0/23 (2 /24's) -- Regards, Ted Grenfell Service Delivery Manager Telecom Online Services T +64 9 357 7277 (extn 97277) F +64 9 357 8157 M +64 27 443 5455 E ted.grenfell(a)telecom.co.nz <mailto:ted.grenfell(a)telecom.co.nz> W www.telecom.co.nz <http://www.telecom.co.nz> Level 9, Mayoral Dr Bldg, 31 Airedale Street Private Bag 92028, Auckland CBD, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

1 0

News - US Federal Judge - IP Addresses are Not Personal or Private Information
by Skeeve Stevens 09 Jul '09

09 Jul '09

FYI to the ISP community. In Today's issue of Commsday International - July 10 2009, Page 2 and 3 sidebar IP ADDRESSES ARE NOT PERSONAL OR PRIVATE A US federal judge has ruled IP addresses do not constitute personal information, establishing a legal precedent that could radically alter Internet privacy norms. Presiding over a class action lawsuit against Microsoft, US District Court judge Richard Jones defended the company's collection of customers' IP addresses during software updates as fair and reasonable despite a user agreement promising not to hoover up identifying data. "In order for 'personally identifiable information' to be personally identifiable, it must identify a person. But an IP address identifies a computer," Jones wrote in a dismissal. The ruling underlines the lack of federal guidance on the issue, with US courts handing out a series of contradictory decisions piecemeal over the last few years. Just last month a New Jersey court determined surfers had a reasonable right to assume their IP addresses would be kept private and barred ISPs from disclosing them to third parties without a subpoena. The New York Times made headlines three years ago when it proved "anonymous" IP addresses provided by AOL would be tied to specific surfers. -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

2 1

Call for Presentations - AusNOG-03
by Jonny Martin 08 Jul '09

08 Jul '09

Forwarded on behalf our good friends over in Aussie. :) Apologies if you've seen this n times already! Cheers, Jonny. Call for Presentations - AusNOG-03 --------------------------------- AusNOG-03 is to be held in Sydney, Australia between 31st August and 1st of September 2009 The AusNOG meeting provides the Australian community with a forum to exchange information and experiences on a number of issues relating to the operation and support of networks, with a specific focus on the coming 6-12 months. The conference is expected to have a strong technical representation from companies operating networks in Australia. Details of AusNOG-03 and past meetings can be found on the AusNOG web site at www.ausnog.net. Submissions ------------ Please read the information below carefully. Send your proposed topics and details to organisers(a)ausnog.net. Please include a detailed overview including the expected length and technical depth of your presentation. The program committee will confirm your application and may get back to you with any questions. Please remember this is a technical event for network operators and presentations should be representative of this. Marketing presentations or presentations focusing on specific products are not suitable for this event. Some areas of current interest to the target audience are listed below. These are simply suggested topic areas and the committee will happily consider proposals for papers covering any facet of network technology, network operation, or the industry. 1. NBN Technology. High speed access, core, edge, border... Access speeds measured at 100M will present all sort of challenges across the provider sphere. As so much is yet unknown how the NBN will land on us, will there be the ability to specify the edge device or policy. Either way talks on experience in this space is what we are seeking. 2. Backhaul. Increasing end user speeds in an NBN world will see a requirement for increased backhaul. How do you implement a multi hundred gigabit backhaul network ? What are the issues for wholesale play with this type of undertaking ? 3. Content to the Edge. Whilst we are about to enter the work of real competition in international access and bandwidth is about as inexpensive as it has ever been we are still a small population very far away from the main Internet trade routes. Experience with CDN, distributed content applications and how operators leverage servers, DNS, load balancers etc to bring about an outcome. 4. Operational Best Practices. Tools, methodologies and techniques that can improve the reliability and efficiency of IP Networks. Configuration management, configuration automation, routing registries, performance monitoring and availability monitoring are always of interest to operators. 5. Regulatory, Market Data and Overseas Trends (Regulatory and Industry Bodies Updates, Market Data and Statistics, Trends from Overseas Markets) Panel Discussions ----------------- - Required Panellists: 8-10 - Panel Length: 45 mins - Number of Panels: 2 Panels are the interactive part of the conference. The job of Panellists will be to stimulate and moderate the discussion. Whether you are on the panel or in the audience your input would be appreciated. The two Panel Topics will be related to the industry at the time of the conference. Propose a topic that you think will be interesting, or if you think you are interesting, propose yourself for inclusion to the panel :-) Keynote Addresses ----------------- - Required Speakers: 2 - Presentation Length: 45 mins - Number of Topics: 2 We are seeking 2 speakers for Keynotes Addresses. Each Keynote will be of 45 mins in length, including time for input from the industry. If you would like to be considered for a Keynote topic, please email organisers(a)ausnog.net with details of yourself and your topic. Important Dates --------------- - 10 July 2009 - Call for Presentations Opens - 26 July 2009 - Deadline for Proposals - 3 August 2009 - Response to presentation proposals - 10 August 2009 - Draft program published to website - 17 August 2009 - Final program published The AusNOG-03 Organisers ...

1 0

Re: [nznog] InternetNZ elections - no free beer involved
by Stu Fleming 08 Jul '09

08 Jul '09

As a sitting (standing? embedded?) Councillor standing again, I'm happy to take comments, queries and criticism off-list. Regards, Stu

1 0

Re: [nznog] InternetNZ elections - no free beer involved
by Steven Heath 08 Jul '09

08 Jul '09

[posted to the list as sent from wrong address first time] On Thu, Jul 9, 2009 at 11:10 AM, Drew Calcott <drew.calcott(a)auckland.ac.nz>wrote: > Michael Wallmannsberger wrote: > > Things haven't been right with governance and leadership at InternetNZ. > > This has been alluded to over the past little while since the subject of > this election was raised on this list, but I believe you're the first > to come right out and say it. > > The first to say it on NZNOG perhaps. As InternetNZ governance issues are not NZNOG related I would be more than willing to discuss either on a INZ list, direct email or over a beverage. I am sure others with INZ exp. would be willing to do the same. I was one of the few at the AGM 2 years to openly oppose most of the changes that were introduced. PS I happen to be standing for INZ council. -- Steven Heath Director, Foxbane Consulting Founder, AltSpace Cell: +64 21 706-067 www.foxbane.co.nz Suite 607 29 Brandon St Wellington AltSpace.co.nz - Shared office space in Wellington for home based workers, freelancers, or nimble companies

1 0

InternetNZ elections - no free beer involved
by Andy Linton 08 Jul '09

08 Jul '09

I posted recently about standing and voting in the InternetNZ elections. You may find the attached helpful in helping you decide about what to do. I'm attaching mail from Michael Wallmannsberger and I perceive this to be an attempt to skew the membership of InternetNZ at the last moment in his favour. I'm offering you the chance to join and redress the balance. Once you're a member I encourage you to read the statements of *all* the candidates and "choose wisely grasshopper". You need to do this today - the deadline is very close. ----- snip << Michael Wallmannsberger <michael(a)wallmannsberger.com <mailto:michael(a)wallmannsberger.com>> *Date: *7 July 2009 5:50:23 PM *Subject: **Help: The Internet* Hi! I need your help with an important mission. I am standing in a contested election for the presidency of InternetNZ. Anyone who joins InternetNZ on or before 15 July is eligible to vote in the upcoming elections. Please help me to help the Internet, by: 1. Joining InternetNZ online at http://www.internetnz.co.nz/membership/apply (membership costs $21) on or before 15 July 2. Voting Michael Wallmannsberger for President, Laurence Millar for Vice President and Judy Speight, Michael Foley, Antony Royal and Pat O'Connell for Council in the upcoming elections (open from 16 to 28 July). Instructions will be sent once you have joined and voting has commenced. My election statement <http://internetnz.net.nz/about/council/2008-2009/2009-election/michae l-wallmannsberger-bio-election-statement> sets out what I hope to achieve by standing. More information about other candidates is here <http://internetnz.net.nz/about/council/2008-2009/2009-election>. 3. Passing this message on to friends who might also be interested in joining InternetNZ. Once a member, you will have a right to participate in decisions about how the Internet is governed and have a say about important issues affecting the Internet. *Why is this important?* * * If InternetNZ failed to do its job of managing New Zealand's country-code (.nz) properly, the infrastructure, policy and processes affecting domain names ending in .nz could perform poorly or fail, affecting most New Zealand businesses and Internet users. InternetNZ receives dividend revenue from the .nz domain name registry, which enables it to fund neutral and professional advocacy, advice and policy development. If InternetNZ does a good job of this, New Zealand will grow richer, socially and economically, through the value unlocked by the Internet. As a nation, we need to take advantage of this opportunity to foster innovation, growth and opportunity. * * *What is InternetNZ?* InternetNZ <http://internetnz.net.nz/> (Internet New Zealand Incorporated) is a member based not-for-profit society and registered charity. The Society advocates for the interests of Internet users and the public good. InternetNZ promotes the Internet and provides independent advice to Government and the public about issues that affect the Internet. InternetNZ is delegated responsibility for .nz by ICANN, the not-for-profit corporation responsible for global Internet address allocation. The Society operates two subsidiary companies. Domain Name Commission Limited (DNCL) is responsible for overseeing the .nz domain name registration and management system while .nz Registry Services (NZRS) maintains the register of .nz domain names and provides the domain name system servers for .nz. Please don't hesitate to get in touch (021 441 318) if you want to know more about InternetNZ and why I think this is a critical election for the future of the New Zealand Internet. Regards, Michael

4 3

Southern Cross to US issues
by Skeeve Stevens 07 Jul '09

07 Jul '09

Hey guys, There seems to be some major issue with Southern Cross to .us at the moment This is effecting Vocus and downstreams and also seems to be effecting AAPT which indicates it is a wider SX issue than any particular provider. ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

2 2

NZRR Route Registry Update
by NZRR Database Notifications 07 Jul '09

07 Jul '09

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-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090522 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090708 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Jul '09

07 Jul '09

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:AS64643 descr: Route set advertised to AS9439 by Clemenger BBDO - AS64643 members: 202.135.231.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: it(a)cclnz.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060302 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64643 descr: advertised to AS9439 by Clemenger BBDO - AS64643 members: 202.27.137.0/24^24-29, 202.135.231.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: guy.lincoln(a)clemenger.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090708 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Jul '09

07 Jul '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090522 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090708 source: NZRR ------------------------------------------------------------

1 0

CCIP Alerts on NZNOG
by Paul McKitrick 07 Jul '09

07 Jul '09

Good Morning All, 1. Thank you for the feedback everyone. There have been a number of requests how to subscribe to CCIP's mailing lists, if you send an email to CCIP Publications <publications(a)ccip.govt.nz> with the subject of "Subscribe" then we will add you to our lists, which are relatively low volume one-two posts per month. If you have a security incident you would like to report it or you are aware of something that you think CCIP should be aware of then please send an email to CCIP Incident Response <incidents(a)ccip.govt.nz> When it comes to security related issues I always say that "I would rather hear about something three times than not at all!" 2. CCIP are not currently not preparing regular summaries of activity but it is something we will consider implementing. 3. Currently the volume of CCIP Alerts is about four a year, so posting those here sounds like it would be appropriate and we will review that if the volume starts increasing significantly. Again the threshold for issuing an alert is when there is active exploitation of a new or unpatched vulnerability. CCIP's current philosophy is that we would rather issues alerts and advisories less frequently but have people listen to us when we do, versus just being another noisy feed that becomes somewhat ignored. We definitely don't want to be considered as another "Chicken Little", but sometimes we have to err on the side of caution. When it comes to security I always say that "I would rather hear about something three times than not at all!" 4. This is a dynamic field we work in and we are constantly reviewing what we do, and how we do it. We are always open to feedback and suggestions either on list or off list. 5. Thanks for reading. Regards, Paul. -- Paul McKitrick Head of Stakeholder Engagement Centre for Critical Infrastructure Protection D: (+64) 4 498 7645 P: (+64) 4 498 7654 F: (+64) 4 498 7655 E: paul.mckitrick(a)ccip.govt.nz W: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

[Fwd: CCIP ALERT: Microsoft unpatched vulnerability is being actively exploited in the wild]
by Paul McKitrick 07 Jul '09

07 Jul '09

Good Morning, CCIP did not initially post this alert to the NZNOG list yesterday as it was felt that members might not deem this type of posting appropriate for the NZNOG list. However there have been a number of requests from NZNOG members requesting for this to be posted here, who had received it from yesterday CCIP's mailing lists. CCIP would be interested in feedback about the applicability of CCIP's Alerts on the NZNOG list. Currently CCIP's threshold for issuing these types of alerts is when there is active exploitation of a new or unpatched vulnerability in the wild. Regards, Paul. -- Paul McKitrick Head of Stakeholder Engagement Centre for Critical Infrastructure Protection D: (+64) 4 498 7645 P: (+64) 4 498 7654 F: (+64) 4 498 7655 E: paul.mckitrick(a)ccip.govt.nz W: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. --- -------- Original Message -------- Subject: CCIP ALERT: Microsoft unpatched vulnerability is being actively exploited in the wild Date: Tue, 07 Jul 2009 13:38:28 +1200 From: CCIP Info <info(a)ccip.govt.nz> To: CCIP <info(a)ccip.govt.nz> CC: incidents(a)ccip.govt.nz Good Afternoon, For those of you who are not already aware, CCIP would like to bring your attention the the Microsoft Security Advisory 972890 that was released today: http://www.microsoft.com/technet/security/advisory/972890.mspx Microsoft have announced a vulnerability in Microsoft Video ActiveX Control that allows remote code execution. This is reported to affect versions of Windows XP and Window Server 2003. CCIP is bringing this to your attention as this vulnerability has been reported as being actively exploited in the wild. MITIGATION Administrators are advised to take the following mitigation steps immediately. There is currently no patch to correct this issue. However you can set the kill-bit to mitigate this vulnerability. Microsoft have provided a way to automatically implement the workaround by following the instructions under "Fix It For Me" in the following Knowledge Base article: http://support.microsoft.com/kb/972890 Alternatively the following quoted text can be included in a .REG file and imported into your registry. ---BEGIN QUOTE--- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0955AC62-BF2E-4CBA-A2B9-A63F772D46CF}] "Compatibility Flags"=dword:00000400 ---END QUOTE--- Please note that in addition to the class identifier listed in the above example there is a full list of class identifiers in the Suggested Actions-->Workarounds section of the Microsoft Advisory: http://www.microsoft.com/technet/security/advisory/972890.mspx It is recommended that all of them are implemented. There is also a writeup on Microsoft's Security Response Centre Blog: http://blogs.technet.com/msrc/archive/2009/07/06/microsoft-security-advisor… Regards, The CCIP Team --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

4 3

NZ Contacts for Integration/Network Work
by Skeeve Stevens 06 Jul '09

06 Jul '09

Hey all, I met a lot of you awesome guys at the last NZNOG and there is a pile of you that I would love to work with more, but in that wide jigsaw piece country of yours, I have no idea where you all are. We've got a lot of proposed projects on at the moment and NZ is featuring heavily in most of them, so I want to get a bunch of people on a list who we can use in different cities for different kinds of work. Work can involve site visits to install DSL services, onsite basic Cisco work, IPv6 work, general IT (fix server, pc, etc), and some consulting perhaps. We're dealing with a lot of large retail, and hotel chains which have networks throughout NZ as well, which is where some of the above work types slot into. I am not fabulous with NZ geography, so I would need someone to help with a list of the key cities, regional cities that might have those massive malls that always seem to have most of the 'common' chains. I prefer small businesses who are reliable, can be well presented, professional and know their towns well, as I will also need local advice on connectivity solutions - fibre, MetroE, wireless and so on in your particular area. There may be possible emergency work for problems, so I need to know your availability, and also your rates. I am looking at implementing a solution (which I've talked about before), where we have DSL handed off for the entire country (if possible) to a LNS in Auckland, so I will start talking to providers soon (don't all start emailing/calling me like last time!) ;-) So if you can send me an email directly on skeeve(a)eintellego.co.nz<mailto:skeeve(a)eintellego.co.nz> ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

2 2

Ops Manager Required at Araneo
by Jonathan Brewer 06 Jul '09

06 Jul '09

Hi Folks, We're looking for someone up to the challenge of running our network. I kind of figured that this would be on topic for NZNOG. :-) The Trademe Jobs advert is here: http://www.trademe.co.nz/Trade-me-jobs/IT/Management/auction-228577017.htm All CVs through the Trademe process, please. I will not be involved in screening the apps, but if you're interested in the job and can remind me of the last time we had a beer at Curry or NZNOG I will ensure your CV gets a thorough read by the team. Regards, Jon

1 0

802.11 Wireless plotting per AP
by Barry Murphy 05 Jul '09

05 Jul '09

Hey Guys, I know this may be a little off topic, however I know there are many wireless operators on list. I'm wondering what you use to track wireless signal from a base station to see what the footprint is. I.e. I would like to drive around down all the streets where this hotspot is located to plot a map of what signal strength is like in this location for a specific AP, I will circle the streets around the AP until I've lost all signal and hope to have some sort of map to work with :) Any help offlist would be appreciated. Thanks Barry Murphy

10 11

OFF-TOPIC - Samoa Vacancy - Chief Technologist - ISP
by Keith Davidson 02 Jul '09

02 Jul '09

All, Please pardon the slightly off topic nature of this post, but given the wintertime blues currently affecting NZ, perhaps just dreaming about a geek position in paradise and perpetual sunshine will bring about cheer and warmth to some. Cheers Keith ___________________ Subject: Vacant Position Chief Technologist - ISP Computer Services Limited is Samoa's oldest and largest IT company and operates Samoa's largest ISP. We are seeking an individual with flair and passion to help take our ISP business to the next level. We need an experienced IT guru wishing to relocate to Samoa to head up our internet Services development and support team. Ideally this person will come from a practical, hands-on environment in the same or a related industry. The chosen person will head up a team of local IT specialists and would have the ability to manage, mentor and develop this team to their full potential. We would like our preferred candidate to have practical knowledge in many of the following skills... * 5+ years of experience in the support and development in an internet services provider or related industry * Advanced programming knowledge of REDHAT or similar OS * Competency on Email server systems - SendMAIL, Mailwasher, SPAM Assassin or similar * Competency in support of MySQL and/or MS'SQL based Applications * General skills in one or more of PERL, JAVA, Flash, MS'Access, ODBC, CGI, PHP, Coldfusion, AJAX. * Familiarity with SQL in billing databases * Familiarity with a RADIUS server solution e.g RADIATOR * General skills in WEB Server maintenance - Microsoft and/or Apache * Ability to develop Caching technology - SQUID, Cisco WCCP or similar * Familiarity with Cisco router Advanced IOS and command structure * Familiarity with network technologies - VLAN, VPN * Familiarity with TCP/IP, BGP, AS, delegation and route assignments * Familiarity with WiFi technologies and hotspot services e.g ChilliSpot etc What we offer is a fun filled company in the warmest , safest and friendliest nation in the Galaxy. Outside of work Samoa has a very relaxed and social lifestyle with the opportunity for you to enjoy our beautiful nation and our strong Faa'Samoa culture... white sand beaches with warm water all year round, ideal for swimming, snorkeling ,diving, fishing, golf, tennis, squash, rugby, reading , running, mountain climbing and socializing. The position would be for a negotiable term of up to three years and includes relocation expenses to Samoa, family accommodation, educational expenses and a generous salary package with bonus. Our desire is for someone to fill this position immediately although we would make exceptions for our ideal candidate. If you feel this is you and your interested in experiencing our Faa'Samoa, please make contact including a copy of your CV with references to Technologist Position C/- CSL Private Bag Apia, Samoa dave(a)csl.ws or tevi(a)csl.ws Dave Main Business Development Manager Computer Services Ltd Apia, SAMOA Ph +685 20926 Fax +685 20932 Cell +685 7771301 dave(a)csl.ws

1 0

IPv6 in NZ - Computerworld article
by Dean Pemberton 29 Jun '09

29 Jun '09

ComputerWorld has today published a lengthy feature article on IPv6 in New Zealand. See the link below: http://computerworld.co.nz/news.nsf/netw/832D6FEFFCA92DB3CC2575E4007362D9

6 5

Fwd: [lca-announce] linux.conf.au Call for Papers are now open!
by Joel Wiramu Pauling 28 Jun '09

28 Jun '09

---------- Forwarded message ---------- From: linux.conf.au Announcements <lca-announce(a)lists.linux.org.au> Date: 2009/6/29 Subject: [lca-announce] linux.conf.au Call for Papers are now open! To: lca-announce(a)lists.linux.org.au === linux.conf.au Call For Papers === linux.conf.au ( http://www.lca2010.org.nz ) is pleased to announce the opening of its Call for Papers for the coming linux.conf.au, LCA2010! LCA2010 will be held from Monday 18 January 2010 to Saturday 23 January 2010 in Wellington, New Zealand. linux.conf.au isn't just a Linux conference. It is a technical conference about Free and Open Source Software, held annually in Australasia since 2001 - covering everything from the Linux Kernel and the BSDs to OpenOffice.org, from networking to audio-visual magic, from hardware hacks to Creative Commons. === Important Dates === Call for Papers opens: Monday 29 June 2009 Call for Papers closes: Friday 24 July 2009 Email Notifications from Papers Committee: Early September 2009 Registrations open: Mid September 2009 Conference Dates: Monday 18 January to Saturday 23 January 2001 === Information on Papers === The LCA2010 Papers Committee is looking for a broad range of papers spanning everything from programming and software to desktop and userspace to community, government and education but there is one essential: The core of your paper must relate to open source in some way, i.e., if it's a paper about software then the software has to be licensed under an Open Source license. The LCA2010 Papers Committee welcome proposals for Papers on the following topics: * Kernel and system topics such as filesystems and embedded devices * Networking topics such as peer to peer networking, or tuning a TCP/IP stack * Desktop topics such as office and productivity applications, mobile devices, peripherals, crypto & security and viruses and other malware * Server topics such as clusters and other supercomputers, databases and grid computing * Systems administration topics such as maintaining large numbers of machines and disaster recovery * Programming topics such as software engineering practices and test driven development * Free Software and Free Culture topics, including licencing and Free and Open approaches outside software * Free Software usage topics, including home, IT, education, manufacturing, research and government usage. Most presentations and tutorials will be technical in nature, but proposals for presentations on other aspects of Free Software and Free Culture, such as educational and cultural aspects are welcome. LCA2010 is pleased to invite proposals for three types of papers: * Presentation - 45 minutes * Tutorials - 1 hour and 45 minutes (short) * Tutorials - 3 hours and 30 minutes (long) Presentations are 45 minute slots (including questions) that are typically a one-way lecture from you to the audience - the typical conference presentation. These form the bulk of the available conference slots. Tutorials are either 1 hour and 45 minutes, or 3 hours and 30 minutes in length, and work best when they are interactive or hands-on in nature. Tutorials are expected to have a specific learning outcome for attendees. To increase the number of people that can view your talk, LCA2010 may video the talks and make them publicly available after LCA2010. When submitting your proposal you will be asked whether materials relating to your paper can be released under a Creative Commons ShareALike License. For more information, see: http://www.lca2010.org.nz/programme/papers_info === About linux.conf.au === linux.conf.au is one of the world's best conferences for free and open source software! The coming linux.conf.au, LCA2010, will be held at the Wellington Convention Centre in Wellington, New Zealand from Monday 18 January to Saturday 23 January 2010. LCA2010 is fun, informal and seriously technical, bringing together Free and Open Source developers, users and community champions from around the world. LCA2010 is the second time linux.conf.au has been held in New Zealand, with the first being Dunedin in 2006. For more information see: http://www.lca2010.org.nz/ === About Linux Australia === Linux Australia is the peak body for Linux User Groups around Australia, and as such represents approximately 5000 Australian Linux users and developers. Linux Australia facilitates the organisation of this international Free Software conference in a different Australasian city each year. For more information see: http://www.linux.org.au/ === Emperor Penguin Sponsors === LCA2010 is proud to acknowledge the support of our Emperor Penguin Sponsor, InternetNZ. For more information see: http://www.internetnz.org.nz/ === Papers Enquiries === LCA2010 Papers Committee Email: papers(a)lca2010.org.nz -- Andrew Ruthven LCA2010 - Director PO Box 11-682 | linux.conf.au 2010 Manners St | Follow the signs. Visit Wellington! Wellington 6142 | http://www.lca2010.org.nz NEW ZEALAND | _______________________________________________ lca-announce mailing list lca-announce(a)lists.linux.org.au http://lists.linux.org.au/listinfo/lca-announce

1 0

S92A copyright notifications
by Thomas Layzell 28 Jun '09

28 Jun '09

Hi, I've got a request from TUANZ regarding who (if anyone) receives 'Education notices' for their networks. If anyone is able to answer the following questions off list it would be appreciated: - Does your system administrator currently receive regular notices form rights holders alleging breach of copyright? - If so, are you able to estimate how many? - What do you currently do with them - determine and follow up with the staff member apparently implicated, or bin them? - If the Act results in a major increase in the number of such notices (say tenfold) and you are required to pass them through and disconnect after 3 allegations, how big an imposition and cost is this? - Do you anticipate difficulties arising with your staff/users as a result? Thanks in advance, nil returns are of interest. Thomas Layzell. THOMAS LAYZELL | NETWORK MANAGER - INFORMATION & COMMUNICATIONS TECHNOLOGY The New Zealand Automobile Association Incorporated Level 16, 99 Albert Street, Auckland | PO Box 5, Shortland Street, Auckland 1140 DDI. +64 9 966 8712 M. +64 21 434363 F. +64 9 966 8759 E. tlayzell(a)aa.co.nz W. www.aa.co.nz Over one million New Zealanders belong to the AA - Join us now! This email may contain information which is confidential. If you are not the intended recipient you must not use or disseminate this email or its attachments. If you have received this in error, please notify us immediately and delete this email. Please think before you print out this email.

1 0

McDonald's Phish
by Drew Broadley 28 Jun '09

28 Jun '09

http://ntcgroupinc.com/mcdonalds.co.nz-customer-satisfaction-survey/ Interesting one, where it gets you to fill in a survey then offers $50 in return for your time. Enter your credit card details (on an insecure page), vio la! (Just a heads up, Welcome to Monday)

3 2

Temperature Check: How's the Internet goin' in NZ?
by jamie baddeley 25 Jun '09

25 Jun '09

nznog has been quiet recently. <operational content> Beer. </operational content> Networks running OK? Cheers Jamie

10 9

APNIC 28 Beijing
by Skeeve Stevens 24 Jun '09

24 Jun '09

Hey all, I am trying to plan my drinking schedule ;-) Anyone else coming to Beijing for APNIC 28? ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

Re: [nznog] Temperature Check: How's the Internet goin' in NZ?
by Jodi Thomson 24 Jun '09

24 Jun '09

> When it's all gone quiet, you know they're up to something. Shhh they'll hear you =) -- Jodi Thomson Systems Engineer Prophecy Networks Ltd P.O.Box 420 21 Browning Street Napier DDI: +64 6 8243901 Ph: +64 6 9742200 FAX: +64 6 9742201 Mob: +64 21 937684 "Right now I'm having amnesia and deja vu at the same time. I think I've forgotten this before." > > -----Original Message----- > From: nznog-bounces(a)list.waikato.ac.nz > [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of jamie baddeley > Sent: Thursday, June 25, 2009 8:42 PM > To: nznog > Subject: [nznog] Temperature Check: How's the Internet goin' in NZ? > > nznog has been quiet recently. > > <operational content> > Beer. > </operational content> > > Networks running OK? > > > Cheers > >Jamie

2 1

NZRR Route Registry Update
by NZRR Database Notifications 22 Jun '09

22 Jun '09

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-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 112.141.0.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.169.16.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.173.224.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.60.4.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 110.76.128.0/23^23-29, 114.111.130.0/23^23-29, 114.111.142.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 117.18.238.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.161.80.0/23^23-29, 119.161.84.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 115.42.1.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.232.0/24^24-29, 117.18.235.0/24^24-29, 117.18.237.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.94.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 168.134.2.0/24^24-29, 192.65.182.0/24^24-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.160.169.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 198.22.61.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090608 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.60.128.0/17^17-29, 112.141.0.0/18^18-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.208.64.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 122.129.128.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.201.128.0/19^19-29, 112.141.96.0/20^20-29, 113.20.0.0/20^20-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 117.55.224.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.68.160.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.93.160.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 112.141.112.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.102.96.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.213.160.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 202.4.232.0/21^21-29, 202.46.136.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.169.16.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.170.8.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 116.90.72.0/22^22-29, 119.15.96.0/22^22-29, 119.63.208.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 110.76.128.0/23^23-29, 114.111.130.0/23^23-29, 114.111.142.0/23^23-29, 114.141.108.0/23^23-29, 115.42.0.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 118.107.60.0/23^23-29, 119.161.80.0/23^23-29, 119.161.84.0/23^23-29, 121.127.196.0/23^23-29, 122.100.0.0/23^23-29, 122.100.10.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.14.248.0/23^23-29, 202.21.136.0/23^23-29, 202.45.152.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.220.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.10.76.0/23^23-29, 203.16.60.0/23^23-29, 203.17.112.0/23^23-29, 203.18.102.0/23^23-29, 203.21.76.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.30.98.0/23^23-29, 203.32.86.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.120.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.60.4.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 220.157.74.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 115.42.5.0/24^24-29, 115.42.6.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.235.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.93.0/24^24-29, 119.161.94.0/24^24-29, 121.127.198.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.136.0/24^24-29, 141.243.60.0/24^24-29, 168.134.2.0/24^24-29, 192.65.182.0/24^24-29, 192.88.85.0/24^24-29, 192.102.239.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.124.13.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 198.22.61.0/24^24-29, 202.0.151.0/24^24-29, 202.6.91.0/24^24-29, 202.14.63.0/24^24-29, 202.14.247.0/24^24-29, 202.14.250.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090623 source: NZRR ------------------------------------------------------------

1 0

Kiwilink
by Geraint Jones (iSERVE) 18 Jun '09

18 Jun '09

I cant seem to find any NOC contact numbers for them, so if anyone from kiwilink is on the list can they give me a shout.

1 0

FW: IP Base & IP Services
by Philip D'Ath 16 Jun '09

16 Jun '09

I'm sure someone will regard this as commercial so apologies to those people already, but this is to exciting to not tell everyone. As of 12.2(50)SE Cisco have now moved basic IPv6 support on the following switches into the base image: 3750-E 3560-E 3750 3560 This reduces the cost of moving to IPv6 substantially, as previsouly you had to buy the very expensive "Advanced IP" image. Once you have one of these images on the kit you need to execute "sdm prefer dual-ipv4-and-ipv6 ..." AND reboot the device. ________________________________ [cid:image001.png(a)01C9EF14.CAF889C0]

2 1

NZRR Route Registry Update
by NZRR Database Notifications 15 Jun '09

15 Jun '09

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:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090614 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 15 Jun '09

15 Jun '09

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:AS23655 descr: advertised to AS24388 by Snap Internet Limited - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090612 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 15 Jun '09

15 Jun '09

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-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090608 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090616 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 13 Jun '09

13 Jun '09

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:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090614 source: NZRR ------------------------------------------------------------

1 0

for the DNS inclined
by bmanning＠vacation.karoshi.com 12 Jun '09

12 Jun '09

With resolution 2009-02-03-04, the ICANN Board asked the Root Server System Advisory Committee (RSSAC), the Security and Stability Advisory Committee (SSAC), and the ICANN staff to study the potential impact on the root zone stability that might arise when IPv6 address records, IDN top level names, other new TLDs, and new records to support DNS security are added to the root zone. The Board has expressed interest in hearing of the impact of the distinct changes, but also their aggregate effect on root zone operations. The Board also asks that the study address the technical and operational concerns regarding expanding the DNS root zone that have been expressed on this topic. A study team has been assembled and is composed of the following: Jaap Akkerhuis Lyman Chapin - Chair Patrik FC$ltstrC6m Glenn Kowack Lars-Johan Liman Bill Manning The goal of the study is to construct a complete, definitive, and authoritative model of the root server system (including all of its provisioning and query components) that shows how the different parts are related, and how changing the value of a variable in one part would affect each of the other parts. It will be as quantitative a model as possible given the relatively short time frame of the study. The idea is not to try to identify all of the bad things that might happen if (for example) the number of TLDs in the root zone were to increase by several orders of magnitude during the same time period in which new RRs were added for DNSSEC (b^@^\how many entries in the root zone is too many?b^@^]), but to construct a model that demonstrates what the effects would be throughout the system of changing the value of one or more variables either individually or in combination (e.g., the rate at which new TLDs are added to the root, or the frequency of key rollover events in a signed root). This model will provide an unbiased factual and analyticalb^@^Trather than anecdotalb^@^Tbasis for recognizing and evaluating concerns about root server system security and stability as the root grows. As a tool for policy makers, it will show the expected impact on the root server system of policy decisions that would change various root zone parameters. The study team has a couple of methods for collecting inputs and encourages interested parties to provide the study team with their concerns. There is a public mailing list: root-scaling(a)icann.org and There is a comment site: +http://www.icann.org/en/public-comment/public-comment-200907.html#root-scaling If there are others whom you think would be interested in this work or have opinions/ideas, please pass along this note. Thanks

1 0

fibre and internet providers in Melbourne?
by Thom Hooker 11 Jun '09

11 Jun '09

Good afternoon If anyone has any recommendations (or advice on who to steer clear of) on internet and/or fibre providers over in Melbourne can you please contact me off-list? We're in Tullamarine if that helps. Cheers Thom -- Thom Hooker Director of Operations SMX Ltd http://smx.co.nz

6 6

NZRR Route Registry Update
by NZRR Database Notifications 11 Jun '09

11 Jun '09

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:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet Limited - AS23655 members: 111.69.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090612 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Jun '09

07 Jun '09

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-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090608 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Jun '09

07 Jun '09

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-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 112.141.0.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 118.127.176.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 118.127.168.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.136.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 117.18.238.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.100.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 110.76.128.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.232.0/24^24-29, 117.18.235.0/24^24-29, 117.18.237.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.84.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.140.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090507 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 112.141.0.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.169.16.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.173.224.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.60.4.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 110.76.128.0/23^23-29, 114.111.130.0/23^23-29, 114.111.142.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 117.18.238.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.161.80.0/23^23-29, 119.161.84.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 115.42.1.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.232.0/24^24-29, 117.18.235.0/24^24-29, 117.18.237.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.94.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 168.134.2.0/24^24-29, 192.65.182.0/24^24-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.160.169.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 198.22.61.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090608 source: NZRR ------------------------------------------------------------

1 0

APNIC 28 Early Bird Registration Now Open
by Elly Tawhai 02 Jun '09

02 Jun '09

_______________________________________________________________________ APNIC 28 Early Bird Registration Now Open _______________________________________________________________________ Hi NZNOG Community, APNIC and CNNIC warmly invite you to join us for APNIC 28 at the Grand Hyatt, Beijing, from 25 to 28 August 2009. Hosted in one of the most dynamic cities in the region, attending APNIC 28 is an excellent opportunity to develop your networking skills and build business relationships. Early Bird Registration ----------------------- Registration for APNIC 28 is opening soon with discounts for early registration of up to 25 per cent. APNIC and CNNIC are also offering a fantastic prize of a portable mini PC for early bird registrations. Note, a convenient gateway is available for credit card payments. http://meetings.apnic.net/28/register Apply for your Visa ------------------- Unless you are a national of Singapore, Brunei, and Japan, you will need to apply for a visa to enter mainland China. Visas usually last for 30 days and must be used within 3 months of issue. Note, your passport must be valid for at least six months after the date you intend to enter to country. http://meetings.apnic.net/28/beijing/visas Speak at APNIC 28 ----------------- APNIC and CNNIC are looking for informational presentations with interesting and topical operational content that will benefit the larger Internet community. If you would like to contribute, here are some potential topics for you to consider: - Four-byte AS numbers - IPv6 real world experiences - ISP and carrier services such as: - Fibre to the home (FTTH) and other 'all optical' deployments - Large network deployments - Next Generation telephony Submit a brief summary of your proposal (two to four paragraphs) or a set of presentation slides to policy(a)apnic.net by 31 July 2009. Final Presentation slides are due on 14 August 2009. How do I find out more about APNIC 28? -------------------------------------- For more information about APNIC meetings, and how you can attend, please see: http://meetings.apnic.net Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ------------------------------------------------------------------------

1 0

The New Zealand Network Operators' Group
by Donald Neal 01 Jun '09

01 Jun '09

The New Zealand Network Operators' Group The NZNOG mailing list exists to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. The NZNOG Trust exists to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. The Trust is not yet GST registered, but work is under way to bring that about. Conference In the NZNOG conference, the people are represented by two separate yet equally important groups. The trust, which is responsible for where the money goes, and the organising committee who do most of the actual work. See http://2009.nznog.org/ for details of this year's conference. Discussions are under way between the organising committee and potential hosts of the 2010 conference. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has around 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of APN Online, Citylink, and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

Working Culture in New Zealand
by Christiaan Theron 01 Jun '09

01 Jun '09

Thanks to everybody that replied. On a different note I would appreciate the opinion of the list on : What are the advantages and disadvantages of working in IT in NZ? Thanks to Gary Benner for that. Chris

4 3

Re: [nznog] Working Culture in IT.
by Gary T. Benner 31 May '09

31 May '09

[Reply] At 08:41 on 1/06/2009 you wrote >I am researching working culture in IT. What does the list dislike about >working in New Zealand? Ask a negative question and you'll get a negative answer - how about re-phrasing the question in a more balanced way, such as "what are the advantages and disadvantages of working in IT in NZ? " kr Gary Ref#: 41006

2 1

Working Culture in IT.
by Christiaan Theron 31 May '09

31 May '09

Hi I am researching working culture in IT. What does the list dislike about working in New Zealand? Thanks Chris Theron

1 0

[Fwd: Apply for an ISIF grant now!]
by Elly Tawhai 27 May '09

27 May '09

Hi NZNOG Community, _______________________________________________________________________ ISIF Grant Program Invites Applicants _______________________________________________________________________ Applications for the Information Society Innovation Fund (ISIF) 2010 grant round are now open. Launched in 2008, the ISIF grant program aims to stimulate creative solutions to ICT development needs in the Asia Pacific region. The program provides grants of up to AUD 40,000 per project that help advance local and regional initiatives that introduce, improve, and apply Internet and other digital communications technologies for the benefit of Asia-Pacific users and communities. This year’s round of funding will benefit about 8 to 10 projects. ISIF is a joint initiative between the Canadian International Development Research Centre (IDRC), the Internet Society (ISOC), and the Asia Pacific Network Information Centre (APNIC). It is proudly sponsored by the DotAsia Organization, the registry operator for the .ASIA top-level domain. The overwhelming success of the first round of applications reflects the importance of technological innovation in today's challenging market circumstances, especially for developing economies. Karen Rose, ISOC Director of Education and Programmes stated: "We received many strong proposals from a diverse pool of applicants in the inaugural year of the ISIF program. We hope to have similar success this year, and strongly encourage new applicants to submit proposals for ISIF funding, as well as revised submissions from applicants that were unsuccessful last year." Project proposals from Asia Pacific-based public or private sector organizations, university, or research and development institutions and non-government organizations will be considered. Applications must be aligned with ISIF program objectives, selection criteria, and administrative guidelines. For example, project results must be shared as stated in the ISIF copyright and license scheme. Individuals are not eligible for grants. "The ISIF grants program is a great opportunity for innovation in the Asia Pacific. We hope that with the global Internet community facing the prospect of IPv4 depletion in the next few years, some 2010 grant applications will feature projects that assist the adoption of IPv6 in the region," said Paul Wilson, Director General of APNIC. Applications for the 2010 grant round closes on 31 July 2009. Grants will be made on a competitive basis and successful applicants will be required to make project details, outcomes, and findings publicly available. Complete information on the project and how to apply is available on the ISIF website at www.isif.asia. For more information: Sylvia Cadena | ISIF Program Officer | info(a)isif.asia | http://www.isif.asia

1 0

Discount Domains NS Down
by Liam Farr 26 May '09

26 May '09

Hi, Anyone else having trouble with discount domains, their name servers aren't responding to queries at the moment. Nameservers for www.discountdomains.co.nz: ns2.discountdomains.co.nz returned (SERVFAIL) ns3.discountdomains.co.nz returned (SERVFAIL) ns1.discountdomains.co.nz returned (SERVFAIL) Cheers Liam

3 4

software patents in New Zealand
by Ciaran O'Riordan 26 May '09

26 May '09

Hi all, As you hopefully know, New Zealand's patent legislation is being changed: http://theyworkforyou.co.nz/bills/patents/2009/may/05/first_reading "...The bill proposes that software should be patentable..." I'm building a wiki for FSF's End Software Patents campaign, and I'd like to gather info to assist anti-swpat campaigns in NZ: http://en.swpat.org/ http://en.swpat.org/wiki/New_Zealand But, I'm living in Europe, so someone recommended this group as a starting point. I know it's a tech list, but maybe I can find the sort of people who are concerned about tech policy. So, can anyone point me to websites I should read, people I should contact, or people I should inform? Thanks in advance, sorry for the OT email. -- Ciarán O'Riordan, +32 487 64 17 54, http://ciaran.compsoc.com/ Software patents wiki: http://en.swpat.org/ End Software Patents: http://www.EndSoftwarePatents.org/ Donate: http://endsoftwarepatents.org/donate List: http://campaigns.fsf.org/cgi-bin/mailman/listinfo/esp-action-alert

4 3

NZRR Route Registry Update
by NZRR Database Notifications 25 May '09

25 May '09

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:AS9483 descr: Route set advertised to AS9439 by Flatnet - AS9483 members: 203.97.150.0/24^24-29, 202.0.32.48/29, 202.0.32.88/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: routing(a)flatnet.gen.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050113 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9483 descr: advertised to AS9439 by Flatnet Networks - AS9483 members: 203.97.150.0/24^24-29, 202.170.163.224/27^27-29, 202.170.160.152/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: routing(a)flatnet.gen.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090526 source: NZRR ------------------------------------------------------------

1 0

NRO Nominations now open
by Srinivas (Sunny) Chendi 21 May '09

21 May '09

_______________________________________________________________________ Nominations now open for Number Resource Organization Number Council _______________________________________________________________________ The nomination period for the Number Resource Organization Number Council (NRO NC) opens today, 22 May 2009. How to nominate --------------- To nominate yourself or someone else as a candidate for the position, submit the details using our nomination page: http://meetings.apnic.net/28/elections/nominate Key dates --------- 22 May - NRO NC nominations open 28 July - NRO NC nominations close (17:30 UTC+10) 12 August - NRO NC online voting opens for APNIC members only 26 August - NRO NC online voting closes (09:00 UTC+8, Beijing time) 28 August - NRO NC onsite voting takes place (09:00-14:00 UTC+8, Beijing time) About the NRO NC ---------------- The NRO NC consists of 15 members, three from each of the five Regional Internet Registry (RIR) regions. Three individuals are appointed to the NRO NC from each of the RIR regions, including two members selected by the respective regional policy forum, and one member appointed by the Board of the RIR. Kenny Huang's position as one of the delegates from the APNIC region will become available on 31 December 2009. One individual from the Asia Pacific region will be selected to serve on the NRO NC for two years - from 1 January 2010 to 31 December 2011. If elected as a member of the NRO NC, you will: - Oversee recommendations on global IP address policy that result from the various RIRs' policy development processes - Have direct influence on the implementation of these policies - Participate in the management of policy development activities - Appoint people to the ICANN Board of Directors More information ---------------- For more information about the role and the NRO NC, please see: http://meetings.apnic.net/28/elections For more on the current members of the NRO NC, please see: http://aso.icann.org/ac/index.html If you have any questions, please contact: helpdesk(a)apnic.net Regards Sunny -- -------------------------------------------------------------------- Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3189/99 ____________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 May '09

21 May '09

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-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090522 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 May '09

21 May '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090522 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 May '09

14 May '09

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:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 May '09

14 May '09

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:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 May '09

14 May '09

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-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.130.120.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 203.147.108.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.219.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 May '09

14 May '09

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-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ LTD - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.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.118.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ LTD - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.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.118.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090515 source: NZRR ------------------------------------------------------------

1 0

.nz growth statistics
by Blair Harrison 10 May '09

10 May '09

Hi Folks, Once again I've re-done my .nz statistics and graphs up to March 2009. .xls and .html data available online at http://jedi.school.nz/nzdg.html Some interesting things to note this time around are the first ever drop in the total number of domains happened in November 2008 (down 217), .org.nzsurpassed . net.nz - though it's done this a few times before - and .geek.nz continues to grow - with a total of 873 domains at the end of March. .co.nz still remains king, consuming 86.1% of all .nz registrations. There were 350,430 total .nz domains at the end of March, up on 324,722 from March 2008 - an increase of 25,708 during the year. If any of you have comments or any ideas for interesting graphs or stats to pull out of this I'm happy to include them - just flick me an email. Cheers, Blair

1 0

Re: [nznog] Email from Xtra never arrives
by Jean-Francois Pirus 10 May '09

10 May '09

> I’m not seeing any incoming connections from anywhere remotely xtra or > yahoo like. Anyone know where I’d expect to see it coming from? Local Xtra seems to be coming from within 210.54.141.0/24 mta01.xtra.co.nz (or mta02 or mta03) fep01.xtra.co.nz (or fep02) Aus Xtra/Yahoo from 124.108.96.0/24 mta106.tnz.mail.aue.yahoo.com smtp103.tnz.mail.aue.yahoo.com (Again different numbers smtp101 etc) -- ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Technical Manager Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 1st Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------

1 0

Email from Xtra never arrives
by Rob McDonald 10 May '09

10 May '09

Hi, I'm having a number of complaints about my users never receiving email sent by xtra users. (presumably yahoo too). I can't seem to get any useful information from xtra helpdesk. Hopefully someone here knows who to talk to, or maybe a hint about their sending policies and how I might comply with them. I'm not seeing any incoming connections from anywhere remotely xtra or yahoo like. Anyone know where I'd expect to see it coming from? Rob McDonald | Director Level 2 Systems Ltd P: 0800-123-698 P: +64 9 950 3652 x 950 M: +64 21 902 929 eFax: +64 9 974 4734 W: <http://www.l2.co.nz/> http://www.L2.co.nz CONFIDENTIAL COMMUNICATION: This email message and any attachments are confidential. Please do not distribute without authorisation. If you are not the intended recipient or have received this message by error, please let me know and delete it from your records. Thank you for your cooperation. P Please consider the environment before printing this email.

1 0

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

10 May '09

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 Second APE6 - AS9503 mp-members: 2402:6000: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: neil.fenemor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090325 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, 2002:0:0:0:0:0:0:0/16^16-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)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR ------------------------------------------------------------

1 0

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

10 May '09

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-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR ------------------------------------------------------------

1 0

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

10 May '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 May '09

07 May '09

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-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 May '09

07 May '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.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.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.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.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.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.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 06 May '09

06 May '09

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-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.90.128.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 202.169.176.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.78.128.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 218.100.52.0/23^23-29, 220.233.4.0/23^23-29, 58.87.6.0/24^24-29, 58.96.0.0/24^24-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.5.127.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.15.243.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.187.0/24^24-29, 203.18.197.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.79.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090409 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 112.141.0.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 118.127.176.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 118.127.168.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.136.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 117.18.238.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.100.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 110.76.128.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.232.0/24^24-29, 117.18.235.0/24^24-29, 117.18.237.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.84.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.140.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090507 source: NZRR ------------------------------------------------------------

1 0

Wholesale DSL Opportunity
by Ben Cornish 05 May '09

05 May '09

All, We are looking at expanding our national Australian network into New Zealand, and as such we are looking for a partner to assist us with this. In the short term, we are looking for Transit and also access to Telecom NZ DSL tails(to be handed off as L2TP sessions over Ethernet preferably). Handoff location would be Sky Tower. Is there anyone interested in this opportunity - please contact me off list Thanks Ben Cornish National Network Manager Direct 07 3234 9302 Direct: 02 8235 3520 Mobile 0417 617 204 Email mailto:benc(a)brennanit.com.au Web http://www.brennanit.com.au/ http://www.brennanit.com.au/

1 0

Re: [nznog] 922Mhz SRD Link
by Brislen, Paul, VF-NZ 01 May '09

01 May '09

Hi all. We can't make any public statement about this interference until after the court hearing, early next week, but after that I'm happy to get one of the network guys to come in and chat about it with you if a: that would help, b: that's of interest and c: they're not already here under their own steam. Cheers Paul -------------------------------------------------------------------- This message was sent from my BlackBerry Wireless Handheld from Vodafone ________________________________ From: nznog-bounces(a)list.waikato.ac.nz To: NZNOG(a)list.waikato.ac.nz Sent: Sat May 02 08:55:23 2009 Subject: Re: [nznog] 922Mhz SRD Link Thanks Ian, Yes I believe that this is likely to be the same problem and the issue is not just causing problems for Vodafone but also smaller operators. The fact that MED have confirmed that they are operating within the allowable channels is of some concern as this would mean there is little that can be done however using equipment legal or not that can squash competition is surely an anticompetitive act. That aside I have completed another can of the area and was wrong on the power levels received from a 3rd cell phone operator, it was just over 2V/m and I’m pretty sure a signal this strong is really not healthy. This was obtained from 150/200m away. Not trying to get up in anyone’s face here but I wonder if in fact Telecom are being blamed for something that is being caused by other vendors networks as well. Have MED created some of the issues by slicing the available channels too fine as was the case with out tests of the WiMAX gear recently. And If MED has and is allowing the deployment of equipment that is making the public spectrum un-usable and they can not force the vendors to clean up their act then maybe they need to look at opening up some more USABLE public spectrum rather than just putting it up for auction where again only the big players have the funds available to purchase these ranges (and associated equipment). Regards Andrew -----Original Message----- From: Ian Batterbee [mailto:ibatterb(a)gmail.com] Sent: Friday, May 01, 2009 10:01 PM To: andrew(a)borg.co.nz Subject: Re: [nznog] 922Mhz SRD Link http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5&objectid=10569… relevant maybe ? andrew(a)borg.co.nz wrote, On Fri 01/05/2009 19:06: Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew ________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ----------------------------------------------------------------------------------------------- Unless otherwise stated, any views or opinions expressed are solely those of the author and do not represent those of Vodafone New Zealand Limited.

3 2

Re: [nznog] 922Mhz SRD Link
by andrew＠borg.co.nz 01 May '09

01 May '09

Thanks Ian, Yes I believe that this is likely to be the same problem and the issue is not just causing problems for Vodafone but also smaller operators. The fact that MED have confirmed that they are operating within the allowable channels is of some concern as this would mean there is little that can be done however using equipment legal or not that can squash competition is surely an anticompetitive act. That aside I have completed another can of the area and was wrong on the power levels received from a 3rd cell phone operator, it was just over 2V/m and I'm pretty sure a signal this strong is really not healthy. This was obtained from 150/200m away. Not trying to get up in anyone's face here but I wonder if in fact Telecom are being blamed for something that is being caused by other vendors networks as well. Have MED created some of the issues by slicing the available channels too fine as was the case with out tests of the WiMAX gear recently. And If MED has and is allowing the deployment of equipment that is making the public spectrum un-usable and they can not force the vendors to clean up their act then maybe they need to look at opening up some more USABLE public spectrum rather than just putting it up for auction where again only the big players have the funds available to purchase these ranges (and associated equipment). Regards Andrew -----Original Message----- From: Ian Batterbee [mailto:ibatterb(a)gmail.com] Sent: Friday, May 01, 2009 10:01 PM To: andrew(a)borg.co.nz Subject: Re: [nznog] 922Mhz SRD Link http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5 <http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5&objectid=1 0569875> &objectid=10569875 relevant maybe ? andrew(a)borg.co.nz wrote, On Fri 01/05/2009 19:06: Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew _____ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] The Internet is in the news!
by Yun Huang Yong 01 May '09

01 May '09

I think this is the Onion piece: http://preview.tinyurl.com/d5h8np At 09:23 AM 1/05/2009, Ian Batterbee wrote: >That was so bad I thought I was reading an article from the onion! > >Ruh roh. We'd better all upgrade to Internet 2. -- (__) Share what you know. Yun Huang Yong `\------(oo) Learn what you don't. gumby(a)mooh.org || (__) --' goosmurf(a)yahoo.com \|/ ||w--|| \|/ --

12 12

922Mhz SRD Link
by andrew＠borg.co.nz 30 Apr '09

30 Apr '09

Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew

1 0

Re: [nznog] The Internet is in the news!
by Scott Weeks 30 Apr '09

30 Apr '09

> >So would you trust a guy in a pink Hawaiian shirt to analyse and > >recommend the future of the internet? Being from Hawaii no, I wouldn't... ;-) Try something like these instead. http://www.alohashirtshop.com/docs/view_image.php?id=11361&width=608 http://www.hawaiian-shirt.net/paradise_found/pf08/bamboo_embroidery_bk_pf.j… ---------- bmanning(a)vacation.karoshi.com wrote: -------------- From: bmanning(a)vacation.karoshi.com pragmatically, WTF are folks going to do when you can't get more IPv4 space from APNIC? Pick the best answer(s): ) IPv6 ) NATs all the way down ) hijack space from others ) find a new line of work as a beer-bottle washer -------------------------------------------------------------- Ipv6 and whatever the new name for NAT-PT is. Then LISP? http://www.1-4-5.net/~dmm/lisp scott ------------------- ------------------- -------------------

1 0

Re: [nznog] The Internet is in the news!
by Scott Weeks 30 Apr '09

30 Apr '09

At 09:23 AM 1/05/2009, Ian Batterbee wrote: >That was so bad I thought I was reading an article from the onion! > >Ruh roh. We'd better all upgrade to Internet 2. -------- gumby_lists(a)mooh.org wrote: -------- From: Yun Huang Yong <gumby_lists(a)mooh.org> I think this is the Onion piece: http://preview.tinyurl.com/d5h8np ------------------------------------------------- That's just about the silliest thing I have seen! "The internet has been up for 5000 days, about 13 years, and hasn't broken down once." According to that the internet was 'started' in 1996! (See RFC 1 by Steve Crocker April 1969) I wonder what the hell I was on in 1987! Surely they wouldn't want to know about the introduction section of RFC 1254: A large number of widely dispersed Internet sites experienced simultaneous slowdown or cessation of networking services for prolonged periods... "youtube transmits more data than the internet." Wow, I didn't know youtube was out of band... ;-) I think the pink aloha shirt was affecting the brain of "sunrise gadget guy". That thing is worse that the old Magnum PI shirts! http://www.mokuman.com/images/magnumpi-shirt_header534.jpg scott ------------------- -------------------- --------------------

2 1

Re: [nznog] The Internet is in the news!
by Stu Fleming 30 Apr '09

30 Apr '09

Isn't a "brown-out" what an "ohnosecond" used to be called, being the approximate period of time between making a live config change and discovering the device non-responsive as a result? Brown-out being more expressive as it also describes the effect on the operator succinctly.

1 0

The Internet is in the news!
by Nathan Ward 30 Apr '09

30 Apr '09

http://technology.timesonline.co.uk/tol/news/tech_and_web/the_web/article61… "Internet users face regular "brownouts" that will freeze their computers as capacity runs out in cyberspace, according to research to be published later this year." Ruh roh. We'd better all upgrade to Internet 2. That beer Jamie made me try last night was pretty good. I forget what it was called. Phew. -- Nathan Ward

5 4

180/8 and 183/8 allocated to APNIC
by Leo Vegoda 30 Apr '09

30 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in April 2009: 180/8 and 183/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFJ+iBAvBLymJnAzRwRAq59AKDYIE9QGQAAJQDuqfQ5Qqo5YiZwWwCg1RNg wwnJkpL3STZw9fDOM7zUToM= =PtJl -----END PGP SIGNATURE-----

1 0

The New Zealand Network Operators' Group
by Donald Neal 30 Apr '09

30 Apr '09

The New Zealand Network Operators' Group The NZNOG mailing list exists to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. The NZNOG Trust exists to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. The Trust is not yet GST registered, but work is under way to bring that about. Conference In the NZNOG conference, the people are represented by two separate yet equally important groups. The trust, which is responsible for where the money goes, and the organising committee who do most of the actual work. See http://2009.nznog.org/ for details of this year's conference. Discussions are under way between the organising committee and potential hosts of the 2010 conference. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has around 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of APN Online, Citylink, and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

Two /8s allocated to APNIC from IANA (180/8, 183/8)
by Elly Tawhai 30 Apr '09

30 Apr '09

_______________________________________________________________________ Two /8s allocated to APNIC from IANA (180/8, 183/8) _______________________________________________________________________ Hi NZNOG Community, The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in April 2009 and will be making allocations from these ranges in the near future: 180/8 183/8 Reachability and routability testing of the new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ------------------------------------------------------------------------

1 0

Re: [nznog] CallPlus Routing
by Stu Fleming 29 Apr '09

29 Apr '09

> > On 30/04/2009, at 12:17 AM, Bradley Scarisbrick wrote: >> > It appears fears of an outbreak were unfounded, CP NOC is alive and >> > well, >> > and with a top notch sense of humor for the late shift ... >> > > > Graveyard shift, perhaps When the WHO downgraded the Mexican flu death toll from 152 to 7 the other day, my first thought was a re-enactment of "From Dusk till Dawn"...145 zombies wandering around looking for networking jobs...

1 0

Re: [nznog] CallPlus Routing
by Stephen Barker 28 Apr '09

28 Apr '09

Will oinkment help? Sorry, I'll crawl back under my rock now. Steve > -----Original Message----- > From: Bradley Scarisbrick [mailto:bradleys(a)republic.net.nz] > Sent: Thursday, 30 April 2009 12:18 a.m. > To: NZNOG(a)list.waikato.ac.nz > Subject: Re: [nznog] CallPlus Routing > > It appears fears of an outbreak were unfounded, CP NOC is > alive and well, > and with a top notch sense of humor for the late shift ... > > > On Wed, 29 Apr 2009 20:31:17 +1000, "Sean K. Finn" > <Sean.Finn(a)ozservers.com.au> wrote: > > Maybe the swine virus is really a Zombie virus in disguise. Uh oh. > > > > -----Original Message----- > > From: nznog-bounces(a)list.waikato.ac.nz > > [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Dean > Pemberton > > Sent: Wednesday, 29 April 2009 7:50 PM > > To: Bradley Scarisbrick > > Cc: NZNOG(a)list.waikato.ac.nz > > Subject: Re: [nznog] CallPlus Routing > > > > Zombie NOC...... Coooooool! > > > > =P > > Dean > > > > Bradley Scarisbrick wrote: > >> Could someone from CallPlus please contact me regarding an > issue with > >> routing to/from that network, CallPlus noc appears lifeless :) > >> > >> Thanks > >> --- > >> > >> Bradley Scarisbrick > >> > >> > >> _______________________________________________ > >> NZNOG mailing list > >> NZNOG(a)list.waikato.ac.nz > >> http://list.waikato.ac.nz/mailman/listinfo/nznog > >> > >> > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > -- > --- > > Bradley Scarisbrick > Creative ">P: +64 9 523 5620 > F: +64 9 523 5621 > M: +64 21 545 960 > W: http://www.republic.net.nz > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.12.3/2076 - Release > Date: 04/28/09 18:02:00 > >

1 0

CallPlus Routing
by Bradley Scarisbrick 28 Apr '09

28 Apr '09

Could someone from CallPlus please contact me regarding an issue with routing to/from that network, CallPlus noc appears lifeless :) Thanks --- Bradley Scarisbrick

5 5

NZRR Route Registry Update
by NZRR Database Notifications 28 Apr '09

28 Apr '09

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-ROUTES:AS23958 descr: advertised to AS9560 by DTS Ltd - AS23958 members: 202.68.94.0/23^23-29, 202.174.178.0/23^23-29, 202.174.190.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070907 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23958 descr: advertised to AS9560 by DTS - AS23958 members: 210.48.160.0/20^20-29, 202.68.94.0/23^23-29, 202.20.6.0/24^24-29, 202.36.172.0/24^24-29, 202.68.82.128/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: technical(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090429 source: NZRR ------------------------------------------------------------

1 0

Domain Propagation
by Thomas Rowley 27 Apr '09

27 Apr '09

Lately I've had a lot of issues with domain nameserver changes taking *ages*to propagate in NZ. They seem to propogate really quickly everywhere else in the world from what i can tell. Do some NZ ISP's take longer to update their DNS records for some reason? Anyone else experienced this? Cheers Thomas

18 27

NZRR Route Registry Update
by NZRR Database Notifications 27 Apr '09

27 Apr '09

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:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.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.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081124 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.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.118.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 27 Apr '09

27 Apr '09

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-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.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.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081203 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ LTD - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.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.118.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR ------------------------------------------------------------

1 0

Website
by Richard Nelson 27 Apr '09

27 Apr '09

Who is maintaining the NZNOG website at the moment? I'm trying to find some slides that were presented at NZNOG'08 but the links to the slides archives now redirect to the NZNOG'09 page. I was wondering if those slide sets are still available? Thanks, Richard.

3 2

APNIC 28 fellowships - apply now
by Srinivas (Sunny) Chendi 25 Apr '09

25 Apr '09

________________________________________________________________________ The APNIC 28 fellowship program ________________________________________________________________________ Dear At APNIC, we understand that it may be difficult for our members from developing economies to attend APNIC meetings. In response, APNIC provides the fellowship awards to enable people from these developing economies to attend the APNIC meeting free of charge. As an APNIC fellow, you can: ---------------------------- - Acquire hands-on experience in IPv6 transition and deployment strategies - Attend all workshops and tutorials at APNIC 28 - Participate in policy discussions that will affect how your organization accesses Internet number resources - Meet a wide range of people in the Internet industry from around the world For more information about the fellowship award packages, selection process, and submitting an application, please visit our website: http://meetings.apnic.net/28/fellowship Deadline -------- The deadline for submissions is Thursday, 21 May 2009. Sincerely, ________________________________________________________________________ Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3189 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

Telstra IP: 218.101.59.4
by Simon Lyall 23 Apr '09

23 Apr '09

Could whoever is in charge of this Proxy/Spider/whatever please contact me ASAP. I've blocked you for now after I unsuccessfully tried to contact you yesterday and had problems again today. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 1

Two blocks of AS Numbers allocated
by Leo Vegoda 22 Apr '09

22 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA AS Numbers registry has been updated to reflect the allocation of two blocks of AS Numbers recently. 53248-54271 Assigned by ARIN whois.arin.net 2009-04-21 54272-55295 Assigned by ARIN whois.arin.net 2009-04-21 The registry can be found at: http://www.iana.org/assignments/as-numbers/as-numbers.xml Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFJ78q5vBLymJnAzRwRAsxhAKCvxeFIPNw/gZnUDnH0Q51wWR7fiACeMKe+ XnUY36jXeaFRj2Ecn+4ZgFE= =cnqY -----END PGP SIGNATURE-----

1 0

What happens when someone attacks your fibre networks?
by Matthew Poole 22 Apr '09

22 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://perens.com/works/articles/MorganHill/ "The city of Morgan Hill and parts of three counties lost 911 service, cellular mobile telephone communications, land-line telephone, DSL internet and private networks, central station fire and burglar alarms, ATMs, credit card terminals, and monitoring of critical utilities. In addition, resources that should not have failed, like the local hospital's internal computer network, proved to be dependent on external resources, leaving the hospital with a "paper system" for the day." (continues in the article). To summarise, it's all very well having redundant systems but if someone takes to the telco infrastructure you still need something that's entirely distinct. Otherwise you end up in a wee bit of a pickle. It's a good case, as if further ones were needed, against BPL. If the power's up but the telco networks are down, interference with ham radio is a "bad thing"[tm]. - -- Matthew Poole "Don't use force. Get a bigger hammer." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ78f8TdEtTmUCdpwRAtuHAJ9ytrxlD9yY7sTN1ScPldX5qo4ynwCeK4YM HHa8f1TryqH5jpfTbspTXfM= =QKQe -----END PGP SIGNATURE-----

2 1

skype
by James Jones 21 Apr '09

21 Apr '09

http://i.gizmodo.com/5221522/skype-offering-country-unlimited-plan-for-6mon… holy crap NZ is included. do they have a local MGW in NZ? James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

2 1

Update on Domainz SQL injection attack--- is it fixed yet?
by Robert Cotter 21 Apr '09

21 Apr '09

And have they rolled back the hacks??? Regards Robert Cotter Sales Engineer rcotter(a)distributioncentral.co.nz<mailto:rcotter(a)distributioncentral.co.nz> Distribution Central NZ Unit 2, Level 1, 194 Victoria Street West, Auckland 1001, New Zealand. Mb 64 21 675550, T 64 9 309 8277, F 64 9 309 8276 www.distributioncentral.co.nz<http://www.distributioncentral.co.nz/> Distributor of : Accellion, Acronis, Aruba, Bluecoat, Boll Engineering, Crossbeam, F5, Force10, Fortinet, Infoblox, Netxen, Riverbed, TippingPoint, Xsigo . Vendor product link => www.distributioncentral.co.nz/Section.asp?section=9 This email is for the intended recipient(s) only, Be advised that if you have received this email in error that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. The sender cannot guarantee that this email or any attachment to it is free of computer viruses or other conditions which may damage or interfere with data, hardware or software with which it might be used. If you have received this email in error, please notify Distribution Central on +61 2 9425 5000 or notify sender.

1 0

msn.co.nz
by Michael Jager 20 Apr '09

20 Apr '09

So, I wouldn't normally make a post like this, but I figure one or two people might notice this at some point in the next day or so: mj(a)coalface:~$ whois msn.co.nz | egrep ^ns_name ns_name_01: fatih1.turkguvenligi.info ns_name_02: fatih2.turkguvenligi.info mj(a)coalface:~$ whois msn.co.nz | egrep ^domain_datelastmodified domain_datelastmodified: 2009-04-21T09:44:21+12:00 From my resolver's cache: ;; ANSWER SECTION: msn.co.nz. 3282 IN A 202.58.48.29 ;; AUTHORITY SECTION: msn.co.nz. 20363 IN NS ns4.msft.net. msn.co.nz. 20363 IN NS ns5.msft.net. msn.co.nz. 20363 IN NS ns1.msft.net. msn.co.nz. 20363 IN NS ns2.msft.net. msn.co.nz. 20363 IN NS ns3.msft.net. ;; ADDITIONAL SECTION: ns1.msft.net. 1571 IN A 207.68.160.190 ns2.msft.net. 1593 IN A 65.54.240.126 ns3.msft.net. 18367 IN A 213.199.161.77 ns4.msft.net. 18367 IN A 207.46.66.126 ns5.msft.net. 1302 IN A 65.55.238.126 From the new NS: ;; ANSWER SECTION: msn.co.nz. 14400 IN A 95.211.11.163 ;; AUTHORITY SECTION: msn.co.nz. 86400 IN NS fatih1.turkguvenligi.info. msn.co.nz. 86400 IN NS fatih2.turkguvenligi.info. ;; ADDITIONAL SECTION: fatih1.turkguvenligi.info. 14400 IN A 95.211.11.163 fatih2.turkguvenligi.info. 14400 IN A 95.211.11.163 It's not still April Fools, is it? -Mike

5 4

NZRR Route Registry Update
by NZRR Database Notifications 20 Apr '09

20 Apr '09

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-ROUTES:AS9790 descr: advertised to AS9560 by CALLPLUS - AS9790 members: 119.224.0.0/17^17-29, 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 119.224.128.0/20^20-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080304 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus - AS9790 members: 119.224.0.0/17^17-29, 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 119.224.128.0/20^20-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 202.37.22.0/24^24-29, 202.37.75.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: networksnoc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090421 source: NZRR ------------------------------------------------------------

1 0

NAND
by James Jones 19 Apr '09

19 Apr '09

is there any nand experts on here? I just was just wondering why none of the moblie phone providers have but local numbers on a cell like we do in the states. I was just wondering not very familiar with NAND stuff here in NZ. James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

7 6

Vector fibre in Auckland CBD
by Skip Parker 16 Apr '09

16 Apr '09

Morning, Anyone else seeing issues with vector fibre in the cbd today? It seems to coincide with a failure at the Vector switchboard as well... So information seems scarce. Skip Parker Rhema Broadcasting Group On 4/2/09, matthew(a)auscert.org.au <matthew(a)auscert.org.au> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > G'day all, > > We are seeing a decent trojan spam out using Facebook as the hook. The > emails all differ slightly but possess the same characteristics. Eg: > > From: "Facebook presentment" <support60(a)facebook.com> > Subject: Facebook announcement: Great looking girl having fun (Last rated > by Bradford Collins) > > Messages from Your Friends on Facebook, April 01, 2009 > > You have 1 friend requests - Personal Message: > Watch the video titled "Drunk Charlize is dancing striptease on my > Birthday Party, March 28, 2009! We're absolutely shocked!". > > Proceed to view full message: > > hxxp://facebook.shared.id-etsmrnhy5e.subject.876panel. > com/home.htm?/identification/authentication=0616n9m12 > > Added 16 minutes ago. Message ID: FB-06nnzbrxizjrzvr > 2009 Facebook community, Message Center. > > Multiple domains are being used all following a naming scheme of > > [3-5 digit number]panel.com > > Eg: > > 2349panel. com > 43553panel. com > 654panel. com > 876panel. com > 987panel. com > > Is anyone else seeing a decent run of this? > > Just trying to work out how widespread it is as we are preparing to do an > alert on it. > > Apologies if you see this across a few lists - looking for any feedback > on numbers on this (and it is all appreciated). > > Best regards, > > - -- Matthew McGlashan -- > Coordination Centre Team Leader | Hotline: +61 7 3365 4417 > Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 > (AusCERT) | Fax: +61 7 3365 7031 > The University of Queensland | WWW: www.auscert.org.au > Qld 4072 Australia | Email: auscert(a)auscert.org.au > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (FreeBSD) > Comment: http://www.auscert.org.au/render.html?it=1967 > Comment: http://www.auscert.org.au/render.html?it=1967 > > iD8DBQFJ1BXZNVH5XJJInbgRAvMqAJ0cqNWqI3riSyf5Tq9lGzxO9C6xegCcCpl0 > KzfS5kwPQpBMNU4TfhQuqDo= > =zKz3 > -----END PGP SIGNATURE----- > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > -- Sent from my mobile device Skip Parker m. 021 793 824 e. skip(a)ignition.net.nz

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Apr '09

14 Apr '09

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-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090415 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Apr '09

14 Apr '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090415 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Apr '09

08 Apr '09

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-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 115.187.128.0/17^17-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 202.4.228.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.36.204.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.145.62.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 206.222.230.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.160.50.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.103.0/24^24-29, 203.18.187.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.24.61.0/24^24-29, 203.25.165.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.29.0.0/24^24-29, 203.29.45.0/24^24-29, 203.29.77.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.31.48.0/24^24-29, 203.32.61.0/24^24-29, 203.32.82.0/24^24-29, 203.33.171.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.140.0/24^24-29, 203.34.200.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.18.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.131.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.27.0/24^24-29, 203.56.186.0/24^24-29, 203.56.230.0/24^24-29, 203.56.234.0/24^24-29, 203.57.93.0/24^24-29, 203.145.60.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.171.208.0/24^24-29, 203.190.217.0/24^24-29, 203.221.207.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.8.113.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.56.153.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: macca(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.90.128.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 202.169.176.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.78.128.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 218.100.52.0/23^23-29, 220.233.4.0/23^23-29, 58.87.6.0/24^24-29, 58.96.0.0/24^24-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.5.127.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.15.243.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.187.0/24^24-29, 203.18.197.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.79.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090409 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Apr '09

07 Apr '09

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-ROUTES:AS38477 descr: advertised to AS9560 by Unleash - AS38477 members: 116.90.128.0/21^21-29, 202.6.116.0/23^23-29, 192.88.99.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: jasper(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080901 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS38477 descr: advertised to AS9560 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 202.6.116.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090408 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Apr '09

07 Apr '09

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-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 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: paul.joslin(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.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.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 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: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090408 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 06 Apr '09

06 Apr '09

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: Route set advertised to AS24388 by Unleash Computers - AS38477 members: 116.90.128.0/21^21-29, 202.6.116.0/23^23-29, 192.88.99.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: jasper(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081114 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, 202.6.116.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090407 source: NZRR ------------------------------------------------------------

1 0

Trojan spam run with Facebook hook (AUSCERT#2009abf45)
by matthew＠auscert.org.au 01 Apr '09

01 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G'day all, We are seeing a decent trojan spam out using Facebook as the hook. The emails all differ slightly but possess the same characteristics. Eg: From: "Facebook presentment" <support60(a)facebook.com> Subject: Facebook announcement: Great looking girl having fun (Last rated by Bradford Collins) Messages from Your Friends on Facebook, April 01, 2009 You have 1 friend requests - Personal Message: Watch the video titled "Drunk Charlize is dancing striptease on my Birthday Party, March 28, 2009! We're absolutely shocked!". Proceed to view full message: hxxp://facebook.shared.id-etsmrnhy5e.subject.876panel. com/home.htm?/identification/authentication=0616n9m12 Added 16 minutes ago. Message ID: FB-06nnzbrxizjrzvr 2009 Facebook community, Message Center. Multiple domains are being used all following a naming scheme of [3-5 digit number]panel.com Eg: 2349panel. com 43553panel. com 654panel. com 876panel. com 987panel. com Is anyone else seeing a decent run of this? Just trying to work out how widespread it is as we are preparing to do an alert on it. Apologies if you see this across a few lists - looking for any feedback on numbers on this (and it is all appreciated). Best regards, - -- Matthew McGlashan -- Coordination Centre Team Leader | Hotline: +61 7 3365 4417 Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 (AusCERT) | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert(a)auscert.org.au -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iD8DBQFJ1BXZNVH5XJJInbgRAvMqAJ0cqNWqI3riSyf5Tq9lGzxO9C6xegCcCpl0 KzfS5kwPQpBMNU4TfhQuqDo= =zKz3 -----END PGP SIGNATURE-----

1 0

Fwd: RFC 5514 on IPv6 over Social Networks
by Nathan Ward 01 Apr '09

01 Apr '09

I got this email at 5:25AM today, which is 6:25PM April 1 in Belgium where Eric lives. I guess the joke is on him? It is only 9:25AM PDT though so the RFC editor is in the clear. Anyway, enjoy: Begin forwarded message: > From: rfc-editor(a)rfc-editor.org > Date: 2 April 2009 5:25:42 AM > To: ietf-announce(a)ietf.org, rfc-dist(a)rfc-editor.org > Cc: rfc-editor(a)rfc-editor.org > Subject: RFC 5514 on IPv6 over Social Networks > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5514 > > Title: IPv6 over Social Networks > Author: E. Vyncke > Status: Experimental > Date: 1 April 2009 > Mailbox: evyncke(a)cisco.com > Pages: 6 > Characters: 10127 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-vyncke-ip-over-social-network-01.txt > > URL: http://www.rfc-editor.org/rfc/rfc5514.txt > > > There is a lack of IPv6 utilization in early 2009; this is partly > linked to the fact that the number of IPv6 nodes is rather low. This > document proposes to vastly increase the number of IPv6 hosts by > transforming all Social Networking platforms into IPv6 networks. > This will immediately add millions of IPv6 hosts to the existing IPv6 > Internet. This document includes sections on addressing and > transport of IPv6 over a Social Network. A working prototype has > been developed. This memo defines an Experimental Protocol for the > Internet community. > > EXPERIMENTAL: This memo defines an Experimental Protocol for the > Internet community. It does not specify an Internet standard of any > kind. Discussion and suggestions for improvement are requested. > Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html > . > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor(a)rfc-editor.org. > Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > USC/Information Sciences Institute -- Nathan Ward

4 4

NZNOG NOC list
by Gerard Creamer 31 Mar '09

31 Mar '09

Hi, Something broke on the NZNOG website when we moved servers and a bunch of NOC list changes were lost. I have reentered as many as I have been able to find based on emails but would appreciate it if you could all check your entries. http://www.nznog.org/?page_id=6 If there is a problem with your entry please email abuse and amendments to info (at) nznog.org and I'll get onto fixing them up. If there are no problems with your entry please keep your abuse and general mutterings about competence to yourself :^) Cheers, Gerard

2 1

The New Zealand Network Operators' Group
by Donald Neal 31 Mar '09

31 Mar '09

The New Zealand Network Operators' Group Work is now nearing completion to establish the NZNOG Trust. The Trust is being set up to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. NZNOG is intended to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. Conference See http://2009.nznog.org/ for details of this year's conference. The plan is that next year's conference will be further south than Auckland. Discussions are now being held with prospective hosts, so if you have a burning desire to host New Zealand's only technical networking conference, now would be the time to speak up. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has around 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of APN Online, Citylink, and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

QoS-IXPs
by Brian E Carpenter 30 Mar '09

30 Mar '09

On behalf of Thomas Knoll: ---------- Forwarded message ---------- Date: Wed, 25 Mar 2009 02:02:42 +0100 (MET) From: Thomas M. Knoll <knoll(a)etit.tu-chemnitz.de> To: nznog(a)list.waikato.ac.nz Subject: QoS-IXPs Dear Sirs, excuse me please for bothering you with the following information, but I thought it could be of use for you as well. Background: I am currently proposing a class of service signalling extension to BGP in order to enhance the current best effort AS interconnection into a simple class-based interconnection. This primitive traffic separation scheme also encompasses lower layer QoS schemes in a consistent manner, which makes it attractive for QoS interested peering partners to meet on peering platforms with Ethernet QoS support. Therefore, I am trying to find out about Internet exchange points, which would a least transparently (untouched) transfer user priority bits across their platform and might even have 802.1p enqueueing and scheduling enabled on their switches. Having said that, I will point you to the current QoS capable IXP list on the web. http://www.bgp-qos.org/qos-ixp/ Furthermore, if you are interested to be recognized by QoS interested peering partners as potential peering platform, I would cordially invite you to register there as well. http://www.bgp-qos.org/qos-ixp/add.php Thank you in advance, Thomas Knoll

23 38

UPDATED CCIP ALERT: Conficker worm
by Paul McKitrick 29 Mar '09

29 Mar '09

Good Evening, CCIP issued an alert on 8/01/2009 about the Conficker worm which attempts to exploit a previously patched stack buffer overflow vulnerability in Microsoft Windows Server Service (MS08-067). CCIP is issuing this update notice to warn organisations of this activity and to prevent further compromises from occurring. The latest variants of the Conficker worm include updates to its ability to communicate to itself and these changes are scheduled to activate on 1 April 2009, it is unknown what will happen on 1 April 2009. CCIP has been working with organisations nationally and with the international Conficker Working Group on this situation and would appreciate being informed of any outbreaks of Conficker or incidents relating to Conficker via incidents(a)ccip.govt.nz as this will assist in CCIP¹s ability to determine the impact of Conficker on New Zealand's networks and to coordinate any responses or flows of information. Further information about Conficker, including how to detect and remove it can be found on the Conficker Working Group website: http://www.confickerworkinggroup.org/wiki/pmwiki.php?n=ANY.GeneralAssistance Further infromation about MS08-067 can be found on Microsofts website: http://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx Regards, Paul. -- Paul McKitrick Head of Stakeholder Engagement Centre for Critical Infrastructure Protection D: (+64) 4 498 7645 P: (+64) 4 498 7654 F: (+64) 4 498 7655 E: paul.mckitrick(a)ccip.govt.nz W: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

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-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.128.0/21^21-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.6.116.0/23^23-29, 202.27.88.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.170.56.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.johnson(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090120 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by bcl-nz - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.128.0/21^21-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.6.116.0/23^23-29, 202.27.88.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.29.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.170.56.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: philip.tan(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

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: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081222 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

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: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

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-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-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, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] VF / Ihug issues with Cisco ADSL Routers
by Terry Wilson 25 Mar '09

25 Mar '09

Thanks for everyone's quick replies. The trick with the 877 was to add "ip tcp adjust-mss 1400" onto the LAN interface and everything started working just like it should. Does anyone have any thoughts about the appropriate segment size to use for traffic in NZ that goes over DSL like this? Thanks again, Terry ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

5 4

Linksys + Netgear Worm
by Philip D'Ath 25 Mar '09

25 Mar '09

Oh joy, a worm is now out that infects Linksys and NetGear DSL routers. http://blogs.zdnet.com/BTL/?p=15197 'Psyb0t' worm infects Linksys, Netgear home routers, modems More information has surfaced about the botnet “psyb0t,” the first known to be capable of directly infecting home routers and cable/DSL modems. It was first observed infecting a Netcomm NB5 modem/router in Australia. Members of the website DroneBL, a real-time IP tracker that scans for and botnets and vulnerable machines, came to the conclusion that the “psyb0t” (or “Network Bluepill”) botnet was a test run to prove the technology. After the botnet’s discovery and public outing, the botnet operator swiftly shut it down, APC reports. [Read more: Stealthy router-based botnet worm squirming] However, the most recently discovered generation (dubbed ‘version 18′ in the code) targets a wide range of devices, and contains the shellcode for over 30 different Linksys models, 10 Netgear models, and 15 other models of cable and DSL modems, APC reports. It did not specify which models. APC: A list of 6000 usernames and 13,000 passwords were also included, to be used for brute force entry to Telnet and SSH logins which are open to the LAN and sometimes even the public WAN side of the routers. Generally, routers do not lock a user out after a number of incorrect password attempts, making brute force attacks possible. According to DroneBL, any router that uses a MIPS processor and runs the Linux Mipsel operating system (a simple operating system for MIPS Processors) is vulnerable if they have the router administration interface, or sshd/telnetd in a DMZ, with weak username/passwords. DroneBL noted this includes devices flashed with the open-source firmwares openwrt and dd-wrt, and the group also said that other routers may be vulnerable, as it had observed the bot running on routers based on the Vxworks operating system. Clearly, exploiting a home network ? which are growing in popularity ? has its benefits: they rarely power down, and a router attack enables hackers to exploit a network with greater levels of stealth, since there’s no affect on individual PCs on the network, APC writes. In fact, the staff of DroneBL wrote that the exploit is very difficult to detect, and the only way to discover it is to monitor traffic going in and out of the router itself ?beyond the reach of desktop computer software. In the past, exploits on professional-grade Cisco routers were easier to detect, as Cisco provides dedicated ports for connecting to the router, monitoring internal performance and configuring them. However, the vast majority of home routers sacrifice these features for the sake of cost savings. DroneBL says that the botnet is capable of scanning for vulnerable PHPMyAdmin and MySQL installations, and can also disable access to the control interfaces of a router, (meaning a factory reset is necessary to clear the worm). DroneBL was successful in shutting down the Command & Control channel that the botnet utilized, and the DNS that was hosted with afraid.org was also nullrouted. The Command & Control channel is now defunct, but at the height of its penetration, the botnet was suspected to control 100,000 hosts. Worse, the author of the botnet claimed to have infected 80,000 routers at one point while chatting anonymously on an IRC channel. WHAT DEVICES ARE AFFECTED According to Drone BL: We don’t know. There are so many devices out there that we could not possibly know. Your best bet would be to take action to upgrade the device firmware and secure any passwords if there is concern that the device may be vulnerable. Such actions will help to avoid exploitation by the worm. WHAT TO DO According to DroneBL: Ports 22, 23 and 80 are blocked as part of the infection process (but NOT as part of the rootkit itself, running the rootkit itself will not alter your iptables configuration). If these ports are blocked, you should perform a hard reset on your device, change the administrative passwords, and update to the latest firmware. These steps will remove the rootkit and ensure that your device is not reinfected.

3 2

Re: [nznog] VF / Ihug issues with Cisco ADSL Routers
by Martin Wilkinson 25 Mar '09

25 Mar '09

Have you tried to manually lock down the dsl operating mode? I.e don't let it autodetect Int atm0 Dsl operating-mode itu ________________________________ From: Terry Wilson <terry(a)pds-dn.co.nz> To: nznog(a)list.waikato.ac.nz <nznog(a)list.waikato.ac.nz> Sent: Thu Mar 26 09:55:05 2009 Subject: Re: [nznog] VF / Ihug issues with Cisco ADSL Routers Problem doesn’t go away if I shutdown and bring up interfaces. Not sure if its ADSL2+ related for us as the 827/837s that have shown this behaviour aren’t ADSL2 capable. Virtual interface comes up ok and I can ping the outside world no problem, can connect in via VPN and incoming email works ok (as long as it doesn’t time out) and web works occasionally. I have also tried with the newer adsl firmware from ftp://ftp.cisco.com/pub/access/800 with no success. ________________________________ This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal ________________________________

1 0

Re: [nznog] VF / Ihug issues with Cisco ADSL Routers
by Terry Wilson 25 Mar '09

25 Mar '09

Problem doesn't go away if I shutdown and bring up interfaces. Not sure if its ADSL2+ related for us as the 827/837s that have shown this behaviour aren't ADSL2 capable. Virtual interface comes up ok and I can ping the outside world no problem, can connect in via VPN and incoming email works ok (as long as it doesn't time out) and web works occasionally. I have also tried with the newer adsl firmware from ftp://ftp.cisco.com/pub/access/800 with no success. ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

1 0

VF / Ihug issues with Cisco ADSL Routers
by Terry Wilson 25 Mar '09

25 Mar '09

Have a lot of sites with 877 / 827 / 837 ADSL routers on ADSL connections, basic configs are all pretty much the same. On Monday last week we started experiencing issues with customers that are on Ihug ADSL accounts. HTTP traffic loads intermittently, incoming SMTP is very slow (100b/sec), pings and VPN appear to work ok. Have tried basic configs and have tested routers ok in our office (through Xtra ADSL line) and they work fine, have tested different Cisco routers with the same results. If however I use a telecom supplied Dlink or a Linksys all in one it all works fine. I have a fault logged with Vodafone but all I'm getting back is that its a Cisco problem. I am going to log a TAC call this morning but I thought I would find out if anyone else has struck this. Thanks, Terry ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

1 0

VoIP Conference
by James Jones 24 Mar '09

24 Mar '09

Would anyone here be intrested in attending a conference similar to Astricon or ClueCon here in New Zealand? -- James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

11 14

Section 92A to be scrapped
by Jean-Francois Pirus 23 Mar '09

23 Mar '09

FYI: http://www.nbr.co.nz/article/section-92a-be-scrapped-89121 -- ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Technical Manager Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 1st Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------

1 0

TCP Well Known Ports SQL File
by Dan Clark 19 Mar '09

19 Mar '09

Gidday, just before I go and re-invent the wheel, does anyone happen to have an up to date SQL dump of TCP Well known ports c/o iana. Cheers Dan Clark

2 2

NZRR Route Registry Update
by NZRR Database Notifications 18 Mar '09

18 Mar '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 18 Mar '09

18 Mar '09

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-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR ------------------------------------------------------------

1 0

Sounce of non-peering ranges or paths
by Simon Lyall 18 Mar '09

18 Mar '09

Just wondering what the easiest way is to get a list of NZ IPs ranges that are not peered at APE or WIX? (and maybe other NZIX pops). Need it to be over 90% accurate and easy to recheck every once in a while. Or is it easier to go the other way and start with a list of NZ IPs (from ?) and subtract what is being peered? I promise I won't use this list to target banner ads for other ISPs :) -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

3 3

Re: [nznog] Sounce of non-peering ranges or paths
by Erin Salmon 18 Mar '09

18 Mar '09

Strictly speaking I believe that's possible, but I'm reasonably sure that if you get a domestic table from one, they includes each other's customer routes. To be sure of course, you could just use both. Erin Salmon Managing Director - Unleash Phone: 03 365 1273 Mobile: 0275 877 913 From: Dan Clark [mailto:danclarknz(a)gmail.com] Sent: 19 March 2009 11:04 a.m. To: Erin Salmon Subject: Re: [nznog] Sounce of non-peering ranges or paths networks could be connected to Telstra and not connected to Telecom? Regards Dan On Thu, Mar 19, 2009 at 10:02 AM, Erin Salmon <erin(a)unleash.co.nz> wrote: Take the APE/WIX lists and subtract the Telecom domestic list? You'll need to be peered* with all the relevant parties of course. *Ahem, or paying for transit. Erin Salmon Managing Director - Unleash Phone: 03 365 1273 Mobile: 0275 877 913 -----Original Message----- From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] Sent: 19 March 2009 11:00 a.m. To: nznog Subject: [nznog] Sounce of non-peering ranges or paths Just wondering what the easiest way is to get a list of NZ IPs ranges that are not peered at APE or WIX? (and maybe other NZIX pops). Need it to be over 90% accurate and easy to recheck every once in a while. Or is it easier to go the other way and start with a list of NZ IPs (from ?) and subtract what is being peered? I promise I won't use this list to target banner ads for other ISPs :) -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Broadband needed
by Richard Naylor 18 Mar '09

18 Mar '09

Anyone have any capacity (of a few Mbps) in Te Kuiti for 3 days ? If so we have money and beer...... Richard

1 0

Re: [nznog] NZNOG & Discussion Topics (Mark Foster)
by Anton Smith 16 Mar '09

16 Mar '09

> ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 16 Mar 2009 16:46:39 +1200 (NZST) > From: "Mark Foster" <blakjak(a)blakjak.net> > Subject: Re: [nznog] NZNOG & Discussion Topics > To: "NZNOG List" <nznog(a)list.waikato.ac.nz> > Message-ID: > <58919.119.15.0.26.1237178799.squirrel(a)webmail.blakjak.net> > Content-Type: text/plain;charset=iso-8859-1 > > > On Sat, March 14, 2009 8:44 am, Andy Linton wrote: >> >> On 13/03/2009, at 16:31 , Leo Vegoda wrote: >> >>> In that spirit I'll repeat my suggestion for the update messages to >>> include >>> diffs. >>> >>> I don't know what software is being run but if it's the RIPE database >>> software then the update processor can be told to produce diffs in the >>> notification messages it sends. If it's a different database then >>> I'm fairly >>> sure it's quite easy to plug in. I just know that knowing what the >>> change is >>> is probably a dead useful feature. >>> >>> http://www.ripe.net/db/news/update-changes-200410.html >> >> The back end is IRRD. The NZRR requirements are simple and running the >> RIPE code simply got too hard. >> >> A good suggestion about the diffs and I know it's been asked for >> before. CityLink and I are planning to do some updates/changes to the >> software soon so that people can submit diffs as well as get them in >> the output etc. >> >> If you have any burning requirements let me know and I'll feed it into >> the mix. Joe's idea of a separate list has some merit - again let me >> know directly and I'll come back to the list with results. >> > > NZNOG in the great scheme of things doesn't seem to be so busy that the > NZRR notifications nor discussion on 'related' topics are that big a deal > from where I sit. > > I don't read the NZRR notifications often as they don't relate directly to > my day-to-day work but i glance at them occaisionally as they help me keep > tabs on 'what's going on' out there. Were they bounced to some other > mailing list, I probably wouldn't read them at all as I don't need to see > them so wouldn't 'opt-in'. > > Suggest the same applies to any sort of 'off topic' mailing list that > diverges from NZNOG itself. The value of the list is diluted when less > people are subscribed; the value of NZNOG is among other things, the > knowledge that clooful, relevant people are likely to be reading it. > Who's to say that theyre going to subscribe to another mailing list where > the SNR is likely worse? > > I like relevant subject lines... it's pretty easy to ignore / postpone for > later / delete threads that you're genuinely not interested in, and I > havn't yet seen the volume of traffic on NZNOG suggest an alternative > means is required. At the same time, i'm not sure that a 'chat' list > would draw in the same crowd necessarily. > > (Anyone remember NZNET? Fizzled. Remember?) > > Mark. IMHO. > I don't have any problems with the amount of traffic - the discussion about laws that will affect operations are relevant imho. That and it is nice to see activity and discussion on the list in general. Unfortunately it seems we have a lengthy discussion about "relevancy" almost every time there is something that only a few object to. Regards, Anton

2 1

NZNOG & Discussion Topics
by Jonathan Brewer 15 Mar '09

15 Mar '09

Hi Folks, For the health and happiness of users of this list, could we perhaps keep discussions to OSI Layer 5-1? If I'm way off-base in asking this, someone please throw a beer at me. Cheers, Jon

18 22

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

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-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 202.55.96.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 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: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090212 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 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: paul.joslin(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

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-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.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, 120.138.22.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.129.253.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.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, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-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, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

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-ROUTES:AS4826 descr: advertised to AS9560 by Vocus - AS4826 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.161.64.0/19^19-29, 120.88.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.32.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.14.32.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 202.182.96.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.145.32.0/19^19-29, 203.201.128.0/19^19-29, 210.56.224.0/19^19-29, 113.20.0.0/20^20-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.141.96.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 117.55.224.0/20^20-29, 119.15.96.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 174.128.16.0/20^20-29, 202.3.96.0/20^20-29, 202.4.224.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.88.112.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.130.160.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.90.128.0/21^21-29, 116.193.176.0/21^21-29, 116.212.64.0/21^21-29, 119.31.232.0/21^21-29, 119.63.200.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.0.0.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 192.173.16.0/21^21-29, 202.36.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.78.240.0/21^21-29, 202.92.240.0/21^21-29, 202.146.208.0/21^21-29, 202.160.112.0/21^21-29, 203.160.8.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 122.100.0.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 125.254.112.0/22^22-29, 140.200.248.0/22^22-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.50.188.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.33.116.0/22^22-29, 203.62.184.0/22^22-29, 203.79.16.0/22^22-29, 203.92.28.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 59.86.160.0/23^23-29, 63.218.156.0/23^23-29, 74.80.126.0/23^23-29, 114.111.132.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.160.230.0/23^23-29, 122.100.6.0/23^23-29, 122.100.8.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.6.42.0/23^23-29, 202.6.116.0/23^23-29, 202.12.90.0/23^23-29, 202.36.204.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.92.94.0/23^23-29, 202.93.4.0/23^23-29, 202.124.106.0/23^23-29, 202.150.60.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.90.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.79.88.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 206.222.230.0/23^23-29, 210.9.230.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 97.64.46.0/24^24-29, 113.212.98.0/24^24-29, 114.111.128.0/24^24-29, 116.50.58.0/24^24-29, 122.100.15.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.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.174.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.168.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.190.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.106.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.247.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.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.122.132.0/24^24-29, 202.160.50.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.4.154.0/24^24-29, 203.5.45.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.16.243.0/24^24-29, 203.17.4.0/24^24-29, 203.17.68.0/24^24-29, 203.17.95.0/24^24-29, 203.17.183.0/24^24-29, 203.18.94.0/24^24-29, 203.18.136.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.24.61.0/24^24-29, 203.26.204.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.28.14.0/24^24-29, 203.29.0.0/24^24-29, 203.29.77.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.31.48.0/24^24-29, 203.32.82.0/24^24-29, 203.33.70.0/24^24-29, 203.33.113.0/24^24-29, 203.33.171.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.140.0/24^24-29, 203.34.200.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.139.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.27.0/24^24-29, 203.56.186.0/24^24-29, 203.56.230.0/24^24-29, 203.57.93.0/24^24-29, 203.63.3.0/24^24-29, 203.63.67.0/24^24-29, 203.79.20.0/24^24-29, 203.92.25.0/24^24-29, 203.96.157.0/24^24-29, 203.98.81.0/24^24-29, 203.111.63.0/24^24-29, 203.111.105.0/24^24-29, 203.119.56.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.166.89.0/24^24-29, 203.171.4.0/24^24-29, 203.190.217.0/24^24-29, 203.221.207.0/24^24-29, 205.233.128.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.55.110.0/24^24-29, 210.56.153.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090114 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 115.187.128.0/17^17-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 202.4.228.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.36.204.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.145.62.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 206.222.230.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.160.50.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.103.0/24^24-29, 203.18.187.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.24.61.0/24^24-29, 203.25.165.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.29.0.0/24^24-29, 203.29.45.0/24^24-29, 203.29.77.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.31.48.0/24^24-29, 203.32.61.0/24^24-29, 203.32.82.0/24^24-29, 203.33.171.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.140.0/24^24-29, 203.34.200.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.18.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.131.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.27.0/24^24-29, 203.56.186.0/24^24-29, 203.56.230.0/24^24-29, 203.56.234.0/24^24-29, 203.57.93.0/24^24-29, 203.145.60.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.171.208.0/24^24-29, 203.190.217.0/24^24-29, 203.221.207.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.8.113.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.56.153.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: macca(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

Four blocks of AS Numbers allocated
by Leo Vegoda 11 Mar '09

11 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA AS Numbers registry has been updated to reflect the allocation of four blocks of AS Numbers recently. 49152-50175 Assigned by RIPE NCC whois.ripe.net 2009-03-06 50176-51199 Assigned by RIPE NCC whois.ripe.net 2009-03-06 51200-52223 Assigned by RIPE NCC whois.ripe.net 2009-03-06 52224-53247 Assigned by LACNIC whois.lacnic.net 2009-03-11 The registry can be found at: http://www.iana.org/assignments/as-numbers/as-numbers.xml Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.9.1.287 wj8DBQFJuUXxvBLymJnAzRwRAkgiAJ4gPAIF9egizyMbGGB/2MAciOCsdQCfXQfX N4gRb5lyNjDDcKZ4bhf5AqY= =LKc/ -----END PGP SIGNATURE-----

1 0

TelstraClear IP Routing Contact
by Matthew Moyle-Croft 11 Mar '09

11 Mar '09

Hi, I've tried phone numbers in the APNIC whois DB for AS9901 and the numbers on the NZNOG NOC contacts page for TelstraClear (AS9901) but I get "no longer in service". Any chance someone who has an ability to talk BGP engineering could contact me about a routing issue causing high latency to us? Phone call or email is fine (see below for details). Thanks, Matthew -- Matthew Moyle-Croft Internode/Agile Peering and Core Networks Level 5, 162 Grenfell Street, Adelaide, SA 5000 Australia Email: mmc(a)internode.com.au Web: http://www.on.net Direct: +61-8-8228-2909 Mobile: +61-419-900-366 Reception: +61-8-8228-2999 Fax: +61-8-8235-6909

1 0

Fwd: [kiwi foo campers] stubbornness
by Andy Linton 11 Mar '09

11 Mar '09

Seems to me that ISPs should follow TelstraClear's lead and get their ass out of the TCF negotiations ASAP. andy Begin forwarded message: > From: Richard Wood <richard(a)internetnz.net.nz> > Date: 12 March 2009 10:32:37 > To: campers(a)groups.baacamp.org > Subject: [kiwi foo campers] stubbornness > Reply-To: campers(a)groups.baacamp.org > > A spokesman for Justice Minister Simon Power told NZPA it was still > the > Government's preference that the industry should sort out the issue > itself. > > "We're advised that the negotiations are going along in a reasonably > constructive way so we're hopeful that could still happen, even > without > TelstraClear," the spokesman said. > > http://www.guide2.co.nz/politics/news/copyright-negotiations-reasonably-con… >

6 8

TelstraClear have rejected s92a
by Spiro Harvey 11 Mar '09

11 Mar '09

for those who haven't seen: http://www.stuff.co.nz/technology//2252415/TelstraClear-rejects-copyright-c… I believe this means that the law will be suspended and rewritten. -- Spiro Harvey UNIX Specialist, Writer, Editor http://twiddle.starforge.net.nz Give us this day our garlic bread and lead us not into vegetarianism but deliver us some pizza. +++ ATH0

4 7

ASO Call for Comments on Nominees for ICANN Board Seat
by Srinivas (Sunny) Chendi 09 Mar '09

09 Mar '09

Dear Colleagues, Following a public nomination period that closed on 22 February 2009, the ASO Address Council (ASO AC) selected the final set of candidates to fill the ASO seat on the ICANN Board. This seat is currently held by Dave Wodelet, whose term expires in May 2009. The candidates are: - Jody Daniel Newman - Ray Plzak - Jordi Palet Martinez - Rajesh Chharia - Suzanne Woolf - Barry Shein The candidates listed above agree to serve in an ASO seat on the ICANN Board of Directors if selected by the ASO Address Council. In April 2009, the ASO AC will make its final selection to appoint one of these individuals to fill the ASO Board seat. To aid them in making their final selection, the ASO AC members request public comments and statements of support for the candidates. The public comment period will remain open until 23:59 (UTC) on 9 April 2009. You can provide your comments and statements of support for the candidates on the aso-announce mailing list. These will be publicly archived at: http://www.aso.icann.org/lists Alternatively, if you would prefer not to subscribe to that mailing list, you may submit your comments directly to the ASO AC Nominations Committee by sending an email to <nom-com(a)aso.icann.org>. A digest of all comments sent to the mailing list or received by the Nominations Committee will be published on the ASO web site at: http://www.aso.icann.org/elections Best regards, Srinivas (Sunny) Chendi External Relations Manager APNIC For; Axel Pawlik Managing Director RIPE NCC On behalf of the ASO/NRO Secretariat

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '09

09 Mar '09

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-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '09

09 Mar '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '09

09 Mar '09

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-ROUTES:AS38333 descr: Route set advertised to AS9560 by Symbio Networks - AS38333 members: 115.187.128.0/17^17-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: arman.hossain(a)symbionetworks.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090213 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS38333 descr: advertised to AS9560 by Symbio Networks Pty ltd - AS38333 members: 115.187.128.0/17^17-29, 125.213.160.0/19^19-29, 210.80.131.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: arman.hossain(a)symbionetworks.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR ------------------------------------------------------------

1 0

APE 6to4
by Michael Fincham 08 Mar '09

08 Mar '09

Hi everyone, Just a quick announcement to say that with the departure of Jasper (who some of you may have met at NZNOG 09/08) we will unfortunately be withdrawing our 6to4 announcements from the APE. This was his project and we no longer have any staff enthusiastic about maintaining it. Expect the routes to disappear at some point in the next few days. If anyone is seriously using this service, feel free to get in touch and we'll see what we can do. -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250 DDI: 03 978 1223 Mobile: 027 666 4482

6 10