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

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.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-sidrops-publication-server-bcp-10

Reviewer: Behcet Sarikaya
Review Date: 2026-09-09
IETF LC End Date: 2026-09-11
IESG Telechat date: Not scheduled for a teletext

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.

It has many issues, editorial which I mainly concentrated and technical as can
be seen in other reviews. Major issues:

Minor issues:

Nits/editorial comments:

Section 1

Par. 3
Publication services operations t

a hanging t???
Par.4

These services typically include the
   Publication Enging (backend) and the public facing repositories for
   RRDP and rsync functions.

Enging -> Engine

Par. 5
seperation of functions ->
   separation of functions

Par 6
In a addition some guidance is provided for CA operators in as far as
   CA operator choices relate to publication
-> In addition ...
There is a figure in Section 1 with no 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.

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


_______________________________________________
Gen-art mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to