Timeline
05/12/15:
- 07:40 Ticket #145 (Section 9.2 (TLS clients) needs more guidance for browsers) created by
- The WG discussions have focussed on browsers as the key TLS client and …
03/12/15:
- 06:32 Ticket #144 (Need to specify how the CA requirements in 12.3 are to be met) created by
- Section 12.3 specifies behaviors of the CA and browsers. I think that …
- 06:11 Ticket #143 (Putting TLS server guidance in one place) created by
- Section 7 recommends that a TLS server provide SCTs from multiple …
02/12/15:
- 16:11 Ticket #142 (Specify what TLS clients should send in the extension_data of the ...) created by
- RFC6962 requires TLS clients to send 'empty "extension_data"' for the …
- 15:52 Ticket #23 (How can TLS clients match an SCT to a certificate?) reopened by
- Ticket #10 laid the groundwork for this ticket, but it left the …
- 15:46 Ticket #104 (Add SCT Inclusion Proof extension) closed by
- duplicate
- 15:45 Ticket #10 (Permit Precertificate SCTs to be delivered via OCSP Stapling and the ...) closed by
- fixed
- 06:13 Ticket #141 (expanding audit description) created by
- The description of Auditing in Section 9.4 is vague and difficult to …
- 05:06 Ticket #140 (move section 8 to CA specification) created by
- Section 8 is devoted to CA's but doesn't specify the requirements …
01/12/15:
- 08:00 Ticket #139 (move text re: domain labels to CA specification) created by
- Section 4 describes the problems posed by private domain labels and …
- 06:28 Ticket #138 (use of term before defining it) created by
- In section 3, “precertificate” is used before being defined. Also, …
30/11/15:
- 21:14 Ticket #125 (change "will return" to "MUST return") closed by
- wontfix
- 16:17 Ticket #137 (Section 13, an unlucky number?) closed by
- fixed
- 16:17 Ticket #117 (log description as "untrusted") closed by
- fixed
- 16:16 Ticket #128 (section 5 over-claims the properties of an STH) closed by
- fixed
- 16:16 Ticket #135 (Subjects (vs. Monitors) observing logs?) closed by
- fixed
- 12:39 Ticket #125 (change "will return" to "MUST return") reopened by
- Reopening, because comment:1 is wrong. The "will return" text is …
27/11/15:
- 19:20 Ticket #83 (CT should mandate the use of deterministic ECDSA) closed by
- fixed
- 18:34 Ticket #125 (change "will return" to "MUST return") closed by
- fixed
- 18:34 Ticket #136 (inconsistent discussion of mis-issued certs and compliance) closed by
- invalid
- 18:33 Ticket #93 (Monitor description: Inconsistency between intro and section 5.4) closed by
- fixed
- 18:33 Ticket #64 (remove specification of signature and hash lags from section 2) closed by
- fixed
26/11/15:
20/11/15:
- 16:28 Ticket #137 (Section 13, an unlucky number?) created by
- 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
- 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
- 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
- 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
- [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
- From …
- 22:11 Ticket #131 (missing guidance for TLS servers to select logs) created by
- [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
- 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
- [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
- From …
17/11/15:
- 21:50 Ticket #127 (confusing case is allowed: submission of pre-cert without embedding ...) created by
- [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
- From …
- 21:35 Ticket #125 (change "will return" to "MUST return") created by
- In …
- 21:16 Ticket #124 (introduction needs work) created by
- The architecture document presents a much clearer characterization of …
- 20:46 Ticket #123 (log clients description too informal, incomplete) created by
- Section 9 discusses log clients, but uses a lot of language that is …
- 20:42 Ticket #122 (TLS server requirements) created by
- Section 7 describes some (but probably not all) requirements for TLS …
- 20:40 Ticket #121 (log metadata dissemination) created by
- 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
- fixed: This seems quite clear - I'm closing it as fixed.
13/11/15:
- 18:47 Ticket #120 (public vs. private logs?) created by
- 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
- The introduction says “The checking operation is asynchronous to allow …
- 18:44 Ticket #118 (Monitor function description problem) created by
- The introduction states “Those who are concerned about misissue [sic] …
- 18:42 Ticket #117 (log description as "untrusted") created by
- The introduction stills refers to logs as “untrusted” yet this is a …
- 18:40 Ticket #116 (ned definition for mis-issuance) created by
- 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
- The algorithm in …
Note: See TracTimeline
for information about the timeline view.