Re: [Sidrops] draft-ymbk-rpki-rov-timing-00.txt

Tim Bruijnzeels <tim@nlnetlabs.nl> Wed, 22 April 2020 11:57 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 C598E3A0A4A for <sidrops@ietfa.amsl.com>; Wed, 22 Apr 2020 04:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.901
X-Spam-Level: **
X-Spam-Status: No, score=2.901 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, GB_SUMOF=5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 oM0sKWIcnxpD for <sidrops@ietfa.amsl.com>; Wed, 22 Apr 2020 04:57:11 -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 239763A0A4B for <sidrops@ietf.org>; Wed, 22 Apr 2020 04:57:11 -0700 (PDT)
Received: from [IPv6:2001:981:4b52:1:143e:3685:6859:5dc0] (unknown [IPv6:2001:981:4b52:1:143e:3685:6859:5dc0]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 0AB6C16C19; Wed, 22 Apr 2020 13:57:09 +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=1587556629; bh=ju5WzGIe+IHCe302f3FyltJLj+FOmXGCpP9Qhke8SNc=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=dmQkizhUdbOJgWXXPp96oM9gni0S31Liudu1yQ54C93t0G+Z4V8vlOHeRuyEdPYhc W2x77SGqNdLv/a0OBNpR3uqI/oaf/n1zHCjzZrAchSpJWNpgCtaDVQ8eIVx91RSIKy XN4xCAYTrIA4wpf7sWxIpvTT5PrJ+bBDboLdpSV4=
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: <m2k128harb.wl-randy@psg.com>
Date: Wed, 22 Apr 2020 13:57:08 +0200
Cc: SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <98A4118B-83F0-4BBD-BA22-794ADA475731@nlnetlabs.nl>
References: <m2k128harb.wl-randy@psg.com>
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/4eom8OtHszQ9H6kQI-YaYx-sCcY>
Subject: Re: [Sidrops] draft-ymbk-rpki-rov-timing-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: Wed, 22 Apr 2020 11:57:13 -0000

Hi,

s/rcynic/rsync/g

Furthermore, I think the document could use some words on the chain before the CA. i.e. timing of creation of ROAs in the CA w.r.t. changes in announcements done.

I would say that for planned changes ROAs should be created in advance, X minutes where X > the sum of the timings after a CA creates a ROA and until it's seen by routers. For unplanned changes, I guess they should just be created ASAP, but it may help to quantify?

As a side note. We are discussing moving from rsync to RRDP in another thread. I believe that RRDP will help reduce propagation times. But I have no doubt that further improvements can be conceived in future. It helps to have guidance for maximum propagation times to serve as guidance for requirements there.

Tim



> On 21 Apr 2020, at 21:58, Randy Bush <randy@psg.com> wrote:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-ymbk-rpki-rov-timing-00.txt
> To: "Randy Bush" <randy@psg.com>om>, "Job Snijders" <job@ntt.net>
> Date: Tue, 21 Apr 2020 12:44:35 -0700
> 
> 
> A new version of I-D, draft-ymbk-rpki-rov-timing-00.txt
> has been successfully submitted by Randy Bush and posted to the
> IETF repository.
> 
> Name:		draft-ymbk-rpki-rov-timing
> Revision:	00
> Title:		Timing Parameters in the RPKI based Route Origin Validation Supply Chain
> Document date:	2020-04-21
> Group:		Individual Submission
> Pages:		6
> URL:            https://www.ietf.org/internet-drafts/draft-ymbk-rpki-rov-timing-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-ymbk-rpki-rov-timing/
> Htmlized:       https://tools.ietf.org/html/draft-ymbk-rpki-rov-timing-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ymbk-rpki-rov-timing
> 
> 
> Abstract:
>   This document explores, and makes recommendations for, timing of
>   Resource Public Key Infrastructure publication, propagation, and use
>   of RPKI ROV data in relying parties and routers.
> 
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
> 
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops