June 2005 - NZNOG - lists.nznog.org

Re: [nznog] Technical Announcement
by Webmaster 28 Jun '05

28 Jun '05

>>> Barry Murphy <barry(a)unix.co.nz> 06/29/05 2:38 PM >>> > For providers not connected to the peering exchanges > will the content be delivered from the USA? Yes, at the 'standard' rate of 16 or 24 kbs. This rate is on a par with other Public Broadcasters. Peering ISPs get higher rates from the local servers. > This would mean those providers will only get the USA > content and wont be allowed to hear the copyright audio? NZ Restricted audio, actually. We use the exchange infrastructure to limit the distribution of some content. At the start there won't be any NZ restricted content (apart from Enzology). We expect demand for the service to be quite high, and don't want to have to sort between help desk calls from consumers who's ISPs do not peer and people who have a genuine problem. R.

3 2

RE: [nznog] Technical Announcement
by Regan Murphy 28 Jun '05

28 Jun '05

>>For providers not connected to the peering exchanges such as telecom and telstra The way I see it is that while these two providers are connected to the one or more exchanges, its just that they don't openly peer with everybody at the exchanges. Therefore they may choose to peer directly with radionz at one of these exchanges thus enabling the content to be provided to their subscribers. -- Regan -----Original Message----- From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Wednesday, 29 June 2005 2:38 p.m. To: Webmaster; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Technical Announcement Hi, For providers not connected to the peering exchanges such as telecom and telstra, will the content be delivered from the USA? I'm guessing this is the case so you don't have to purchase domestic links from those providers. This would mean those providers will only get the USA content and wont be allowed to hear the copyright audio? Thanks Barry P.S. www.ispmap.co.nz is backup and running people, sorry the hardware died and took a while to replace. ----- Original Message ----- From: "Webmaster" <Webmaster(a)radionz.co.nz> To: <nznog(a)list.waikato.ac.nz> Sent: Wednesday, June 29, 2005 2:24 PM Subject: [nznog] Technical Announcement > Hi, > > Radio New Zealand has recently installed content servers at the > Auckland (APE), Wellington (WIX), and Palmerston North (PNIX) internet > exchanges. We also have a server located in California, USA to serve > content to New Zealanders overseas. > > These servers have been deployed within the R2 infrastructure and will > be used for the soon-to-be-launched on-demand and simulcast audio > service. > There will be a range of on-demand content from programmes broadcast > on both networks, and we are hoping to provide live streams of > National Radio and Concert FM (subject to resolving some outstanding > copyright issues). When the service commences we expect about 60 hours > of new content to be available each week. The servers will also be > used by Radio NZ International for their on-demand and simulcast audio. > > All streams will initially be 16 kbs maximum, and this may increase to > 24 kbs once we have a handle on traffic flows. Everyone will be able > to access content at this rate. > > We have chosen to deploy a multi-homed architecture for the following > reasons: > 1. Greater diversity and redundancy than a single site/provider > architecture. > 2. Reduced network latency for improved streaming performance. > 3. Shortest path for broadband consumers (reducing network congestion > for Operators). > 4. Scalability, allowing us to add servers at new exchanges in the > future. > 5. To minimise national transit costs for the ISP's of customers using > the content. > 6. Lowest cost to serve content. > > The servers have a globally consistent anycast IP address which will > be advertised at each exchange to ensure that the content is delivered > from the nearest server to the consumer. > > As new exchanges are installed throughout the country we intend to > deploy content servers at them, subject to certain minimum criteria > being met. This also includes MUSH style networks outlined in the NZ > Government's Digital Strategy. > > In order to get the best performance we recommend that you peer > directly with the anycast routers at all the exchanges where you have > connectivity. > > For those who wish to peer locally an enhanced service is available > from the NZ exchange-based content servers. Maximum data rates will > increase to 32 or 48 kbs for on-demand content and 48 or 64 kbs for > live streams. The live simulcasts (when available) will be available > in stereo at these rates. > > Where content is limited to NZ for copyright reasons there will be no > international route, meaning customers of non-peering ISPs will not be > able to access the content. This is currently the case with the > Enzology series (www.radionz.co.nz/enzology/). > > Please contact our peering coordinator at peering(a)radionz.co.nz if you > need to establish a peering session with our content servers. > > We will be maintaining a list of peers and a help page on our new > website so that consumers can be informed about how to access the > enhanced service. > > Operators may expect increased help desk activity due to their > customers not being able to access NZ restricted content, or asking > for access to the enhanced service. > > We are publishing our intentions to this list in advance of the launch > so that Operators can prepare for what we expect will be a very > popular service with the 686,000 people who listen each week to > National Radio and Concert FM. > > We expect to go live in 2-3 weeks. > > > regards, > > > Richard Hulse > New Media Manager > Radio New Zealand > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Technical Announcement
by Webmaster 28 Jun '05

28 Jun '05

Hi, Radio New Zealand has recently installed content servers at the Auckland (APE), Wellington (WIX), and Palmerston North (PNIX) internet exchanges. We also have a server located in California, USA to serve content to New Zealanders overseas. These servers have been deployed within the R2 infrastructure and will be used for the soon-to-be-launched on-demand and simulcast audio service. There will be a range of on-demand content from programmes broadcast on both networks, and we are hoping to provide live streams of National Radio and Concert FM (subject to resolving some outstanding copyright issues). When the service commences we expect about 60 hours of new content to be available each week. The servers will also be used by Radio NZ International for their on-demand and simulcast audio. All streams will initially be 16 kbs maximum, and this may increase to 24 kbs once we have a handle on traffic flows. Everyone will be able to access content at this rate. We have chosen to deploy a multi-homed architecture for the following reasons: 1. Greater diversity and redundancy than a single site/provider architecture. 2. Reduced network latency for improved streaming performance. 3. Shortest path for broadband consumers (reducing network congestion for Operators). 4. Scalability, allowing us to add servers at new exchanges in the future. 5. To minimise national transit costs for the ISP's of customers using the content. 6. Lowest cost to serve content. The servers have a globally consistent anycast IP address which will be advertised at each exchange to ensure that the content is delivered from the nearest server to the consumer. As new exchanges are installed throughout the country we intend to deploy content servers at them, subject to certain minimum criteria being met. This also includes MUSH style networks outlined in the NZ Government's Digital Strategy. In order to get the best performance we recommend that you peer directly with the anycast routers at all the exchanges where you have connectivity. For those who wish to peer locally an enhanced service is available from the NZ exchange-based content servers. Maximum data rates will increase to 32 or 48 kbs for on-demand content and 48 or 64 kbs for live streams. The live simulcasts (when available) will be available in stereo at these rates. Where content is limited to NZ for copyright reasons there will be no international route, meaning customers of non-peering ISPs will not be able to access the content. This is currently the case with the Enzology series (www.radionz.co.nz/enzology/). Please contact our peering coordinator at peering(a)radionz.co.nz if you need to establish a peering session with our content servers. We will be maintaining a list of peers and a help page on our new website so that consumers can be informed about how to access the enhanced service. Operators may expect increased help desk activity due to their customers not being able to access NZ restricted content, or asking for access to the enhanced service. We are publishing our intentions to this list in advance of the launch so that Operators can prepare for what we expect will be a very popular service with the 686,000 people who listen each week to National Radio and Concert FM. We expect to go live in 2-3 weeks. regards, Richard Hulse New Media Manager Radio New Zealand

2 1

Telstra Problems
by Lyndon 27 Jun '05

27 Jun '05

I took a traceroute this morning as Telstra were fixing the issue, it was indeed interesting. First 3 hops are removed (my firewall, local router and next hop). I am connected by Cable Modem. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * 20 ms 20 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 8 153 ms 153 ms 154 ms so.jb.wils.telstraclear.net [203.98.42.66] 9 155 ms 156 ms 154 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21] 10 148 ms 147 ms 147 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 11 156 ms 157 ms 154 ms 0.so-1-1-0.XL1.LAX7.ALTER.NET [152.63.57.78] 12 154 ms 153 ms 155 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41] 13 148 ms 148 ms 146 ms so-2-0-0.gar1.LosAngeles1.Level3.net [209.0.227.37] 14 148 ms 149 ms 146 ms so-0-1-0.bbr2.LosAngeles1.Level3.net [4.68.96.89] 15 167 ms 169 ms 168 ms as-2-0.bbr2.SanJose1.Level3.net [4.68.128.157] 16 167 ms 168 ms 168 ms ae-23-54.car3.SanJose1.Level3.net [4.68.123.109] 17 217 ms 213 ms 213 ms unknown.Level3.net [64.152.102.58] 18 205 ms 207 ms 205 ms po3-0.gw1.akl1.asianetcom.net [202.147.55.213] 19 206 ms 204 ms 204 ms ip-202-147-45-74.asianetcom.net [202.147.45.74] 20 206 ms 205 ms 206 ms 203-109-156-100.ihug.net [203.109.156.100] 21 206 ms 204 ms 205 ms oldresolver3.ihug.co.nz [202.36.94.1] Cheers L

1 0

RE: [nznog] TelstraClear/ICONZ Fault (IHUG as well?)
by Simon Allard 27 Jun '05

27 Jun '05

There was earlier, we had to shut down our BGP session to TCL because of some weirdness in the BGP advertisements from TCL. It has been resolved now and the BGP session was brought back up. > -----Original Message----- > From: Tony Wicks [mailto:nzog(a)road.gen.nz] > Sent: Tuesday, 28 June 2005 9:55 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] TelstraClear/ICONZ Fault (IHUG as well?) > > No issues to Ihug via TCL Auckland. > > > [root(a)fire root]# traceroute ihug.co.nz > traceroute to ihug.co.nz (203.109.252.75), 30 hops max, 38 byte packets > 1 router2 (203.97.9.132) 0.982 ms 1.136 ms 0.993 ms > 2 203.97.85.221 (203.97.85.221) 25.973 ms 27.754 ms 25.487 ms > 3 ge9-0-954.u11.pnr.telstraclear.net (218.101.61.41) 25.982 ms > 30.724 ms 30.487 ms > 4 g1-0-927.u11.tspn.telstraclear.net (218.101.61.6) 27.482 ms > 30.195 ms 29.486 ms > 5 g1-926.u12.brh.telstraclear.net (218.101.61.35) 26.982 ms 27.230 > ms 26.486 ms > 6 lnk1-ihug-ge-1-0-1642.u12.telstraclear.net (203.98.18.162) 28.482 > ms 30.234 ms 25.486 ms > 7 203-109-156-97.ihug.net (203.109.156.97) 35.982 ms 36.202 ms > 45.986 ms > 8 ihug.co.nz (203.109.252.75) 26.974 ms 28.200 ms 25.985 ms > [root(a)fire root]# > Simon wrote: > > Michael Bordignon wrote: > > > >>> Since then we have about 55% packet loss, with ICONZ as at 12:05 > >> > >> > >> saying that they have not been given an ETA by TelstraClear. > >> > >>> 12 hours of substandard performance with no ETA seems a bit poor to > >> > >> > >> me. > >> > >>> If anyone has any updates on this please feel free to let me know. > >> > >> > >> > >> Same here - unusable. > > > > > > I am possibly seeing the same problem here? we are on tesltraclear DSL > > and cant get to any of IHUG's network... Anyone seeing this same issue > > this morning? Other major ISP's are fine. > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

RE: [nznog] TelstraClear/ICONZ Fault
by Michael Bordignon 27 Jun '05

27 Jun '05

> Since then we have about 55% packet loss, with ICONZ as at 12:05 saying that they have not been given an ETA by TelstraClear. > 12 hours of substandard performance with no ETA seems a bit poor to me. > If anyone has any updates on this please feel free to let me know. Same here - unusable. Michael

5 5

RE: [nznog] Trademe problems ?
by Jay Rama 27 Jun '05

27 Jun '05

Hi Simon, Telstra/Paradise are currently having some DNS issues, there is a quickfix in place, but I believe problems still persist... Regards, Jay ________________________________ From: Simon Byrnand [mailto:simon(a)igrin.co.nz] Sent: Tue 28/06/2005 9:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Trademe problems ? Hi All, Anyone else seeing problems getting to trademe this morning ? Seems to die somewhere between global gateway and telstraclear... Regards, Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Trademe problems ?
by Simon Byrnand 27 Jun '05

27 Jun '05

Hi All, Anyone else seeing problems getting to trademe this morning ? Seems to die somewhere between global gateway and telstraclear... Regards, Simon

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 26 Jun '05

26 Jun '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: AS9560:RS-ROUTES:AS24324 descr: Route set advertised to AS9560 by BCL - AS24324 members: 202.49.128.0/24^24-29, 202.49.135.0/24^24-29, 202.49.133.0/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050610 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 202.49.128.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050627 source: NZRR

1 0

APNIC Updates @ Telstra
by Jonathan Brewer 26 Jun '05

26 Jun '05

Hi Folks, Would someone at Telstra capable of performing updates to Telstra-managed AS9436 please contact me off-list? Thanks, Jonathan Brewer

1 0