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

Job Snijders <> Fri, 26 March 2021 16:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3268C3A223C for <>; Fri, 26 Mar 2021 09:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id o0rnrcbEOw1b for <>; Fri, 26 Mar 2021 09:16:33 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B96973A23BC for <>; Fri, 26 Mar 2021 09:15:46 -0700 (PDT)
Received: by with SMTP id u9so9232290ejj.7 for <>; Fri, 26 Mar 2021 09:15:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=AHmY6vTINdb3FJOOfM1TRs03lMqMaxnRRHELka9ZAM0=; b=qGA/vCMzOw3M1RGOQbeySOw3241Eja2WE09F1flOHg6MdZI262/j/DojnEWcnJu0qf 7/3ME7veC3B61KkLhyWgxuYty392pNa+nUFdn+Tlc7wOXM0+XtpdrXcDgYfXzrPjkH2b gLUjC5PjMJURB7fQzRx5jf898EynSpHLwbaNs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=AHmY6vTINdb3FJOOfM1TRs03lMqMaxnRRHELka9ZAM0=; b=jlgG08wUHSd5+ZpEZetmXgSv59gehRbyk4hNsZ0g1De76L6ka0FW3t+Z31G1i+BpoE sKbJQVDsRJOAzeEoqfBuVR7rmzwbbZoO0HajlWOWV4nZbx6NUVWmgy5HZFwKPXxeif/S PtljCmnXavoTFUg2gx8pzVXClQ93hp8oyIZCRify/cFzqN6wKyHmKzTT5m6yt/8YBZNN AmtgToMdOnCF8qDBrh65UqVVEl11jHvuhUwFymRMbIv5O5b8TuepbXWjfysulDjcR+75 QcZx/gJlwZq5bxZYu7tRYF95MP1YLZGaKOvRSI0qAlV1mqXMcIZQR4L2OHRDKH4WiEXl cbhA==
X-Gm-Message-State: AOAM533XGiknMWVwn7RnHgMmaLe0ne6p8pADCDkJONkrlseweGpUEC4T 7Ecgyj5FfLwuTFdkvoiXjxmL6A==
X-Google-Smtp-Source: ABdhPJwGGPiRBKK5uN0ffJVu30y8n4GPb2xUFNWmBZ2vuqXo9cbOllOo5SPIkKaZZcmiAMdF0AR1bQ==
X-Received: by 2002:a17:906:d9c9:: with SMTP id qk9mr15951636ejb.504.1616775343971; Fri, 26 Mar 2021 09:15:43 -0700 (PDT)
Received: from snel ( []) by with ESMTPSA id n25sm4477065edq.55.2021. (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Mar 2021 09:15:43 -0700 (PDT)
Date: Fri, 26 Mar 2021 17:15:42 +0100
From: Job Snijders <>
To: Ties de Kock <>
Cc: Tim Bruijnzeels <>, SIDR Operations WG <>
Message-ID: <YF4Irln8qM4w8i3o@snel>
References: <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-prefer-rrdp-00.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 26 Mar 2021 16:16:37 -0000

On Fri, Mar 26, 2021 at 10:43:15AM +0100, Ties de Kock wrote:
> However, scaling rsync so it is available when all clients fallback in
> a short period (we see ~1170 unique ips retrieve notification.xml in a
> 10 minute window) is difficult.

Have you considered using a TCP proxy application like 'haproxy' to
distribute rsync clients across multiple rsync backends? One can even
anycast rsync servers to distribute load!

> Fallback will happen rarely, which implies that their copy of the
> repository is potentially (very) outdated. A clean copy from rsync
> takes ~10-15 CPU-seconds per client (and potentially a large number of
> IOPS hitting the backing storage) on the server-side.

Unless the validator constructs a cache as if the data was fetched via
rsync... It is possible to make a validator that'll have a 'warm' cache
when connecting to rsync after having connected to RRDP a few times.

The RIPE RPKI repository currently is only ~ 200 megabytes, I project
that in the next 4 years it won't reach 1 gigabyte. This is such a small
size that one can easily serve this from RAM in frontend caches and not
waste IOPS from 'backing storage'.

It appears Randy came up with a simple suggestion:

another consideration:

The rpki-client default installation on OpenBSD/Ubuntu/Debian will be
launched at a random minute of the hour, and will (for the lifetime of
the governing cron/systemd process) fetch at that choosen minute of the

Validator implementations which are started in 'oneshot' mode
(rpki-client, 'routinator vrps', 'fort --mode=standalone') should
immediately try rsync when RRDP fails for one reason or another.

A 'oneshot' implementation should not insert a 'sleep' between a failed
rrdp fetch and an attempt to connect using rsync.

Kind regards,