Skip to content

Commit d750987

Browse files
committed
subjectPublicKeyInfoAlgorithm => subjectPublicKeyAlgorithm
1 parent 0c87255 commit d750987

1 file changed

Lines changed: 25 additions & 26 deletions

File tree

draft-ietf-plants-merkle-tree-certs.md

Lines changed: 25 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -942,29 +942,29 @@ When `type` is `tbs_cert_entry`, `N` is the number of bytes needed to consume th
942942

943943
~~~asn.1
944944
TBSCertificateLogEntry ::= SEQUENCE {
945-
version [0] EXPLICIT Version DEFAULT v1,
946-
issuer Name,
947-
validity Validity,
948-
subject Name,
949-
subjectPublicKeyInfoAlgorithm AlgorithmIdentifier{PUBLIC-KEY,
950-
{PublicKeyAlgorithms}},
951-
subjectPublicKeyInfoHash OCTET STRING,
952-
issuerUniqueID [1] IMPLICIT UniqueIdentifier OPTIONAL,
953-
subjectUniqueID [2] IMPLICIT UniqueIdentifier OPTIONAL,
954-
extensions [3] EXPLICIT Extensions{{CertExtensions}}
955-
OPTIONAL
945+
version [0] EXPLICIT Version DEFAULT v1,
946+
issuer Name,
947+
validity Validity,
948+
subject Name,
949+
subjectPublicKeyAlgorithm AlgorithmIdentifier{PUBLIC-KEY,
950+
{PublicKeyAlgorithms}},
951+
subjectPublicKeyInfoHash OCTET STRING,
952+
issuerUniqueID [1] IMPLICIT UniqueIdentifier OPTIONAL,
953+
subjectUniqueID [2] IMPLICIT UniqueIdentifier OPTIONAL,
954+
extensions [3] EXPLICIT Extensions{{CertExtensions}}
955+
OPTIONAL
956956
}
957957
~~~
958958

959959
The fields of a TBSCertificateLogEntry are defined as follows:
960960

961961
* `version`, `issuer`, `validity`, `subject`, `issuerUniqueID`, `subjectUniqueID`, and `extensions` have the same semantics as the corresponding TBSCertificate fields, defined in {{Section 4.1.2 of !RFC5280}}.
962962

963-
* `subjectPublicKeyInfoAlgorithm` describes the algorithm of the subject's public key. It is constructed identically to the `algorithm` field of a SubjectPublicKeyInfo ({{Section 4.1.2.7 of !RFC5280}}).
963+
* `subjectPublicKeyAlgorithm` describes the algorithm of the subject's public key. It is constructed identically to the `algorithm` field of a SubjectPublicKeyInfo ({{Section 4.1.2.7 of !RFC5280}}).
964964

965965
* `subjectPublicKeyInfoHash` contains the hash of subject's public key, encoded as a SubjectPublicKeyInfo. The hash uses the log's hash function ({{log-parameters}}) and is computed over the SubjectPublicKeyInfo's DER {{X.690}} encoding. The `issuer` field MUST be the issuance log's log ID as a PKIX distinguished name, as described in {{log-ids}}.
966966

967-
Note the subject's public key algorithm is incorporated into both `subjectPublicKeyInfoAlgorithm` and `subjectPublicKeyInfoHash`.
967+
Note the subject's public key algorithm is incorporated into both `subjectPublicKeyAlgorithm` and `subjectPublicKeyInfoHash`.
968968

969969
MerkleTreeCertEntry is an extensible structure. Future documents may define new values for MerkleTreeCertEntryType, with corresponding semantics. See {{certification-authority-cosigners}} and {{new-log-entry-types}} for additional discussion.
970970

@@ -1302,7 +1302,7 @@ When verifying the signature on an X.509 certificate (Step (a)(1) of {{Section 6
13021302

13031303
1. Construct a TBSCertificateLogEntry as follows:
13041304
1. Copy the `version`, `issuer`, `validity`, `subject`, `issuerUniqueID`, `subjectUniqueID`, and `extensions` fields from the TBSCertificate.
1305-
1. Set `subjectPublicKeyInfoAlgorithm` to the `algorithm` field of the `subjectPublicKeyInfo`.
1305+
1. Set `subjectPublicKeyAlgorithm` to the `algorithm` field of the `subjectPublicKeyInfo`.
13061306
1. Set `subjectPublicKeyInfoHash` to the hash of the DER encoding of `subjectPublicKeyInfo`.
13071307

13081308
1. Construct a MerkleTreeCertEntry of type `tbs_cert_entry` with contents the TBSCertificateLogEntry. Let `entry_hash` be the hash of the entry, `MTH({entry}) = HASH(0x00 || entry)`, as defined in {{Section 2.1.1 of !RFC9162}}.
@@ -1711,19 +1711,18 @@ IMPORTS
17111711
id-mod-trustAnchorIDs-2025(TBD) } ;
17121712

17131713
TBSCertificateLogEntry ::= SEQUENCE {
1714-
version [0] EXPLICIT Version DEFAULT v1,
1715-
issuer Name,
1716-
validity Validity,
1717-
subject Name,
1718-
subjectPublicKeyInfoAlgorithm AlgorithmIdentifier{PUBLIC-KEY,
1719-
{PublicKeyAlgorithms}},
1720-
subjectPublicKeyInfoHash OCTET STRING,
1721-
issuerUniqueID [1] IMPLICIT UniqueIdentifier OPTIONAL,
1722-
subjectUniqueID [2] IMPLICIT UniqueIdentifier OPTIONAL,
1723-
extensions [3] EXPLICIT Extensions{{CertExtensions}}
1724-
OPTIONAL
1714+
version [0] EXPLICIT Version DEFAULT v1,
1715+
issuer Name,
1716+
validity Validity,
1717+
subject Name,
1718+
subjectPublicKeyAlgorithm AlgorithmIdentifier{PUBLIC-KEY,
1719+
{PublicKeyAlgorithms}},
1720+
subjectPublicKeyInfoHash OCTET STRING,
1721+
issuerUniqueID [1] IMPLICIT UniqueIdentifier OPTIONAL,
1722+
subjectUniqueID [2] IMPLICIT UniqueIdentifier OPTIONAL,
1723+
extensions [3] EXPLICIT Extensions{{CertExtensions}}
1724+
OPTIONAL
17251725
}
1726-
17271726
id-alg-mtcProof OBJECT IDENTIFIER ::= {
17281727
iso(1) identified-organization(3) dod(6) internet(1) security(5)
17291728
mechanisms(5) pkix(7) algorithms(6) TBD }

0 commit comments

Comments
 (0)