IETF Network Maintenance Announcement

Glen <glen@amsl.com> Wed, 16 July 2014 17:06 UTC

Return-Path: <glenams@gmail.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3AE11A007A for <ietf-announce@ietfa.amsl.com>; Wed, 16 Jul 2014 10:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.278
X-Spam-Level:
X-Spam-Status: No, score=-101.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 qyVVEzYx249s for <ietf-announce@ietfa.amsl.com>; Wed, 16 Jul 2014 10:06:55 -0700 (PDT)
Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 062E71A0076 for <ietf-announce@ietf.org>; Wed, 16 Jul 2014 10:06:54 -0700 (PDT)
Received: by mail-vc0-f169.google.com with SMTP id hu12so2281892vcb.14 for <ietf-announce@ietf.org>; Wed, 16 Jul 2014 10:06:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:date:message-id:subject:from:to :content-type; bh=Fuv4P/HAo5eI5AcBAbYP1wfEdz6mnJ7eIiNBSwgL3nI=; b=z5DG0Qn3shSGMk5isaMyG+jWnPW/Mz1joCfDZPkrC3uESjzTOMJOevG+0S+86CnH+8 GBd5yoCi0XEtXuyB9dcXvPiGkDw+4AE6s3/MiEjvJh0nZeZveg/JhLw2B7a/I4AonSkU XJebBzI4z/bSdRn3bje3y5gn7zLegVwAj+xFPwe/dZHPHDdkXLqhoU0AxxNoVA+Y/Qx9 qAIdqIglyuazeMO115K6jY9r2lSTOHN/M23+RVfKL1mnd1lmWj8g33zORim7x4BCH1Og Rxk/fEzEArW2iMRBTcbJlnPZ4Jf9P3TAlm5rN8i4XcmWGYJbHkUbW5p9qI0HxoFIZBXz EM9g==
MIME-Version: 1.0
X-Received: by 10.220.81.194 with SMTP id y2mr16714204vck.29.1405530407614; Wed, 16 Jul 2014 10:06:47 -0700 (PDT)
Sender: glenams@gmail.com
Received: by 10.58.245.227 with HTTP; Wed, 16 Jul 2014 10:06:47 -0700 (PDT)
Date: Wed, 16 Jul 2014 10:06:47 -0700
X-Google-Sender-Auth: j43T04QV2JCdHPN-7mWdWtUM-lg
Message-ID: <CABL0ig7nKLtprbAh6rRjBzv5XyfK-7O_-J4SMFjvfASw1eU0WQ@mail.gmail.com>
Subject: IETF Network Maintenance Announcement
From: Glen <glen@amsl.com>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/XMgfTH8Nc-6bZ-7w2XU2A4yPV5w
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org, glen@amsl.com
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2014 17:06:57 -0000

IETF Community -

Level 3, the provider at our primary colocation facility, has notified
us that they will be performing a card swap and software update on the
router serving the IETF and RFC-Editor servers on Thursday, July 17th,
beginning at 0800GMT.  Procedures of this type generally take about 10
minutes, although things can certainly go wrong, and cause the outage
to take longer.  Because of this, Level 3 warns that the outage might
take as long as 2 hours, so please be prepared for that possibility.

As you may be aware, the IETF public website is now supported by a
content delivery network, and so the public website should not be
impacted.  Note, however, that the Datatracker will be unavailable
during the outage period, as will other dynamic services such as the
RFC Editor website, Mailman, the mail archive tool, and Jabber.  Those
services are not cached by any content delivery network.  Email sent
to mailing lists will be held by your sending servers, and forwarded
on automatically when the upgrade is complete, but list traffic will
be halted during the process.

AMS staff will be online during the outage window to monitor and be
online during the upgrade process.  Please be assured that we are
aware of the planned outage and will be watching it.  Thank you for
your support as our colocation vendor performs this upgrade.

Thanks,
Glen
Glen Barney
IT Director
AMS (IETF Secretariat)