Hi Lancheng,

Thank you for your suggestion! We, the authors, think it is a good idea to use 
“roles” in an entity object to distinguish CA operator from publication 
repository operator.

There is also an ongoing discussion about the newly proposed “rdap-base-down” 
relation type (along with few others vis-a-vis base versus full URIs), which 
would obviate the “rdap-help” relation type proposal in the "RDAP for Delegated 
and Hybrid RPKI” section [1].

We’d incorporate your suggestion in the next version of the draft.

Thanks,
Jasdip

[1] 
https://www.ietf.org/archive/id/draft-ietf-regext-rdap-rpki-04.html#name-rdap-for-delegated-and-hybr


From: Lancheng <[email protected]>
Date: Wednesday, September 16, 2026 at 10:59 PM
To: [email protected] <[email protected]>
Cc: [email protected] 
<[email protected]>
Subject: Suggestion on publication repository operator information 
(draft-ietf-regext-rdap-rpki)

Dear Authors and all,

I have reviewed draft-ietf-regext-rdap-rpki and would like to offer a 
suggestion for your consideration.

Publication repositories are an important component of the RPKI infrastructure. 
Operational or availability issues with a repository can affect RPKI data 
synchronization and, consequently, the information derived from RPKI. 
Therefore, being able to identify and contact the organization operating a 
publication repository can be useful for troubleshooting.

As I understand it, the document associates RPKI objects with entities and also 
provides publicationUri, notificationUri, and rpkiType. However, the CA and the 
publication repository are not necessarily operated by the same organization. 
In such cases, it seems that the current model does not explicitly identify the 
organization operating the publication repository or provide its contact 
information.

Would it be useful to consider representing both the CA operator and the 
publication repository operator when they are different entities? For example, 
the associated entities could have different roles to distinguish the CA 
operator from the repository operator.

Best,
Lancheng
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to