Timeline


and

20/03/15:

18:00 Ticket #78 (algorithm agility discussion is inadequate) created by kent@…
Section 6 does not provide an adequate description of how algorithm …
17:59 Ticket #77 (normative client behavior specified in Section 5) created by kent@…
Section 5 says that it describes “some” clients and “how they could …
17:56 Ticket #76 (Normative client behavior specified in Section 3.4) created by kent@…
Section 3.4 does a much better job of explaining why there are 3 …
17:56 Ticket #75 (run on sentence in section 3) created by kent@…
Section 3 states: If a certificate is accepted and an SCT issued, the …
17:55 Ticket #74 (normative statement of TLS client behavior in Section 3) created by kent@…
Section 3 states: A certificate not accompanied by an SCT (either for …
17:54 Ticket #73 (Section 3 text re log cert validation is ambiguous) created by kent@…
Section 3 states “When a valid certificate is submitted to a log …” It …
17:53 Ticket #72 (Section 2.1.4 cites specific algorithms) created by kent@…
it would be preferable to cite a separate document that defines the …
17:52 Ticket #71 (Section 1 does not define mis-issuance) created by kent@…
Since mis-issuance is cited as the rationale for CT, it really must be …

13/03/15:

05:41 Ticket #24 (Add a section about log metadata) closed by melinda.shore@…
fixed

09/03/15:

21:06 Ticket #14 (Clarify ASN.1 encoding) closed by rob.stradling@…
needs-review: Whilst tackling this ticket, I took the opportunity to revamp the …
14:14 Ticket #62 (change title for section 1) closed by melinda.shore@…
fixed
14:14 Ticket #61 (Precertificates are not proper nouns) closed by melinda.shore@…
fixed

06/03/15:

17:45 Ticket #67 (no specification of how a log advertises the max cert chain length it ...) closed by melinda.shore@…
fixed
17:41 Ticket #60 (The number of redacted labels should be revealed in the Precertificate) closed by melinda.shore@…
fixed
16:09 Ticket #70 (SCT spec needs to define top-level extension syntax) created by kent@…
The description of the extensions field seems to be inspired by …
16:06 Ticket #69 (old data name (sha256_root_hash) in 3.6) created by kent@…
This section has been updated to support algorithm agility for STH, …
16:05 Ticket #68 (specification of sha-256 for the SCT) created by kent@…
Section 3.3 specifies use of SHA-256 for SCTs. This is not supportive …
16:02 Ticket #67 (no specification of how a log advertises the max cert chain length it ...) created by kent@…
Section 3.1 says that logs SHOULD impose a max cert chain length, but …
16:00 Ticket #66 (revise the description of what logs MAY do re cert syntax checking) created by kent@…
The current text does not specify log behavior wrt cert syntax …
15:57 Ticket #65 (remove section 5.4 and reference to "Auditor" in section 3) created by kent@…
The WG has been told that the editors no longer believe that the audit …
15:54 Ticket #64 (remove specification of signature and hash lags from section 2) created by kent@…
curent practice in the IETF, in support of alg agility, is to specify …
15:52 Ticket #63 (remove all normative references to client behavior) created by kent@…
the text contains several normative statement about client behavior, …
15:47 Ticket #62 (change title for section 1) created by kent@…
to remove the word "Informal" see https://www.rfc-editor.org/policy.html

05/03/15:

18:22 Ticket #9 (Security Considerations for number and variety of SCTs) closed by melinda.shore@…
fixed: New text: […]
18:15 Ticket #9 (Security Considerations for number and variety of SCTs) reopened by benl@…
15:25 Ticket #9 (Security Considerations for number and variety of SCTs) closed by benl@…
needs-review: Proposed resolution: …
12:45 Ticket #61 (Precertificates are not proper nouns) created by benl@…
We should spell it "precertificate" not "Precertificate".

02/03/15:

18:19 Ticket #48 (Enforce the rules for Name-constrained Intermediates) closed by benl@…
fixed: Closed with …
18:15 Ticket #47 (Clarify how to deal with (minor) DER violations when manipulating a ...) closed by benl@…
fixed: Closed at …
18:14 Ticket #59 (Clarify STH versioning) closed by benl@…
fixed: Closed with …

27/02/15:

15:34 Ticket #46 (Provide explicit instructions for how log servers should handle ...) closed by benl@…
fixed: Fixed by …
14:42 Ticket #49 (Explain why OCSP Stapling is acceptable but OCSP Fetching is not) closed by benl@…
invalid: We already explain why, closing.

25/02/15:

16:04 Ticket #36 (error indications for log/client exchanges) closed by benl@…
fixed: Closed by …

20/02/15:

15:39 Ticket #34 (use of RFC 5246 syntax to define the SCT) closed by benl@…
wontfix: TLS extensions are defined using RFC 5246 format, so clearly it is …
15:16 Ticket #39 (Monitor behavior) reopened by benl@…
Re-opened in case anyone wants to write a client behaviour doc.
12:33 Ticket #39 (Monitor behavior) closed by benl@…
wontfix: As agreed, we are not specifying client behaviour.
11:30 Ticket #17 (Add advice on CNs) closed by rob.stradling@…
fixed: Committed as... …
11:27 Ticket #56 ("*" domain labels MUST NOT be redacted) closed by rob.stradling@…
fixed: Committed as... …

19/02/15:

13:04 Ticket #33 (Cert chain length as log metadata) closed by benl@…
fixed: Fixed at …
Note: See TracTimeline for information about the timeline view.