Skip to content
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.

Mirja comments #324

Merged
merged 6 commits into from
Apr 14, 2021
Merged

Mirja comments #324

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a318681
Add pointers to Merkle docs
richsalz Mar 26, 2021
cda11f2
Explain lack of OID registry
richsalz Mar 26, 2021
210ae24
Clarify ignoring SCT extensions
richsalz Mar 26, 2021
dfc8196
Clarification on timeouts and limits
richsalz Mar 26, 2021
a95689b
fixup! Explain lack of OID registry
richsalz Mar 30, 2021
6beb8d7
Add clarifying notes to SignatureScheme registry
richsalz Mar 31, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion draft-ietf-trans-rfc6962-bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -868,7 +868,11 @@ chain that the log used to verify the submission.
Each log is identified by an OID, which is one of the log's parameters (see
{{log_parameters}}) and which MUST NOT be used to identify any other log. A
log's operator MUST either allocate the OID themselves or request an OID from
the Log ID Registry (see {{log_id_registry}}). Various data structures include
the Log ID Registry (see {{log_id_registry}}).
(Recall that OID's are do not require a central registration, although
richsalz marked this conversation as resolved.
Show resolved Hide resolved
logs will most likely want to make themselves known to potential clients
through out of band means.)
Various data structures include
the DER encoding of this OID, excluding the ASN.1 tag and length bytes, in an
opaque vector:

Expand Down