Received: from mail-ed2-x10.google.com (mail-ed2-x10.google.com
 [IPv6:2a00:1450:4864:33::10])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange x25519 server-signature ECDSA (prime256v1) server-digest
 SHA256)
	(No client certificate requested)
	by mx.ietf.org (Postfix) with ESMTPS id 5B89A3F
	for <sidrops@ietf.org>; Tue, 22 Sep 2026 11:26:13 +0000 (UTC)
Authentication-Results: mx.ietf.org;
	dkim=pass header.d=ripe.net header.s=google1 header.b=onxkfDkq;
	dmarc=pass (policy=none) header.from=ripe.net;
	spf=pass (mx.ietf.org: domain of tbruijnzeels@ripe.net designates
 2a00:1450:4864:33::10 as permitted sender)
 smtp.mailfrom=tbruijnzeels@ripe.net
Received: by mail-ed2-x10.google.com with SMTP id
 4fb4d7f45d1cf-6a996c8adf3so6691092a12.1
        for <sidrops@ietf.org>; Tue, 22 Sep 2026 04:26:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=ripe.net; s=google1; t=1790076366; x=1790681166; darn=ietf.org;
        h=to:references:message-id:content-transfer-encoding:cc:date
         :in-reply-to:from:subject:mime-version:content-type:from:to:cc
         :subject:date:message-id:reply-to:content-type;
        bh=UFwm/SxQ5xhIFgvKd3153JSLTHsyPwRQCWeR8T0afp4=;
        b=onxkfDkqKCtRHYmCckOtPFqW9QlhgVyomLIvms1c81v4jEKdTSOMVefzetnxxp9nJ9
         xPEx8rytn4N15F29Dm5wys67qFs4cq+jbnHLhBkIsht7/FIP8cMgQkzdUTS8Cg7vDnVn
         Ze8rs9Rj3DEnJraQPnWhDRXfFr9VrrpEpX9iBgeuBIa1/BA8uU9V6BIjrBBXvTnr88Z9
         nKZVxauZ8HdTyc93nBEdV9FDCcJ+T/VZJ8hDUClC0e0kEgDAbukAhFjO3frO4ADsZ+Be
         JBbunwDk4qnPXPr6vw6QXct37zZQqJXOJR/iKA6BsILBYK62GaSiZyNVxVfe1afjXo+Q
         zDAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20260707; t=1790076366; x=1790681166;
        h=to:references:message-id:content-transfer-encoding:cc:date
         :in-reply-to:from:subject:mime-version:content-type:x-gm-gg
         :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to
         :content-type;
        bh=UFwm/SxQ5xhIFgvKd3153JSLTHsyPwRQCWeR8T0afp4=;
        b=Nib9MVDFC4+GQ/GP1KvBntPcnSR7luuuFXDjUFv4xFzY3FUUL6Pejx0VWWJfLvuq33
         XLC1W1AyFomr/8qwg8fQgZaXOgj2hGUVX4LY3qrLD4D8VMAiekIUW2Pl8LnX4OdRvQh/
         TYQh/7VsAz6GRjH9GJbv4NrqIV1BphVC3+vk6n2X2DLoCkkbBcdqWTOmk9O52pns6JUn
         qyKnqzJDcbi3/LAsG+BCpw20L37nMS8QrQFR/A71FiCDSYlAsu/xtK01q+YYdyjU70Jn
         +Rj1pOfRcigaIl1w6Kohohs2dTDBhWVYNUKsw6dBNALOOlt22JWPOeJA32B/kAWJn4FJ
         L0sQ==
X-Forwarded-Encrypted: i=1;
 AKwUvBwPD5HfqpYFcJzO2VQoGR4Ddk0VZ1YZHDTWrxJfdTkbxqQDnEOdU6WM4T8sZCNW5ObJnGQXRaaz@ietf.org
X-Gm-Message-State: AFuF++ltnQiBzOGjRNFl4KqrFFqAo6XdZwwok/DQQlsBlZoWPKQck8TI
	coohL7DIzbtiuCjTUsnqM+2uPcXlJchcgXZBa4r05OMlI1JAHIgxo9YuAiHAi4khYrw=
X-Gm-Gg: AYBFou1mq4KKagOJZLPp+CqKnFe9SHaaSdOUGXu0z7VdFagZDQxJK3dANoYDelIBLj9
	zYJspwS1eFs5v1dIBN++k8wm0JluI/E5kARd+WYTjEUy8hyvztG5oQh3s8YxPNUhl0lMQjkLFrQ
	tulGwrh409Q5FiiKCIn1/TRvV5d7cPVkMBpTdTtn460YhlokmdUw504aS2Q5AGQG/D0UG0fCeT6
	S2RmMzqVRI4jV6a3MAUR6+JITIcv8Og+gUtEhMpMHFJD92mxwaDGJNOxXEinhVC3LL8KOscaRWx
	ht9XBGffAz1PmRgbY+0pOtD87PrnHfY257ECRbYOM2xK3irVDHQyeVdlNFjn8MDFvZAti4LmTs2
	TK7PSpuddOYxGu5yOFexwtpI0d1yqx5OIHU/OB1pgO/UImANsPdXZ4jF+cxANglALYb8e4T1EJz
	+7d0zFO8CWlcUVqO8Rj3NXllNila0xvHordqZhKWXd2Yt0Ex7k0SkVx2UgYs8s7K0bO4HRBfdnj
	I4xVmoPgKYUXDYDK9GEFXmqUSu+VrwARyDd1jT7+NmWWOqj
X-Received: by 2002:a17:907:c48b:b0:c29:3e59:fd03 with SMTP id
 a640c23a62f3a-c2a156eb039mr1146229966b.18.1790076365884;
        Tue, 22 Sep 2026 04:26:05 -0700 (PDT)
Received: from smtpclient.apple (dhcp-21-129.ripe.net. [193.0.21.129])
        by smtp.gmail.com with ESMTPSA id
 a640c23a62f3a-c2a9c5b2cc0sm68871566b.35.2026.09.22.04.26.05
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 22 Sep 2026 04:26:05 -0700 (PDT)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.3\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: 
 <178976427618.1287.16841443831092394455@dt-datatracker-fffdbdc97-wjd6q>
Date: Tue, 22 Sep 2026 13:25:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F051FCC-D1B6-42FA-9F8A-63B87DAA3D7F@ripe.net>
References: 
 <178976427618.1287.16841443831092394455@dt-datatracker-fffdbdc97-wjd6q>
To: Roman Danyliw <rdd@cert.org>
X-Mailer: Apple Mail (2.3864.700.51.1.3)
X-Spamd-Bar: --
Message-ID-Hash: CMB5QCRKFKAAP3GZJKT4JX5ZTZG564GU
X-Message-ID-Hash: CMB5QCRKFKAAP3GZJKT4JX5ZTZG564GU
X-MailFrom: tbruijnzeels@ripe.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; header-match-sidrops.ietf.org-0; emergency;
 member-moderation; nonmember-moderation; administrivia; implicit-dest;
 max-recipients; max-size; news-moderation; no-subject; digests;
 suspicious-header
CC: The IESG <iesg@ietf.org>,
 draft-ietf-sidrops-publication-server-bcp@ietf.org, ggx@gigix.net,
 sidrops-chairs@ietf.org, sidrops@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Sidrops] Re: Roman Danyliw's Discuss on
 draft-ietf-sidrops-publication-server-bcp-11: (with DISCUSS and COMMENT)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/sidrops/Dd-LRysbXggM0D3WXQD1bihJOzg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Hi Roman, all,

> On 18 Sep 2026, at 22:44, Roman Danyliw via Datatracker =
<noreply@ietf.org> wrote:
>=20
> ** Section 6.3.
>   It is RECOMMENDED to serve rsync repositories from local storage, so
>   that the host operating system can optimally use its I/O cache.
>   Using network storage is NOT RECOMMENDED, because it may not benefit
>   from this cache.  For example, when using NFS, the operating system
>   might not be able to cache the directory listing(s) of the
>   repository.
>=20
> Is the WG confident that this generic statement considers all of the =
nuances of
> the very diverse set of network storage options in the marketplace.  =
Host OS
> I/O cache management is but one of many considerations.

To be honest, no...

This text was (of course) well intended and inspired by a real issue one
of the co-authors experienced. So, we believe it's good to raise =
awareness
but perhaps a tuned down statement is more appropriate.

How about:

   It is recommended to choose a storage backing that minimizes I/O
   overhead and allows the host operating system to fully leverage its
   filesystem cache. Operators should be cautious about using network
   storage, as doing so can have a negative impact on this and result
   in severely degraded rsync performance, especially on large
   repositories.

> If the WG confident it should be specifying hardware configurations =
for RPKI?

No, probably not.=20

Kind regards

Tim



