Timeline


and

16/03/17:

23:26 Ticket #187 (Use IANA-managed OIDs) created by rlb@…
I disagree with the conclusion reached in #81, and agree with Russ …

15/03/17:

22:08 Ticket #186 (Add a registry for error codes) created by rlb@…
Doesn't need to be fancy, but you're going to want new ones, and there …
22:08 Ticket #185 (Don't violate BCP 190) created by rlb@…
BCP 190 says basically that you shouldn't restrict the structure of …
22:04 Ticket #184 (Remove unnecessary restrictions on clients) created by rlb@…
It is always up to a relying party's local policy (1) which …
22:04 Ticket #183 (Don't violate the TLS Feature extension definition) created by rlb@…
Section 8.2.6 says that a requirement expressed in a TLS Feature …
22:03 Ticket #182 (Clarify notation in the Merkle tree section) created by rlb@…
There are a couple of confusing things in the description of Merkle …
22:03 Ticket #181 (Consolidate "Add Chain" and "Add PreCertChain" endpoints) created by rlb@…
There is no need for separate endpoints here. The server can tell …
22:03 Ticket #180 (Consolidate all Merkle tree data formats and computations) created by rlb@…
Right now, the rules for how you (1) represent aspects of a Merkle …
22:03 Ticket #179 (Indicate certificate / precertificate in Entry and SCT) created by rlb@…
Right now, a client in possession of a certificate and an SCT does not …
22:02 Ticket #178 (Add description of how to validate an SCT) created by rlb@…
The "Signed Certificate Timestamp (SCT)" section needs to explain how …
22:02 Ticket #177 (Instructions for constructing leaf hash from cert + SCT) created by rlb@…
In the current specification, the client requests inclusion proofs / …
22:02 Ticket #176 (Remove `X509ChainEntry` and `PrecertChainEntryV2`) created by rlb@…
Presenting these as types is confusing, since now you have multiple …
22:02 Ticket #175 (Clarify guarantees around MMD, STH age) created by rlb@…
The TreeHeadDataV2 struct includes a timestamp, which is the only …
22:01 Ticket #174 (Remove use of `digitally-signed`?) created by rlb@…
TLS 1.3 removes the digitally-signed construct in favor of just …
22:00 Ticket #173 (De-duplicate Extension types) created by rlb@…
There is no need for separate extension data types for SCTs and STHs. …
22:00 Ticket #172 (Pick one structure for multiple TransItems) created by rlb@…
The specification should define only one of TransItemList and …
22:00 Ticket #171 (Simplify Log IDs) created by rlb@…
It's unclear to me why the log IDs are OIDs, as opposed to say a …
21:59 Ticket #170 (Allow for separate SCT and STH keys?) created by rlb@…
Should there be a way for a log to have separate keys for signing SCTs …
21:59 Ticket #169 (Don't guess at STHs) created by rlb@…
A call to get-sth-consistency should either return a consistency …
21:59 Ticket #168 (Remove STH from `get-entries` response) created by rlb@…
An STH is only meaningful to a client if (a) its consistency with …
21:58 Ticket #167 (Define "incorporate") created by rlb@…
Section 4 says that "An SCT is the log's promise to incorporate the …
21:58 Ticket #166 (State the log parameters in the section that defines a log) created by rlb@…
The "Log Format and Operation" section makes reference to several …
21:58 Ticket #165 (Remove unnecessary operational restrictions on logs) created by rlb@…
The following restrictions are stated with RFC 2119 MUST language, but …
21:58 Ticket #164 (Incorporate new protocol mechanisms into TLS Client section) created by rlb@…
Section 8.2 "TLS Client" is currently written as if SCT validation …
21:57 Ticket #163 (The entire STH history of the log must be accessible) created by rlb@…
The public verifiability properties of this system rest on logs …
21:57 Ticket #162 (Bound the set of artifacts a log is expected to produce) created by rlb@…
This is far more work than is required for the protocol to function. …
Note: See TracTimeline for information about the timeline view.