This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

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

• Previous message (by thread): [bcop] Correlation between network complexity and troubleshooting time (and resources)...
• Next message (by thread): [bcop] Correlation between network complexity and troubleshooting time (and resources)...

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

James Bensley jwbensley at gmail.com
Tue Oct 21 13:46:38 CEST 2014

Hi Jan,

I have seen papers from vendors before on this, such as
http://www-05.ibm.com/uk/juniper/pdf/200249.pdf

I am keep on this ideaology of keeping things simple as possible to
reduce the surface area of potential human error. This is of course
caveated against (i) unavoidable complexity because that's the service
we've sold to a customer or just simply the service the customer
requires and (ii) more densely interconnected networks can't avoid a
minimum level of complexity.

We can catch up at RIPE if you'd like?

Kind regards,
James.

• Previous message (by thread): [bcop] Correlation between network complexity and troubleshooting time (and resources)...
• Next message (by thread): [bcop] Correlation between network complexity and troubleshooting time (and resources)...

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ BCOP Archives ]