Re: IETF Website Outage

Jari Arkko <jari.arkko@piuha.net> Thu, 08 May 2008 22:04 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB3603A6B02; Thu, 8 May 2008 15:04:17 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03F7A3A6824 for <ietf@core3.amsl.com>; Thu, 8 May 2008 15:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.386
X-Spam-Level:
X-Spam-Status: No, score=-2.386 tagged_above=-999 required=5 tests=[AWL=0.213, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cYU6KkBiACzQ for <ietf@core3.amsl.com>; Thu, 8 May 2008 15:04:15 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 26FE63A6B02 for <ietf@ietf.org>; Thu, 8 May 2008 15:04:15 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id B034F1987F3; Fri, 9 May 2008 01:04:12 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 3189819875F; Fri, 9 May 2008 01:04:12 +0300 (EEST)
Message-ID: <482378E4.9090609@piuha.net>
Date: Fri, 09 May 2008 00:04:20 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.14ubu (X11/20080306)
MIME-Version: 1.0
To: Alexa Morris <amorris@amsl.com>
Subject: Re: IETF Website Outage
References: <C448A56E.4E5AD%amorris@amsl.com>
In-Reply-To: <C448A56E.4E5AD%amorris@amsl.com>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Alexa,

First: thanks for getting the system up and running again. Then a small
addition to what you said:

> Many of you in Europe attempted to notify us of the outage and were unsure
> of how to reach us, or what number to call. Thank you to everyone who
> attempted to notify us, and I apologize for the fact that the process was
> more confusing and time-consuming than it should have been.
>   

Actually, I think some of us learned a lesson during this incident. The
confusion was not entirely your fault. I think we would have had access
to a few more phone numbers to call... had those phone numbers been
somewhere else than on the web site that went down. Duh :-)

> 2) In case the email notification doesn't work properly for some reason, we
> are also setting up an emergency IT hotline be to used to notify the AMS IT
> department, whatever the hour. This number will be activated within the next
> 24 hours and I will distribute the phone number to the entire community as
> soon as I have it available.
>   
I think this will be very helpful. And now: everyone store that number
somewhere locally. Don't expect to be able to go to the IETF mail
archives to search for it at the time that you will need it.

Jari

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf