IETF Logo Mail Archive

[Rfced-future] Community input

Carsten Bormann <cabo@tzi.org> Wed, 25 November 2020 16:40 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1C83A1A78 for <rfced-future@ietfa.amsl.com>; Wed, 25 Nov 2020 08:40:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=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 5ypT1yljbcnW for <rfced-future@ietfa.amsl.com>; Wed, 25 Nov 2020 08:40:32 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0413A1A75 for <rfced-future@iab.org>; Wed, 25 Nov 2020 08:40:31 -0800 (PST)
Received: from [192.168.217.120] (p548dce71.dip0.t-ipconnect.de [84.141.206.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Ch67x6t2Mz114k; Wed, 25 Nov 2020 17:40:29 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 628015229.453391-234dd283fb89dfa6787489085489e775
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 25 Nov 2020 17:40:29 +0100
Message-Id: <9D0D4CBA-677A-410F-95F3-5C452970B842@tzi.org>
To: rfced-future@iab.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/FyQmxCzercpGPwH2EuwTM93yxis>
Subject: [Rfced-future] Community input
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Nov 2020 16:40:35 -0000

For a good view at the skeptical components of my stance on running the publishing activity entirely based on “community input”, please see these messages.  

https://mailarchive.ietf.org/arch/search/?q=retiring+ftp+service

All 196 of them.

And when you are done, please keep in mind that this is only a revival of an attempt in 2015 to retire IETF’s FTP service, which (attempt) was eventually abandoned.
We continue to offer FTP access to our documents.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email