- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jan '06

11 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.20.6.0/24^24-29, 202.36.119.0/24^24-29, 202.46.190.0/24^24-29, 202.49.159.0/24^24-29, 202.78.240.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050119 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.78.240.0/21^21-29, 202.36.119.0/24^24-29, 202.46.190.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: routing(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060112 source: NZRR

1 0

IANA IPv4 allocations and bogon updates: 121/8, 122/8, and 123/8
by Rob Thomas 09 Jan '06

09 Jan '06

-----BEGIN PGP SIGNED MESSAGE----- [ Apologies to those of you who receive this note in multiple forums. ] Hi, team. The numerous Team Cymru bogon projects have been updated as of 05 JAN 2006 to reflect the following IANA allocation made on 05 JAN 2006: 121/8 Jan 06 APNIC (whois.apnic.net) 122/8 Jan 06 APNIC (whois.apnic.net) 123/8 Jan 06 APNIC (whois.apnic.net) IANA allocations change over time, so please check regularly to ensure you have the latest filters if you are not using the bogon BGP feed(s). We do announce updates to the bogon projects to sundry lists, such as the bogon-announce list. We can not stress this point strongly enough - these allocations change. If you do not adjust your filters, you will be unable to access perhaps large portions of the Internet. Worse yet, you may end up blocking access for people who transit through you. Please do not apply any filters or blocks to your network without carefully considering the ramifications of doing so. As a point of reference, the Team Cymru master Bogon Reference Page can be found here: <http://www.cymru.com/Bogons/> A quick summary of the documents and projects that have been updated include the following: HTTP The Bogon List - <http://www.cymru.com/Documents/bogon-list.html> The Text Bogon Lists - <http://www.cymru.com/Documents/bogon-bn-nonagg.txt> - <http://www.cymru.com/Documents/bogon-bn-agg.txt> Secure BIND Template - <http://www.cymru.com/Documents/secure-bind-template.html> Secure IOS Template (Cisco) - <http://www.cymru.com/Documents/secure-ios-template.html> Secure BGP Template (Cisco) - <http://www.cymru.com/Documents/secure-bgp-template.html> Secure JUNOS Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-template.htm> Secure JUNOS BGP Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-bgp-template.htm> Ingress Prefix Filter Templates, Loose and Strict (Cisco) - <ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix- Filter-Templates/> Ingress Prefix Filter Template, Loose (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix- filter-loose.htm> Ingress Prefix Filter Template, Strict (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix- filter-strict.htm> BGP Bogon route-server for AUTOMATED updates of bogon filters - All bogon route-server peers have already received the appropriate BGP prefix updates. - <http://www.cymru.com/BGP/bogon-rs.html> RADb fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#radb> RIPE NCC fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#ripe> DNS Bogon (bogons.cymru.com) zone - <http://www.cymru.com/Bogons/index.html#dns> Monitoring Bogon prefix monitoring - <http://www.cymru.com/BGP/robbgp-bogon.html> Bogus ASN monitoring - <http://www.cymru.com/BGP/asnbogusrep.html> Please feel free to contact Team Cymru <team-cymru(a)cymru.com> with any comments, questions, or concerns. Thank you for your continued support. Thanks, Rob. - -- Rob Thomas Team Cymru http://www.cymru.com/ ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQ8MiDlkX3QAo5sgJAQEHwwP/X6Jh/sZ+j46KosfJ6H3+Wzb7sE3xXjl9 ktuNLb7Xfvo0A4PwUSv5NF5aS4Yp1C5NWZcrBDKkwIMA4WcC7DZK+qvFHeOX7EVS vzXzpw2FGCyImU1m49qNR+437vM0CNVaeFeMc+zjHnnXlsAEVVIhwQ7lz0KE+rlM G2ZKbvaQRyw= =qtQ6 -----END PGP SIGNATURE-----

1 0

ANZ website broken?
by Blair Harrison 31 Dec '05

31 Dec '05

Hmm, Maybe someone pushed a wrong button? domain_name: anz.co.nz query_status: 210 PendingRelease domain_dateregistered: 1997-03-10T00:00:00+13:00 domain_datebilleduntil: 2006-01-01T00:00:00+13:00 domain_datelastmodified: 2005-12-31T22:01:03+13:00 domain_datecancelled: 2005-12-31T22:01:03+13:00 Oops. Internet banking still available via www.anz.com/nz at least. -Blair

1 0

Re: [nznog] Studio Cam Update
by Webmaster 26 Dec '05

26 Dec '05

After receiving a number of requests from people viewing the Matinee Idle studio cams, I have opened up access to the 384k and 2M streams to all comers. This means that all NZ consumers can watch the high rate streams if they want to, regardless of whether their ISP peers or not. Non-peering ISPs may see a big increase in international bandwidth usage between 12:30 pm and 5 pm daily on weekdays until 20 Jan 2006. regards, Richard _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Streaming Event
by Ian Cogill 23 Dec '05

23 Dec '05

Hi There We will be providing live streams of the ASB Classic and Heineken Open tennis from Jan 2 - Jan 14 To ensure all New Zealanders get the best possible service we strongly recommend peering with the R2/Citylink anycast cluster at 202.7.7.90 via WIX, APE and/or PNIX. As it is the holidays we're not exctly sure how many people will be watching coverage online, so this is just a heads up. Regards Ian Cogill Systems Engineer TVNZ Interactive ===================================================================== CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it. ================================================================ For more information on the Television New Zealand Group, visit us online at http://www.tvnz.co.nz ================================================================

1 0

Studio Cam Update
by Webmaster 22 Dec '05

22 Dec '05

The studio cams for the Matinee Idle radio show are now in operation with a jpg slide: http://www.radionz.co.nz/nr/programmes/matineeidle I have noted on the web cam page that some customers may not be able to get the high bandwidth streams due to their ISP not peering. These consumers will get a message suggesting that they use one of the lower rate streams or contact their ISP. Time for a beer now, my work is done.... regards, Richard

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 Dec '05

22 Dec '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051219 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051219 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 source: NZRR

1 0

Re: [nznog] ipv6
by Philip D'Ath 22 Dec '05

22 Dec '05

Pretty much every Cisco DSL router supports IPv6. We just need an ISP to start selling the IPv6 transit ... -----Original Message----- From: Richard Hector [mailto:richard(a)walnut.gen.nz] Sent: Thursday, 22 December 2005 2:46 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] ipv6 On Thu, 2005-12-22 at 14:35 +1300, Matt Brown wrote: > With the introduction of UBS I'm hoping that it's going to become a > lot more common for ISPs to be able to offer IPv4/IPv6 circuits, even > if it is only on ad Ad-Hoc basis to the 'geeks' to start with. To offer it on UBS, wouldn't your DSL router have to support IPv6? Do any of them? I suppose you could use either a plain modem, or one of those ones that bridges PPPoA to PPPoE, but I've never tried setting one up. Richard _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

9 11

SANOG VII - Mumbai, India, 16-24 January 2006
by Andy Linton 22 Dec '05

22 Dec '05

South Asian Network Operators Group (SANOG) VII 16-24 January 2006, Mumbai, India Hosted by ISPAI. SANOG VII Program Announcement SANOG VII program and agenda are now published on http://www.sanog.org/sanog7/. SANOG VII is being held by ISP Association of India (ISPAI) in Mumbai, India from 16-24 January 2006. Daniel Karrenberg, Chief Scientist, RIPE NCC and Paul Wilson, DG,APNIC will address the plenary session of SANOG VII. There will be 3 workshops, 10 tutorials, 3 BoFs and over 16 presentations during the event. APNIC will hold a special Open Policy Meeting Showcase at SANOG VII, and for the first time at SANOG, we'll have a Peering Panel and Debate. Registration Discounts available for ISPAI, APNIC, APIA members. Detailed information is available at http:/www.sanog.org/sanog7/ Program and Agenda: Three hands-on workshops: 16-20 January 2006 * ISP Routing and BGP Multihoming Workshop * IPv6 Essentials, Applications and Routing Workshop * Multicast Routing and Applications Workshop Ten Tutorials: 21-22 January 2006 * BGP and High Availability Routing Tutorial, Prasad Babu * DNS / DNSSec Deployment Tutorial, Champika Wijayatunga * IXP Construction and BGP Multihoming, Philip Smith, Gaurab Raj Upadhaya * L2VPN - Changing and Consolidating Networks - Paresh Shah, Md.Waris * Layer2 Attacks and Mitigation techniques, Yusuf Bhaiji * DDoS prevention in Service Provider Networks, Wireless Security,Pravin Mahajan * The Basics of Multicast - Marshall Eubanks, * QoS and Multicast on MPLS Networks , Rajesh Shinde * QoS on Low Bandwidth & High Delay Links, Prakash Shende Birds-of-a-Feather (Special Evening Sessions) : 21-23 January 2006 * Managed Services * Anti-SPAM Tools and Techniques * Internet Society (ISOC) BoF APNIC Special Sessions * APNIC Helpdesk sessions throughout SANOG VII * APNIC Open Policy Meeting Showcase on 24th January 2006 Two Days Conference Program : 23-24 January 2006 * Alternative architectures for Broadcast Video Distribution - Srinath Beldona, Cisco * RA-MPLS services - Kapil Kumar, Reliance * Network Infrastructure for IPTV - Saisree Subramanian, Wipro * Efficient Resource Broker Architecture to Provide Guaranteed QoS - Praveen Kumar, Anna University * Graceful Restart of Routing Protocols - Prasad Babu, Juniper * Backbone Architectures for NLD/ILD: Design; Optmization & Services - Chandan Mendiratta (Cisco) * Network Infrastructure Security in Cellular Data Networks: An Initial Investigation - Vishal Sharma (IIT-Bombay) * Traffic Engineering and Network Planning Tools for MPLS Networks - Dr. Girish P. Saraph (IIT-Bombay) * pmacct; a new player in the network management arena - Paolo Lucente (CNR-Italy) * Flow measurements from the packet-switched NREN PIONIER: technology and experience - Wiktor Procyk (Poznan S&N Center) * Interest Based Group Management Mechanisms for E-learning Design using the Peer to Peer Technologies - Surya (AIT) * Internet Routing Table Update - Philip Smith (Cisco) * INOC - DBA Update - Gaurab Raj Upadhaya ( PCH) * Data Network Management for Telecom Operators in ASIA - Sufi Faruq (AKTEL) Peering Penel and Debate * Nigel Titley, Peering Manager, FLAG Telecom * Sylvie Laperriere, Director- Peering, Teleglobe * Sharad Shangi, Net4India * Gaurab Raj Upadhaya, PCH, (moderator) Local Fellowships are still available. We expect a huge turn out from the region at this SANOG meeting owing to the popularity at previous meets. We also welcome participants from West Asia, with our established collaboration with the RIPE NCC. With more involvement of APNIC in the content of overall program, We hope you would be able to make it to this meeting. The meeting is open to everyone from the operational community, and thus anyone who wants to find out more about Internet operations in South Asia is welcome. You can register for SANOG by sending in the form available at www.sanog.org/sanog7 or using the online registration system. Registrations from inside India can be paid by DD Looking forward to seeing you there. Thanks - SANOG

1 0

Re: [nznog] ipv6
by Philip D'Ath 22 Dec '05

22 Dec '05

Not being from a service provider my view is somewhat simplistic. Telecom offers a layer 2 service called UBS, which uses L2TP between their RAN and the ISP. Over this PPP runs. So I don't see any reason why an ISP couldn't offer IPv6 over UBS. -----Original Message----- > Pretty much every Cisco DSL router supports IPv6. We just need an ISP > to start selling the IPv6 transit ... The last I knew (which was admittedly many years ago) Telecom's wholesale DSL was a layer-3 service, with frames being routed through a twisty maze of RFC1918-numbered routers before they arrived at the user's ISP. If that was still the case, then surely Telecom would need to route v6 frames between the customer and the ISP for the customer to receive native v6 service? If there has been a subsequent layer-2 wholesale DSL service offered, along the lines that is done elsewhere, is there not still a requirement for Telecom to switch v6 frames from PPPoA into L2TP, or whatever framing is used to present a user's traffic to an ISP?

1 0