Re: Call for Community Feedback: Retiring IETF FTP Service

Keith Moore <moore@network-heretics.com> Mon, 30 November 2020 18:39 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 4E7993A105B for <ietf@ietfa.amsl.com>; Mon, 30 Nov 2020 10:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4lSKlG8BFEUh for <ietf@ietfa.amsl.com>; Mon, 30 Nov 2020 10:39:51 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 016D03A1047 for <ietf@ietf.org>; Mon, 30 Nov 2020 10:39:50 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 3B726F69 for <ietf@ietf.org>; Mon, 30 Nov 2020 13:39:50 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 30 Nov 2020 13:39:50 -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=461KjWTx+Crpb0NmZD8DIM1B6LmBPfgmqS1NTNob/ f0=; b=bYjlXpDo0UDIQXtCfFL6Gi9RADG9POi/DRWu0VbaciN9Cs2Z6whjvYV8D PXFMxvXvrRuiNo1RUIQDjOedrPMfvZlZVYOkxPBhntmdsSfQ6pn6Dsi/jT+rw/d/ d6xu/J0G2pHqKt3Zapvn0TzleKPHoTPmU+ix8h/d3HkwbjUDLz4oGI2u2BUQECNE SOUkf4YeV8LsS0X11poGQcAvNWBOYI9C8++Tj3lvj9kXKlLRaAYzV31YmIr4sQZ9 IlbxuzMSZu7fD8U1OpB1kS997GHPhFDqktC8BmnEMimbxFz4IdgkLytyrvhgFQui Tw77X3PNes6oIbqOXcKbEL/3DMoQA==
X-ME-Sender: <xms:dTzFX0CrDh7sPnwhgpwmXrbXbW08W3QDPV0eXGPmGRa8lEdg33RlLg> <xme:dTzFX2iGEKG6gYZEVVZKYGafYPDQZsJXRZTSJpn8sgBE6Ln30qx1M4pyNNcasUecM Va7lXOj_he6CQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeitddguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepgfelveekie fgtdekuedvhefggeetgeefueeuieegjeelkeevgfdvleevhffgiefgnecuffhomhgrihhn pehhthhtphgtlhhivghnthhshhhouhhluggrshhsuhhmvgihohhufigrnhhtthhouhhsvg hthhgrthhfihhlvghnrghmvghonhihohhurhgtlhhivghnthdrshhonecukfhppedutdek rddvvddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:dTzFX3kCC3y6tpxCJIB9c3YPzH2RV-dll-fIlZdEHTRkLza-QEJT9w> <xmx:dTzFX6wvWC8_qhLccT4HRDYqopM4506HZNMcg-nS6K55c8PNjzPgbw> <xmx:dTzFX5SYNLqKv1G7Ylgs8JcBj8qqq7wxLLauiNt-74GK6PCtcOyKAg> <xmx:dTzFXzCpSA9BAg2NUnzaYknrG6bhH4buvy6dxhO4IlWe5XQHkhIBhg>
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 215B23280060 for <ietf@ietf.org>; Mon, 30 Nov 2020 13:39:49 -0500 (EST)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: ietf@ietf.org
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <5FC24768.2020603@btconnect.com> <e170d248-8559-a64b-eaa0-620d78746f1c@gmx.de> <69878065-D4F0-438F-A57F-B45F052CA94F@akamai.com> <5FC4E79F.5090207@btconnect.com> <AF1C8668-041D-425B-8350-0B70D3BE76D0@tzi.org> <a92c9bf8-2682-6150-a9db-d6185c6720ec@network-heretics.com> <8210e140-815c-1905-45a6-109075138a08@gmx.de> <1663649a-7f99-5eb2-3dd5-c146aebf6fa3@network-heretics.com> <01RSM30KYRKO0085YQ@mauve.mrochek.com> <f88ae3bbdc3b4beda88eb094dde85784@cert.org> <01RSM4KK2V5I0085YQ@mauve.mrochek.com> <63b7d79aabbf4ddf9256e8368958a1e7@cert.org> <CAKq15vd37ZkyyADKQAXC4J-vbkVORxrq8kTfuaW4VrxSEszDzw@mail.gmail.com> <602614cf63af411887ff6bf3a1803940@cert.org> <5FC52CF4.2050206@btconnect.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <d6701316-5596-9339-7eef-eccc1329d38d@network-heretics.com>
Date: Mon, 30 Nov 2020 13:39:48 -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: <5FC52CF4.2050206@btconnect.com>
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/H1W_BdcZHYf95Oc-5WURA142o58>
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: Mon, 30 Nov 2020 18:40:00 -0000

On 11/30/20 12:33 PM, tom petch wrote:

> But I don't have the option.  From my browser (IE) I only have 'Save 
> as ...' and the 'Save' option is greyed out and this is the behaviour 
> I am used to when accessing RFC-Editor, data tracker, IETF etc and I 
> think that that is the case for most if not all web sites.  My 
> alternative is to select all, copy and paste into a word processor or 
> editor but it is not an approach I would commend. 

When downloading a file via FTP, the client knows what the file name is 
on the server, and it's often reasonable to save the file on the client 
machine with the same name.

When downloading a file via HTTP, the URL might be anything at all, and 
there's no reason an HTTP client should assume you want to use that 
filename on your client.   So in practice an HTTP client should 
generally expect you to specify the destination filename as default 
behavior.

Keith