Re: Regarding "Call for Community Feedback: Retiring IETF FTP Service"
John C Klensin <john-ietf@jck.com> Wed, 25 November 2020 19:59 UTC
Return-Path: <john-ietf@jck.com>
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 AE5883A1C5A; Wed, 25 Nov 2020 11:59:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 K41KSvFFpEde; Wed, 25 Nov 2020 11:59:37 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46B893A1C57; Wed, 25 Nov 2020 11:59:37 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ki0wy-0000J8-03; Wed, 25 Nov 2020 14:59:36 -0500
Date: Wed, 25 Nov 2020 14:59:30 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Livingood, Jason" <Jason_Livingood=40comcast.com@dmarc.ietf.org>
cc: ietf@ietf.org
Subject: Re: Regarding "Call for Community Feedback: Retiring IETF FTP Service"
Message-ID: <1B09850EB82653E9AA3D6AA8@PSB>
In-Reply-To: <D831FAF7-2E73-406C-AAF1-3F623A537230@cable.comcast.com>
References: <AM0PR08MB37169603FE46A63AB67CC62CFAFB0@AM0PR08MB3716.eurprd08.prod.outlook.com> <CAC8QAcdwdokF8NKLhFgKS3LOPwvchRe0sTrMUH52095kYywY_Q@mail.gmail.c om> <D831FAF7-2E73-406C-AAF1-3F623A537230@cable.comcast.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/isz_qsWZyu5xGEGO-ta5FkhZ-vY>
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, 25 Nov 2020 19:59:39 -0000
--On Wednesday, November 25, 2020 19:27 +0000 "Livingood, Jason" <Jason_Livingood=40comcast.com@dmarc.ietf.org> wrote: >> The other day I pressed a link, it turned out to be ftp link >> and surprise: it worked as major Web browsers support it. > > [JL] That will end fairly soon. Chromium will disable FTP in > 1Q2021 and fully remove the supporting code a few months after > that. > https://docs.google.com/document/d/1JUra5HnsbR_xmtQctkb2iVxRPu > hPWhMB5M_zpbuGxTY/edit But, fwiw, part of the justification given in that article (from the first paragraph) is: "In addition more capable FTP clients are available on all affected platforms." It goes on to say that that their implementation is broken and, essentially, that they don't feel like fixing it. "Broken and we don't want to invest resources in fixing it" feels quite different to me than "we have a service that works (almost) perfectly well and we'd like to discontinue it". And, fwiw, their explanation sounds very nearly like an invitation for someone to add support back in via a third-party plug-in. So, yes, their dropping support is interesting but I don't think has much to do with the IETF issue. john
- Regarding "Call for Community Feedback: Retiring … Hannes Tschofenig
- Re: Regarding "Call for Community Feedback: Retir… Behcet Sarikaya
- RE: Regarding "Call for Community Feedback: Retir… Hannes Tschofenig
- Re: Regarding "Call for Community Feedback: Retir… Keith Moore
- Re: Regarding "Call for Community Feedback: Retir… Livingood, Jason
- Re: Regarding "Call for Community Feedback: Retir… John C Klensin
- RE: Regarding "Call for Community Feedback: Retir… Hannes Tschofenig
- Re: Regarding "Call for Community Feedback: Retir… Michael Richardson
- Re: Regarding "Call for Community Feedback: Retir… Keith Moore
- RE: Regarding "Call for Community Feedback: Retir… Hannes Tschofenig
- RE: Regarding "Call for Community Feedback: Retir… Roman Danyliw
- Re: Regarding "Call for Community Feedback: Retir… Keith Moore
- Re: Regarding "Call for Community Feedback: Retir… Keith Moore
- RE: Regarding "Call for Community Feedback: Retir… Hannes Tschofenig
- Re: Regarding "Call for Community Feedback: Retir… Keith Moore
- Re: Regarding "Call for Community Feedback: Retir… Adam Roach
- Re: Regarding "Call for Community Feedback: Retir… Adam Roach
- Re: Regarding "Call for Community Feedback: Retir… Keith Moore
- Re: Regarding "Call for Community Feedback: Retir… Behcet Sarikaya
- RE: Regarding "Call for Community Feedback: Retir… Roman Danyliw
- Re: Regarding "Call for Community Feedback: Retir… Keith Moore