[Sidrops] What are the RFC 5280 § 6.1.1 inputs for (c) (e) (f) (g) in context of RFC 8360?

[Job Snijders <[e-mail]>]

Dear working group,

The rpki-client project developers are studying how to implement support
for RFC 8360, while at the same time maintain compliance with RFC 6487 and
RFC 5280.

RFC 5280 § 6.1.1 defines a number of "Inputs" which are used in the
algorithm to establish validity.

RFC 8360 doesn't specify the following inputs:

(c)  user-initial-policy-set: A set of certificate policy
identifiers naming the policies that are acceptable to the certificate user.

(e)  initial-policy-mapping-inhibit, which indicates if policy mapping is
allowed in the certification path.

(f)  initial-explicit-policy, which indicates if the path must be valid for
at least one of the certificate policies in the user-initial-policy-set.

(g)  initial-any-policy-inhibit, which indicates whether the anyPolicy OID
should be processed if it is included in a certificate.

Without the above information implementation is somewhat challenging.

Perhaps it’s worthwhile to re-re-consider updating the algorithm to allow
for intermediate CAs to overclaim? This expired draft by no means is
perfect but it might be a starting point
https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-validation-update-02.html

Kind regards,

Job