IETF Logo Mail Archive

Re: documenting rsync, or, what are we here for anyway? (was: Re: what is rsync)

Joseph Touch <touch@strayalpha.com> Fri, 27 November 2020 21:04 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 49CB83A0E8B for <ietf@ietfa.amsl.com>; Fri, 27 Nov 2020 13:04:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 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, 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 CylyxOcYTKKx for <ietf@ietfa.amsl.com>; Fri, 27 Nov 2020 13:04:19 -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 A318C3A0E3A for <ietf@ietf.org>; Fri, 27 Nov 2020 13:04:19 -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: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To: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=FXjm42mN1wKsmAXyZ7nRwXpPb/6K9CRWtzpM2+1OxWI=; b=QfnmwCSPqILOjJOuodsKlr5M1 AhRcxk93k9qXnuolk4k3e7398vaENPQ5q6o90wbs4NsMAr1OUpQAbngO2LAq74L9GB6xyKyj4piPx bjzhGHI+w+NJS0t9tOpuvbY8nyaFK/Olz+hWC2M9XOqzH9H1P+4U5Xp/InRSBXCuYVF4R5QOcjUGs 6yHH3AmxsmcxtMGMy2vCcuP+t2qXiOHXQCCxJDtfM/R8MnO/8iTpcbEyY2eeoaWrNQEzBkCocsAqC CHWoahACSoYOQ7jiBsar4LawJv5Rf8xq2atCXUbGOX4S345AUS7Gj5Id49D9RMYsmfom/Rm91dOni skCnBn26w==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:57496 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 1kikuc-002KuY-Lt; Fri, 27 Nov 2020 16:04:19 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
Subject: Re: documenting rsync, or, what are we here for anyway? (was: Re: what is rsync)
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <rprp1j$2qt5$1@gal.iecc.com>
Date: Fri, 27 Nov 2020 13:04:14 -0800
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <52FABF93-A929-427D-8A3B-81DDA4C3D34F@strayalpha.com>
References: <20201127184550.656B32844AF7@ary.qy> <99E37AC2-FE81-441E-9BCF-EF549413C6E1@strayalpha.com> <66C95F81-0822-406E-8C15-1FF4787F1176@akamai.com> <C0FCEC98-B6CD-4F35-BA09-428732ADFDAF@strayalpha.com> <rprp1j$2qt5$1@gal.iecc.com>
To: John Levine <johnl@taugh.com>
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/qawWt3CkrqoL58AjaPRPBE4bJJg>
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: Fri, 27 Nov 2020 21:04:21 -0000


> On Nov 27, 2020, at 12:54 PM, John Levine <johnl@taugh.com> wrote:
> 
> In article <C0FCEC98-B6CD-4F35-BA09-428732ADFDAF@strayalpha.com>,
> Joseph Touch  <touch@strayalpha.com> wrote:
>>> Does FTP do multiplexing?  How?  Which RFC?
>> 
>> Yes; it opens a connection per exchange and let’s IP multiplexing do its job.
> 
> Web browsers were doing multiple http requests in parallel in the
> 1990s.

Largely to get around TCP slow start as a hack at the time - not to rely on IP multiplexing.

I.e., HTTP  still had HOL blocking because it tried to reuse a connection for multiple xfers. Not the same thing as exclusively relying on IP multiplexing. 

We discussed this in several webmux meetings in the IETF back then.

Joe

v2.23.0 | Report a Bug | By Email