Re: Regarding "Call for Community Feedback: Retiring IETF FTP Service"

Keith Moore <moore@network-heretics.com> Fri, 27 November 2020 14:51 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 BA4693A0F2F for <ietf@ietfa.amsl.com>; Fri, 27 Nov 2020 06:51:48 -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_H3=-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 lWF_pFZJ316T for <ietf@ietfa.amsl.com>; Fri, 27 Nov 2020 06:51:47 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BC193A0E93 for <ietf@ietf.org>; Fri, 27 Nov 2020 06:51:47 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 403ECD46; Fri, 27 Nov 2020 09:51:46 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 27 Nov 2020 09:51:46 -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=QvI3lZHFKT5IDwm3PfoEabh2ajGPyCZNf+VBSSZ2z Dc=; b=IX5O51PTN2EXhZbz3XxR/TL7X72usuqz11ZYHoMaL1xOI6gpOGys2bP5P PJ+AAdEDiHdEOYhADa86pIVAoldvMn+nX+F9OVgXvT2K/U0Sf76SgB5ZFxGqZ2Kd 9UXoCeda5cHke39I6IPXk6c7HRDwmzTBIw8DgjYpmfMv6g2k8g5paIK+4nGCsTjj 2JqK06FRAlFdocgAgDvwUQZ961f0nIXC1JTQ5za9IOQiYho1eTVrZfJpNnCD5dCV ghSY8x3aStTs3MYfjPdc21a41Phpn4S5mFENpvq0C0PyHiRG/FTbF0RlJeIBhDII HOTJUl1cFwQMayjl014FtQSxms4sw==
X-ME-Sender: <xms:gRLBX-tStunt5s6bRNEmV4Fasx5Wxi4POnn4CwJMhsrArlX9KPisww> <xme:gRLBXzeMutO_6uW4Xj5e0jc9mbjEQ2zQePrGoS0NYW1yx4R_estHbGNfYfvVY0Ce3 riWuF7wcFY4pA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehgedgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvihht hhcuofhoohhrvgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh eqnecuggftrfgrthhtvghrnhephefhuedtheefgfefgffhkeehgfeugfeiudeugeejkeef leelueeiffetfeeuudeunecukfhppedutdekrddvvddurddukedtrdduheenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:gRLBX5x1e6x8gxDfduRebNU58fUj1Jj2US8oGQux88RFjdmnhhzZUQ> <xmx:gRLBX5On7lS7G_WcGJkihhYFZd004F8P_J4d1TxIzPnx6yEMfiDi0A> <xmx:gRLBX-8v88UUwJrQAaSziSZgKa_PtMEpWDvZV2Qr6Iaa5BaXS4ibdA> <xmx:gRLBXxIQSNtAAD8t4cBSdymLyDkSbDmu9DA-xqJiS-_1L3PeRNwOpQ>
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 18184328005A; Fri, 27 Nov 2020 09:51:44 -0500 (EST)
Subject: Re: Regarding "Call for Community Feedback: Retiring IETF FTP Service"
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <AM0PR08MB37169603FE46A63AB67CC62CFAFB0@AM0PR08MB3716.eurprd08.prod.outlook.com> <CAC8QAcdwdokF8NKLhFgKS3LOPwvchRe0sTrMUH52095kYywY_Q@mail.gmail.com> <AM0PR08MB371609551C99B529A343BF29FAFA0@AM0PR08MB3716.eurprd08.prod.outlook.com> <0b606488-4e2c-3df8-9f99-7ee429c0e553@network-heretics.com> <AM0PR08MB371656AC76A3E527FEFB3140FAFA0@AM0PR08MB3716.eurprd08.prod.outlook.com> <082f3e6c-d726-af79-f7b0-947185aae9cc@network-heretics.com> <AM0PR08MB371689EBF636D14F3CE086D1FAF90@AM0PR08MB3716.eurprd08.prod.outlook.com> <53912733-914a-3c78-31a1-a3aae0b440ab@network-heretics.com> <AM0PR08MB371666E193744FCAC72B6DF6FAF80@AM0PR08MB3716.eurprd08.prod.outlook.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <19beb271-483c-174d-d01d-6d6ac094ffc6@network-heretics.com>
Date: Fri, 27 Nov 2020 09:51:44 -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: <AM0PR08MB371666E193744FCAC72B6DF6FAF80@AM0PR08MB3716.eurprd08.prod.outlook.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/Ri-UFEt5aoIwv2MVD_nIdr8-bHQ>
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: Fri, 27 Nov 2020 14:51:49 -0000

On 11/27/20 6:06 AM, Hannes Tschofenig wrote:

> I hope we can find a way to maintain our creativity and efficiency without using FTP.
>
> Our goal is to produce high-quality specifications of protocols that get widely deployed in a secure way. I believe there are is still room for improvement on all fronts but I am less convinced that the protocols used for fetching the documents we read play a crucial part in that story.

IMO, the effort to deny people tools that are useful for them, without 
actually providing any observable justification for doing so, does not 
bode well for IETF's creativity or efficiency.

Though I would miss FTP, it could certainly be replaced without loss of 
functionality IF IETF would support something that's equivalent (rsync 
doesn't seem to be, but WebDAV might), AND several dozen or maybe even 
hundreds of participants were willing to retool.   But disregarding the 
effort required on the part of participants to retool because it's 
Somebody Else's Problem does not reflect well on the organization's 
leadership.

More broadly it seems like many participants in this conversation 
believe that everyone should work and think like they do, and that 
everyone else should be considered obsolete.   That doesn't bode well 
for IETF's creativity or efficiency either.

And the evident bias against open standard solutions, among participants 
of an organization that has standardization as its purpose, seems like a 
Very Bad Sign.

Keith