IETF Logo Mail Archive

RE: Call for Community Feedback: Retiring IETF FTP Service

Roman Danyliw <rdd@cert.org> Wed, 11 November 2020 14:57 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 73F813A0E3C; Wed, 11 Nov 2020 06:57:01 -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 ow6EH2gmsGJv; Wed, 11 Nov 2020 06:57:00 -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 CE9653A0E30; Wed, 11 Nov 2020 06:56:59 -0800 (PST)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0ABEuwU7004026; Wed, 11 Nov 2020 09:56:58 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 0ABEuwU7004026
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1605106618; bh=3Ey/LNhbNcfa/dVRD+M55k3SgQ0PRzLhpmRVf7FdYjg=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=cRF576t8I5Kh7pi1KpO4scLE1lSDvvnzZi7b72YOImTA1Gyj5L4BkQydDK56oL/dg +H/lvErenkoDC+RFEdUkyLI9Fi/bOVcvgIBYr4lTrHOZxTksQEOtKFPLSW6QTTMaRD /liTNmui7docXwFaIxOPN2afXtZo4mcysFrkOfeE=
Received: from MORRIS.ad.sei.cmu.edu (morris.ad.sei.cmu.edu [147.72.252.46]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0ABEuvMW035654; Wed, 11 Nov 2020 09:56:57 -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; Wed, 11 Nov 2020 09:56:57 -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; Wed, 11 Nov 2020 09:56:57 -0500
From: Roman Danyliw <rdd@cert.org>
To: John C Klensin <john-ietf@jck.com>, "Scott O. Bradner" <sob@sobco.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "iesg@ietf.org" <iesg@ietf.org>
Subject: RE: Call for Community Feedback: Retiring IETF FTP Service
Thread-Topic: Call for Community Feedback: Retiring IETF FTP Service
Thread-Index: Ada3CD1BnAYFDyoMT8WUdvX4VBiWMQAehD4AAAJV+4AAA6QV0AAnH1DAAAEFcqA=
Date: Wed, 11 Nov 2020 14:56:56 +0000
Message-ID: <22ccc6a73d7445b797768bfd5fdb5072@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com> <97529AEECF47C0474F4A828F@PSB> <a383240da17845399eb0cd676d3b23f6@cert.org> <22a3d596cb634f619685558f4d1cd338@cert.org>
In-Reply-To: <22a3d596cb634f619685558f4d1cd338@cert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.203.59]
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/msG2Z-13TWJi2W5mUUqn8No3qio>
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: Wed, 11 Nov 2020 14:57:01 -0000

Hi John!

> -----Original Message-----
> From: Roman Danyliw
> Sent: Wednesday, November 11, 2020 9:33 AM
> To: 'John C Klensin' <john-ietf@jck.com>; 'Scott O. Bradner' <sob@sobco.com>;
> 'ietf@ietf.org' <ietf@ietf.org>
> Cc: 'iesg@ietf.org' <iesg@ietf.org>
> Subject: RE: Call for Community Feedback: Retiring IETF FTP Service
> 
> Hi John!
> 
> > -----Original Message-----
> > From: Roman Danyliw
> > Sent: Tuesday, November 10, 2020 12:19 PM
> > To: 'John C Klensin' <john-ietf@jck.com>; Scott O. Bradner
> > <sob@sobco.com>; ietf@ietf.org
> > Cc: iesg@ietf.org
> > Subject: RE: Call for Community Feedback: Retiring IETF FTP Service
> >
> > Hi John!
> >
> > > -----Original Message-----
> > > From: ietf <ietf-bounces@ietf.org> On Behalf Of John C Klensin
> > > Sent: Tuesday, November 10, 2020 8:02 AM
> > > To: Scott O. Bradner <sob@sobco.com>; ietf@ietf.org
> > > Cc: iesg@ietf.org
> > > Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
> > >
> > > +1
> > >
> > > And, while I suspect my scripts are less complicated than
> > > Scott's, I do have them and am dependent on them.   So two
> > > additional thoughts:
> > >
> > > (i) I know the conventional wisdom in the IETF is to obsolete HTTP
> > > in favor of HTTPS.  However, if conversation is necessary,
> > > conversion from FTP to simple, no negotiation HTTP is likely to be
> > > lots easier the conversation to HTTPS, certificate handling, etc.
> > > So, while the report seems to circle around this a bit, if FTP is
> > > discontinued, will we be assured that plain HTTP access will be
> > > available long-term rather than those who do convert waking up one
> > > day and discovering that
> > HTTP is being discontinued because HTTPS is more virtuous?
> >
> > To be clear, the proposal is completely reductive -- spinning down
> > FTP.  The posture of HTTP vs. HTTPs is outside the scope of this
> > proposal and would be a separate community discussion to change that
> > (and I'm not aware of this being under consideration).
> 
> I was privately reminded of a particular nuance that I wanted to make note of
> publicly -- IETF web properties (www.ietf.org, datracker.ietf.org, etc.) are all
> already HTTPS only, and has been the case for several years.

And to clarify further, "several years" ago was 2015 per https://www.ietf.org/about/groups/iesg/statements/maximizing-encrypted-access/

Roman

v2.23.0 | Report a Bug | By Email