IETF Logo Mail Archive

Re: Tombstone README for FTP service

Jared Mauch <jared@puck.nether.net> Thu, 28 April 2022 14:21 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 56919C15E6CD for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2022 07:21:49 -0700 (PDT)
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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtsClK9QKrXE for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2022 07:21:44 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B03A4C159A2A for <ietf@ietf.org>; Thu, 28 Apr 2022 07:21:44 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2001:4878:a048:3000:992f:f958:50f8:a77a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id E30365400D7; Thu, 28 Apr 2022 10:20:19 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: Tombstone README for FTP service
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <BN2P110MB1107650B16F3338FF4765314DCFD9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
Date: Thu, 28 Apr 2022 10:20:08 -0400
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1719A995-08AF-41A3-A9A1-B7DDACAB07D3@puck.nether.net>
References: <BN2P110MB1107650B16F3338FF4765314DCFD9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
To: Roman Danyliw <rdd@cert.org>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bcpAlRuqviOxOLVQ5wD1GuV_6Ms>
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: Thu, 28 Apr 2022 14:21:49 -0000

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.

- Jared

> On Apr 28, 2022, at 8:58 AM, Roman Danyliw <rdd@cert.org> wrote:
> 
> Hi!
> 
> We need a tombstone README to drop into the FTP service.  Any objections or polish for:
> 
> ==[ snip ]==
> Last updated: April 28, 2022
> 
> The IETF FTP Service has been retired.  
> 
> Please visit https://www.ietf.org for more information about the IETF.
> 
> The previously served assets continue to be available through other means:
> 
> via HTTPS 
> (in a similar directory layout)
> https://www.ietf.org/ietf-ftp/
> 
> via IETF Datatracker 
> (for internet-drafts, RFCs, WG information, and meeting materials)
> https://datatracker.ietf.org
> 
> via IETF MailArchive 
> (for mailing lists)
> https://mailarchive.ietf.org/arch/
> 
> via RSYNC
> https://www.ietf.org/how/ids/internet-draft-mirror-sites/
> 
> The RFC Editor continues to operate the following FTP service for RFCs:
> 
> ftp://ftp.rfc-editor.org
> 
> ==[ end ]==

v2.8.7 | Report a Bug | By Email