[Sidrops] ADOPTION: draft-sidrops-bruijnzeels-deprecate-rsync (Ends 2020/27/5)

Chris Morrow <morrowc@ops-netman.net> Wed, 06 May 2020 22:33 UTC

Return-Path: <morrowc@ops-netman.net>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 50C8E3A0D94; Wed, 6 May 2020 15:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 40aGcx224JyZ; Wed, 6 May 2020 15:33:13 -0700 (PDT)
Received: from relay.ops-netman.net (relay.kvm02.ops-netman.net [IPv6:2606:700:e:550:5c82:28ff:fe4c:9503]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9FDC3A0D95; Wed, 6 May 2020 15:33:12 -0700 (PDT)
Received: from mail.ops-netman.net (mailserver.ops-netman.net []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by relay.ops-netman.net (Postfix) with ESMTPS id 7F9A73C21A1; Wed, 6 May 2020 22:33:11 +0000 (UTC)
Received: from mailserver.ops-netman.net.ops-netman.net (localhost []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id 45E0623A; Wed, 6 May 2020 22:33:11 +0000 (UTC)
Date: Wed, 06 May 2020 22:33:11 +0000
Message-ID: <87y2q4ofrs.wl-morrowc@ops-netman.net>
From: Chris Morrow <morrowc@ops-netman.net>
To: sidrops@ietf.org, sidrops-ads@ietf.org, sidrops-chairs@ietf.org
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 Mule/6.0 (HANACHIRUSATO)
Organization: Operations Network Management, Ltd.
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/yc1b1i-t5ThQaFHRhAYEb55Q09k>
Subject: [Sidrops] ADOPTION: draft-sidrops-bruijnzeels-deprecate-rsync (Ends 2020/27/5)
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: Wed, 06 May 2020 22:33:16 -0000

Howdy WG Folks!  Can we please read/consider and think back to our
robust conversation at the interim meeting :) about:


and consider whether or not we should adopt this draft as a working-group
work item? We shall endeavor to close out this adoption call 27 May 2020.

Abstract included:
  "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.

   In short this plan consists of the following phases.

   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 must no longer be used.

   Measurements will need to be done to help determine when it will be
   safe to transition to the final phase of this plan.  During this
   phase Repositories will no longer be required to provide rsync access
   for RPKI validation purposes.  However, they may still provide rsync
   access for direct access to files for other purposes, if desired, at
   a best effort basis.

   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 separate documents for the plan, and each phase, so that it
   might be more clear to all when the updates to RFCs take effect."

There have already been ~10 folk express support on-list for this, so we'll
count their votes in the final tally 5/27/2020.