IETF Logo Mail Archive

Re: [Sidrops] [WG ADOPTION] Adoption call: draft-timbru-sidrops-publication-server-bcp - ENDS 02/08/2024

Tim Bruijnzeels <tbruijnzeels@ripe.net> Tue, 06 February 2024 09:57 UTC

Return-Path: <tbruijnzeels@ripe.net>
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 DE78FC14F691; Tue, 6 Feb 2024 01:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ripe.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57ZpX6gcyVrO; Tue, 6 Feb 2024 01:57:39 -0800 (PST)
Received: from mail-mx-2.ripe.net (mail-mx-2.ripe.net [IPv6:2001:67c:2e8:11::c100:1312]) (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 ietfa.amsl.com (Postfix) with ESMTPS id CFE9FC14F696; Tue, 6 Feb 2024 01:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ripe.net; s=s1-ripe-net; h=To:Message-Id:Cc:Date:From:Subject:Mime-Version:Content-Type ; bh=aAP1nTDP+mVvqXkAo+v+tkiPjmDWPFWfzW6nJzgO5eA=; b=a+01dcImBKgC7g2RuqicM2Eu 70ZgslKmxIBDKCjbhiE1uwBssTdCSmHc4Cw0mpziiwlRjhD8fiPLAcVvDY566Y4WLS+5dhOCodXk4 L2c8ugcZbnTr6E98c595dDqD8dwubaiIaPWhMrfotuJpMQLxXAqYo6xvhaEGb01dKQmJB5IAfO8Ay cenCJehC16bB5OEA7upCWN7BRgvpfzxxs8RCfun+hpsbtiH3avlDnAQgyw7pT+k73pLhUVN7FqCCO N+hbyM6LfmFvqspEkXvHsYBPqCQ5o9QJOUEFG0vfmQVUFhRRfThksAaYTWXZp6iLjkeT2o+c3hroK 0KcbpsNLYw==;
Received: from imap-01.ripe.net ([2001:67c:2e8:23::c100:170e]:59082) by mail-mx-2.ripe.net with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <tbruijnzeels@ripe.net>) id 1rXICr-00Aafq-0m; Tue, 06 Feb 2024 09:57:33 +0000
Received: from sslvpn.ipv6.ripe.net ([2001:67c:2e8:9::c100:14e6] helo=smtpclient.apple) by imap-01.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <tbruijnzeels@ripe.net>) id 1rXICr-00AvEb-0P; Tue, 06 Feb 2024 09:57:33 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: <ZcFNNfrkMFxKf5hN@snel>
Date: Tue, 06 Feb 2024 10:57:22 +0100
Cc: Russ Housley <housley@vigilsec.com>, IETF SIDRops <sidrops@ietf.org>, IETF SIDRops Chairs <sidrops-chairs@ietf.org>, sidrops-ads@ietf.org, Keyur Patel <keyur@arrcus.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8E04A04-D270-4E31-B72D-AB048398712E@ripe.net>
References: <87h6j1kug1.wl-morrowc@ops-netman.net> <B60D7B39-FA81-45AF-BCBD-2784F91B43C3@vigilsec.com> <ZcFNNfrkMFxKf5hN@snel>
To: Job Snijders <job=40fastly.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
X-RIPE-Signature: 7105a661eeefe5d5c9c241e9d0d5d890c6ba18877c6050f3a36403cd4e9a6a19
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/EggUrW0dFxA394kMEH2kHfNaUGk>
Subject: Re: [Sidrops] [WG ADOPTION] Adoption call: draft-timbru-sidrops-publication-server-bcp - ENDS 02/08/2024
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
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, 06 Feb 2024 09:57:43 -0000

Hi Job, all,

Job, thank you for your feedback. I will go over some of your other points later, but wanted to respond to this point now:

> On Feb 5, 2024, at 22:03, Job Snijders <job=40fastly.com@dmarc.ietf.org> wrote:
> 
> - Section 6 could perhaps (in addition to the phrase 'consistent')
>  describe the desired outcome using the phrase 'atomic'. I think within
>  our community we often describe the cause of 'failed fetches' as the
>  repository being updated in a non-atomic fashion. 

This section is really about having a consistent, unchanging, view in rsync.

There is another, related, issue though that CAs need to publish all their content in a consistent way, using a multi-element RFC 8181 publication, to ensure that their Manifest, CRL and all signed certificates and RPKI objects are published atomically. I thought of including some text on this, but technically it’s a BCP for a CA, rather than a Publication Server. I don’t mind extending this document with CA concerns, but if preferred we could consider having a separate BCP for CAs.

Tim

v2.27.8 | Report a Bug | By Email | System Status