At 9:20 AM +0200 10/8/10, Andrei Robachevsky wrote:
Steve,
Stephen Kent wrote on 7/10/10 12:20 AM:
[...]
Andrei: I do not agree with your suggestion to remove the CPS MUSTs in
the CP. The intent is to help ensure that each CA (as amended below, in
2.2) has a CPS, and that the CPS covers certain basic info. If each
parent registry were to act as an approver for a subordinate CPS, this
would not encourage RPKI-wide uniformity re CPS's.
The third parties are machines in the PKI. No one will ever read a CPS,
not check if it is there (with an exception of RIRs and IANA, maybe).
The only way to make it less pro forma is to request the parent to sign
off on the compliance of the child CA (hence my comment re 1.6.3.). But,
IMO, this will be an overkill at this stage. I understand the intention,
but suggest relaxing it to at least SHOULD to make it more realistic.
Andrei
Andrei,
A CA is not a machine. A CA is an entity, usually an organizational
entity, that uses people to execute procedures and uses a computer to
perform algorithmic functions. If a registry (at any tier) offers a
managed CA service for folks to whom it has allocates resources, it
is the registry that is acting as a CA in conjunction with the org
that took advantage of the managed service offer. (pardon the overly
long sentence.)
Noentheless, we'll change the text from MUST to SHOULD.
Steve
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr