Re: [Sidrops] I-D Action: draft-ietf-sidrops-prefer-rrdp-00.txt

Tim Bruijnzeels <tim@nlnetlabs.nl> Tue, 23 February 2021 07:44 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 77C773A27EB for <sidrops@ietfa.amsl.com>; Mon, 22 Feb 2021 23:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=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 mAvp-Pw7IVr7 for <sidrops@ietfa.amsl.com>; Mon, 22 Feb 2021 23:44:19 -0800 (PST)
Received: from outbound.soverin.net (outbound.soverin.net [116.202.65.215]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2E453A27EA for <sidrops@ietf.org>; Mon, 22 Feb 2021 23:44:18 -0800 (PST)
Received: from smtp.soverin.net (unknown [10.10.3.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id 226D2612A7 for <sidrops@ietf.org>; Tue, 23 Feb 2021 07:44:15 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [159.69.232.138]) by soverin.net
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nlnetlabs.nl; s=soverin; t=1614066254; bh=ZDjIivU1FTtmEfVkAd9QpwHWUDA/7djh9YIlQ2g0QAY=; h=Subject:From:In-Reply-To:Date:References:To:From; b=OVt40UFMQ/tHVS/244Bs0Tfb11tc389yheLedf4SL0ulDisSXmRIbAJkDmFU4hv+A GkX4AlH3a7Tl9PUup7XGrKc++LfGwMxstSegWORNF9/eZnsVt+nVXjIilBiM6X+mh3 z+T5q5p6mVFVfVzBa9G9BLcayEGnlsoIaKVE4faF1Gakt7r+t4w/6bs83428J1b6sk nkkjQAyvlOndIOAjl0MREd7bjjtk/35+EzVgj1wreZQDJmUUwzXzLVEkLi15Sd19Fk 3AfdbFNqcv1xfHqUqnQT02Idx29NMlF7mFfBGAnxyMoHV/TXubqt3c1uwVUg9DjQfT wpcqdYR+qubVg==
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Tim Bruijnzeels <tim@nlnetlabs.nl>
In-Reply-To: <161403751321.2598.9484858333244233389@ietfa.amsl.com>
Date: Tue, 23 Feb 2021 08:44:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <76D4E3AD-97BD-40D5-804C-3ED6B875044F@nlnetlabs.nl>
References: <161403751321.2598.9484858333244233389@ietfa.amsl.com>
To: SIDR Operations WG <sidrops@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/_puFT4-132pondEDgKSIVUI76-4>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-prefer-rrdp-00.txt
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, 23 Feb 2021 07:44:22 -0000

Dear working group,

I have asked for 15 minutes on this subject at the upcoming WG session.

Differences in this version:
- rename 'deprecate-rsync' -> 'prefer-rrdp' - as this is the first goal (phases 0-1-2)
- discuss deprecate rsync as a post-phase-2 goal
- start discussion of what would be needed to have transport agnostic names (no rsync in uris)
- moved implementation status overview to the end


Regards,
Tim



> On 23 Feb 2021, at 00:45, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the SIDR Operations WG of the IETF.
> 
>        Title           : Resource Public Key Infrastructure (RPKI) Repository Requirements
>        Authors         : Tim Bruijnzeels
>                          Randy Bush
>                          George Michaelson
> 	Filename        : draft-ietf-sidrops-prefer-rrdp-00.txt
> 	Pages           : 13
> 	Date            : 2021-02-22
> 
> Abstract:
>   This document formulates a plan of a phased transition to a state
>   where RPKI repositories and Relying Party software performing RPKI
>   Validation will use the RPKI Repository Delta Protocol (RRDP)
>   [RFC8182] as the only mandatory to implement access protocol.
> 
>   The first objective is to make RRDP the preferred access protocol,
>   and require rsync as a fallback option only.  This will greatly
>   reduce the operational burden and concerns for RPKI repository
>   operators.
> 
>   In phase 0, today's deployment, RRDP is supported by most, but not
>   all Repositories, and most but not all RP software.
> 
>   In the proposed phase 1 RRDP will become mandatory to implement for
>   Repositories, in addition to rsync.  This phase can start as soon as
>   this document is published.
> 
>   Once the proposed updates are implemented by all Repositories phase 2
>   will start.  In this phase RRDP will become mandatory to implement
>   for all RP software, and rsync will be required as a fallback option
>   only.
> 
>   It should be noted that although this document currently includes
>   descriptions and updates to RFCs for each of these phases, we may
>   find that it will be beneficial to have one or more separate
>   documents for these phases, so that it might be more clear to all
>   when the updates to RFCs take effect.
> 
>   Furthermore, this document currently includes an early discussion of
>   a future objective, which would be to change the RPKI standards such
>   that names in RPKI objects are no longer tightly coupled to rsync.
>   By using transport independent names and validation, we will obtain
>   the agility needed to phase out rsync altogether and/or introduce
>   other future access protocols.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sidrops-prefer-rrdp/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sidrops-prefer-rrdp-00
> https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-prefer-rrdp-00
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops