IETF Logo Mail Archive

RE: Call for Community Feedback: Retiring IETF FTP Service

Roman Danyliw <rdd@cert.org> Tue, 17 November 2020 14:51 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 4B4F43A13CF for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 06:51:16 -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 iDa6rONoCpSg for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 06:51:14 -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 6CB483A13BC for <ietf@ietf.org>; Tue, 17 Nov 2020 06:51:14 -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 0AHEpC82012351; Tue, 17 Nov 2020 09:51:13 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 0AHEpC82012351
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1605624673; bh=wkZBS9XYcjtzUf3am07/560GSHV+7zSoph6lec5O5Og=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=o/yO10WIO6+99OyNbuxiHR14F0Bmfzt4AVuNd4pqqhGdwljsoCbKOG7kQgqDhElx6 8DqONrKbFzqslgb4sB93YkeasqoLJAusBhL0ea0gMxbNIZeJYpToyIKAhbeddRH3YB 6fRBf5Q2vcatwEF0+rs45N3XopuLdrPL4868DuO0=
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 0AHEpCSC020678; Tue, 17 Nov 2020 09:51:12 -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; Tue, 17 Nov 2020 09:51:11 -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; Tue, 17 Nov 2020 09:51:11 -0500
From: Roman Danyliw <rdd@cert.org>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
CC: 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: Ada3CD1BnAYFDyoMT8WUdvX4VBiWMQFJu10AAABKp4AADHZ9AAAA1a8AAAqaGQAAD5dtAAADcuSAAAdFdID//+X51///+Jzg
Date: Tue, 17 Nov 2020 14:51:10 +0000
Message-ID: <7057e29825514008a06b749cb5c476f6@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com> <D26DCBB6-3997-4A73-BB46-867B4FD79BD2@eggert.org> <27b80ed2-76fb-aee7-f22d-de56019e9aa9@nostrum.com> <a8bdd67a-13ea-4433-aa38-9cfd48ea28da@network-heretics.com> <0e875497-9986-a0d9-8354-3eac26b7f882@nostrum.com> <a02e15f2-34fb-4124-7ba0-c0ee0070b39f@network-heretics.com> <6a29096e-c76e-9bde-388c-bf411b235346@nostrum.com> <6ff3c8a8-57c9-a278-51ce-ce24fd2dfc0e@network-heretics.com> <01RS3W7DNPHA005PTU@mauve.mrochek.com>
In-Reply-To: <01RS3W7DNPHA005PTU@mauve.mrochek.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-jfms6u2UCMiepia0RP1R_LoBrA>
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: Tue, 17 Nov 2020 14:51:16 -0000

Hi Ned!

Thanks for the feedback.

> -----Original Message-----
> From: ietf <ietf-bounces@ietf.org> On Behalf Of
> ned+ietf@mauve.mrochek.com
> Sent: Tuesday, November 17, 2020 9:02 AM
> To: ietf@ietf.org
> Cc: Keith Moore <moore@network-heretics.com>
> Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
> 
> The discussion of FTP service retirement has actually been surprisinginly
> informative. Things I've learned include:
> 
> (1) The IETF no longer provides HTTP access, leaving FTP as the only
>     access mechanism that doesn't require a crypto layer. With FTP gone,
>     crypto becomes a requirement for access.

Could you help me better understand which way your concern leans.  Let's abstract away HTTP and FTP, and just consider a communications channel.  Do you have a use case where access to IETF artifacts need to happen over unencrypted channels (i.e., getting the same artifacts over an encrypted channels breaks the use case)?  Put via analogy, if you always get something via postcard (in the clear), but got it in an envelope (encrypted) instead, it break something.  Or are you stating a philosophical position on not providing channel security?

Roman

v2.23.0 | Report a Bug | By Email