Re: Call for Community Feedback: Retiring IETF FTP Service

Keith Moore <moore@network-heretics.com> Tue, 17 November 2020 23:22 UTC

Return-Path: <moore@network-heretics.com>
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 C2D133A0F4A for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 15:22:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 6pKK5g7EbJwr for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 15:22:03 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94EC83A0F47 for <ietf@ietf.org>; Tue, 17 Nov 2020 15:22:03 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 0EA855C027F for <ietf@ietf.org>; Tue, 17 Nov 2020 18:22:02 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 17 Nov 2020 18:22:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=vpgajgpaoPZYKy6K/qacYxCY2RpsRiyfTnQDI66UU fU=; b=PGS4KHKPOh+BsPNDzRMvbj3vIro7ucZkmvNoZ6s9nVXenUiKO2njENFjH BTFjQo7/DL6lGAMg79Z+K2E0k6Yiw2646oQGLYhIJ+7cxtFzvNHkgxJUfARBC30A vbrZSoeCTG9XNMH7qAE7ZSCf/lVduun6nrUHgmCyRpmmoCaW4YTemv4KWk0uksf/ ECEPM4LCy5VKgqshDpU+HO9S4c9KJ0V4FgFZA2iHQuKwTcA90ewK9Z/R98fzimwo 6QLLYJElTACeemojvm/pQjIg4BiGqfO0dN1wh94ibqiH/MFoH8wykQrTIFDYC1Pi dnjP0iP34qnaF4P6aVSvAal4X/HnA==
X-ME-Sender: <xms:GVu0X8rhKdXI8-bCiEeCRTUOVddOHC8crFPyNG7dk11wUNrcTibkzA> <xme:GVu0Xyq73v3WuzZY_RB26LCcFWs9rXuyWBCevmSH1w48ujQd3Y2D-lxZcgbNSL5mj kHJ4qilbgP_lA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudefgedgtdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeehhfeutdehfe fgfefghfekhefguefgieduueegjeekfeelleeuieffteefueduueenucfkphepuddtkedr vddvuddrudektddrudehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:GVu0XxPFFSJg0VBd5Z5DhU9cb5DvG2jtq5zF0AB7KuReyyp3oKyZrw> <xmx:GVu0Xz5nu37qydzlmooo92VWGoIEV_xPF_cbq01tETlGfbg_o6n79Q> <xmx:GVu0X75t-IGWmZpLR5fWEdHiGRMR0yBPtOwYL_RMYeKEWJvKgAx2RQ> <xmx:Glu0X-KHlpHzcFmtTz8bVkOSmFRQc0EIU1u87FTvHzq3cFLWRFYEaw>
Received: from [192.168.1.85] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 871D8328005A for <ietf@ietf.org>; Tue, 17 Nov 2020 18:22:01 -0500 (EST)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: ietf@ietf.org
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> <20201117231100.GC538542@mit.edu>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <9b36bfca-5c8b-b156-af72-416ee3f1d02d@network-heretics.com>
Date: Tue, 17 Nov 2020 18:22:01 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20201117231100.GC538542@mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ff1qs3jFcQKauFBLlgtq63mVwhk>
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:22:05 -0000

On 11/17/20 6:11 PM, Theodore Y. Ts'o wrote:

> 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 assume you've also done some of this before.    As I understand it 
there are practical limits on the number of witnesses that can be 
called, some witnesses cannot be used because they've assisted other 
parties in the case, etc.   All I know is that I've had law firm clients 
ask for such dates and be willing to cite them.
>> (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.

Well, I do have experience to draw from about this.   So I disagree.

Keith