IETF Logo Mail Archive

Re: what is rsync, was Call for Community Feedback: Retiring IETF FTP Service

Keith Moore <moore@network-heretics.com> Thu, 26 November 2020 19:11 UTC

Return-Path: <moore@network-heretics.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 A68D43A0332 for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 11:11:24 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=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=messagingengine.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 Cj3EfsezHzcr for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 11:11:23 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66B1D3A0317 for <ietf@ietf.org>; Thu, 26 Nov 2020 11:11:23 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 6220D1320 for <ietf@ietf.org>; Thu, 26 Nov 2020 14:11:22 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 26 Nov 2020 14:11:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=ufos8DZZtaPM+54TbdaHuYkFGX48qtYcS9YtIHPXX AU=; b=DLSxGPhtCDQ+ahD+cmC7MYDM2uivoGAagMsk5GDveQUO4uM96KMsXWV6w tbTLiwd+RYeOBChZHz0JeDUTNCQjwWtZRVaEnXi3V67snzsAYAh58OjhnVxlfD5d XgobjnbZe2so+/KqXyf1MmgWX46PABmWLjr6ORG9s2cxrw42Lh7Zcy+j+iNq2Gu3 kNbK/Z7KJoX6PP5JylP0ND/bu7rtbqKL0NQG8QgQ7GEbLnCYIyQUNr7F+Evuhvfv mZR1LZ4Hq0O3TOo/FuyDJw2Ta8mPW91uFkg0eNWBLuBFdH+OumJiQ3uaOPAq/4Ru ABJSZMjXH5HcjVuVt+ldTMKL0R8pA==
X-ME-Sender: <xms:2P2_X31XZ1JkJkSd6-OZEHfhnaKPxXYB7OCVolB2OwdB54RAZRvxiw> <xme:2P2_X2GqzENTaxa2vRTIkCnjtha85ppTZpJUbSZlf1MkFiS4SCcOvHmgfEG9Y3pZs WSk_sJjaHUg7g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehvddguddvfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ejredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepjefhieefie eikeettdejheeuteejvdefkeekveehhefgtdetgedutedtuddthfelnecuffhomhgrihhn pehsrghmsggrrdhorhhgnecukfhppedutdekrddvvddurddukedtrdduheenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:2P2_X34JBOY9UMwqRYrb3dnPQJwuwHjIH3BcEqbZGqywzTX9lnJAZA> <xmx:2P2_X82qStlTACIBQi1TEF6qhdwHKodHr73-lthjVwG3bAArbMU_sw> <xmx:2P2_X6GrfhGwFPfc_NSsX4KBizCPiJfeCwPbUD35Ln35A3JEai-yOA> <xmx:2v2_X2EVwNTzWX5vlB6oJtKWRoBbxlq4UigZSOtmhLtYC9y1Mqwfbg>
Received: from [192.168.1.85] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 98C1B3064AAF for <ietf@ietf.org>; Thu, 26 Nov 2020 14:11:20 -0500 (EST)
Subject: Re: what is rsync, was Call for Community Feedback: Retiring IETF FTP Service
To: ietf@ietf.org
References: <20201126170826.F2FF8281C9C3@ary.qy>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <c34ed9df-0d12-cab0-551e-ec146bc949b7@network-heretics.com>
Date: Thu, 26 Nov 2020 14:11:19 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20201126170826.F2FF8281C9C3@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tNjvuKOrzUMCvPAoXC2SpM82Tpc>
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: Thu, 26 Nov 2020 19:11:25 -0000

On 11/26/20 12:08 PM, John Levine wrote:

> If you're wondering if there's an RFC for it, nope. RFC 5781 specifies
> the rsync: URI but refers back tohttp://rsync.samba.org/  for details
> on rsync.
>
> I don't suppose anyone would object if we made an RFC out of the spec
> but given that the tech report, thesis, and multiple implementations
> are widely available without restriction (other than GPL on some of
> the code) it doesn't seem worth a lot of effort.

I remember when IETF cared about making standards and promoting broad 
interoperability.

Keith

v2.23.0 | Report a Bug | By Email