IETF Logo Mail Archive

Re: Tombstone README for FTP service

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 29 April 2022 08:39 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 5ED35C13A8D0 for <ietf@ietfa.amsl.com>; Fri, 29 Apr 2022 01:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.751
X-Spam-Level:
X-Spam-Status: No, score=-3.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.857, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4_4_YFAMa0k for <ietf@ietfa.amsl.com>; Fri, 29 Apr 2022 01:39:44 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 0F383C159492 for <ietf@ietf.org>; Fri, 29 Apr 2022 01:39:41 -0700 (PDT)
Received: (qmail 30123 invoked from network); 29 Apr 2022 08:35:10 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 29 Apr 2022 08:35:10 -0000
Message-ID: <ae7ea75a-dde4-e66d-661d-a29cf7028b6b@necom830.hpcl.titech.ac.jp>
Date: Fri, 29 Apr 2022 17:39:39 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Subject: Re: Tombstone README for FTP service
Content-Language: en-US
To: ietf@ietf.org
References: <BN2P110MB1107650B16F3338FF4765314DCFD9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM> <173db55f-3fdc-e6e6-e230-e235cc9ce673@network-heretics.com> <Ymqfln+LYyqXd/YF@nic.fr> <3dcbff03-fca4-e5b2-f82d-3889e8c51a82@network-heretics.com> <BN2P110MB11070B5E6602DE0E35D81690DCFD9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <BN2P110MB11070B5E6602DE0E35D81690DCFD9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3z7VZDqvfcuWkVS4eYO1vPLH6KI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
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: Fri, 29 Apr 2022 08:39:46 -0000

Roman Danyliw wrote:

> There is community consensus [1] to execute the FTP retirement plan [2].

 > [1] 
https://mailarchive.ietf.org/arch/msg/ietf/vi-8bFqlgBFjB2jJ1SIAGHiNRdg/

That's rather an IESG decision to manage IETF based
on collective stupidities of committees.

Jared Mauch wrote:

 > Either the service is too difficult and painful to run, which is what
 > was told to the community, or it’s not and posting a tombstone file
 > gives an impression there was not accuracy in that messaging.

Right. But, see above.

							Masataka Ohta

v2.8.7 | Report a Bug | By Email