RE: Call for Community Feedback: Retiring IETF FTP Service

Roman Danyliw <rdd@cert.org> Thu, 26 November 2020 14:39 UTC

Return-Path: <rdd@cert.org>
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 22CF23A120F for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 06:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 Zuw3QBOLukrx for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 06:39:33 -0800 (PST)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69B293A1244 for <ietf@ietf.org>; Thu, 26 Nov 2020 06:39:32 -0800 (PST)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AQEdV9d006076; Thu, 26 Nov 2020 09:39:32 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 0AQEdV9d006076
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1606401572; bh=yKMUO+Z7w0HXCM5exbbyxfO9Ayq8ORftGvj491EUkIE=; h=From:To:Subject:Date:References:In-Reply-To:From; b=K/Ulnk6s9o7CjNh4mrh0Gm3W4ARlrUg9yEzalAzwG877E5pt3uveFrSBc7S+y1TLD Wt/Hbztw2+fEFxNSIMSZeT4zykCSR/rAqbNpqCEi26MnXmWwJzKImn0UeS3eLemjEi NYYvtxXnKjFCyBQK5OVf74iXBi0Mz7zCMjMjmRnk=
Received: from MORRIS.ad.sei.cmu.edu (morris.ad.sei.cmu.edu [147.72.252.46]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AQEdRQo003509; Thu, 26 Nov 2020 09:39:27 -0500
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 26 Nov 2020 09:39:27 -0500
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Thu, 26 Nov 2020 09:39:26 -0500
From: Roman Danyliw <rdd@cert.org>
To: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Call for Community Feedback: Retiring IETF FTP Service
Thread-Topic: Call for Community Feedback: Retiring IETF FTP Service
Thread-Index: AdbEAfAPXMbkhktKtkuXzTvNROwZjA==
Date: Thu, 26 Nov 2020 14:39:25 +0000
Message-ID: <45d4a41f37e7434483cfbda549f44a84@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <b993def4eb0140698042781e0b790af0@cert.org> <50D6883540A39384617ABEBF@PSB> <725c1a373fbc77e5@orthanc.ca> <b2b172a2d793499bb4da094f1cceb105@cert.org> <36C92F732011DE95088B8427@PSB> <9ff7a889-2d9a-f0fc-f2bd-a3ea80f6ef1e@network-heretics.com>
In-Reply-To: <9ff7a889-2d9a-f0fc-f2bd-a3ea80f6ef1e@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.202.48]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FgHBIxSbF-YNvKwTBRXE-J_mEHg>
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 14:39:35 -0000

Hi Keith!

> -----Original Message-----
> From: ietf <ietf-bounces@ietf.org> On Behalf Of Keith Moore
> Sent: Wednesday, November 25, 2020 11:55 PM
> To: ietf@ietf.org
> Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
> 
> On 11/25/20 11:30 PM, John C Klensin wrote:
> 
> > 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.
> 
> I'm probably ok with that also... as long as _that_ ftp server doesn't go away
> anytime soon or without a good reason.   To me it's more important that the
> service exist than that it be run by IETF. (especially since the IETF server is being
> run so poorly)

As I just noted to John (https://mailarchive.ietf.org/arch/msg/ietf/FDhwYSxK0WSV0cdwf2aZiPfMQbI/), I want to be crystal clear on positions -- have you moved from "opposed" to "no objection contingent on continued operations of an alternative ftp source such as ftp://ftp.rfc-editor.org"?

Unlike John, we had discussed a broad array of content, so I also want to point out that the ftp.rfc-editor.org site has different content that ftp.ietf.org -- RFCs and I-Ds are there.  However, for example, the mailing list archives and charters are NOT on the rfc-editor site.

> Maybe just change the DNS for ftp.ietf.org to a CNAME that points to it?

When considering what do if the ftp.ietf.org were to be deprecated, the proposal suggested as few things related to handling document pointers and explicitly turning it off (i.e., no service on that port or resolution of that name).  A few parties (https://mailarchive.ietf.org/arch/msg/ietf/XFJOyi9a8KsrF4vmBAghb0Zo3mo/, https://mailarchive.ietf.org/arch/msg/ietf/SZBuNoGOiSajpsvurZ9hQuiNINc/, https://mailarchive.ietf.org/arch/msg/ietf/-nZbFI-D1bp-o-LYGJNA_U1k9fQ/) suggested something less dramatic by putting in a pointer-like README file as the sole content.  Is your position that you would preferred to instead CNAME ftp.ietf.org to ftp.rfc-editor.org instead?

I ask because the directory layout from ftp.ietf.org and ftp-rfc.editor.org is NOT the same.  My question is which seems better, when you go to ftp.iett.org and the directory you expect is not there, but you find a README on where to go; OR you are redirected to another server which has the content, but no hint on where to go (although it might be clear from the presented directories)

Regards,
Roman

> Keith
>