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

Russ Housley <housley@vigilsec.com> Fri, 26 January 2024 19:56 UTC

Return-Path: <housley@vigilsec.com>
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 51B65C14F60E; Fri, 26 Jan 2024 11:56:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=ham autolearn_force=no
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 KOvQtS7LssfP; Fri, 26 Jan 2024 11:56:06 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 7C7F4C14F5F9; Fri, 26 Jan 2024 11:56:06 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id D820C12E0D4; Fri, 26 Jan 2024 14:56:05 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id C178812DE57; Fri, 26 Jan 2024 14:56:05 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <87h6j1kug1.wl-morrowc@ops-netman.net>
Date: Fri, 26 Jan 2024 14:55:55 -0500
Cc: IETF SIDRops Chairs <sidrops-chairs@ietf.org>, sidrops-ads@ietf.org, Keyur Patel <keyur@arrcus.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B60D7B39-FA81-45AF-BCBD-2784F91B43C3@vigilsec.com>
References: <87h6j1kug1.wl-morrowc@ops-netman.net>
To: IETF SIDRops <sidrops@ietf.org>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/fS_OPKAjPWcxmft9wXYWnUE_RPE>
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: Fri, 26 Jan 2024 19:56:10 -0000

Hi.

<no_hats>

I this the WG should adopt this document.

Section 4 says:

   The Publication Server handles the server side of the [RFC8181]
   Publication Protocol.  The Publication Server generates the content
   for the public-facing RRDP and Rsync Repositories.  It is strongly
   RECOMMENDED that these functions are separated from serving the
   repository content.

This is fine, but is should probably say more about all of the files that are referenced by a Manifest being available before the Manifest is published.

</no_hats>

Russ



> On Jan 25, 2024, at 3:51 PM, Chris Morrow <morrowc@ops-netman.net> wrote:
> 
> 
> Howdy WG Folks!
> It looks like Tim put together a document to talk about operations / BCPs for
> publication servers, having to do with Rsync/Rrdp and such:
> 
>  draft-timbru-sidrops-publication-server-bcp-02:
>  (https://datatracker.ietf.org/doc/draft-timbru-sidrops-publication-server-bcp/)
> 
> I would like to ask that folks review the document and think about whether or not
> this should be taken up as a WG item, and fixed up for eventual publication.
> 
> Thanks!
> -chris
> co-chair-2-of-3
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops