Opened 7 years ago

Closed 7 years ago

#37 closed defect (fixed)

client gossping

Reported by: kent@… Owned by: draft-ietf-trans-rfc6962-bis@…
Priority: critical Milestone:
Component: rfc6962-bis Version:
Severity: - Keywords:
Cc:

Description

Section 5 calls for clients to gossip, to detect inconsistent responses from logs, but there is no defined protocol for this. At the meeting in Toronto there seemed to be consensus that gossiping is not sufficiently well understood to be part of this version of the CT standard. If so, then this text needs to be removed.

Change History (3)

comment:1 Changed 7 years ago by eranm@…

Linus has started working on a draft describing gossip, so this ticket could probably be assigned to him.
Also, a new component should be created for this.

Bottom line:
Suggest that clients should somehow 'gossip' (by detailing, in the security considerations, what would happen if clients don't do this).
Defer the definition of gossiping to the document produced by Linus.

comment:2 Changed 7 years ago by benl@…

Text updated to:

a) Be less prescriptive about how STHs are exchanged,

b) Point to the gossip I-D.

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.