- NZNOG - lists.nznog.org

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 21 Dec '05

21 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

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

21 Dec '05

I've tried: Orcon Maxnet WorldXchange Telecom told me that are playing with it, at best, and had no plans to offer it commercially. Didn't bother trying Xtra. I tried to speak to TelstraClear about it, but couldn't really find the right people to understand what I was asking. -----Original Message----- From: Matt Brown [mailto:matt(a)mattb.net.nz] Sent: Thursday, 22 December 2005 2:35 p.m. To: Philip D'Ath Cc: Simon Lyall; nznog Subject: Re: [nznog] ipv6 On Thu, 2005-12-22 at 14:26 +1300, Philip D'Ath wrote: > I've tried to buy a dual stack IPv4/IPv6 circuit, but no one I've > contacted is prepared to sell me one. Are you able to share who you tried to purchase one off? There seem to be three NZ providers advertising v6 prefixes at the present time: http://www.sixxs.net/tools/grh/dfp/all/?country=nz 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. Cheers -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

1 0

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

21 Dec '05

I've tried to buy a dual stack IPv4/IPv6 circuit, but no one I've contacted is prepared to sell me one. I'm having to use 6to4 tunnelling at the moment. -----Original Message----- Is anyone in NZ actually using IPV6 for "real world" / "People paying for IPv6 service" stuff as against "just playing with IPv6" ?

3 2

Streaming Event
by Webmaster 21 Dec '05

21 Dec '05

Over the summer break we will be providing a Studio Cam for the top rating Matinee Idle radio show, hosted by Phil O'Brien. HTTP://www.radionz.co.nz/nr/programmes/matineeidle This is a first for Radio NZ and as far as I am aware a first for New Zealand Radio in general. We'll be providing video streams at 56k, 128k, 384k and 2 Mbs. Operators should be aware that the Studio Cam will be promoted extensively on air. 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. The US node is intended to serve consumers outside New Zealand. Limited NZ bound bandwidth has been allocated for this event, and operators may experience an increase in help desk calls when this allowance is exceeded. regards, Richard Hulse Radio New Zealand

2 1

ipv6
by Simon Lyall 21 Dec '05

21 Dec '05

Interesting wee discussion about real world IPv6 usage on NANOG that some here might be interested in, some have said things have improved a little in the last 18 months though: http://www.merit.edu/mail.archives/nanog/msg14543.html Is anyone in NZ actually using IPV6 for "real world" / "People paying for IPv6 service" stuff as against "just playing with IPv6" ? Ob Friday Afternoon link (many will have seen before): http://www.livejournal.com/users/pjammer/153928.html -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

New IPv6 Address Block Allocated to the RIPE NCC
by filiz＠ripe.net 20 Dec '05

20 Dec '05

[Apologies for Duplicates] Dear Colleagues The RIPE NCC received the IPv6 address range 2A01:0000::/16 from the IANA in December 2005. 2A01:0000::/23 was allocated to the RIPE NCC in July 2005. This latest range includes that previous allocation. You may wish to adjust any filters you have in place accordingly. You can find more information about the IP space administered by the RIPE NCC on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Regards, Filiz Yilmaz RIPE NCC

1 0