IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

John Levine <johnl@taugh.com> Tue, 10 November 2020 16:54 UTC

Return-Path: <johnl@iecc.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 CDE423A0AA3 for <ietf@ietfa.amsl.com>; Tue, 10 Nov 2020 08:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=pLXAlFTb; dkim=pass (2048-bit key) header.d=taugh.com header.b=D6qAvrsT
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 3DzMmg8FRapw for <ietf@ietfa.amsl.com>; Tue, 10 Nov 2020 08:54:19 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C4903A0AA7 for <ietf@ietf.org>; Tue, 10 Nov 2020 08:54:18 -0800 (PST)
Received: (qmail 32467 invoked from network); 10 Nov 2020 16:54:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=7ed1.5faac5b9.k2011; bh=OmtZaPBACtFm2vRzdzqmBYQymcLzWVDbyYlHPy2LZ4o=; b=pLXAlFTbnH416ROCBeCGEg2726VQQKTnnyuB6RWaRvyv1IdIgc0GtZtmIwz6s+wLxnEFMs9PHhk3uxSILo8NacoE6bJFRj17BgvRN+v/4bKvp8MT05B5QZqZ1fPpnJfjpmKg7LaC7wR+WV0BAYcWsuPGSXEk3AC+MiQlCSqN9Zvl7N3r8I/6JAe/uJiyD9D7KB5zJ1ddXQUAgrHrCaYUEomtGY/TuBowKDDY15PGBDxoj3ICjwN0FFPQqONFhUAKKGx3ajnz1ud/QwUS/M011iq+t1vxFQqhC3oDGvxHZcSQJleoxpm0UZ4fASOv92ycfsdgslx43+W/WjY+ACH0uw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=7ed1.5faac5b9.k2011; bh=OmtZaPBACtFm2vRzdzqmBYQymcLzWVDbyYlHPy2LZ4o=; b=D6qAvrsTFgBlSR6MM68mnBvgwqkr0eC2b0gpAaMSelRpCcUxJv6C5PU7retGndQypBSDL5O9ZIaP8Z1V4U7EDbQ4kPpntHJtvz/wS3OiGuhRh+eLBMZf9bqXmJ92z8dCT1dwt1Zjl64J6txjUdQp+/HrmQvCn6Jr7XLJLEFUYaxze8BNvSwYpiJN6gX0SH8lu64+Bj/Bt9cxOMWZ1+v4wHf4hjcF75mUU3BkZjudSYj6cW9g3g/RGQyBz0hkyvMzghnThfG8m7kRA4iyuPpMXKDPYpk+yJbBJi/RUR0LESRY9dSscM6LqQmdW1h477RDPST0bYFuzXUT0sf0s3+TUg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 10 Nov 2020 16:54:17 -0000
Received: by ary.qy (Postfix, from userid 501) id B336925E6A90; Tue, 10 Nov 2020 11:54:16 -0500 (EST)
Date: Tue, 10 Nov 2020 11:54:16 -0500
Message-Id: <20201110165416.B336925E6A90@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
In-Reply-To: <5609c6f296a54b24a2b7a5cd319fbd46@cert.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qp4YiN_m0iDyK9mZJaQAKiBVHHA>
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: Tue, 10 Nov 2020 16:54:21 -0000

In article <5609c6f296a54b24a2b7a5cd319fbd46@cert.org> you write:
>You noted that your scripts perform functions that you don't know how to do in "non-ftp ways".  Can you
>clarify that use case/function more (offline ok too)?   In preparing the contingency plan, it appeared
>that using an HTTP API or rsync covered the known use cases.

I do all of my scripted downloads with wget or curl which I think is
pretty typical. In those two programs, changing from ftp to https generally
only involves changing ftp:// to https:// in the command arguments.

I'd also be interested in hearing about what other FTP clients people are using
that are hard to switch to https.

R's,
John

v2.23.0 | Report a Bug | By Email