[147008] in North American Network Operators' Group
RE: ATT GigE issue on 11/19 in Kansas City
daemon@ATHENA.MIT.EDU (Soni, Miraaj)
Wed Nov 30 13:01:51 2011
Date: Wed, 30 Nov 2011 11:00:56 -0700
In-Reply-To: <4ED66BD3.3050603@ttec.com>
From: "Soni, Miraaj" <msoni@virtela.net>
To: "Joe Maimon" <jmaimon@ttec.com>,
"Brad Fleming" <bdflemin@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
No. It doesn't prevent it from happening again. But at least you can
have them check for that same issue when it happens next time.
I guess the RFO gives the customer the feeling that the vendor was able
to isolate the issue and fix it; as opposed to "issue was resolved
before isolation".
- Miraaj Soni
-----Original Message-----
From: Joe Maimon [mailto:jmaimon@ttec.com]=20
Sent: Wednesday, November 30, 2011 10:46 AM
To: Brad Fleming
Cc: nanog@nanog.org
Subject: Re: ATT GigE issue on 11/19 in Kansas City
Brad Fleming wrote:
>>
> In either case I'm a customer and will likely never be told what went
wrong. I'm OK with that so long as it doesn't happen again!
>
>
Does being told what happened somehow prevent it from happening it
again?
What is the utilitarian value in an RFO?
Joe
