RE: Call for Community Feedback: Retiring IETF FTP Service

John C Klensin <john-ietf@jck.com> Thu, 26 November 2020 04:31 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 819BA3A083E for <ietf@ietfa.amsl.com>; Wed, 25 Nov 2020 20:31:02 -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 O2xQeEOcL3X4 for <ietf@ietfa.amsl.com>; Wed, 25 Nov 2020 20:31:01 -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 E68EC3A082F for <ietf@ietf.org>; Wed, 25 Nov 2020 20:31:00 -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 1ki8vq-0003Re-HQ; Wed, 25 Nov 2020 23:30:58 -0500
Date: Wed, 25 Nov 2020 23:30:53 -0500
From: John C Klensin <john-ietf@jck.com>
To: Roman Danyliw <rdd@cert.org>, Lyndon Nerenberg <lyndon@orthanc.ca>
cc: ietf@ietf.org
Subject: RE: Call for Community Feedback: Retiring IETF FTP Service
Message-ID: <36C92F732011DE95088B8427@PSB>
In-Reply-To: <b2b172a2d793499bb4da094f1cceb105@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <b993def4eb0140698042781e0b790af0@cert.org> <50D6883540A39384617ABEBF@PSB> <725c1a373fbc77e5@orthanc.ca> <b2b172a2d793499bb4da094f1cceb105@cert.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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/b44kDpg46lfRCE6PMfDHdV_r-Uw>
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: Thu, 26 Nov 2020 04:31:03 -0000


--On Thursday, November 26, 2020 03:09 +0000 Roman Danyliw
<rdd@cert.org> wrote:

>...
> To have as a backup, there is also
> ftp://ftp.rfc-editor.org/in-notes/internet-drafts against
> which I-Ds can be mirrored.

Roman,

I didn't know about that and, at least for me, that completely
changes the equation.  If there is at least one IETF (or IETF
LLC)-supported site that is kept synchronized with the IETF I-D
collection and offers FTP, I don't see any strong reason why
there needs to be access to the IETF repository on the IETF
site.  Even for those who need to change scripts, changing one
site and path for another (either in human memory or in a
script) should not be a big deal and, IIR, IETF has moved things
around often enough that most FTP users have had to do that once
or twice already.

On the other hand, if the LLC has to support, or fund AMS to
support, FTP access to a repository on the RFC Editor site/path,
it seems that the case that there are significant marginal costs
for maintaining FTP access to the IETF repository just got a
little more dubious.

thanks,
   john