IETF Logo Mail Archive

Re: IETF Service Outage

Randy Bush <randy@psg.com> Thu, 24 March 2016 01:52 UTC

Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39A7A12D0EB for <ietf@ietfa.amsl.com>; Wed, 23 Mar 2016 18:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TARWzVI9_90V for <ietf@ietfa.amsl.com>; Wed, 23 Mar 2016 18:52:04 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B75E12D18E for <ietf@ietf.org>; Wed, 23 Mar 2016 18:52:04 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1aiuRO-0002X1-Fz; Thu, 24 Mar 2016 01:52:02 +0000
Date: Thu, 24 Mar 2016 10:52:00 +0900
Message-ID: <m28u184p8f.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Scott Weeks <surfer@mauigateway.com>
Subject: Re: IETF Service Outage
In-Reply-To: <20160323112007.8BBF1AE2@m0087795.ppops.net>
References: <20160323112007.8BBF1AE2@m0087795.ppops.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FgwKG4UmIMkc1Rc3ZR-GhnMeWAI>
Cc: IETF Disgust List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2016 01:52:06 -0000

> If you can't tell whether it was a DoS or a bad network cable 
> you should talk to network operators.  We can help.  We deal 
> with these things all the time.

i knew glen when he was a network operator.  his team is competent.
chill.  as you may remember from being a network operator, diagnosis
and attribution are hard and come secondary to bringing services back
up.

randy

v2.23.0 | Report a Bug | By Email