IETF Logo Mail Archive

Re: Two FTP issues

Joseph Touch <touch@strayalpha.com> Tue, 01 December 2020 04:11 UTC

Return-Path: <touch@strayalpha.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 500603A00D9 for <ietf@ietfa.amsl.com>; Mon, 30 Nov 2020 20:11:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 tvPC6T7rqpDI for <ietf@ietfa.amsl.com>; Mon, 30 Nov 2020 20:11:46 -0800 (PST)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (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 DAA763A011B for <ietf@ietf.org>; Mon, 30 Nov 2020 20:11:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4L9rjM8De3MleMD09Y4cdrKpT/ZybC2Xwun8oc/nrcs=; b=ZeAT+04JphCGKr0yIAvIwFmCT O/vmZK+VLVX1qGL9E+bhmSUSvBxcVL5Z0KfAAi/MQwo6YpVVONemd0FIFP2iLZOqoHGP91iIJf7ol nZtLXEtgE/wgq67XfqKJoYZuB3Y/eLxmkWS4O1alTceOL6xF2ZuBguRy/ByBofzAAg/6I6Z1fPuLk JfldA58PdboGXB4kVbMizHvJxHBbmpZOtO7d1SXkacettZcAP81h4CVO2reKqzHx1d072rWB2bdZD bzEI5iHPAP3ks+cW+FglPNPiANuGfsH00IGFszJjWiZlh6HaaPfWL9hrbiithaldhg4RP70csvnRt awcAayTOw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:64295 helo=[192.168.1.14]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1kjx0u-000Z5U-Iu; Mon, 30 Nov 2020 23:11:45 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_66469159-3692-40EE-AE70-E482112F4E69"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
Subject: Re: Two FTP issues
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <20201201030759.GJ5364@mit.edu>
Date: Mon, 30 Nov 2020 20:11:39 -0800
Cc: John C Klensin <john-ietf@jck.com>, Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
Message-Id: <37D3D7F3-6908-424A-84E0-6C38F302377A@strayalpha.com>
References: <AA1E0A8464BC45FB4FA44684@PSB> <2D63A357-E253-462C-864D-2BF96D3E2E18@tzi.org> <F4CD3381C5D0E24C91FC4A91@PSB> <20201201030759.GJ5364@mit.edu>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tOT6-b4fAmUM9uM7JSIz2XJx1vo>
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, 01 Dec 2020 04:11:48 -0000


> On Nov 30, 2020, at 7:07 PM, Theodore Y. Ts'o <tytso@mit.edu> wrote:
> 
> On Mon, Nov 30, 2020 at 06:26:00PM -0500, John C Klensin wrote:
>> --On Monday, November 30, 2020 23:38 +0100 Carsten Bormann
>> <cabo@tzi.org <mailto:cabo@tzi.org>> wrote:
>> 
>>> I believe a hard-earned piece of experience I took from using
>>> FTP is that you don't want to do conversions during transit.
>> 
>> I think we had figured that out by early in 1971. At least in
>> general, I think it is still true.
> 
> And yet, just recently on this mailing list, some of the people
> arguing for the inherent superiority of the ftp protocol as compared
> to http is that with ftp, it *Would* do conversions of text files
> (e.g., crlf mangling, etc.)

Conversion can be useful. I can FTP a text file of Perl and run it just fine on different platforms.

Doing the same with HTTP either requires explicitly excising the surrounding HTML or doing CRLF conversion - still.

At least with FTP, it was a choice (ASCII vs binary).

Joe

v2.23.0 | Report a Bug | By Email