Opened 5 years ago

Closed 5 years ago

#169 closed defect (wontfix)

Don't guess at STHs

Reported by: rlb@… Owned by: draft-ietf-trans-rfc6962-bis@…
Priority: major Milestone: review
Component: to-be-decided Version:
Severity: - Keywords:


A call to get-sth-consistency should either return a consistency proof between
the two indicated tree heads or it should fail. The server should not change
the request to something it like better. If the front-end the client is talking
to is behind, then the client needs to wait until it catches up; an intermediate
STH is not useful.

Likewise, if a get-all-by-hash query can't provide the requested proof, it
should fail.

Change History (4)

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@…

  • Milestone set to review

See discussion on issue 168 and Andrew Ayer's objection on the list:

Given the justification for keeping it, suggest closing as wontfix.

comment:3 Changed 5 years ago by eranm@…

I'll note this came up today again in an out-of-band discussion with colleagues: Having the option of getting the new STH by not specifying the 2nd tree size is an efficient way to catch up with the log without calling get-sth first - a single call is enough to get a new STH and a consistency proof to it from the STH the client currently knows about.

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

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