Opened 5 years ago

Closed 5 years ago

#172 closed defect (fixed)

Pick one structure for multiple TransItems

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

Description

The specification should define only one of TransItemList and
SCTWithProofDataV2. I can see the appeal of having a more structured format,
but TransItemList? seems more flexible, and thus a better option in the long run.

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

  • Component changed from to-be-decided to rfc6962-bis
  • Milestone set to review

I support removing the SCTWithProofDataV2 structure from 6962-bis.

This structure was used to hold a combination of SCT + STH + inclusion proof to that STH.
The same functionality can be achieved with a TransItemList? that contains each of those, so it makes sense to remove it (as it would simplify parsing of TransItems? without affecting functionality).

The change was reviewed and merged in https://github.com/google/certificate-transparency-rfcs/pull/225.

Leaving for the chairs to approve, if there's no objection on the list.

comment:3 Changed 5 years ago by rob.stradling@…

Further editorial changes were reviewed and merged in https://github.com/google/certificate-transparency-rfcs/pull/243

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

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