[AusNOG] Small Pipe BNE/Agile issue

[McDonald Richards]

MMC - Understood and agreed, it's part of why I much prefer working in
smaller organisations these days, but I'm sure many of us have found
ourselves in this situation in the past.

Sometimes the people in charge of commercials in a large environment don't
see eye-to-eye with the engineers, and the engineers have to use the tools
at their disposal to ensure continued smooth-ish operation.

If you were the head of a company and faced with the situation where you'd
lose $$$ per month to increase the size of an expensive transit link, or
de-aggregate a few prefixes to bring it in a link with free capacity, which
would you choose..? I'm not talking about gross de-aggregation down to every
/24, but this IS part of the protocol... 



-----Original Message-----
From: Matthew Moyle-Croft [mailto:mmc at internode.com.au] 
Sent: Sunday, 15 June 2008 5:55 PM
To: McDonald Richards
Cc: 'David J. Hughes'; ausnog at ausnog.net
Subject: Re: [AusNOG] Small Pipe BNE/Agile issue


> If someone has a better solution to this, please educate away!
>   
It strikes me that rather than trying to solve commercial issues with 
BGP that you should be solving BGP issues with commercials.

If you've got a disconnect between your engineering side and 
commercial/carrier relations side such that you've got transit links and 
SDH links which are poorly arranged and inflexible compared to your 
actual requirements and business model then maybe that's the issue you 
need to fix rather than stoop to disaggregation on such a large scale?

MMC

-- 
Matthew Moyle-Croft - Internode/Agile - Networks
Email: mmc at internode.com.au  Web: http://www.on.net