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

Adam Roach <adam@nostrum.com> Sat, 28 November 2020 00:22 UTC

Return-Path: <adam@nostrum.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 468D73A08B0 for <ietf@ietfa.amsl.com>; Fri, 27 Nov 2020 16:22:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level:
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 jnzuBroOrbAO for <ietf@ietfa.amsl.com>; Fri, 27 Nov 2020 16:22:19 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C8103A08AF for <ietf@ietf.org>; Fri, 27 Nov 2020 16:22:19 -0800 (PST)
Received: from [172.17.121.48] (76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 0AS0M9IB022864 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 27 Nov 2020 18:22:10 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1606522931; bh=RBljHwZjO8F5Mu4MqiC+OHehLxRRg2u/NlcVCTEk4t8=; h=Subject:To:References:From:Date:In-Reply-To; b=q/oDBjH1jkjjkqdRFUPm7SHXlBJ7u1TBYdoPTuBi//wDPLBk85L8n5rc4zOOzOjT4 u4CuCo2DaPfMghp/T0Hgd0ghbAKm3ElZukFyqxXqgR2i9cHOlIVZoP9uQ8lKeLOO6+ /6OgnTQEsnu+kMLGIRvs/klQiNYj+RayzVAKtjNM=
X-Authentication-Warning: raven.nostrum.com: Host 76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253] claimed to be [172.17.121.48]
Subject: Re: Regarding "Call for Community Feedback: Retiring IETF FTP Service"
To: Roman Danyliw <rdd@cert.org>, Keith Moore <moore@network-heretics.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> <dc23d86011ce43f39c8180cbdecd774e@cert.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <2d2bd9b9-8c45-c5b6-a371-5adac894a966@nostrum.com>
Date: Fri, 27 Nov 2020 18:22:02 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <dc23d86011ce43f39c8180cbdecd774e@cert.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QfLnuQ6XdV_UWzMwU09PfYOurpk>
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: Sat, 28 Nov 2020 00:22:20 -0000

On 11/26/2020 6:12 AM, Roman Danyliw wrote:
> Up front -- there is no way to currently mount a remote filesystem from IETF services with anytime but FTP.

So, that's not *strictly* accurate. Someone's put a FUSE wrapper around 
the rsync commmand in a way that makes the remote rsync module mount as 
a local filesystem:

https://github.com/zaddach/fuse-rsync

I'm not sure this is the kind of solution people would be happy with, 
though.

/a