Opened 5 years ago
Closed 5 years ago
#167 closed defect (fixed)
Define "incorporate"
Reported by: | rlb@… | Owned by: | eranm@… |
---|---|---|---|
Priority: | major | Milestone: | review |
Component: | rfc6962-bis | Version: | |
Severity: | - | Keywords: | |
Cc: |
Description
Section 4 says that "An SCT is the log's promise to incorporate the submitted
entry in its Merkle Tree no later than a fixed amount of time". What does it
mean for a certificate to be incorporated? Does it mean that it is covered by
an STH? Does it mean that the certificate is available via the get-entries
endpoint? Being precise on this point is important, given that a lot of policy
ink is being spilled about enforcement of this requirement.
Change History (5)
comment:1 Changed 5 years ago by rob.stradling@…
- Component changed from client-behavior to to-be-decided
comment:2 Changed 5 years ago by eranm@…
- Component changed from to-be-decided to rfc6962-bis
- Owner changed from draft-ietf-trans-rfc6962-bis@… to eranm@…
- Status changed from new to assigned
comment:3 Changed 5 years ago by eranm@…
Out for review in https://github.com/google/certificate-transparency-rfcs/pull/254
Note I plan a bigger change that unifies the names of data structures with their semantic meaning.
comment:4 Changed 5 years ago by eranm@…
- Milestone set to review
Committed in https://github.com/google/certificate-transparency-rfcs/commit/1916b9a570a718588b80aaafc3168f4b9464172c, please review.
comment:5 Changed 5 years ago by melinda.shore@…
- Resolution set to fixed
- Status changed from assigned to closed
The different phases of a certificate being added to the tree:
Incorporation should be defined as the allocation of an sequence number to the entry and production of an STH that includes the hash of that sequenced entry.