IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

John C Klensin <john-ietf@jck.com> Sat, 28 November 2020 18:54 UTC

Return-Path: <john-ietf@jck.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 452793A0FB5 for <ietf@ietfa.amsl.com>; Sat, 28 Nov 2020 10:54: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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 r83QAttlGr5V for <ietf@ietfa.amsl.com>; Sat, 28 Nov 2020 10:54:37 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F38B23A0EBE for <ietf@ietf.org>; Sat, 28 Nov 2020 10:54:36 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1kj5Mh-000Nmi-Cp; Sat, 28 Nov 2020 13:54:35 -0500
Date: Sat, 28 Nov 2020 13:54:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: Julian Reschke <julian.reschke@gmx.de>, ietf@ietf.org
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
Message-ID: <9DFC5A3241B586AE58B4649A@PSB>
In-Reply-To: <e170d248-8559-a64b-eaa0-620d78746f1c@gmx.de>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <5FC24768.2020603@btconnect.com> <e170d248-8559-a64b-eaa0-620d78746f1c@gmx.de>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VP6sxNz8DaZKsafxPVaDZ-DmSVc>
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 18:54:38 -0000


--On Saturday, November 28, 2020 17:47 +0100 Julian Reschke
<julian.reschke@gmx.de> wrote:

> Am 28.11.2020 um 13:49 schrieb tom petch:
>> Retiring the FTP service will impair my ability to contribute
>> to the IETF.
>> 
>> For a long time, I struggled to download copies of IETF
>> documents in the form that the author intended.  The topic
>> arose on this list and I was pointed at the FTP service and
>> this solved my problems; the amount of work I could do in the
>> IETF increased.
>> ...
> 
> Ok, I'll bite.
> 
> Are you saying that when you open
> 
>    https://www.rfc-editor.org/rfc/rfc7230.txt
> 
> in a browser and do a "save as...", you're getting a broken
> document?

Julian,

In the hope of being clear about what we are talking about and
given Roman's repeated reassurances that none of the plan to
retire the IETF's FTP serices has anything to do with the RFC
Editor, would it be correct to say that you meant to ask about
the IETF's I-D collection, RFC mirror collection, and assorted
other documents available from the IETF to IETF tools sites?

I'd almost equally or more chagrined if the RFC Editor site was
producing broken documents, especially broken TXT documents (see
note sent a few minutes ago), but they are not the same question.

    john

v2.23.0 | Report a Bug | By Email