- NZNOG - lists.nznog.org

Fwd: [itar-announce] End of Life Notice for ITAR
by Andy Linton 04 Nov '10

04 Nov '10

-------- Original Message -------- Subject: [itar-announce] End of Life Notice for ITAR Date: Thu, 4 Nov 2010 12:18:55 -0700 From: Kim Davies <kim.davies(a)icann.org> To: itar-announce(a)icann.org <itar-announce(a)icann.org> Dear colleagues, The Interim Trust Anchor Repository is now being retired from service. Starting today, no new listings will be accepted by the service. Later this month, existing listings will be removed; with the entire service turned off early next year. *** If you are using the ITAR service, please discontinue using it as soon *** *** as possible. We recommend you transition to using the signed DNS root *** *** zone. *** Since the beginning of 2009, ICANN has operated a service known as the Interim Trust Anchor Repository (ITAR). This allowed top-level domain operators who use DNSSEC to publish their trust anchor in absence of a signed DNS root zone. On 15 July 2010, the DNS root zone was signed, and in the following months TLD operators have transitioned to using it. With the last remaining TLDs transitioning to the signed root zone, the ITAR is no longer required. The service was a successful bottom-up collaboration with the Internet community. ICANN was asked to operate the service to help DNSSEC adoption during its initial phases. During its lifetime, the ITAR supported over a hundred listing requests for dozens of top-level domains that were early adopters of DNSSEC. The operational experience ICANN gained in operating ITAR also helped inform the roll-out of the signed DNS root zone. The expected date for existing listings to be removed is 18 November 2010, with the service fully retired in January 2011. These dates are subject to adjustment based on operational requirements or community feedback. With kindest regards, Kim Davies Manager, Root Zone Services ICANN _______________________________________________ itar-announce mailing list itar-announce(a)icann.org https://mm.icann.org/mailman/listinfo/itar-announce

1 0

Member and Stakeholder Survey 2010 - We need your feedback!
by Elly Tawhai 03 Nov '10

03 Nov '10

Hi NZNOG Community, We have just launched APNIC 2011 Stakeholder Survey, an important feedback mechanism that will be used to guide APNIC secretariat's operational plan in 2011-2012. Please note that you do not have to be an APNIC member to complete this survey. Just select 'No' in the first question: Are you an APNIC Account holder? There is a prize draw for an iPad if survey is completed by 9 November. Kind regards, Elly APNIC _______________________________________________________________________ Member and Stakeholder Survey 2010 - We need your feedback! _______________________________________________________________________ On behalf of the APNIC Executive Council, the Asia Pacific Network Information Centre (APNIC) is commissioning a Member and Stakeholder survey, to assess the Secretariat's performance during 2010. The survey is conducted every two years. The results of this survey will form the basis of the APNIC operational plan for 2011-2012. APNIC is a not-for-profit organization responsible for distributing and registering Internet resources, such as IP addresses, throughout the Asia Pacific region. You may have encountered APNIC in the region through our: - Training and liaison activities with local ISPs and governments - Participation in regional forums for Internet Governance - Media coverage on issues relevant to the Internet community such as IPv4 exhaustion and IPv6 deployment An independent consultant, Professor Ang Peng Hwa, Director of the Singapore Internet Research Center, will conduct the survey and analyse the findings using a completely neutral process guaranteeing the highest quality result. The survey is designed so that you only need to complete the sections that are relevant to your experience with APNIC. Early Birds who complete the survey before 24:00 (UTC +10) on 9 November 2010, will be entered to win an Apple iPad! Participation in the Stakeholder Survey is completely anonymous. The survey is open from 2 November 2010 - 21 November 2010 until 24:00 (UTC +10). For more information on how you can participate, visit: http://www.apnic.net/survey _______________________________________________________________________ APNIC Secretariat secretariat(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 _______________________________________________________________________ * Sent by email to save paper. Print only if necessary.

1 0

Root Zone DNSSEC KSK Ceremony 3 Completed
by Joe Abley 02 Nov '10

02 Nov '10

KSK CEREMONY 3 The third KSK ceremony for the root zone took place in Culpeper, VA, USA on Monday 2010-11-01. The Ceremony Administrator was Mehmet Akcin. The ceremony was completed successfully. Video from Ceremony 3 was recorded for audit purposes. Video and associated audit materials will be published in 1 to 2 weeks, and will be available as usual by following the "KSK Ceremony Materials" link at <https://www.iana.org/dnssec/>. Ceremony 3 included processing of a Key Signing Request (KSR) generated by VeriSign, and the resulting Signed Key Response (SKR) contained signatures for Q1 2011, for use in the root zone between 2011-01-01 and 2011-02-28. CONTACT INFORMATION We'd like to hear from you. If you have feedback for us, please send it to rootsign(a)icann.org.

1 0

Filtering Previously Unallocated Addresses
by Elly Tawhai 01 Nov '10

01 Nov '10

Hi NZNOG Community, I realize that Andy Linton sent this to the list a couple of weeks ago. However please note that 36/8 and 42/8 have now been added as newly allocated address blocks managed, by APNIC. Kind regards, Elly APNIC _______________________________________________________________________ Filtering Previously Unallocated Addresses _______________________________________________________________________ APNIC recognizes that as the IANA pool of unallocated IPv4 addresses nears exhaustion, there may be increasing community concern about the quality of the new address blocks made available for distribution. It is important that you ensure your router Access Control Lists (ACLs) are updated so addresses are not mistakenly filtered through your routers. It may also be time to consider whether you should stop any form of BOGON filtering. This is especially important for newly allocated address blocks: * 1.0.0.0/8 * 14.0.0.0/8 * 27.0.0.0/8 * 36.0.0.0/8 * 42.0.0.0/8 * 49.0.0.0/8 * 101.0.0.0/8 * 223.0.0.0/8 Keep informed about IANA allocations at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml For those with recently allocated address space here are several tips to check whether your IP Addresses are filtered: * Your own firewall might be blocking the new IP addresses by default, if you set up your servers to block bogon IP ranges. To avoid blocking potential new customers, consider whether you should stop any form of BOGON filtering. * Run a traceroute to see if the new IP is consistently blocked along the same network path. It is advisable also, to test forward and reverse paths. Use of technology like the Routing Information Service (RIS) is highly recommended to assist in identifying routing conditions for prefixes under test. http://www.ripe.net/projects/ris/index.html * Do a search on your IP address and contact those organizations that appear to be blocking you. You may be blocked due to activity of one of your customers. http://whatismyipaddress.com/blacklist-check * Use a looking glass service as part of the diagnostic tool, set to detect network filters. http://www.ris.ripe.net/cgi-bin/lg/index.cgi Ongoing testing --------------- As part of our service commitment to our Members and the wider community, APNIC is working hard to evaluate the usability of address space allocated to APNIC before it is distributed. For further information on Resource Quality Assurance and the testing results, visit: http://www.apnic.net/rqa For further assistance, contact: helpdesk(a)apnic.net ____________________________________________________________________ APNIC Secretariatsecretariat(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, QLDhttp://www.apnic.net _______________________________________________________________________ * Sent by email to save paper. Print only if necessary.

1 0

New Zealand Network Operators' Group
by Donald Neal 31 Oct '10

31 Oct '10

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 is registered as a charitable entity under the Charities Act. The 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 four trustees, the NZNOG does not have a formal membership. Conference NZNOG holds New Zealand's only annual technical networking conference. The next conference is scheduled for the week beginning 24 January 2011 in Wellington, to be hosted by Vodafone. The call for participation can be read at http://list.waikato.ac.nz/pipermail/nznog/2010-November/017047.html . 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 1100 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 | I don't approve of gambling. I'll just | spend my time in the bar. High Performance Computing | - NZNOG 2010 attendee The University of Waikato |

1 0

NZNOG 2011 - Call for Participation and Papers
by Neil Fenemor 31 Oct '10

31 Oct '10

[Apologies for duplicates...] NZNOG 2011 - Call for Participation and Papers The next conference of the New Zealand Network Operators' Group is to be held in Wellington, New Zealand between 26 January and 28 January 2011. Our host is Vodafone New Zealand. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of network services, with particular emphasis on New Zealand. The conference is low priced and has a strong technical focus with the aim and history of getting a strong turnout of technical personal from New Zealand Internet orientated companies. Conference Overview ------------------- NZNOG 2011 will consist of up to three days of workshops and tutorials followed by two days of conference presentations. There will also be opportunity for more informal and small lightening talks. These are typically around five minutes long and are organised closer to the actual conference. Important Dates --------------- Call for Papers opens: 1 November 2010 Deadline for speaker submissions: 1 December 2010 Responses to speaker submissions: 7 December 2010 Draft program published: 15 December 2010 Final program published: 15 January 2011 NZNOG 2011 Conference: 26 - 29 January 2011 SIG / Miniconf / Tutorials / Workshops -------------------------------------- In previous years we have had a single day of workshops and tutorials, this year however we are looking at having up to three days of workshops and tutorials, if we can get the submissions. Examples of past activities workshops include 'MPLS and fixed access networks for beginners', 'Mikrotik RouterOS Training', 'APNIC Internet Resource Management Essentials', and a System Administrators mini-conference which included talks on 'Using Debian packages for system administration' and '42 hosts in 1U: Using virtual machines'. Conference Presentations ------------------------ The main conference program for 2011 will be made up of two days with a single stream where possible. Presentations don't need to fit any particular fixed length and can be from 30 minutes to 3 hours in length. NZNOG conferences have traditionally spanned the entire operational spectrum, and then some. Proposals for conference presentations are invited for virtually any topic with a degree of relevance to the NZNOG community. Past years' talks have included the following: - Internet exchange operations - Global anycast networks and the building thereof - Peering, peering, and peering - Network security - 10GB ethernet operations - How to build a router in these tough and difficult economic times - Current Internet research in NZ - Wireless networking - QOS over carrier networks - Content distribution networks and media streaming - Open Source VoIP Platform in Carrier Environments - Lawful Interception - Designing networks for High Availability - ISP scenarios for IPv6 deployment - Monkeying around on the APE Some ideas for this year also include the following: - IPv6, been there done that - DNS Security - Routing Security - Review of 2010 - IPSec - Internet Filtering - How Cloud Computing has impacted Network Design If you are interested in submitting a talk please fill out the questions at then end of this document and submit them to http://submission.nznog.org Alternatively, you can and email them to talks(a)nznog.org Submission Guidelines --------------------- When considering a presentation or SIG, remember that the NZNOG audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the SIGs and to address issues relevant to the day-to-day operations of ISPs and network operators in the conference sessions. The inclusion of a title, bio, topic, abstract, and slides with proposals is not compulsory but each will help us determine the quality of your proposal and increase the likelihood it will be accepted. Final slides are to be provided by 15 January 2011. Note: While the majority of speaking slots will be submitted by 15 December 2010, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. The NZNOG conference is a TECHNICAL conference so marketing and commercial content is NOT allowed within the program. The program committee is charged with maintaining the technical standard of NZNOG conferences, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and unforgiving, and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. Funding and Support ------------------- NZNOG conferences are community run and funded events that try to keep the cost to attendees as low as possible so generally we are unable to pay the travel costs of speakers. There is a limited amount of funding available to international speakers. Conference presenters will not have to pay any registration fee for the day they are presenting. Discounts for SIG and lightning talk presenters may be available but are not automatic. Lightning talks --------------- Lightning talks are short talks/presentations that last no more than 10 minutes. This is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to go to a full talk. At NZNOG 2011 it is planned that there will be at least one hour long lightning talk session. Sponsors -------- There are opportunities remaining for organisations to sponsor various aspects of the NZNOG meeting. Please contact sponsorship(a)nznog.org for more information Contact ------- General Enquiries * info(a)nznog.org Talks and Papers * http://submission.nznog.org * talks(a)nznog.org Talk Proposals -------------- Please submit all talk proposals (including lightning talks) via http://submission.nznog.org or email talks(a)nznog.org along with the requested information. Questions regarding talks can be sent to the same address. Sponsorship may be available for a limited number of overseas speakers to attend the conference, please indicate if you require assistance with travel and/or accommodation. Author's Full Name: Author's Email Address: Author's affiliation: Author's short biography: Title of Talk: Abstract: Length of talk: Please provide details if a version of this talk has previously been given: Will travel and accommodation assistance be required:

2 1

APRICOT 2011 Call For Papers
by Jonny Martin 31 Oct '10

31 Oct '10

[Obligatory apology for duplicates...] Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) 15 - 25 February 2011, Hong Kong http://www.apricot2011.net CALL FOR PAPERS =============== The APRICOT 2011 Programme Committee is now seeking contributions for Presentations and Tutorials for APRICOT 2011. We are looking for people and proposals that would: - Offer a technical tutorial on an appropriate topic; and/or - Participate in the technical conference sessions as a speaker; and/or - Convene and chair a Birds of a Feather (BOF) session. Please submit proposals on-line at http://www.apricot2011.net/call-for-papers/submission CONFERENCE MILESTONES --------------------- Call for Papers Opens: 29 October 2010 First Deadline for Submissions: 29 November 2010 First Draft Programme Published: 6 December 2010 Final Deadline for Submissions: 4 February 2011 Final Programme Published: 11 February 2011 Final Slides Received: 19 February 2011 PROGRAM MATERIAL ---------------- The APRICOT Programme is organised in three parts, including workshops, tutorials and the conference. The APNIC Policy SIG and Annual Members Meeting will be held during the APRICOT conference. Topics for tutorials and conference would include amongst others relevant to Internet Operations and Technologies: - IPv4 / IPv6 Routing and operations - IPv4 address runout / IPv6 deployment and transition technologies - Backbone operations - ISP and Carrier services - Network security issues (NSP-SEC, DDoS Anti-Spam, Anti-Malware) - Peering / IXPs - DNS / DNSSEC - Internet policy (Security, Regulation, Content Management, Addressing, etc) - Access and Transport Technologies, including broadband deployment, Cable/DSL, wireless, WiMax, metro ethernet, fiber network, MPLS - Content & Service Delivery (Multicast, Voice, Video, "telepresence", Gaming) CFP SUBMISSION -------------- Draft slides for both tutorials and conference sessions MUST be provided with CFP submissions otherwise the Programme Committee will be unable to review the submission. For work in progress, the most current information available at time of submission is acceptable. Final slides are to be provided by the specified deadline for publication on the APRICOT website. While the majority of speaking slots will be filled by the first submission deadline, a limited number of slots may be available up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Please submit on-line at http://www.apricot2011.net/call-for-papers/submission Any questions or concerns should be addressed to the Programme Committee by e-mail. We look forward to receiving your presentation proposals. Jonny Martin & Mark Tinka Co-Chairs, APRICOT Programme Committee program(a)apricot.net

1 0

Root Zone DNSSEC KSK Ceremony 3
by Joe Abley 29 Oct '10

29 Oct '10

KSK CEREMONY 3 The third KSK ceremony for the root zone will take place in Culpeper, VA, USA on Monday 2010-11-01. The ceremony is scheduled to begin at 1300 local time (1700 UTC) and is expected to end by 1900 local time (2300 UTC). Video from Ceremony 3 will be recorded for audit purposes. Video and associated audit materials will be published 1 to 2 weeks after the ceremony, and will be available as usual by following the "KSK Ceremony Materials" link at <https://www.iana.org/dnssec/>. ICANN will operate a separate camera whose video will not be retained for audit purposes, but which will instead be streamed live in order to provide remote observers an opportunity to watch the ceremony. The live stream will be provided on a best-effort basis. The live video stream will be available at <http://dns.icann.org/ksk/stream/>. Ceremony 3 will include processing of a Key Signing Request (KSR) generated by VeriSign, and the resulting Signed Key Response (SKR) will contain signatures for Q1 2011, for use in the root zone between 2011-01-01 and 2011-02-28. CONTACT INFORMATION We'd like to hear from you. If you have feedback for us, please send it to rootsign(a)icann.org.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Oct '10

28 Oct '10

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:AS45831 descr: advertised to AS9439 by Datalight Limited - AS45831 members: 180.189.192.0/19^19-29, 113.197.96.0/22^22-29, 203.114.148.128/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: davey(a)opto.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100721 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS45831 descr: advertised to AS9439 by Datalight Limited - AS45831 members: 180.189.192.0/19^19-29, 120.136.0.0/21^21-29, 113.197.96.0/22^22-29, 203.114.148.128/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: davey(a)opto.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20101029 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Oct '10

28 Oct '10

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 Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 118.148.0.0/15^15-29, 27.252.0.0/16^16-29, 58.7.0.0/16^16-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 124.148.0.0/16^16-29, 124.169.0.0/16^16-29, 124.170.0.0/16^16-29, 131.203.0.0/16^16-29, 157.128.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, 182.154.0.0/16^16-29, 203.59.0.0/16^16-29, 220.253.0.0/16^16-29, 14.137.0.0/17^17-29, 113.203.0.0/17^17-29, 114.198.0.0/17^17-29, 124.149.0.0/17^17-29, 124.150.0.0/17^17-29, 124.168.0.0/17^17-29, 180.181.0.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 220.235.0.0/17^17-29, 14.137.128.0/18^18-29, 58.6.192.0/18^18-29, 114.129.128.0/18^18-29, 124.149.192.0/18^18-29, 124.168.128.0/18^18-29, 124.171.0.0/18^18-29, 125.209.128.0/18^18-29, 125.253.0.0/18^18-29, 180.181.128.0/18^18-29, 180.200.128.0/18^18-29, 182.160.128.0/18^18-29, 202.72.128.0/18^18-29, 202.173.128.0/18^18-29, 203.113.192.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, 203.206.0.0/18^18-29, 203.208.64.0/18^18-29, 210.15.192.0/18^18-29, 210.84.0.0/18^18-29, 210.185.0.0/18^18-29, 220.235.128.0/18^18-29, 14.137.192.0/19^19-29, 58.6.0.0/19^19-29, 58.6.64.0/19^19-29, 58.6.160.0/19^19-29, 61.245.128.0/19^19-29, 111.67.0.0/19^19-29, 112.141.0.0/19^19-29, 112.141.64.0/19^19-29, 112.141.128.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 118.127.64.0/19^19-29, 119.15.0.0/19^19-29, 119.252.0.0/19^19-29, 120.88.64.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 124.149.160.0/19^19-29, 124.157.64.0/19^19-29, 124.171.192.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.200.192.0/19^19-29, 180.214.64.0/19^19-29, 180.222.0.0/19^19-29, 182.48.128.0/19^19-29, 202.45.96.0/19^19-29, 202.59.32.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, 202.181.0.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.158.32.0/19^19-29, 203.173.192.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.96.0/19^19-29, 203.217.64.0/19^19-29, 210.54.160.0/19^19-29, 220.235.192.0/19^19-29, 223.27.0.0/19^19-29, 58.6.32.0/20^20-29, 58.6.112.0/20^20-29, 58.6.144.0/20^20-29, 58.84.208.0/20^20-29, 58.84.224.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.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.199.208.0/20^20-29, 117.55.224.0/20^20-29, 118.127.16.0/20^20-29, 119.10.128.0/20^20-29, 119.15.96.0/20^20-29, 119.47.112.0/20^20-29, 119.63.208.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 120.138.16.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 122.252.0.0/20^20-29, 124.149.144.0/20^20-29, 124.155.224.0/20^20-29, 124.168.192.0/20^20-29, 124.168.240.0/20^20-29, 124.171.176.0/20^20-29, 124.171.240.0/20^20-29, 124.248.128.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 175.107.160.0/20^20-29, 180.235.192.0/20^20-29, 202.3.192.0/20^20-29, 202.22.160.0/20^20-29, 202.43.224.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.80.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.86.96.0/20^20-29, 202.87.16.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.174.160.0/20^20-29, 203.2.80.0/20^20-29, 203.17.96.0/20^20-29, 203.82.96.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, 203.173.0.0/20^20-29, 203.173.224.0/20^20-29, 203.206.160.0/20^20-29, 203.206.192.0/20^20-29, 203.214.32.0/20^20-29, 203.214.80.0/20^20-29, 203.214.144.0/20^20-29, 203.217.32.0/20^20-29, 210.14.96.0/20^20-29, 210.56.32.0/20^20-29, 220.235.240.0/20^20-29, 223.165.64.0/20^20-29, 27.121.64.0/21^21-29, 58.6.56.0/21^21-29, 110.44.24.0/21^21-29, 111.125.160.0/21^21-29, 112.109.80.0/21^21-29, 112.140.176.0/21^21-29, 112.141.104.0/21^21-29, 112.141.232.0/21^21-29, 113.192.56.0/21^21-29, 113.212.168.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.111.144.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.90.72.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.8.0/21^21-29, 119.63.200.0/21^21-29, 119.82.144.0/21^21-29, 120.89.80.0/21^21-29, 121.0.0.0/21^21-29, 121.79.224.0/21^21-29, 121.127.200.0/21^21-29, 122.49.200.0/21^21-29, 122.201.72.0/21^21-29, 122.201.104.0/21^21-29, 124.168.216.0/21^21-29, 124.168.232.0/21^21-29, 124.171.232.0/21^21-29, 175.45.128.0/21^21-29, 175.107.176.0/21^21-29, 175.176.200.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 180.235.208.0/21^21-29, 182.23.176.0/21^21-29, 182.23.192.0/21^21-29, 202.4.232.0/21^21-29, 202.7.144.0/21^21-29, 202.12.248.0/21^21-29, 202.20.0.0/21^21-29, 202.36.16.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.49.0.0/21^21-29, 202.49.128.0/21^21-29, 202.72.32.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.200.0/21^21-29, 202.169.208.0/21^21-29, 203.14.40.0/21^21-29, 203.14.168.0/21^21-29, 203.33.160.0/21^21-29, 203.98.88.0/21^21-29, 203.149.80.0/21^21-29, 203.173.40.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.188.216.0/21^21-29, 203.190.208.0/21^21-29, 203.206.64.0/21^21-29, 203.206.176.0/21^21-29, 203.212.16.0/21^21-29, 203.214.64.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 203.217.48.0/21^21-29, 210.9.136.0/21^21-29, 220.235.232.0/21^21-29, 27.96.64.0/22^22-29, 27.100.24.0/22^22-29, 27.106.200.0/22^22-29, 27.112.96.0/22^22-29, 58.6.108.0/22^22-29, 58.179.124.0/22^22-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.76.132.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.125.168.0/22^22-29, 111.235.140.0/22^22-29, 112.141.112.0/22^22-29, 112.141.240.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 113.197.96.0/22^22-29, 115.69.28.0/22^22-29, 115.69.60.0/22^22-29, 115.178.28.0/22^22-29, 116.90.132.0/22^22-29, 118.127.4.0/22^22-29, 118.127.32.0/22^22-29, 118.127.52.0/22^22-29, 118.127.56.0/22^22-29, 119.161.84.0/22^22-29, 119.252.176.0/22^22-29, 120.136.0.0/22^22-29, 121.127.192.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, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 124.171.224.0/22^22-29, 125.254.48.0/22^22-29, 125.254.60.0/22^22-29, 175.41.40.0/22^22-29, 175.106.4.0/22^22-29, 175.107.184.0/22^22-29, 175.111.100.0/22^22-29, 180.148.24.0/22^22-29, 180.148.176.0/22^22-29, 180.189.152.0/22^22-29, 180.210.208.0/22^22-29, 180.222.64.0/22^22-29, 180.235.216.0/22^22-29, 182.50.160.0/22^22-29, 182.237.4.0/22^22-29, 192.189.208.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.7.152.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.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.45.152.0/22^22-29, 202.69.132.0/22^22-29, 202.71.164.0/22^22-29, 202.71.172.0/22^22-29, 202.89.4.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 202.129.244.0/22^22-29, 202.130.44.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.161.0.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.216.0/22^22-29, 202.177.40.0/22^22-29, 202.177.212.0/22^22-29, 202.177.220.0/22^22-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20101028 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 118.148.0.0/15^15-29, 27.252.0.0/16^16-29, 58.7.0.0/16^16-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 124.148.0.0/16^16-29, 124.169.0.0/16^16-29, 124.170.0.0/16^16-29, 131.203.0.0/16^16-29, 157.128.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, 182.154.0.0/16^16-29, 203.59.0.0/16^16-29, 220.253.0.0/16^16-29, 14.137.0.0/17^17-29, 113.203.0.0/17^17-29, 114.198.0.0/17^17-29, 124.149.0.0/17^17-29, 124.150.0.0/17^17-29, 124.168.0.0/17^17-29, 180.181.0.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 220.235.0.0/17^17-29, 14.137.128.0/18^18-29, 58.6.192.0/18^18-29, 114.129.128.0/18^18-29, 124.149.192.0/18^18-29, 124.168.128.0/18^18-29, 124.171.0.0/18^18-29, 125.209.128.0/18^18-29, 125.253.0.0/18^18-29, 180.181.128.0/18^18-29, 180.200.128.0/18^18-29, 182.160.128.0/18^18-29, 202.72.128.0/18^18-29, 202.173.128.0/18^18-29, 203.113.192.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, 203.206.0.0/18^18-29, 203.208.64.0/18^18-29, 210.15.192.0/18^18-29, 210.84.0.0/18^18-29, 210.185.0.0/18^18-29, 220.235.128.0/18^18-29, 14.137.192.0/19^19-29, 58.6.0.0/19^19-29, 58.6.64.0/19^19-29, 58.6.160.0/19^19-29, 61.245.128.0/19^19-29, 111.67.0.0/19^19-29, 112.141.0.0/19^19-29, 112.141.64.0/19^19-29, 112.141.128.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 118.127.64.0/19^19-29, 119.15.0.0/19^19-29, 119.252.0.0/19^19-29, 120.88.64.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 124.149.160.0/19^19-29, 124.157.64.0/19^19-29, 124.171.192.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.200.192.0/19^19-29, 180.214.64.0/19^19-29, 180.222.0.0/19^19-29, 182.48.128.0/19^19-29, 202.45.96.0/19^19-29, 202.59.32.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, 202.181.0.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.158.32.0/19^19-29, 203.173.192.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.96.0/19^19-29, 203.217.64.0/19^19-29, 210.54.160.0/19^19-29, 220.235.192.0/19^19-29, 223.27.0.0/19^19-29, 58.6.32.0/20^20-29, 58.6.112.0/20^20-29, 58.6.144.0/20^20-29, 58.84.208.0/20^20-29, 58.84.224.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.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.199.208.0/20^20-29, 117.55.224.0/20^20-29, 118.127.16.0/20^20-29, 119.10.128.0/20^20-29, 119.15.96.0/20^20-29, 119.47.112.0/20^20-29, 119.63.208.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 120.138.16.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 122.252.0.0/20^20-29, 124.149.144.0/20^20-29, 124.155.224.0/20^20-29, 124.168.192.0/20^20-29, 124.168.240.0/20^20-29, 124.171.176.0/20^20-29, 124.171.240.0/20^20-29, 124.248.128.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 175.107.160.0/20^20-29, 180.235.192.0/20^20-29, 202.3.192.0/20^20-29, 202.22.160.0/20^20-29, 202.43.224.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.80.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.86.96.0/20^20-29, 202.87.16.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.174.160.0/20^20-29, 203.2.80.0/20^20-29, 203.17.96.0/20^20-29, 203.82.96.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, 203.173.0.0/20^20-29, 203.173.224.0/20^20-29, 203.206.160.0/20^20-29, 203.206.192.0/20^20-29, 203.214.32.0/20^20-29, 203.214.80.0/20^20-29, 203.214.144.0/20^20-29, 203.217.32.0/20^20-29, 210.14.96.0/20^20-29, 210.56.32.0/20^20-29, 220.235.240.0/20^20-29, 223.165.64.0/20^20-29, 27.121.64.0/21^21-29, 58.6.56.0/21^21-29, 110.44.24.0/21^21-29, 111.125.160.0/21^21-29, 112.109.80.0/21^21-29, 112.140.176.0/21^21-29, 112.141.104.0/21^21-29, 112.141.232.0/21^21-29, 113.192.56.0/21^21-29, 113.212.168.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.111.144.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.90.72.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.8.0/21^21-29, 119.63.200.0/21^21-29, 119.82.144.0/21^21-29, 120.89.80.0/21^21-29, 121.0.0.0/21^21-29, 121.79.224.0/21^21-29, 121.127.200.0/21^21-29, 122.49.200.0/21^21-29, 122.201.72.0/21^21-29, 122.201.104.0/21^21-29, 124.168.216.0/21^21-29, 124.168.232.0/21^21-29, 124.171.232.0/21^21-29, 175.45.128.0/21^21-29, 175.107.176.0/21^21-29, 175.176.200.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 180.235.208.0/21^21-29, 182.23.176.0/21^21-29, 182.23.192.0/21^21-29, 202.4.232.0/21^21-29, 202.7.144.0/21^21-29, 202.12.248.0/21^21-29, 202.20.0.0/21^21-29, 202.36.16.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.49.0.0/21^21-29, 202.49.128.0/21^21-29, 202.72.32.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.200.0/21^21-29, 202.169.208.0/21^21-29, 203.14.40.0/21^21-29, 203.14.168.0/21^21-29, 203.33.160.0/21^21-29, 203.98.88.0/21^21-29, 203.149.80.0/21^21-29, 203.173.40.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.188.216.0/21^21-29, 203.190.208.0/21^21-29, 203.206.64.0/21^21-29, 203.206.176.0/21^21-29, 203.212.16.0/21^21-29, 203.214.64.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 203.217.48.0/21^21-29, 210.9.136.0/21^21-29, 220.235.232.0/21^21-29, 27.96.64.0/22^22-29, 27.100.24.0/22^22-29, 27.106.200.0/22^22-29, 27.112.96.0/22^22-29, 58.6.108.0/22^22-29, 58.179.124.0/22^22-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.76.132.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.125.168.0/22^22-29, 111.235.140.0/22^22-29, 112.141.112.0/22^22-29, 112.141.240.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 113.197.96.0/22^22-29, 115.69.28.0/22^22-29, 115.69.60.0/22^22-29, 115.178.28.0/22^22-29, 116.90.132.0/22^22-29, 118.127.4.0/22^22-29, 118.127.32.0/22^22-29, 118.127.52.0/22^22-29, 118.127.56.0/22^22-29, 119.161.84.0/22^22-29, 119.252.176.0/22^22-29, 120.136.0.0/22^22-29, 121.127.192.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, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 124.171.224.0/22^22-29, 125.254.48.0/22^22-29, 125.254.60.0/22^22-29, 175.41.40.0/22^22-29, 175.106.4.0/22^22-29, 175.107.184.0/22^22-29, 175.111.100.0/22^22-29, 180.148.24.0/22^22-29, 180.148.176.0/22^22-29, 180.189.152.0/22^22-29, 180.210.208.0/22^22-29, 180.222.64.0/22^22-29, 180.235.216.0/22^22-29, 182.50.160.0/22^22-29, 182.237.4.0/22^22-29, 192.189.208.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.7.152.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.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.45.152.0/22^22-29, 202.69.132.0/22^22-29, 202.71.164.0/22^22-29, 202.71.172.0/22^22-29, 202.89.4.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 202.129.244.0/22^22-29, 202.130.44.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.161.0.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.216.0/22^22-29, 202.177.40.0/22^22-29, 202.177.212.0/22^22-29, 202.177.220.0/22^22-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20101029 source: NZRR ------------------------------------------------------------

1 0