[bcop] Correlation between network complexity and troubleshooting time (and resources)...

Dear BCOP community,

While traveling the world and speaking with different operators - what I 
hear is some sort of need to have a document or "study" of ways to 
simplify your network in order to cut down costs of owning, running and 
mainly troubleshooting it.

We can hear lot's of presentations (mainly from vendors and also young 
enthusiastic admins that sees complexity as a challenge) how to 
introduce new shiny features X that would do Y to your network, but also 
make it more complex to maintain and troubleshoot, specially makes 
troubleshooting longer when disaster happens. Operators started to 
understand that "less is more", but have troubles escaping the 
influences from the past, that are keeping them tied in complexity 
business, so the need emerged to put together some content that would 
explain pros and cons of complexity, how to weight and balance 
complexity vs. needed features and functionality and also the 
correlation of increased complexity on longer and harder troubleshooting.

I had a quick word with some "usual suspects", but I would like to ask 
BCOP community if there's any interest in working together to pull this 
through and shed some light for new (and old operators) that making your 
network as complex as possible is not necessarily the best idea.

If there is some interest - any volunteers to work on this subject/topic?

See you all at BCOP TF meeting in London on Monday at 18:00, the first 
day of RIPE69 meeting ;)

Cheers, Jan