IETF Ticketing System Outage
Glen <glen@amsl.com> Thu, 15 February 2018 22:43 UTC
Return-Path: <glen@amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14F0F127871 for <ietf-announce@ietfa.amsl.com>; Thu, 15 Feb 2018 14:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 0U87R_5tEdjz for <ietf-announce@ietfa.amsl.com>; Thu, 15 Feb 2018 14:43:12 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81727124D68 for <ietf-announce@ietf.org>; Thu, 15 Feb 2018 14:43:12 -0800 (PST)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id AC7881CA3EC for <ietf-announce@ietf.org>; Thu, 15 Feb 2018 14:43:11 -0800 (PST)
Received: from mail-it0-f49.google.com (mail-it0-f49.google.com [209.85.214.49]) by c8a.amsl.com (Postfix) with ESMTPSA id 8B1D11CA3F1 for <ietf-announce@ietf.org>; Thu, 15 Feb 2018 14:43:11 -0800 (PST)
Received: by mail-it0-f49.google.com with SMTP id l187so8734ith.4 for <ietf-announce@ietf.org>; Thu, 15 Feb 2018 14:43:12 -0800 (PST)
X-Gm-Message-State: APf1xPA+J89j7glyF9Ztwcy5z19mHKEXfL1JBYAIxKBHrZEx/hYBDHJv ag3o3ULvRAeA2FO/FQOa0yNH5Xh6T7d74TTzIt0=
X-Google-Smtp-Source: AH8x224OEifrapNlrXbYhfvKz94KjQDcU0cf2A2aOCO0+6yomis1q7wd4oSnHmDYrDGk7xpXEiKeNRPZ/hmWSnot4ZQ=
X-Received: by 10.36.44.194 with SMTP id i185mr5468023iti.37.1518734591680; Thu, 15 Feb 2018 14:43:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.1.68 with HTTP; Thu, 15 Feb 2018 14:42:51 -0800 (PST)
From: Glen <glen@amsl.com>
Date: Thu, 15 Feb 2018 14:42:51 -0800
X-Gmail-Original-Message-ID: <CABL0ig5RWioZfPuHprYA=9nyG7n6Hetjj304Gmc4Ez=8K3Drzw@mail.gmail.com>
Message-ID: <CABL0ig5RWioZfPuHprYA=9nyG7n6Hetjj304Gmc4Ez=8K3Drzw@mail.gmail.com>
Subject: IETF Ticketing System Outage
To: ietf-announce@ietf.org
Content-Type: multipart/alternative; boundary="001a1143dc60d87e28056547f314"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/JS1FJZDVSAH1Vl-cy6PAugvNtiA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 15 Feb 2018 22:43:14 -0000
Dear IETF Community and Participants - As many of you know, the IETF uses a ticketing system, known as "RT" and operated by the Secretariat, to receive incoming requests for help from the community and to manage and respond to those requests. I am sorry to announce that there has been a partial RT outage over the past 24 hours, during which time some requests sent to the Secretariat might not have been delivered. As you are all aware, there exists an ever-growing problem with DMARC-related email rejections. Many of you are starting to experience this firsthand as your ISPs implement various blocking rules, and the side-effects of those rules are felt. Because of this, the Tools team, led (in this effort) by Russ, Alexey and Henrik, are working to develop a way of processing mail that solves this problem for all of our participants, regardless of related ISP settings or rules. To this end, a number of experiments are underway, and one of these experiments has, unfortunately, caused the loss of some emails sent to the IETF's Ticketing System ("RT"). Since not all emails and queues were impacted, we did not immediately detect this problem. However, once detected, we were able to fix it quickly, and the RT system is back online now. We now want to make sure that any unresolved requests sent in by the community are handled and resolved. Whenever anyone sends an email to our RT system, at one of the well-published addresses, such as IETF-Action, the RT system sends a reply with a ticket number. If you have emailed the ticketing system (or indeed any IETF staff or service addresses in IETF domains) within the past 24 hours, and have not received a ticket number, or a response back from a human, we ask that you please re-submit your request. We understand that this is an annoyance, but we want to ensure that nothing critical was lost. We apologize for this inconvenience, and ask for your patience and understanding with this issue as we all continue to work for a solution to the challenges at hand. Thank you, Glen -- Glen Barney IT Director AMS (IETF Secretariat)