July 2009 - NZNOG - lists.nznog.org

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