[Tools-discuss] Deferred: IETF mail service outage

Robert Sparks <rjsparks@nostrum.com> Tue, 03 September 2024 12:45 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D43AC180B67; Tue, 3 Sep 2024 05:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.522
X-Spam-Level:
X-Spam-Status: No, score=0.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_DISCARD=1.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tdPCFQWlU_5c; Tue, 3 Sep 2024 05:45:31 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4180EC15154D; Tue, 3 Sep 2024 05:45:31 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.18.1/8.18.1) with ESMTPSA id 483CjT6m090761 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 3 Sep 2024 07:45:30 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1725367530; bh=3cv0Hilf5++ZQU85hEvY4vMQX8NODq+gHEzJZ/dqZ3w=; h=Date:Subject:From:To:Reply-To:References:In-Reply-To; b=rhjmxKI504Pm4UqIZqdnJ9fAjQE7xZ0gkkLh+Z8SA54jWKVnec75iw22lc8GNh0/l pdpdNG6rvJag2jE/YJdYUk/XVJoRje1HkAYe11szPhLLOM58EljVYUqNlGWElLOiQh WkDAIpgk7iHpCUYnzXYdk3exFP+OAI9+W12NIhFw=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Content-Type: multipart/alternative; boundary="------------jvLRzqHdnEOdqXM0GKGcTJO2"
Message-ID: <0a8c48cf-ee80-46c4-b0ee-949da79cfecf@nostrum.com>
Date: Tue, 03 Sep 2024 07:45:24 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Robert Sparks <rjsparks@nostrum.com>
To: tools-discuss <tools-discuss@ietf.org>, Working Chairs <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, "irsg@irtf.org" <irsg@irtf.org>, RFC Interest <rfc-interest@rfc-editor.org>, RFC Editor <rfc-editor@rfc-editor.org>
References: <e5cfd2c6-ac65-4d7f-9dc2-290651ae1b66@nostrum.com> <a01627b1-3d77-4fe5-9d59-f6cced37aafd@nostrum.com> <fc2dbf43-a368-4bf1-9aae-3afddc1212ac@nostrum.com> <ca11206e-5325-4587-b577-9d6683c99839@nostrum.com> <e63b9bc1-6251-481b-bfcb-47f75e303f7e@nostrum.com>
Content-Language: en-US
Autocrypt: addr=rjsparks@nostrum.com; keydata= xsDNBFx4PQwBDADIIJqFKIeYNmVR3iH8YnNqwApV+ci83VqFaPg0UXZAZ1utH/2O2LOLJKmV Ol11+lOSfH4OJgpARt37PWbqfG2TzzGfEucRBPMAV8TEDmzKL+7/OUMLEoPeexgxz6ADxK2Q ACKKzHhF30y4fx2fn9rYZrCvYHV9HDKcfFotNLna0U6P6wu70L0mT2hcjQgZ7+8HSZCpK2XG PTya1mEiMklH6+UHfcTLoAxd3chQiseRi19/TQZZCD3LuuaGFWyTIeF9ZNWV9yL0HQeb/XMs tmZnObSSHSUbZwn5PR9Uf+3iW7jdG5JuXBvNbDpAHfLyPXRqxErM/nCLrbwGB6AgNSKFCwkL lb3uxsGFWcOt6sedrjixoVUO2k4zQWVnCUCwFHGrgIxUK24dI8oqydGPctXAKj5VqoCVJBv6 4JxSpiR+V8fl3A8gksBUnuIMLNlRjB5RAgZaSUpaOkXsWUBA8Z75wQWoIzkJIeMm29w2l1kB B9kGMdyiXGr2JV8VQZ4lAscAEQEAAc0kUm9iZXJ0IFNwYXJrcyA8cmpzcGFya3NAbm9zdHJ1 bS5jb20+wsEUBBMBCAA+FiEEGNywdGDCHUYBwWN3bipqV3X5ExgFAmXhDnYCGwMFCQ0rmNQF CwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQbipqV3X5ExiEpwwAknrYjNHDI2l50IC1lpQB SnmCLvuu4pEESpRaBx1Te7vZBHr740dMbKQv/ZYYekw/NfFfoq2Ptguz5BXHwtyx3hKKjBUA U/rP62bl+x77yTJ0+I5k2hJ1p1DWNqXHWK3SEM0IUvjWpMGlfXPu7iVYCBGPKBDglQ4GWpzU HmSAX/8Zww6+ZbrXM0VgA+hLSHivyHextX4mJwoLRcuY99ecvkdWwFnKoDlEsKozdv9NW+QT h1rFvAtXf2ZCGwIveAMJPbHbRY3uFVp+oMvBbP7m5teffB8Ki5kuO1Y1Wqd9UPhiVDZmUuyC PXymQErskbOB6DcNSSFH7ZHuLM4V+zyziYWTT6foBv0ynA+a3Ofxo+rKPVHLybZlO9bQcI0Q TIE8yT0oqd3kWMaMIyrKZURVUpzcDgRnx6ujckLLyAC1H8L0tuntPwZOo5PAq3P7SUiWlc0L 5HbA0L//BE6eeWn6U3xOgaJNF2+YRVICNtWpXcR3Mr4k1uXW4JkE7lyoufbnzsDNBFx4PQwB DAC03e1kk41e9Z9FuVW8UKWIkVUBeH3gfJMsb94d/c0cqBMRw5rulSY7+U76rw4AXo792LZn ydjDfoL0GQxGqkrZh397Sn9P/sLCb5I+wC14251nkmh5tmU2sQqCk+g9nykcE/NJft/zFkeb HHCKAosK6glO+W0YPHc/k7nXt/fLz7dMRpFpmqFXWjeN2VtwKr9znMg9+iX6XfgAJPMdDNH8 fn30Cp5TIsn5WCI70+JztgvfjFhD15Eb3rtDdOfOydjGCV2ZVxfM8ECmc8Z3DrThyiC2M3uo 2Y50rs6MH+TmVCtpHkISnH7B+80Vy2SC60K9l2xgCaezN1SlkQy3ZpprzcDrNTI8FcJa/UUM ayMGvSDGEGuHZRaNUyXP3jQ8oss+067axmNr5vgjpf01kmE1RJtiGEDWmCr8u1SbVQjdax6C pDqq3RKoX2ZVGLtkdDYZbsqSq4TgmFukoijWRbLxsFBdeEgruTViWRw4PKZav0piLxrhHUGI m6F6JFngapUAEQEAAcLA/AQYAQgAJhYhBBjcsHRgwh1GAcFjd24qald1+RMYBQJl4Q52AhsM BQkNK5jUAAoJEG4qald1+RMYaCML/jp+3W9OedMRVk5XQ3Urxu7g09qaeAfBAArLlE7F13Xt WuGUN7JwZ8hZt8Rsx1+Uz/Zq2TIPjl8PmgIqCSkuvZrxacr+drYARtO00Af71qHVoh4gZTae iOwEuOGhhtCVI3vvKLMDv1ex0scvD4rJTsIk/zqEDCJNDVOf09Szj0CW0vJOYxrIV0sG/UoM 7Ui5/eB4tlN5AFIXuTJzo6BzaUAJVut74Ss2i93qwtwjGw44iEqPVhqKMCDYuB9+bm13ft+H Vr7viRZobd+60NTWrfZhkpmzhb4Qiib9qXhrUoa2EXqVOIy+LMQoiwjF9/iK+5FSA18c52FP ODkDgkica826W9AnBasS6gXQr0bO1BCJu84Fp2RQcjB4IFP+sKVoN3EZTByyUKK4NnSLF3lJ /G+vQhisnuJS+e+emZ8UxZBOK8upAhrhHJj0Wju2W0uTQTxlBME0/uNsvA/KaudLNhlQiUYN 7Fl3rswvQk/iD+utnQdWJbRgIsqesNXbQCOimQ==
In-Reply-To: <e63b9bc1-6251-481b-bfcb-47f75e303f7e@nostrum.com>
Message-ID-Hash: IZPPSUEDQFCNAAGX25CSHEWJM7IKHLPX
X-Message-ID-Hash: IZPPSUEDQFCNAAGX25CSHEWJM7IKHLPX
X-MailFrom: rjsparks@nostrum.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Reply-To: tools-discuss <tools-discuss@ietf.org>
Subject: [Tools-discuss] Deferred: IETF mail service outage
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/UW0URt-jtzitoRPHrK3_nxHPVSc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

Today's scheduled outage of the IETF email processing system has been 
deferred againto allow time to complete further work discovered to be 
required for a successful transition.

The current email processing infrastructure remains in service.

An updated schedule for the transition will be announced as soon as it 
is set.

RjS

IETF Tools Project Manager

On 8/30/24 11:41 AM, Robert Sparks wrote:
>
> The previously scheduled outage of the IETF email processing system 
> has been deferred to 3 September 2024 at 1200 UTC to allow time to 
> complete further work discovered to be required for a successful 
> transition.
>
> The current email processing infrastructure remains in service.
>
> The timing and duration of the outage on the 3rd is expected to be the 
> same, from 1200 to 1400 UTC.
>
> RjS
>
> IETF Tools Project Manager
> On 8/29/24 7:44 AM, Robert Sparks wrote:
>>
>> The previously scheduled outage of the IETF email processing system 
>> has been deferred againto allow time to complete further work 
>> discovered to be required for a successful transition.
>>
>> The current email processing infrastructure remains in service.
>>
>> An updated schedule for the transition will be announced as soon as 
>> it is set.
>>
>> RjS
>>
>> IETF Tools Project Manager
>>
>>> On 8/27/24 7:43 AM, Robert Sparks wrote:
>>>>
>>>> The previously scheduled outage of the IETF email processing system 
>>>> has been deferred to 29 August 2024 at 1200 UTC to allow time to 
>>>> complete further work discovered to be required for a successful 
>>>> transition.
>>>>
>>>> The current email processing infrastructure remains in service.
>>>>
>>>> The timing and duration of the outage on the 29th is expected to be 
>>>> the same, from 1200 to 1400 UTC.
>>>>
>>>> RjS
>>>>
>>>> IETF Tools Project Manager
>>>>
>>>> On 8/22/24 8:57 AM, Robert Sparks wrote:
>>>>> As the final major part of the transition of IT infrastructure, we 
>>>>> are planning an outage of the IETF mail processing system starting 
>>>>> around 1200 UTC on 27 August 2024. The outage window is from 1200 
>>>>> UTC to 1400 UTC. The actual outage duration is expected to last no 
>>>>> more than 1 hour.
>>>>>
>>>>> During the outage, delivery of messages to addresses at ietf.org, 
>>>>> iab.org, irtf.org, iesg.org, and rfc-editor.org, including email 
>>>>> lists, will be paused. The goal is to deliver all mail received 
>>>>> during the outage once the transition is complete. However, it is 
>>>>> possible that some mail meant to be received during this window 
>>>>> will not be recoverable.
>>>>>
>>>>> This transition is being undertaken by Sirius, the company 
>>>>> selected to migrate the IETF’s email processing systems to a new 
>>>>> cloud infrastructure and manage our email and mailing list 
>>>>> systems. [1]
>>>>>
>>>>> This transition will move our primary mail sending to be through 
>>>>> Amazon SES. The relevant SPF records have already been updated. 
>>>>> Further preparation is currently underway and is expected to 
>>>>> continue until just before the migration begins.
>>>>>
>>>>> An update will be provided once the work is complete, and no later 
>>>>> than 1500 UTC on 27 August 2024.
>>>>>
>>>>> The current system has a large number of moving parts accumulated 
>>>>> over decades of customization for the IETF community. This makes 
>>>>> the system exceedingly complex and the transition especially 
>>>>> brittle. If the transition can not be completed on 27 August we 
>>>>> will revert to the current infrastructure and reschedule the 
>>>>> transition.
>>>>>
>>>>> Issues encountered after the transition should be reported to:
>>>>>
>>>>> support@ietf.org
>>>>>
>>>>> These will be forwarded to Sirius for handling.
>>>>>
>>>>> RjS
>>>>>
>>>>> IETF Tools Project Manager
>>>>>
>>>>> [1] 
>>>>> https://mailarchive.ietf.org/arch/msg/rfp-announce/8Ar1AodThJvj6Ro0WxPnIj2SOk8/
>>>>>