Opened 7 years ago

Closed 4 years ago

#103 closed defect (fixed)

Evaluate if we need tighter requirements around STHs when we take into account multiple logs.

Reported by: tom@… Owned by: linus@…
Priority: major Milestone:
Component: gossip Version:
Severity: - Keywords:
Cc:

Description

We've been kicking this around a bit, but wanted to make sure we captured it concretely.

Bryan mentioned this in his emails also, see https://mailarchive.ietf.org/arch/msg/trans/7FR3aRVwi4FZLhmJfy9UnAxQNuU

Change History (3)

comment:1 Changed 6 years ago by linus@…

Upcoming -02 has

  • text limiting STH pollination using the logs STH issuance rate and STH freshness
  • section "Privacy in STH Interaction" describing some of the privacy issues
  • section "Record Distribution Recommendations" suggesting ways of how servers can mix STHs (and SCTs) in order to be performant while preserving user privacy

Are we satisfied with this or should we limit STH handling further?

comment:2 Changed 6 years ago by linus@…

  • Owner changed from draft-ietf-trans-threat-analysis@… to linus@…
  • Status changed from new to assigned

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

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