Re: [Sidrops] draft-sidrops-bruijnzeels-deprecate-rsync

Tim Bruijnzeels <tim@nlnetlabs.nl> Tue, 21 April 2020 11:26 UTC

Return-Path: <tim@nlnetlabs.nl>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4159D3A08EA for <sidrops@ietfa.amsl.com>; Tue, 21 Apr 2020 04:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nlnetlabs.nl
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 jdRZMqlaaX9y for <sidrops@ietfa.amsl.com>; Tue, 21 Apr 2020 04:26:20 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [185.49.140.10]) (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 65BB03A08ED for <sidrops@ietf.org>; Tue, 21 Apr 2020 04:26:20 -0700 (PDT)
Received: from [IPv6:2001:981:4b52:1:10c1:16a5:febc:ba2a] (unknown [IPv6:2001:981:4b52:1:10c1:16a5:febc:ba2a]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id C5E0714C48; Tue, 21 Apr 2020 13:26:18 +0200 (CEST)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=fail (p=none dis=none) header.from=nlnetlabs.nl
Authentication-Results: dicht.nlnetlabs.nl; spf=fail smtp.mailfrom=tim@nlnetlabs.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1587468378; bh=cxIKrXmUB7zu5kBWlqi7vCt/VTdcHdZXL/aMhqniiXE=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=LVj9ugdBgaGeOvHTNTZoFc/d9fDyeRQaU9I3UXUfrvduGb2ZfGeuuW1ZpCoaEKCI5 T/r6AHDgpsnaQNNqrpd+IZvIqU09DoUS4t496D38FHoahk5tHfRGtxaFiLIx4i94dG d+gmLTY0lFztabJmJCXLf8vpj0ecDGlpFoD1rTeE=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Tim Bruijnzeels <tim@nlnetlabs.nl>
In-Reply-To: <3D9F48FC-822B-4C82-A5CB-D90B2746922B@nlnetlabs.nl>
Date: Tue, 21 Apr 2020 13:26:18 +0200
Cc: SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FD05E35-B0E9-4BC4-BC8D-8ADC9907FF32@nlnetlabs.nl>
References: <m2tv1ehtso.wl-randy@psg.com> <3D9F48FC-822B-4C82-A5CB-D90B2746922B@nlnetlabs.nl>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/0VcuzWxgEYeRNkljU2lZXD8tGSo>
Subject: Re: [Sidrops] draft-sidrops-bruijnzeels-deprecate-rsync
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2020 11:26:23 -0000


> On 21 Apr 2020, at 13:07, Tim Bruijnzeels <tim@nlnetlabs.nl> wrote:
> 
> Hi,
> 
>> On 20 Apr 2020, at 20:54, Randy Bush <randy@psg.com> wrote:
>> 
>>> https://datatracker.ietf.org/doc/draft-sidrops-bruijnzeels-deprecate-rsync/
>> 
>> quite willing to discuss this and am still willing to co-author if you
>> wish.  but i am pretty firm about not breaking the running internet.
>> 
>> to quote myself from last year
>> 
>>   great to get the draft out there.  wish it was more specific about
>>   how this is operationally accomplished.  e.g. from the discussion i
>>   was trying to have with you:
>> 
>>   0 - publishers publish rcynic and some rrdp.  rps use rcynic and some
>> 	use rrdp
>>   1 - all publishers offer both.
>>   2 - then you can ask all rps to move to rrdp and prefer it
>>   3 - you can see, at the publishers, when no rcynic requests come
>>   4 - you can turn off rcynic at the publishers
>>   5 - you can remove rcynic from the rps
>> 
>> whether we like it or not, there are a significan number of rcynic-only
>> relying parties out there.  we need to help and encourage the
>> transition.  we MAY NOT break the running internet.
> 
> I agree with your approach, now that it's really only Lacnic who still need to do work on this. They have told me *informally* that they think it can be done this year, but that was before covid. Still, the will is there and it should not be show stopper.

My apologies lacnic, I did not mean to send this to all.

Still I hope there is no harm done here. I am sure that everybody understands that engineering resources need to be managed, especially now.

> 
> Shall I try to spin a new version with these changes and send it to both of you by Thursday? Do you both want to co-author?
> 
> Thanks
> Tim
> 
> 
> 
> 
>> 
>> there 
>> 
>> _______________________________________________
>> Sidrops mailing list
>> Sidrops@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidrops