Skip to content

Commit dc632c8

Browse files
committed
Detail landmark-relative certificate construction
Give an exact procedure for selecting the landmark and covering subtree when constructing a landmark-relative certificate.
1 parent 36cb851 commit dc632c8

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1428,8 +1428,8 @@ It is RECOMMENDED that this format be published as an HTTP resource {{!RFC9110}}
14281428

14291429
Given the inputs in {{certificate-inputs}} and a landmark sequence, a landmark-relative certificate is constructed as follows:
14301430

1431-
1. Wait for the first landmark to be allocated that contains the entry.
1432-
2. Determine the landmark's subtrees and select the one that contains the entry.
1431+
1. Let `L` be the smallest landmark number in the active window whose tree size is strictly greater than the entry index `i`. Because the landmark sequence is strictly monotonically increasing, `L - 1`'s tree size is less than or equal to `i`. If no such `L` has been allocated yet (`i` is greater than or equal to `last_landmark`'s tree size), wait for one to be allocated. If every landmark that once covered the entry is no longer in the active window (`last_landmark - num_active_landmarks`'s tree size is greater than `i`), abort this process.
1432+
2. Determine landmark `L`'s subtrees ({{landmark-tree-sizes}}) and select the unique one whose `[start, end)` interval contains `i`.
14331433
3. Construct a certificate ({{certificate-format}}) using the selected subtree and no signatures.
14341434

14351435
Before sending this certificate, the authenticating party SHOULD obtain an application-protocol-specific signal that implies the relying party has been configured with the corresponding landmark. ({{trusted-subtrees}} defines how relying parties are configured.) The trust anchor ID of the landmark may be used as an efficient identifier in the application protocol. {{use-in-tls}} discusses how to do this in TLS {{!RFC9846}}.
@@ -2670,3 +2670,5 @@ In draft-04, there is no fast issuance mode. In draft-05, frequent, non-landmark
26702670
- Add an informative reference to the MTC-TLOG profile (c2sp.org/mtc-tlog) and mention it where tile-based logs are discussed.
26712671

26722672
- Clarify that a landmark consists of both a number and a tree size, and that a landmark's subtrees share its landmark number.
2673+
2674+
- Give an exact procedure for selecting the landmark and covering subtree when constructing a landmark-relative certificate.

0 commit comments

Comments
 (0)