Opened 6 years ago

Closed 5 years ago

#182 closed defect (fixed)

Clarify notation in the Merkle tree section

Reported by: rlb@… Owned by: eranm@…
Priority: major Milestone: review
Component: rfc6962-bis Version:
Severity: - Keywords:
Cc:

Description

There are a couple of confusing things in the description of Merkle tree
operations:

  • The document uses parens to indicate indexing (e.g., d(0)) and square brackets to indicate the length of a list (e.g., D[n]). Developers reading this specification are pretty universally going to be using languages that use square brackets for indexing, so this notation ends up being really confusing.
  • "... the length $LENGTH list $ELEMENTS" -> "... the list $ELEMENTS of length $LENGTH" in a few spots

Change History (7)

comment:1 Changed 6 years ago by eranm@…

Suggested text would be welcome. Rob and I researched syntax for a few things, couldn't find a consistent syntax for this.

We could have a go at making sure lengths are clarified in the text.

comment:2 Changed 6 years ago by rob.stradling@…

  • Component changed from client-behavior to to-be-decided

comment:4 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:5 Changed 5 years ago by eranm@…

A follow-up PR is out:
https://github.com/google/certificate-transparency-rfcs/pull/251

It'd get too messy to merge Richard's original PR and incorporate Ben's comments in a follow-up commit, so I've merged it all to a new PR.

comment:6 Changed 5 years ago by eranm@…

  • Milestone set to review

Merged - please review.

comment:7 Changed 5 years ago by melinda.shore@…

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.