December 2008 - NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 18 Dec '08

18 Dec '08

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, 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.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.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.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 20081204 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, 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 ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 18 Dec '08

18 Dec '08

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.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.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 20081212 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.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 ------------------------------------------------------------

1 0

IPv6 Steering Group Technical SIG - Announcement/Invitation
by Dean Pemberton 18 Dec '08

18 Dec '08

A workshop at held at InternetNZ on the 28 November in Wellington saw the formation of a New Zealand IPv6 Steering Group. This group includes representatives from telecommunications carriers, internet service providers, ICT vendors, and industry and user associations. The members of this steering group consist of invited senior representatives from the following organisations: InternetNZ TUANZ ISPANZ Telecommunications Carriers Forum Digital Development Forum Telecom TelstraClear WorldXChange Orcon FX Networks REANNZ Canterbury Development Corporation Kordia Cisco Vodafone Juniper Networks Alcatel Lucent Braintrust This steering group will primarily be concerned with high level discussion regarding the deployment of IPv6 within New Zealand. The steering group will not necessarily be a place where technical discussion takes place. As with so many things these days, a combination of business and technical expertise must be bought together to solve a given problem. To this end at the same workshop a Technical Special Interest Group (TechSIG) was also established. The goals of this group are: . To act as a central point for IPv6 technical discussion within the New Zealand Internet community. . To identify to the IPv6 Steering Group any business related barriers to IPv6 deployment which have been identified by the SIG's technical contributors. . To comment and provide potential solutions to technical related barriers identified by members of the IPv6 Steering Group. . To stimulate the production of relevant technical documentation. The co-conveners of this group are Andy Linton Nathan Ward Brian Carpenter Dean Pemberton A mailing list has been created and membership is open to all interested parties. Subscription details can be found at the link below; http://listserver.internetnz.net.nz/mailman/listinfo/ipv6-techsig I would encourage anyone who has an interest in the deployment and growth of IPv6 to join and contribute to the list. Please do not feel that this is a 'Networking Specialist Only' list. The deployment of IPv6 (and depletion of IPv4) has just as significant an impact on system administrators and content/application providers as it does on network administrators. I welcome all technical viewpoints onto the list. Thank you for your time. Dean Pemberton (Co-convener, IPv6 Steering Group Technical SIG)

1 0

NZRR Route Registry Update
by NZRR Database Notifications 18 Dec '08

18 Dec '08

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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-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, 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.205.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 20081121 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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.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 20081219 source: NZRR ------------------------------------------------------------

1 0

Microsoft releasing emergency patch for perilous IE flaw
by Dean Pemberton 16 Dec '08

16 Dec '08

Interesting reading. http://news.yahoo.com/s/afp/20081216/ts_alt_afp/uschinaitinternetsoftwarecr… Microsoft will release an emergency patch on Wednesday to fix a perilous software flaw allowing hackers to hijack Internet Explorer browsers and take over computers. The US software giant said on Tuesday that in response to "the threat to customers" it immediately mobilized security engineering teams worldwide to deliver a software cure "in the unprecedented time of eight days." According to researchers at software security firm Trend Micro, attacks based on the vulnerability in the world's most popular Web browser are spreading "like wildfire" with millions of computers already compromised.

1 0

FW: Media Release - Industry agrees - IPv6 transition plan needed
by Mark Foster 16 Dec '08

16 Dec '08

This just came to my attention... Industry agrees - IPv6 transition plan needed Media Release - 15 December 2008 Following a workshop convened by the Ministry of Economic Development, major ICT industry and stakeholder organizations have agreed on the need for New Zealand to develop a transition plan from IPv4 to IPv6, the next generation Internet addressing protocol. The transition plan will include education, and identification and removal of roadblocks to IPv6 deployment. There is growing urgency for the Internet to support both IPv4 and IPv6, which together will offer vastly increased resources. More than one million new devices connect to the Internet every week and the pool of four billion IPv4 addresses is expected to be exhausted by 2010. IPv6 supports a much larger pool of addresses, enough to assign an IP address to each grain of sand in a fine layer covering the entire planet. Internet advocacy group InternetNZ, a key sponsor of IPv6-related initiatives in New Zealand, has agreed to provide continued support for furthering IPv6 as a national industry initiative under the auspices of the Digital Development Forum. The forum is a multi-stakeholder initiative designed to promote New Zealand's transition into the digital economy. The workshop was held on 28 November in Wellington and saw the formation of an IPv6 Steering Group, which includes representatives from telecommunications carriers, internet service providers, ICT vendors, and industry and user associations. A complete list of stakeholder organizations is included at end of this release. Telecommunications industry consultant Dr Murray Milner has been confirmed as independent convenor for the steering group. Milner says IPv6 provides much more flexibility in allocating addresses, and will allow Internet growth in New Zealand to keep pace with the expected worldwide trend. InternetNZ Executive Director Keith Davidson says the initiative is more than welcomed and indicates increasing recognition that IPv6 deployment will be a business-critical issue as IPv4 exhaustion looms. While this is not a Y2K scenario, unless New Zealand has a clear plan for the introduction of IPv6 then there is an increased risk of Internet black holes developing. "This may mean that communication via the internet may not be possible in the near future between parts of New Zealand's IPv4-based Internet and certain developing countries such as China and India, where IPv6-only Internet infrastructure is currently being deployed," says ISPANZ President Jamie Baddeley. Digital Development Council Executive Director Paul Alexander points out that it is not time to panic but it is time for the ICT industry to get organised and reach out to the wider business community to explain the issue. CEO of the Telecommunications Carrier's Forum Ralph Chivers says that progress can only be made with a co-coordinated and concerted effort across the ICT sector to ensure New Zealand has a timely and trouble-free transition to IPv6. IPv6 was highlighted in Digital Strategy 2.0, which mirrored the growing urgency expressed in global ICT technical forums on the need for leadership amongst key industry stakeholders in transitioning to IPv6. IPv4 was deployed in the mid 1980's, at a time when billions of Internet connections were never contemplated. IPv6 has been under development since the mid 1990's, and currently exists in small pockets around the world. TUANZ Chief Executive Ernie Newman says that users welcome the initiative and that TUANZ stands ready to take an active part in educating users once equipment suppliers and the registry have ensured they are fully prepared and have clarified the major steps users need to take. Next steps include development of a technical education plan to stimulate IPv6 skills in New Zealand's ICT and academic sectors. This will be followed by development of a roadmap for the deployment of IPv6 for New Zealand and a business sector outreach programme. A national IPv6 Hui anticipated for September 2009 is also planned. For more information contact: Murray Milner Independent Convenor IPv6 Steering Group 027 443 0120 murray.milner(a)xtra.co.nz Keith Davidson Executive Director InternetNZ 021 377 587 exe.dir(a)internetnz.net.nz Industry organizations supporting the need for a transition plan to IPv6: * InternetNZ * TUANZ * ISPANZ * Telecommunications Carriers Forum * Digital Development Forum * Telecom * TelstraClear * WorldXChange * Orcon * FX Networks * REANNZ * Canterbury Development Corporation * Kordia * Cisco * Vodafone * Juniper Networks * Alcatel Lucent * Braintrust

15 27

Vendor Reception at NZNOG09
by Nathan Ward 15 Dec '08

15 Dec '08

Hi all, At NZNOG09 in January we are intending on trying something a little new - having a "Vendor Reception" on the Wednesday evening. This is to give vendors the chance to meet people with glossy pieces of paper handy, and also to encourage the social aspect of the conference and networking with industry peers. The format of this is roughly: - Vendors/someone wanting to sell something sets up some sort of stand, table, demo, whatever[1] around a room/pool. - Vendor swag encouraged[2]. - Open bar, possibly dinner depending on numbers and budget. - Informal. We may do a bit at some point early in the evening where vendors can stand up and read out a short[3] personals ad - we'll decide how that goes closer to the time based on how many people are interested in participating and exhibiting, and other arbitrary criteria we have yet to invent. This will be open to sponsors automagically. Non-sponsors can participate, and would be asked to contribute to offset the cost of drinks and food for the evening. Please contact me on nznog(a)daork.net if you're interested in exhibiting. Cheers! -- Nathan Ward [1] Jonny "Mr Marketing" Martin suggests a bar leaner with a bottle of some premium liquor. [2] Those FX coffee mugs from 2002 or whenever it was were great, I still use mine but I feel it's time for a change. Hint hint. [3] "Short": adjective. An arbitrary period of time in minutes counted on one hand.

1 0

Telstraclear datacentre offline?
by Joel van Velden 15 Dec '08

15 Dec '08

Hi Can anyone else confirm that the telstra clear north shore datacentre is offline? Last hop to our box or www.telstraclear.co.nz is: ge-9-0-927.u11.telstraclear.net Have obviously tried from more than one ISP :) -Joel

4 3

NZNOG09 Fellowships
by Jonny Martin 15 Dec '08

15 Dec '08

Hi All, NZNOG09 is being hosted by FX Networks at the Mount Richmond Hotel and Conference Centre in Mt. Wellington, Auckland from Wednesday 28 to Friday 30th January, 2009. Following on from the successful fellowship program offered last year there will once again be a small number of fellowship packages available. Fellowships are open to all - employed, unemployed, students, programmers. The aim of this is to provide assistance to those people that mightn't otherwise be able to come - but have a lot to offer to, or gain from, the NZNOG community. Fellowships will cover conference and tutorial registration fees, and up to three nights accommodation at the NZNOG venue. Travel assistance may be considered if applicants are able to provide solid justification for why it would be needed. Up to five fellowship packages are being made available. Applicants must: - Write a few paragraphs explaining why they need a fellowship to NZNOG'09 and what they hope to get out of it. - Their employer can't or won't cover them and they're having to cover costs personally or they're a student / unemployed. - Demonstrate a history of involvement in some aspect of the NZNOG community or an intent to become involved, and how attending NZNOG'09 will benefit them. - Actually attend the NZNOG sessions! Fellowship prospects will be helped greatly if applicants are presenting, or intend to present a conference paper, lightning talk, convene a BOF, or otherwise contribute to the conference. Submissions will be evaluated by the NZNOG 2008 organising committee. We need to be satisfied that there is a legitimate need for the fellowship. Email your submissions to talks(a)nznog.org - and while you are there, why not tell us about the talk/lightning talk/BOF you wish to provide... Closing date for applications Monday 15th December Successful applicants will be notified by Wednesday 17th December. Cheers, Jonny.

1 1

NZRR Route Registry Update
by NZRR Database Notifications 14 Dec '08

14 Dec '08

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: Route set advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 113.20.0.0/20^20-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 20081120 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus - 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, 115.187.128.0/17^17-29, 113.192.0.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, 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, 123.100.128.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.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, 114.31.192.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, 202.3.96.0/20^20-29, 202.4.224.0/20^20-29, 202.53.176.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.149.64.0/20^20-29, 210.48.160.0/20^20-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.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, 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.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.78.240.0/21^21-29, 202.146.208.0/21^21-29, 202.160.112.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 122.100.0.0/22^22-29, 124.108.96.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, 202.37.48.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.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.140.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.184.0/22^22-29, 203.185.228.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, 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.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.12.90.0/23^23-29, 202.36.204.0/23^23-29, 202.92.94.0/23^23-29, 202.124.106.0/23^23-29, 202.150.60.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.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.22.70.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.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.161.134.0/23^23-29, 203.161.136.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 203.185.226.0/23^23-29, 206.222.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, 114.111.128.0/24^24-29, 116.50.58.0/24^24-29, 122.100.15.0/24^24-29, 122.200.59.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, 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.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.41.194.0/24^24-29, 202.44.75.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, 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.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.124.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.95.0/24^24-29, 203.17.183.0/24^24-29, 203.18.94.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.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.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.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.32.82.0/24^24-29, 203.33.70.0/24^24-29, 203.33.113.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.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.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.230.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.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.166.89.0/24^24-29, 203.185.225.0/24^24-29, 203.190.217.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.56.153.0/24^24-29, 4.53.16.144/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: tech(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081215 source: NZRR ------------------------------------------------------------

1 0