IETF Logo Mail Archive

[Tools-discuss] Re: [EXTERNAL] Re: Re: Fwd: Brief outage for the RPC infrastructure tomorrow (15May)

John Levine <johnl@taugh.com> Fri, 17 May 2024 01:47 UTC

Return-Path: <johnl@iecc.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 23FD7C18DB86 for <tools-discuss@ietfa.amsl.com>; Thu, 16 May 2024 18:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.149
X-Spam-Level:
X-Spam-Status: No, score=-4.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="H97Q5QoK"; dkim=pass (2048-bit key) header.d=taugh.com header.b="QtOqoUhg"
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 tkHsxhReApgu for <tools-discuss@ietfa.amsl.com>; Thu, 16 May 2024 18:47:40 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496DBC18DA39 for <tools-discuss@ietf.org>; Thu, 16 May 2024 18:47:39 -0700 (PDT)
Received: (qmail 39485 invoked from network); 17 May 2024 01:47:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=9a376646b73a.k2405; bh=q5LeJDcolD8bAVzJKJPW5G8nQh84RE1mVLpD3LKHq1o=; b=H97Q5QoK2VcxdiLocowDsC1AOvVH2KRm6Y9Oc+tHGOLskstli6y7uE9YJG1pkqJaw7lYnRKD6uO+RhTtQ+zJ9tHFtPgSilD6Jvz7hj6ZsBVo8Kj1JYRwjl5IwFyKDEf/RvrRDzMN7PdsWa/cGi0EYb4RAHn8iVhEoeAlheRgKyGA7qR4fuXvpHYcPYAtr1zfGA1EOm0oaqGfDYW6Vagosxt0behdmqYejaLDWEDQJDOgDb6oI3e97jKHTw40h6Dx5dT/TDHfKyt+dI1uM1IQF595zjKx9zs6vMpLDEYGD8bOiWx0nShURD7ahpy/+7po1J6B+5r2BWt7Wzt1uTltkA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=9a376646b73a.k2405; bh=q5LeJDcolD8bAVzJKJPW5G8nQh84RE1mVLpD3LKHq1o=; b=QtOqoUhgrfYWDsX5CbTe96lzryhAIGL/NtoH7C95MblGHDAIlFkUDqLFPn88MW1+zKgALVIPzmRHSMqYHLar2Ov5y5XD/OILlkT7ynNnhQ9NHozQz+Sl1J584tVN+mDdSvmYFQLMzbZLqxw2oPougQPebE/NCOpaOfD/JVFVj96kQeXCqmPVltVCLSBfBKZYGDuKwXFSMA/EH0zVgtDhiW+hAXJjSr2qa7nDUzMnxdCYluGmOxo0c/bRxn1FHdbV2VIqZcKnUht6qDgd13O6QsB38l4ZqeJCxigyTqLgW3df9d0cPhqg15V8gzyy0ijcXTFbcrHVEN+Mc6to3uoTwA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 17 May 2024 01:47:37 -0000
Received: by ary.qy (Postfix, from userid 501) id 3ED558B5947F; Thu, 16 May 2024 21:47:36 -0400 (EDT)
Date: Thu, 16 May 2024 21:47:36 -0400
Message-Id: <20240517014737.3ED558B5947F@ary.qy>
From: John Levine <johnl@taugh.com>
To: tools-discuss@ietf.org
In-Reply-To: <CABcZeBOiTk0hw=UoSUGnhaHh7=_NwvfdyboNyw_1s1bpy6oo1w@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: WMZT7LANHXE7PZ43NRXF5I3AJB5DBZNX
X-Message-ID-Hash: WMZT7LANHXE7PZ43NRXF5I3AJB5DBZNX
X-MailFrom: johnl@iecc.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
Subject: [Tools-discuss] Re: [EXTERNAL] Re: Re: Fwd: Brief outage for the RPC infrastructure tomorrow (15May)
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Rtb_1dIy3rjmC5AcH0srycpk1Qc>
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>

It appears that Eric Rescorla  <ekr@rtfm.com> said:
>Retrieving the documents over HTTPS provides both:
>
>1. Confidentiality of which document is retrieved.
>2. Integrity of the document contents (to the level that this is what the
>server currently believes).
>
>FTP provides neither of these.

You're right, and if we had reports of maliciously tampered copies of
RFCs floating around or a lot of politically sensitive stuff in RFCs,
I would be more concerned.

We have better ways to transfer documents including rsync and https,
and it is fine to encourage people to use them, but in a world where
there have been unsigned copies of RFCs floating around for 50 years,
FTP tampering has to be rather low on my list of things to worry
about.

I would be more concerned about the effort needed by the RPC to keep
the FTP server going, but if their FTP server is like my FTP server,
looking at the same files the rsync and https servers do, the extra
cost of FTP rounds to zero.

R's,
John

PS: On the other hand, the Googlebot got stuck in my FTP server a few
weeks ago and was hammering on it several times a second listing the
same empty directory, which was just strange.

v2.46.0 | Report a Bug | By Email | System Status