RE: Call for Community Feedback: Retiring IETF FTP Service

Roman Danyliw <rdd@cert.org> Thu, 26 November 2020 14:52 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 48B1C3A132B for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 06:52:40 -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 r_pMy4HUv3Hg for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 06:52:38 -0800 (PST)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 C05643A132A for <ietf@ietf.org>; Thu, 26 Nov 2020 06:52:38 -0800 (PST)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AQEqb3G033167; Thu, 26 Nov 2020 09:52:37 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 0AQEqb3G033167
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1606402357; bh=FB0qogGFScDCXoyVen3ToBMhHUbDtqqssAaBr2nZ6+k=; h=From:To:Subject:Date:References:In-Reply-To:From; b=RZvA9ES3QZh0yUNhFR9IhYdKFQoFwrFJye4tfWPhhrIPckULcKtT3Ols3m+4RAxgA w7/+2IkgEwFz20HC1JCmnNYe+f/NmiI4pqMwsLR9+/vKyGuMu9ZhjYKqQOEpHzPAae ceoHXJ1efHMcFxwUTbk79NY3TzGbTLJX0w4kjoK0=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AQEqZR3007097; Thu, 26 Nov 2020 09:52:35 -0500
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MURIEL.ad.sei.cmu.edu (147.72.252.47) 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:52:34 -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:52:34 -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: AdbD/yeNvmuf4/MLL0WTiEg/iyBVzgALYEIAAApD1+A=
Date: Thu, 26 Nov 2020 14:52:33 +0000
Message-ID: <69d37447a35840d6b58e9f7848ca6d8d@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <b993def4eb0140698042781e0b790af0@cert.org> <50D6883540A39384617ABEBF@PSB> <725c1a373fbc77e5@orthanc.ca> <b2b172a2d793499bb4da094f1cceb105@cert.org> <36C92F732011DE95088B8427@PSB> <ef036e20609b4388aeb07d8f5fd5caae@cert.org> <6dd1bed8-9451-955b-5fb4-3fab2787d255@network-heretics.com>
In-Reply-To: <6dd1bed8-9451-955b-5fb4-3fab2787d255@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/gG6xWeT1BBfJLAXXbz5rzqvph7Y>
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:52:40 -0000

Hey Keith

> -----Original Message-----
> From: ietf <ietf-bounces@ietf.org> On Behalf Of Keith Moore
> Sent: Thursday, November 26, 2020 9:45 AM
> To: ietf@ietf.org
> Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
> 
> On 11/26/20 9:19 AM, Roman Danyliw wrote:
> 
> > Since we talked exchanged notes on being clear on positions
> (see:https://mailarchive.ietf.org/arch/msg/ietf/GXzI5CRCVLhfKzFR4s5BwKmjhio
> /), am I correct in interpreting that you have moved from "opposed" to "no
> objection contingent on continued operations of an alternative ftp source such
> asftp://ftp.rfc-editor.org"?
> 
> You didn't ask me, but that's my position. 

Ooops.  Cut-and-paste error from my earlier note to John (https://mailarchive.ietf.org/arch/msg/ietf/FDhwYSxK0WSV0cdwf2aZiPfMQbI/) :-).  Sorry.

Roman

 I won't insist that IETF host the
> service, but I do think it needs to continue to exist, at least until there's been
> time to put up and test and transition to something that provides similar
> services but works better (perhaps webdav).
> 
> My fallback position was to set up such a service myself, but even for such a
> simple service that's a big commitment if the service is going to be useful in the
> long-term, and I'm not already in the business of running public-facing servers.
> (OTOH, if AWS's FTP hosting supported public access, I would have already set
> up such a service.)   But if the rfc editor is going to continue to maintain their
> FTP server, that's sufficient, particularly when it is now clear that IETF
> management would really resent maintaining it.
> 
> More broadly, this conversation has convinced me that IETF cannot be relied on
> to provide the tools that IETF participants need, and in fact that IETF
> management has become hostile to participation in IETF by some kinds of
> people.   So if IETF is going to continue to be a viable consensus-based
> standards-making organization, either the management needs to do a
> significant about-face in its attitude toward participation, or IETF participants
> need to take on the burden of providing those tools.
> 
> Keith
>