[155225] in North American Network Operators' Group
Re: cost of misconfigurations
daemon@ATHENA.MIT.EDU (Simon Knight)
Thu Aug 2 00:22:53 2012
In-Reply-To: <CAK__KzseYJ_gtRAx8zGELscwxTmU=63bt4boSYci==fBGYXVzw@mail.gmail.com>
From: Simon Knight <simon.knight@gmail.com>
Date: Thu, 2 Aug 2012 13:52:02 +0930
To: George Herbert <george.herbert@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Quantifying the business costs would be very complex.
Here are some reports and research papers that may be a starting point:
[1] Juniper Networks, Inc., =E2=80=9CWhat's Behind Network Downtime?,=E2=80=
=9D pp.
1=E2=80=9312, May 2008.
[2] R. Mahajan, D. Wetherall, and T. Anderson, =E2=80=9CUnderstanding BGP
misconfiguration,=E2=80=9D Proceedings of the 2002 conference on Applicatio=
ns,
2002.
[3] A. Medem, R. Teixeira, N. Feamster, and M. Meulle, =E2=80=9CJoint analy=
sis
of network incidents and intradomain routing changes,=E2=80=9D Network and
Service Management (CNSM), 2010 International Conference on, pp.
198=E2=80=93205, 2010.
[4] D. Turner, K. Levchenko, A. C. Snoeren, and S. Savage, =E2=80=9CCalifor=
nia
fault lines: understanding the causes and impact of network failures,=E2=80=
=9D
presented at the SIGCOMM '10: Proceedings of the ACM SIGCOMM 2010
conference on SIGCOMM, 2010.
[5] Z. Yin, X. Ma, J. Zheng, Y. Zhou, L. N. Bairavasundaram, and S.
Pasupathy, =E2=80=9CAn empirical study on configuration errors in commercia=
l
and open source systems,=E2=80=9D presented at the SOSP '11: Proceedings of
the Twenty-Third ACM Symposium on Operating Systems Principles, 2011.
[6] Z. Kerravala, =E2=80=9CAs the Value of Enterprise Networks Escalates,=
=E2=80=A8So
Does the Need for Configuration Management
,=E2=80=9D cs.princeton.edu, 01-Jan.-2004. [Online]. Available:
https://www.cs.princeton.edu/courses/archive/fall10/cos561/papers/Yankee04.=
pdf.
[Accessed: 09-May-2012].
[7] W. Enck, P. McDaniel, S. Sen, and P. Sebos, =E2=80=9CConfiguration
management at massive scale: System design and experience,=E2=80=9D USENIX
'07, Jun. 2007.
[8] R. D. Doverspike, K. K. Ramakrishnan, and C. Chase, =E2=80=9CStructural
overview of ISP networks,=E2=80=9D Guide to Reliable Internet Services and
Applications, pp. 19=E2=80=9393, 2010.
On 2 August 2012 10:46, George Herbert <george.herbert@gmail.com> wrote:
> On Wed, Aug 1, 2012 at 5:32 PM, Diogo Montagner
> <diogo.montagner@gmail.com> wrote:
>> Hi Darius,
>>
>> You are right. The lost of a customer due to those things. However, I
>> would classify this as an unknown situation (in terms of risk
>> analisys) because the others I mentioned are possible to calculate and
>> estimate (they are known). But it is very hard to estimate if a
>> customer will cancel the contract because 1 or n network outages. In
>> theory, if the customer SLA is not being met consecutively, there is a
>> potential probability he will cancel the contract.
>>
>> Regards
>
> On the end customer side, I've done a bunch of reliability / risk cost
> assessments for various customers over the years. It's never easy.
>
> For an ISP... customers are fairly locked in, but for big networks and
> customers, especially multihoming customers, business goes where they
> want it.
>
> SLA costs are easy. Predicting the final financial impact is hard.
>
>
> --
> -george william herbert
> george.herbert@gmail.com
>
