IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

"Theodore Y. Ts'o" <tytso@mit.edu> Tue, 17 November 2020 23:11 UTC

Return-Path: <tytso@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 153B73A0EE2 for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 15:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 hJ25IALvjSRY for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 15:11:03 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D11D13A0EE0 for <ietf@ietf.org>; Tue, 17 Nov 2020 15:11:02 -0800 (PST)
Received: from callcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0AHNB0rT026662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Nov 2020 18:11:01 -0500
Received: by callcc.thunk.org (Postfix, from userid 15806) id 8B925420107; Tue, 17 Nov 2020 18:11:00 -0500 (EST)
Date: Tue, 17 Nov 2020 18:11:00 -0500
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Keith Moore <moore@network-heretics.com>
Cc: ietf@ietf.org
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
Message-ID: <20201117231100.GC538542@mit.edu>
References: <a02e15f2-34fb-4124-7ba0-c0ee0070b39f@network-heretics.com> <6a29096e-c76e-9bde-388c-bf411b235346@nostrum.com> <6ff3c8a8-57c9-a278-51ce-ce24fd2dfc0e@network-heretics.com> <01RS3W7DNPHA005PTU@mauve.mrochek.com> <17A1F2FA-CFDB-4775-8E50-A7842E45F5A7@cable.comcast.com> <3b47a817-0884-2379-6654-cd8d6c2d914b@htt-consult.com> <fcd7505d-f21d-5504-a3fa-e87ea222ac11@nostrum.com> <41d6f9eb-20a7-4547-859e-2eef5aedd3b2@network-heretics.com> <20201117224752.GA538542@mit.edu> <94ad1eb6-38ea-2912-3cc7-2c8c505cdcb5@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <94ad1eb6-38ea-2912-3cc7-2c8c505cdcb5@network-heretics.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y_LXxCNf25I8L6PoUPTqb-PBTgo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
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>
X-List-Received-Date: Tue, 17 Nov 2020 23:11:04 -0000

On Tue, Nov 17, 2020 at 05:58:34PM -0500, Keith Moore wrote:
> On 11/17/20 5:47 PM, Theodore Y. Ts'o wrote:
> 
> > Whether those dates are returned by http or ftp, they're going to be
> > trivially foreable
> 
> So are the dates in old email and usenet messages.  And yet, such dates are
> routinely cited.

Note that I said that this would be combined with the **sworn**
testimony of the owner of said e-mail archive.

> (I don't claim to understand a court's or patent office's reasoning about
> what makes a date valid or not valid - their logic is different than those
> of engineers. )

Yes, which is why it's not particularly a good argument for preserving
FTP on IETF's servers.

As others have said, most of the arguments on this are pretty weak on
both the "pro" and "anti" side.

					- Ted

v2.23.0 | Report a Bug | By Email