Re: Call for Community Feedback: Retiring IETF FTP Service

Larry Masinter <LMM@acm.org> Mon, 16 November 2020 16:43 UTC

Return-Path: <masinter@gmail.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 21BF93A12A3 for <ietf@ietfa.amsl.com>; Mon, 16 Nov 2020 08:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level:
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 gmv1ENKWzcda for <ietf@ietfa.amsl.com>; Mon, 16 Nov 2020 08:43:25 -0800 (PST)
Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) (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 257AE3A12A8 for <ietf@ietf.org>; Mon, 16 Nov 2020 08:43:13 -0800 (PST)
Received: by mail-lj1-f177.google.com with SMTP id 11so20910449ljf.2 for <ietf@ietf.org>; Mon, 16 Nov 2020 08:43:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oTgsA3rzZeULdvDXb5mUhb4O99HjDGYY3lLflr/rcRI=; b=TVUy96ex6WwhZX1ujdK1n+bmHYOFkJyOWdaBn7yLPolSI6bZlY29XktGyF4jDrvVUV UZSVJIAvvz/6UKpDUtQD759pPSRCFmp8wKyV8sA4aicR02Mvqr4/Ooy+Kpr5uITGKabc tGTxPsrk9ninUVRXbqM9hrzbtK7jZO9FyxUZmyettLbLYZpcyQfoU8dAkX0pZ/HeJ2yV Popie52oSvgwusXoEMXpIJQFnIDhS2dAHtq6lP1likRP1xZaHQEuJ/nqRWnbdnaV8eSD B4qxtQ7nPpVbS3uRu0WdnnuHUAu1GFhTyCfku2oe3b3iEXQHO7HaBswZxJCjhvgSBP7u fOJg==
X-Gm-Message-State: AOAM532F4Pc6u8fTMcYPsby8VfL9h2pFI/yMkCUwXaL4Stc2dCctzI9C zn229kSLYHjSJafWHwIkr7pUA/DqYhhvbjiEC2qyCP5b
X-Google-Smtp-Source: ABdhPJyiAyfnY13q6401s/q3hkq4EckJj2uakou007T2ZebmHdYHN0OTEZV2Iy3xmkVP4GVKOcQYz/Q5EyxSWGHCX4I=
X-Received: by 2002:a2e:7607:: with SMTP id r7mr97320ljc.156.1605544991171; Mon, 16 Nov 2020 08:43:11 -0800 (PST)
MIME-Version: 1.0
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com> <37c218db-0373-879b-1b68-01e50e4cc34b@network-heretics.com>
In-Reply-To: <37c218db-0373-879b-1b68-01e50e4cc34b@network-heretics.com>
From: Larry Masinter <LMM@acm.org>
Date: Mon, 16 Nov 2020 08:43:00 -0800
Message-ID: <CAKq15vfvwCe384i4cH-Z-anc9SMHwbsXDBzoEwX19CfO0C3kFw@mail.gmail.com>
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: Keith Moore <moore@network-heretics.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dea9a005b43c1263"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2Ir9MUzPgD3hJMmfPArruDXPd0A>
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, 16 Nov 2020 16:43:26 -0000

I think the cheap solution to this issue would be to build a FTP / rsync
gateway which rsync'd the available data and offered the data with FTP
services. I'd budget $500 to build such a service and $20/month to run it,
depending on how much data there is, although it's likely to cost less.  I
imagine some enterprising engineer would build it for free in exchange for
permission to include a one-line acknowledgment to their engineering
cleverness in the FTP service's greeting. Build it as a docker container
based on a small linux distro.

The only problem I see is that port forwarding from ftp://ietf.org but I
imagine someone around here could manage.
--
https://LarryMasinter.net https://interlisp.org