- NZNOG - lists.nznog.org

Charging for IPv6
by Philip D'Ath 24 Aug '08

24 Aug '08

Initially those transit providers and ISPs that do offer IPv6 transit will be able to charge for this service as it will be a premium value add. However I can't see this business model being able to last for more than 6 years (through to 2012), and possibly only three years. After this point in time I expect IPv6 deployment will be standard, and will no longer be a premium service offering - it will be the standard offering, like IPv4 is today. Once IPv4 has become exhausted and you can't actually give a customer an IPv4 address then you definitely wont be able to charge more for IPv6 - otherwise the customer will walk. So do providers start implementing slowly now, and recoup some of their investment while they can, or wait till they are forced to do the upgrades and are not able to recoup any of their "new" investment. Rhetorical question.

23 40

China Netcom gets a case DNS cache poisoning
by Juha Saarinen 21 Aug '08

21 Aug '08

http://computerworld.co.nz/news.nsf/netw/96ECA39DC47E6603CC2574AC006C4506 Thought the article might be of interest. -- Juha www.techsploder.com

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Aug '08

20 Aug '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: AS9439:RS-ROUTES:AS9245 descr: advertised to AS9439 by COMPASS NZ - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 120.136.0.0/21^21-29, 123.108.144.0/21^21-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 202.174.6.0/23^23-29, 116.90.131.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080702 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9245 descr: advertised to AS9439 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 120.136.0.0/21^21-29, 123.108.144.0/21^21-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 202.6.116.0/23^23-29, 202.174.6.0/23^23-29, 116.90.131.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080821 source: NZRR ------------------------------------------------------------

1 0

History of the Internet in New Zealand
by Roger Williams 19 Aug '08

19 Aug '08

In July last year InternetNZ advised this list: >InternetNZ has commissioned Keith Newman to write a >history of the Internet in New Zealand. The book will >go to the publishers later this year. I happened to wonder what had happened with this. Finding my way to http://www.internetnz.net.nz/projects/history/ I read ... "5pm, 21 August - Book launch at the National Library" That's tomorrow evening. -- Roger Williams, GNS Science, New Zealand : www.gns.cri.nz : xyzzy

1 0

uTorrent, IPv6
by Nathan Ward 18 Aug '08

18 Aug '08

(Also posted to NANOG. Apologies if you're sensitive about that sort of thing.) Sit up and pay attention, even if you don't now run IPv6, or even if you don't ever intend to run IPv6. Your off-net bandwidth is going to increase, unless you put some relays in. As a friend of mine just said to me: "Welcome to your v6-enabled transit network, whether you like it or not ;-)". uTorrent 1.8 is out, as of Aug 9. uTorrent actively enables IPv6 on XP SP2 and Vista machines in the install process (by default, it can be turned off). IPv6 is turned on, on lots of PCs. uTorrent does DHT, so that uTorrent users will talk to eachother to exchange peers - IPv6 does not require tracker support. uTorrent (as far as I understand) knows how to set IPV6_PROTECTION_LEVEL appropriately on sockets, so that Teredo is actually used. What does this mean? It means that many uTorrent end users will have Teredo addresses, and many will have 6to4 addresses. As we roll out IPv6 globally, more and more uTorrent users will have non-tunnelled IPv6 addresses. uTorrent users move **LOTS** of data. This means relay load. There are very few 6to4 relays around the world. There are fewer Teredo relays. If you run a network today and do not have 6to4 and Teredo relays, traffic between a 6to4 end user and a Teredo end user will go off-net. That costs you money. So, if you run a network today, deploy 6to4 and Teredo relays, regardless of whether you have customer facing IPv6 or not. If you serve IPv6 content, you are already running Teredo and 6to4 relays, so that Windows Vista users get near to IPv4-speed access to your IPv6 content, right? Right... Azureus does IPv6 now, but does not turn on IPv6, and does not set the IPV6_PROTECTION_LEVEL (as far as I understand), so Teredo is not used. Windows uses 6to4 if you have a non-RFC1918 address, and it uses Teredo if you do not (typically, this means you are behind NAT). With the huge amount of end users behind NAT, this means that uTorrent will have a much wider effect than Azureus has had. Running a relay *does not* mean that people outside your network can use it. - Who uses your 6to4 relay is controlled by how far you advertise the well known IPv4 and IPv6 prefixes. - Your Teredo relay is used only by Teredo clients trying to get to your non-Teredo connected users (ie your 6to4 or natively connected users). 6to4 relays can be Cisco boxes, Juniper NetScreen, FreeBSD, Linux, etc. OpenBSD does not have 6to4 support. Teredo relays can be Windows boxes, or Linux/FreeBSD/etc. boxes running `Miredo'. I have pre-built FreeBSD images that run both 6to4 and Teredo relays, and can talk BGP to your network. They are about 30MB, so will run on a compact flash card, and will happily run on anything from a 133Mhz 468 (ie. Soekris net4501) through to whatever top of the line server you have. They can also optionally do this "Tui" thing, which uses 6to4 and BGP to build direct IPv6 over IPv4 tunnels to everyone else with one of these boxes, without you having to configure each tunnel manually - I have some central route-servers. Optional, experimental, YMMV, etc. Thankfully, both Teredo and 6to4 use anycast for relay discovery, so if you have load problems you can deploy more of these for the cost of a server. As per usual, I'm giving it away free, see the following URL, or contact me off list: http://www.braintrust.co.nz/tui/ If you don't care about the "Tui" stuff, ignore those parts of the document, the rest will work just fine. ps. I'm looking at packet dumps of things right now, captured from torrent clients from the last wee while. I'll be rambling about this and pointing at pretty graphs in about a week at APNIC26. -- Nathan Ward

2 1

IPv6 Technical Workshops - PCH / Cisco - REMINDER
by Keith Davidson 18 Aug '08

18 Aug '08

All, I know I have already posted this message to the NOG list, but given there are still a few vacancies in both Auckland and Wellington, thought that I could again intrude with a reminder for folks who haven't yet responded... InternetNZ, in conjunction with REANNZ, Cisco, Packet Clearing House, NZRS, auDA and FX Networks, is offering IPv6 technical workshops in Christchurch and Auckland. This follows on from having already run this workshop in Wellington in August last year. The first 5 day programme will run in Christchurch from Saturday 30 August to Wednesday 3 September, and the second in Auckland from Monday 8 September to Friday 12 September. Attendence on each course is limited to 28 participants. Registration is on a first come, first served basis. Please see the attached document for details. More details are available at http://blog.internetnz.net.nz/wp-content/uploads/2008/07/2008-augsep-ipv6-w… To register email richard at internetnz.net.nz To keep this message list-compliant, please note InternetNZ will possibly provide beer to workshop participants. Cheers Keith Davidson Executive Director - InternetNZ

3 3

Getting your websites ready for Internet Explorer 8 - Come to our free Roadshow!
by Nick MacKechnie 13 Aug '08

13 Aug '08

HI All, FYI - This may be useful to you and your customers - feel free to pass this information on and participate where appropriate. Many thanks, Nick. Nick MacKechnie | Senior Technical Account Manager | Microsoft New Zealand Level 3, State Building, 88 Division Street, PO Box 8953, Riccarton, Christchurch 8041 p +64 3 961 7246 | m +64 21 999 010 | f +64 3 355 5527 | e nick.mackechnie(a)microsoft.com <mailto:nick.mackechnie(a)microsoft.com> Microsoft Premier Online <https://premier.microsoft.com/> Security Central <http://www.microsoft.com/security/> New Zealand Events <http://www.microsoft.com/nz/events/> New Zealand Press Centre <http://www.microsoft.com/nz/presscentre/> Technet/MSDN Flash <https://profile.microsoft.com/RegSysProfileCenter/SubCntDefault.aspx?lc id=5129> Services Catalogue <http://download.microsoft.com/documents/australia/services/mssrvcat_cur rent_lowres.pdf> OpenXML <http://www.microsoft.com/downloads/details.aspx?familyid=941b3470-3ae9- 4aee-8f43-c6bb74cd1466&displaylang=en> Blog <http://blogs.msdn.com/nickmac> This email is intended solely for the use of the addressee and may contain information that is confidential or subject to legal professional privilege. If you receive this email in error please immediately notify the sender and delete the email. If you prefer not to receive these types of communications from the sender, please forward this email to uptodate(a)microsoft.com <mailto:uptodate(a)microsoft.com> with "unsubscribe" in the subject line. To learn how to manage your contact preferences for other parts of Microsoft, please read our privacy statement <http://privacy.microsoft.com/en-nz/default.aspx> . From: Nick MacKechnie Sent: Wednesday, 13 August 2008 5:06 p.m. Subject: Getting your websites ready for Internet Explorer 8 - Come to our free Roadshow! Importance: High Hi All, Internet Explorer 8 takes the web experience beyond the page and introduces a new way to seamlessly experience the best of the web whether you are a web developer writing to standards or an end-user discovering a new online service integrated into the browser. We've also taken steps to deliver the fastest version of Internet Explorer available, making it easy to launch quickly, find what you want efficiently, and navigate seamlessly. Consistent with our efforts to promote further interoperability across the Web, Microsoft will be releasing Internet Explorer 8 to render content in its most standards-compliant way by default. Giving top priority to Web standards interoperability allows us to help web developers and designers drive toward the ideal of "write once, run anywhere", freeing up more time to innovate rather than modify content for different browsers. This commitment also addresses several development and design pain points from previous Internet Explorer releases. However, browsing with this default setting may cause content written for previous versions of Internet Explorer to display differently than intended. This creates a call to action for site owners to ensure their content will continue to display seamlessly in Internet Explorer 8. As such, we have provided a meta-tag usable on a per-page or per-site level to maintain compatibility for sites designed for Internet Explorer 7. Adding this tag instructs Internet Explorer 8 to render content like Internet Explorer 7, without requiring any additional changes. We are encouraging site administrators to get their sites ready now for broad adoption of Internet Explorer 8, as there will be a beta release in the third quarter of this year targeted for all consumers. Internet Explorer 8 Roadshow Come and have an overview of the new features and capabilities of Internet Explorer 8 straight from a senior member of the US based Internet Explorer team. Jefferson Fletcher is a Senior Product Manager working on Internet Explorer. Since joining Microsoft in 1996, Jefferson has spent the bulk of his career in engineering and has helped to deliver end-user features in multiple versions of Windows and Internet Explorer. A Seattle native, he left life as a poor Political Science major at the University of Washington 12 years ago because earning some extra cash as a software tester sounded like a good idea. (He has yet to find his way back...) Christchurch Monday 8th September Register <http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032385768&C ulture=en-NZ> 1.45pm: registrations/refreshments 2pm: Session begins 3pm: Session concludes Wellington Wednesday 10th September Register <http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032385790&C ulture=en-NZ> 1.45pm: registrations/refreshments 2pm: Session begins 3pm: Session concludes Auckland Friday 12th September Register <http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032385793&C ulture=en-NZ> 10.45pm: registrations/refreshments 11am: Session begins 12pm: Session concludes To learn more and to get started, please visit the New Zealand Internet Explorer Readiness website <http://www.microsoft.co.nz/ie8> and the New Zealand Internet Explorer 8 blog <http://blogs.msdn.com/nzie8> for more information. Many thanks, Nick. Nick MacKechnie | Senior Technical Account Manager | Microsoft New Zealand Level 3, State Building, 88 Division Street, PO Box 8953, Riccarton, Christchurch 8041 p +64 3 961 7246 | m +64 21 999 010 | f +64 3 355 5527 | e nick.mackechnie(a)microsoft.com <mailto:nick.mackechnie(a)microsoft.com> Microsoft Premier Online <https://premier.microsoft.com/> Security Central <http://www.microsoft.com/security/> New Zealand Events <http://www.microsoft.com/nz/events/> New Zealand Press Centre <http://www.microsoft.com/nz/presscentre/> Technet/MSDN Flash <https://profile.microsoft.com/RegSysProfileCenter/SubCntDefault.aspx?lc id=5129> Services Catalogue <http://download.microsoft.com/documents/australia/services/mssrvcat_cur rent_lowres.pdf> OpenXML <http://www.microsoft.com/downloads/details.aspx?familyid=941b3470-3ae9- 4aee-8f43-c6bb74cd1466&displaylang=en> Blog <http://blogs.msdn.com/nickmac> This email is intended solely for the use of the addressee and may contain information that is confidential or subject to legal professional privilege. If you receive this email in error please immediately notify the sender and delete the email. If you prefer not to receive these types of communications from the sender, please forward this email to uptodate(a)microsoft.com <mailto:uptodate(a)microsoft.com> with "unsubscribe" in the subject line. To learn how to manage your contact preferences for other parts of Microsoft, please read our privacy statement <http://privacy.microsoft.com/en-nz/default.aspx> .

1 0

AusNOG-02
by Jonny Martin 12 Aug '08

12 Aug '08

Just a reminder on behalf of our Austrlian colleagues that AusNOG-02 takes place next Thursday and Friday in Sydney. A NZ presence there would be much appreciated, particularly given many around the world hold NZNOG up as an example of a well- functioning NOG. I'm sure that's just asking for smart remarks from the dysfunctional amongst us! :) Full details at the now spangly http://www.ausnog.net/ Cheers, Jonny. (oh, and register for APNIC26 in Christchurch if you haven't already. Otherwise you'll be missing out on some good training and presentations. And more importantly leaving it up to others to decide what to do with the remaining IPv4 space...)

4 4

NZRR Route Registry Update
by NZRR Database Notifications 11 Aug '08

11 Aug '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: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 120.138.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-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, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 199.212.92.0/23^23-29, 202.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 210.4.212.0/23^23-29, 192.88.85.0/24^24-29, 198.32.66.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.45.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.37.57.0/24^24-29, 202.37.73.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.163.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.0/24^24-29, 205.233.243.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080627 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 120.138.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 199.212.92.0/23^23-29, 202.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 192.88.85.0/24^24-29, 198.32.66.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.45.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.37.57.0/24^24-29, 202.37.73.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.163.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.0/24^24-29, 205.233.243.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080812 source: NZRR --- 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.53.176.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, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.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.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080724 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.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, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.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.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.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 20080812 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 11 Aug '08

11 Aug '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.53.176.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, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.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.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080724 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.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, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.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.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.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 20080812 source: NZRR ------------------------------------------------------------

1 0