IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Jared Mauch <jared@puck.nether.net> Tue, 17 November 2020 16:02 UTC

Return-Path: <jared@puck.nether.net>
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 719DD3A149B for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 08:02:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 t6IP96YU8LAf for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 08:02:11 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F56F3A1575 for <ietf@ietf.org>; Tue, 17 Nov 2020 08:01:56 -0800 (PST)
Received: by puck.nether.net (Postfix, from userid 162) id E5CEA54017D; Tue, 17 Nov 2020 11:01:55 -0500 (EST)
Date: Tue, 17 Nov 2020 11:01:55 -0500
From: Jared Mauch <jared@puck.nether.net>
To: Adam Roach <adam@nostrum.com>
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
Message-ID: <20201117160155.GB2146486@puck.nether.net>
References: <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> <27622517-8EC3-44D1-BB21-1F2071BCA2C2@cable.comcast.com> <5dc7b0d1-d565-92c5-293e-093040596f35@network-heretics.com> <4b46fe4f-0b5b-dbf4-9bd5-f0a4a6ee30c9@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4b46fe4f-0b5b-dbf4-9bd5-f0a4a6ee30c9@nostrum.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q0Sk8c3kGfMjJSSEvEgMI8biiCA>
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 16:02:12 -0000

On Tue, Nov 17, 2020 at 09:57:34AM -0600, Adam Roach wrote:
> On 11/17/20 09:45, Keith Moore wrote:
> > Are those web browsers that are deprecating FTP also deprecating HTTP
> > without TLS?
> 
> 
> Yes.
> 
> https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/
> 
> https://www.chromium.org/Home/chromium-security/marking-http-as-non-secure

	There's a difference between preferring https vs http and pulling
http support entirely.  There's many devices that will never get https,
upgrades or certificates.

	We must be careful in how quickly we drag viable technology
to the digital (and perhaps physical) dumpster.

	- Jared


-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.

v2.23.0 | Report a Bug | By Email