Timeline


and

27/11/15:

19:20 Ticket #83 (CT should mandate the use of deterministic ECDSA) closed by melinda.shore@…
fixed
18:34 Ticket #125 (change "will return" to "MUST return") closed by melinda.shore@…
fixed
18:34 Ticket #136 (inconsistent discussion of mis-issued certs and compliance) closed by melinda.shore@…
invalid
18:33 Ticket #93 (Monitor description: Inconsistency between intro and section 5.4) closed by melinda.shore@…
fixed
18:33 Ticket #64 (remove specification of signature and hash lags from section 2) closed by melinda.shore@…
fixed

26/11/15:

19:45 Ticket #116 (ned definition for mis-issuance) closed by melinda.shore@…
duplicate

20/11/15:

16:28 Ticket #137 (Section 13, an unlucky number?) created by kent@…
The text in section 13 seems like an afterthought; it might better be …
16:27 Ticket #136 (inconsistent discussion of mis-issued certs and compliance) created by kent@…
Section 12.1 contradicts text in Section 9.2. 12.1 says that a …
16:25 Ticket #135 (Subjects (vs. Monitors) observing logs?) created by kent@…
Section 12 says “ … the client knows that the subject of the …
16:22 Ticket #134 (client use of logs to detect mis-issued certs) created by kent@…
Section 12 says that TLS clients can use logs and SCTs to reduce the …

19/11/15:

22:40 Ticket #133 (incomplete Misbehaving Logs section) created by david@…
[https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-10#section-12
22:26 Ticket #132 (unclear motivation for and handling of re-logging entries from a frozen log) created by david@…
From …
22:11 Ticket #131 (missing guidance for TLS servers to select logs) created by david@…
[https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-10#section-7
16:24 Ticket #130 (Support Delegation of SCT Feedback/STH Pollination) created by tom@…
Delegation is always possible, it's just currently difficult. Maybe …
02:25 Ticket #129 (how do submitters determine what a log will accept?) created by david@…
[https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-10#section-5. …
02:19 Ticket #128 (section 5 over-claims the properties of an STH) created by david@…
From …

17/11/15:

21:50 Ticket #127 (confusing case is allowed: submission of pre-cert without embedding ...) created by david@…
[https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-10#section-3. …
21:42 Ticket #126 (text leaves open the possibility that a submitter might not verify the ...) created by david@…
From …
21:35 Ticket #125 (change "will return" to "MUST return") created by david@…
In …
21:16 Ticket #124 (introduction needs work) created by kent@…
The architecture document presents a much clearer characterization of …
20:46 Ticket #123 (log clients description too informal, incomplete) created by kent@…
Section 9 discusses log clients, but uses a lot of language that is …
20:42 Ticket #122 (TLS server requirements) created by kent@…
Section 7 describes some (but probably not all) requirements for TLS …
20:40 Ticket #121 (log metadata dissemination) created by kent@…
After Prague I agreed that log metadata can be supplied by browser …

16/11/15:

04:49 Ticket #76 (Normative client behavior specified in Section 3.4) closed by melinda.shore@…
fixed: This seems quite clear - I'm closing it as fixed.

13/11/15:

18:47 Ticket #120 (public vs. private logs?) created by kent@…
Section 3.1 says “Anyone can submit a certificate (Section 6.1) to a …
18:45 Ticket #119 (confusing wording about log checking in Introduction) created by kent@…
The introduction says “The checking operation is asynchronous to allow …
18:44 Ticket #118 (Monitor function description problem) created by kent@…
The introduction states “Those who are concerned about misissue [sic] …
18:42 Ticket #117 (log description as "untrusted") created by kent@…
The introduction stills refers to logs as “untrusted” yet this is a …
18:40 Ticket #116 (ned definition for mis-issuance) created by kent@…
the document does not include a definition for misissuance [sic], even …
11:06 Ticket #115 (Verify that recommended consistency checking algorithm is correct) created by eranm@…
The algorithm in …

04/11/15:

12:41 Ticket #114 (Name the OCSP Stapling TLS extension correctly) created by rob.stradling@…
Currently we say "where the OCSP response is provided in the …
12:20 Ticket #113 (Add advice about the tls-feature TLS extension) created by rob.stradling@…
RFC7633 standardizes the TLS Feature certificate extension. This …

03/11/15:

15:22 Ticket #112 (Consider permitting the status_request_v2 TLS extension) created by rob.stradling@…
Currently we require TLS clients to implement the original …
14:46 Ticket #111 (Consider using the cached-info TLS extension) created by rob.stradling@…
It looks like the cached-info RFC will be published very soon: …
01:13 Ticket #99 (Clearer definition of when a certificate is CT-compliant needed) closed by melinda.shore@…
fixed
01:11 Ticket #99 (Clearer definition of when a certificate is CT-compliant needed) reopened by eranm@…
01:05 Ticket #99 (Clearer definition of when a certificate is CT-compliant needed) closed by eranm@…
needs-review: Propose this ticket be closed (Fixed) as the term 'compliant' is now …

28/10/15:

21:05 Ticket #105 (Shrink LogID) closed by melinda.shore@…
fixed
21:05 Ticket #110 (Reorganize requirements into appropriate sections) closed by melinda.shore@…
fixed
Note: See TracTimeline for information about the timeline view.