[LINK] Net back-ups reviewed after cable breakdown

[Chirgwin, Richard]

> Yep, it's time for the technical press to not take things at 
> face value ...

Peter,

Who said the SMH, the Australian, the Fin were *technical* press? Look up
The Register for an explanation of the acronym "PFY"...

Re the route notification you attached, the semi-technical (me, for eg)
might like more info on the impact...

Richard


> -----Original Message-----
> From: Peter J. Cherny [mailto:peterc@arquebus.com.au]
> Sent: Monday, 27 November 2000 9:53
> To: link@www.anu.edu.au
> Subject: RE: [LINK] Net back-ups reviewed after cable breakdown
> 
> 
> Yep, it's time for the technical press to not take things at 
> face value ...
> 
> The cable cut just exposed Telstra's inadequate engineering in the
> construction
> of their IP routing tables i.e. their approach to route 
> aggregation and
> internal vs. external routing announcements.
> 
> Unfortunately, their ill-considered/erzatz solution will 
> result in another
> SNAFU on or around the 4 Dec., though only SOME of their 
> clients (and their
> users) will the ones isolated from the Internet.
> 
> >Date: Wed, 22 Nov 2000 16:27:32 +1100 (EST)
> >From: routing@telstra.net
> >To: noc@luddite.com.au
> >Subject: Routing Change Notice from Big Pond Direct
> >
> >Please note that as of 0700hrs AEDT on 4 December 2000, Big Pond
> >Direct will cease advertising the aggregate route 203.0.0.0/10 to its
> >customers, peers and providers.
> >
> >If you are advertising routes from the provider independent address
> >space within 203.0.0.0/10, you should ensure that all of those routes
> >have a maximum length of /24 to ensure that the routing advertisement
> >is accepted by other Internet Service Providers worldwide.
> >
> >BGP-connected customers of Big Pond Direct should note that they will
> >receive an extra 1900 routes from their BGP sessions as a result of
> >this disaggregation. Telstra does not expect any other impact arising
> >from this change.
> > ...
>