I carefully read draft-ietf-pkix-dpv-dpd-00.txt because we are
probably going to use it in order to build such a PKI server.
I noticed some typos in the draft and would like to suggest some
changes.
Best regards - Petra
chapter 5.2. Detailed Protocol
Three more terms need to be imported:The terms imported from elsewhere are: Extensions, CertificateSerialNumber, SubjectPublicKeyInfo, Name, AlgorithmIdentifier, CRLReason, CompleteCertificateRefs, CompleteRevocationRefs.
chapter 5.2.1. Request
ValPolicyID :: = CHOICE {
policybyOId OBJECT IDENTIFIER,
policybyURN NAME }
What is the ASN.1 term "NAME"? I only know Name, which is
I guess you meant:The value for valPolicyHash SHALL be computed on the hash of the DER encoding of ValidationPolicyDef when ...
Again, I'd suggest to use a GeneralName:ValPolLocations :: = SEQUENCE OF Name
PathValues :: = SEQUENCE {
certificateValues CertificateValues,
revocationValues RevocationValues }
Move the definition to chapter 5.2.2. Response Syntax
I guess, it should be:validationPolicyRef is a reference to the validation policy to be used.
Later on in the same paragraph:
add at the end of the sentence:... It is composed of an OID or a URN, the hash algorithm to be used to compute the hash value of the policy and the hash value of the policy.
chapter 5.2.2. Response Syntax
Just a typo. I think it should be:The value for returnedRefsHash SHALL be computed on the hash of the DER encoding of CertPathRefs.
To make it easier to understand you could add at the end of the sentence:
... CertPathRefs which are part of the DPVResponse.
The same for the next sentence:
The value for pathValuesHash SHALL ...The value for returnedValuesHash SHALL be computed on the hash of the DER encoding of CertPathValues
... this allows to keep the whole response short and ...pathReferencesHash is a hash computed over the references of the path (both the references of the certificates used and the references of the revocation information used). It may also include a sequence of time-stamps, if this has been requested in the request. Since only the hash is included in the signature, this allows to keep signatures short and does not mandate to know the values of the references of the path to verify the dPVResponseStatus from the response.
The same for the next paragrah!
responseExtensions is a way...requestExtensions is a way to allow additional elements to be added later on, if needed.
chapter 6.2. Detailed Protocol
One more terms needs to be imported:
OtherCertID
chapter 8.2. Response
TbsDefResponse ::= SEQUENCE {
tbsResponseData VPDefResponseData,
signatureAlgorithm AlgorithmIdentifier OPTIONAL,
signature BIT STRING OPTIONAL,
certs [0] EXPLICIT SEQUENCE OF Certificate
OPTIONAL }
It should be:
TbsVPDefResponse ::=
SEQUENCE {