![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Timeline
30/07/14:
- 22:34 WikiStart edited by
- Initial version, added implementation section (diff)
- 22:08 Ticket #43 (key rollover) created by
- Section 9 alludes to key rollover, but does not address how this …
- 22:07 Ticket #42 (redacted cert dangers) created by
- Section 7.3 alludes to the dangers of accepting an SCT for a redacted …
- 22:04 Ticket #41 (missing threat model and security analysis) created by
- There is no threat model for CT, and thus nor analysis of how the …
- 22:03 Ticket #40 (Auditor behavior) created by
- Section 5.4 purports to describe Auditor clients, but the text is very …
- 22:01 Ticket #39 (Monitor behavior) created by
- Sectio 5.3 says that a monitor “watches for certificates of interest” …
- 22:00 Ticket #38 (Client Behavior: A separate document for specifying client behavior) created by
- Section 5.2 contains some comments about TLS client behavior, but the …
- 21:57 Ticket #37 (client gossping) created by
- Section 5 calls for clients to gossip, to detect inconsistent …
- 21:55 Ticket #36 (error indications for log/client exchanges) created by
- Section 4 defines interfaces to logs for access by clients. it calls …
- 21:35 Ticket #35 (server SCT transmission restriction is misstated) created by
- Section 3.4.1 explains how a client notifies a server that the client …
- 21:25 Ticket #34 (use of RFC 5246 syntax to define the SCT) created by
- Section 3.3 defines the syntax of the SCT using the syntax developed …
- 21:17 Ticket #33 (Cert chain length as log metadata) created by
- Section 3.1 notes that a log operator may limit the length of chains …
- 21:16 Ticket #32 (algorithm needed for client checks of SCT) created by
- Section 3 does not detail the checks that a client is expected to …
- 21:16 Ticket #31 (incremental deployment and client behavior) created by
- Section 3 states that a client MUST rejects that are not accompanied …
- 21:15 Ticket #30 (Publish MMD as log metadata) created by
- Section 3 introduces the term “Maximum Merge Delay (MMD)” but no means …
- 21:15 Ticket #29 (what does "immediately" mean?) created by
- Section 3 of 6962-bis says that a log operator MUST return an SCT …
- 21:14 Ticket #28 (Algorithm agility) created by
- 6962-bis does not address algorithm agility. Revise the document to …
- 21:11 Ticket #27 (Signature & hash alg specification) created by
- Section 2.1.4 says that a log operator MUST use one of two specified …
29/07/14:
- 13:52 Ticket #20 (Do we want to be tied to TLS signing algorithms?) closed by
- fixed: If a hash/signature algorithm is not good enough to be used in TLS …
22/07/14:
- 10:29 Ticket #26 (Precertificates: Find alternative format to X.509) created by
- A fundamental problem with the existing Precertificates mechanism …
21/07/14:
- 15:25 Ticket #25 (Freezing a log's state) created by
- Describe a way to make a log read only. This is useful for: * A …
10/07/14:
- 16:53 Ticket #24 (Add a section about log metadata) created by
- Such a section should describe what is considered a log's metadata, …
- 15:45 Ticket #23 (How can TLS clients match an SCT to a certificate?) created by
- (Relevant to SCTs from stapled OCSP response and TLS handshake) …
07/07/14:
- 14:09 Ticket #22 (Explain why there are three delivery mechanisms for SCTs) created by
- [EOM]
- 13:57 Ticket #21 (Clarify signature checking purpose and mechanism) created by
- Signatures on submissions are checked to mitigate spam. Make this …
04/07/14:
- 15:57 Ticket #20 (Do we want to be tied to TLS signing algorithms?) created by
- Russ Housley observes: In Section 2.1.4, this protocol supports two …
Note: See TracTimeline
for information about the timeline view.
