Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.1\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: 
 <178898307521.113676.17486976009212895070@dt-datatracker-9769b79f-kjm76>
Date: Fri, 11 Sep 2026 14:53:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DA17B1D-2379-43F9-8829-6AAC9931DF1F@ripe.net>
References: 
 <178898307521.113676.17486976009212895070@dt-datatracker-9769b79f-kjm76>
To: Behcet Sarikaya <sarikaya@ieee.org>
Message-ID-Hash: 5ODXV25HPWSO355ACAMRIKJ5QJF5D6ZM
CC: gen-art@ietf.org, draft-ietf-sidrops-publication-server-bcp.all@ietf.org,
 last-call@ietf.org, sidrops@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BGen-art=5D_Re=3A_draft-ietf-sidrops-publication-server-bcp-10_i?=
 =?utf-8?q?etf_last_call_Genart_review?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/gen-art/V54EwngBslatPClJmijfy3SDivQ>

Hi Behcet,

Thank you for your review. Updated text is in this commit:
=
https://github.com/timbru/draft-sidrops-publication-server-bcp/commit/2b44=
1e82332516e886628b2cad0103e33ec8f73c

See inline, for quick responses.


> On 9 Sep 2026, at 21:44, Behcet Sarikaya via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Document: draft-ietf-sidrops-publication-server-bcp
> Title: Best Practices for Operating Resource Public Key Infrastructure =
(RPKI)
> Publication Services Reviewer: Behcet Sarikaya Review result: Ready =
with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://wiki.ietf.org/en/group/gen/GenArtFAQ>.
>=20
> Document: draft-ietf-sidrops-publication-server-bcp-10
>=20
> Reviewer: Behcet Sarikaya
> Review Date: 2026-09-09
> IETF LC End Date: 2026-09-11
> IESG Telechat date: Not scheduled for a teletext
>=20
> Summary:The document is intended to be a BCP to describe operating =
Resource
> Public Key
>   Infrastructure publication engine and its associated publicly
>   accessible rsync and RPKI Repository Delta Protocol repositories.
>=20
> It has many issues, editorial which I mainly concentrated and =
technical as can
> be seen in other reviews. Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
>=20
> Section 1
>=20
> Par. 3
> Publication services operations t
>=20
> a hanging t???

Dangling sentence was removed. Apologies, overlooked this when editing.


> Par.4
>=20
> These services typically include the
>   Publication Enging (backend) and the public facing repositories for
>   RRDP and rsync functions.
>=20
> Enging -> Engine

This was already fixed in an earlier commit (after publication of -10)

>=20
> Par. 5
> seperation of functions ->
>   separation of functions

ack

>=20
> Par 6
> In a addition some guidance is provided for CA operators in as far as
>   CA operator choices relate to publication
> -> In addition ...

ack

> There is a figure in Section 1 with no caption

As the figure is introduced in the text and not referenced elsewhere
I don't think it needs a caption.

> Section 2.3
> RP Relying Party
> This document discusses the use of RP in routing however there is =
another very
> important area where RP is used, in identity protocols like OAUTH 2.0. =
The
> resources they protect in each case are completely different. This =
leads to a
> confusion in readers mind. I think the document should have one or two
> paragraphs to explain this unfortunate (?) name convention or if there =
are
> places where they interact.

Answered by Job in another thread.

>=20
> Section 4.1
> 2nd par.
> the acronym CDN is expanded here but already used in Section 1 twice.

Ok, I expended the mention in the text of section 1 instead. I left the =
acronym
in the figure because of space.


Thank for you for the review.

Tim


>=20
>=20