Opened 7 years ago

Closed 7 years ago

#59 closed defect (fixed)

Clarify STH versioning

Reported by: rob.stradling@… Owned by: draft-ietf-trans-rfc6962-bis@…
Priority: major Milestone:
Component: rfc6962-bis Version:
Severity: - Keywords:
Cc:

Description

The current draft defines TreeHeadVersion? v2, denoting a v2 STH. However, in a couple of places the current draft still requires the STH version to be v1.

The only reason for TreeHeadVersion? v2 was to add the CtSthExtensions? field, which we perhaps don't need.

We should either:

  1. Revert the changes that introduced TreeHeadVersion? v2.

or

  1. Change the text that currently requires STH v1 to require STH v2 instead.

Change History (3)

comment:1 Changed 7 years ago by benl@…

I can't find anywhere that requires a v2 STH.

However, I agree that we do not need to make this change yet: if we discover a need for extensions in an STH, then we can introduce a v2 STH and new APIs that deal with v2 STHs. Existing code can continue to use v1 STHs and the corresponding APIs.

comment:3 Changed 7 years ago by benl@…

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