IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Keith Moore <moore@network-heretics.com> Tue, 17 November 2020 22:58 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 2F62B3A0E68 for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 14:58:38 -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 5LtdNBfgi427 for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 14:58:36 -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 CEEE63A0E6F for <ietf@ietf.org>; Tue, 17 Nov 2020 14:58:36 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 148CE5C0312; Tue, 17 Nov 2020 17:58:36 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 17 Nov 2020 17:58:36 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=tHqxRB2PwKDjw4aqMORCGcJ6+/9DYUIPp0Rk/OaL3 Y4=; b=GEVrEryDJiz6H49FMxRdKb1Qg6O20BBd1BI8aC4o3aNLj49BvhehXaY7T qxNxY83Gkz13I1WWv61u92/vSlxMNjrUFElgC20v+UbYnqSO1i5YNttYnEdJJiuj 1k1gj9Qqkq3jq4aZYH7zzwhWovsc1Q6caN3sPjdJCCUOIK8w5d1fnNL3LwSudzHh yyzKY4Gnaf80sH6zMgSSemNEI7jcP1yye92MbgkY79G+gjvblUTrQO2XOzzAvsi/ mBj9Hkz9vamnFERnYVNy9uEICBQ+Yru2I0sGgKchhbOqvBKD+FGiBgnzVNvUJ9Rh Jv0ualWPWAhIkF0m/ol8QlbT1P7vA==
X-ME-Sender: <xms:m1W0XwcsQ_w2xx3hPdXf8FBcHPXdmZJNFVKpfIeezupJZhvYn8z86A> <xme:m1W0XyMlkrI8B5MVHIcR93PnzYYvQzkJhol50pTHQhO73MnqhEOyAsc2Qwot30ZYH 48ipkHSCtopxw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudefgedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeehhfeutdehfe fgfefghfekhefguefgieduueegjeekfeelleeuieffteefueduueenucfkphepuddtkedr vddvuddrudektddrudehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:m1W0XxiaO-Pbwt7BZ84Z-I6MNG5W3p9fTQ3ylJNAMU_rq1RsFnGVZQ> <xmx:m1W0X1-Y1W_NlXos5Cd0ZYepGWXhidzrKNrhIb0Zdlc-mlVgrXPaEQ> <xmx:m1W0X8v-rpqV4bjMML1SgjmHT06O5mLM1TNDX6hl5VyCqci4e8-1Vg> <xmx:nFW0X65wVH9CuHUQfVKcjcv6XYfLSAvQfJFoPjb27T9gjR7SrfjKGA>
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 37A8E3280064; Tue, 17 Nov 2020 17:58:35 -0500 (EST)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ietf@ietf.org
References: <a8bdd67a-13ea-4433-aa38-9cfd48ea28da@network-heretics.com> <0e875497-9986-a0d9-8354-3eac26b7f882@nostrum.com> <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>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <94ad1eb6-38ea-2912-3cc7-2c8c505cdcb5@network-heretics.com>
Date: Tue, 17 Nov 2020 17:58:34 -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: <20201117224752.GA538542@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/Z7aCd-R2POdFtylcrfnCv_9xnFg>
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 22:58:38 -0000

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.

(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. )

I was also once involved in a case where the RFC Editor screwed up and 
the mod date on an RFC on their server was incorrect.   The declaration 
was edited to omit mention of that RFC to support the argument, even 
though the RFC editor attested as to the correct date, fixed the mod 
date on the server, and verified that their copy exactly matched the 
original.

So basically - preserve the dates and make sure they're available via 
the protocol.   It's not difficult.

Keith

v2.23.0 | Report a Bug | By Email