IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Larry Masinter <LMM@acm.org> Thu, 12 November 2020 05:45 UTC

Return-Path: <masinter@gmail.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 58BA13A1438 for <ietf@ietfa.amsl.com>; Wed, 11 Nov 2020 21:45:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 pAVjdCm7MMka for <ietf@ietfa.amsl.com>; Wed, 11 Nov 2020 21:45:25 -0800 (PST)
Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE3E93A1437 for <ietf@ietf.org>; Wed, 11 Nov 2020 21:45:24 -0800 (PST)
Received: by mail-lj1-f180.google.com with SMTP id h23so4681060ljg.13 for <ietf@ietf.org>; Wed, 11 Nov 2020 21:45:24 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qqDrXm29zKuC3c1Yohqx/F9RkJ6NqNUj/2lKL7+X4J4=; b=pX/ozgBK0fUe8N5BoeScVAHnVSsaha6/ygqgHx6qQ3Mna9SCmHR4/MD+dnJP0K8JII tLIfhEx2eLNJrge7tBg3HSIuRn8mriYTW64JpIFdZ3cyBXWOWDWxaf8ep5NynD2Vq9GD RhjqlfAJYENxMiY5kb7595rhQGljCoEzCSOKsIftkLEoH50LDWHksydJLxgaOroyPXBa gSmC1a+6m51qjMZlTPaWDcKnMvdULuVKyKQpN0/O+WseP6l+9JOOyb09PhTiZhebP/j6 PyjrLJiKWoxRXE4NqR+N89nOx6WmHClLZfNQvrEN+ALqp93HmEINbHT1OuSAiiuIR+kd PjKw==
X-Gm-Message-State: AOAM5336xnOUWopmnKUWOvzIe4Wwo4ZqFbueC4wEmXq0wBJz7YfOrFCg nVjtPz/uO+aU8QX0dIMcC9gUmi3/syqYJQ3xRiBCLFft8MQ=
X-Google-Smtp-Source: ABdhPJzFDYg5fB/zQwq1zMGk43jPKijEDPtpCOt7VcqXWqL5LAnIcW8drVHF/lyNCKMvo1aG1yA9yWDYUZg0kjZ+Reg=
X-Received: by 2002:a2e:7803:: with SMTP id t3mr11043112ljc.156.1605159922889; Wed, 11 Nov 2020 21:45:22 -0800 (PST)
MIME-Version: 1.0
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <20201110225502.GA60333@faui48f.informatik.uni-erlangen.de> <d08945117193451596a4f3860113747e@cert.org>
In-Reply-To: <d08945117193451596a4f3860113747e@cert.org>
From: Larry Masinter <LMM@acm.org>
Date: Wed, 11 Nov 2020 21:45:11 -0800
Message-ID: <CAKq15vcprxiKHLx_GD7oCp4hU-CA63xwTNMPu4omaSZF7OJ_eg@mail.gmail.com>
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: Roman Danyliw <rdd@cert.org>
Cc: Toerless Eckert <tte@cs.fau.de>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000002fccd05b3e26b93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XS0l20JP1Q-wBlLkK4EdE24vrL8>
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, 12 Nov 2020 05:45:26 -0000

I read your data differently. If' you have ~91 different users that's a lot.
I agree with the sentiment that you've spent more attention bandwidth
trying to retire the service than it should take to run it a few more years.
Chrome had a 2-year plan
https://docs.google.com/document/d/1JUra5HnsbR_xmtQctkb2iVxRPuhPWhMB5M_zpbuGxTY/edit#heading=h.7bs9792ml0ln
to remove ftp from the browser by 2q 2021

  https://news.ycombinator.com/item?id=20721609
Anyway, cool url's don't change.


but c

[2]

v2.23.0 | Report a Bug | By Email