change serialized 'TLS' structure to serialized 'SCT' structure about certificate-transparency HOT 4 CLOSED

In the Section 'Including the Signed Certificate Timestamp in the TLS Handshake':
The 'SerializedSCT sct_list' is defined as "an opaque byte string that contains the serialized TLS structure." I believe this should read "the serialized SCT structure"
[This wording is also in the RFC, would that warrant an errata report?]

from certificate-transparency.

After benl@google referenced the github repo on the trans list this morning, I proposed this same change there.. not sure where the source of record is. (I'm now assuming it to be github, if it is, this change can be ignored/closed/etc).

from certificate-transparency.

FYI, about the source of record, we're still in the progress of migrating to GitHub (and I've personally been a little bit surprised at how quickly people jumped on it!), so technically Google Code is still the source of record, but this should change quickly (today).

I have been keeping the two in sync, to be on the safe side.

from certificate-transparency.

This has been pushed here:

google/certificate-transparency-rfcs@bb08803

And also, the source of record are now the GitHub repositories, as announced on the mailing list:

https://groups.google.com/d/topic/certificate-transparency/ImPSD07ezFc/discussion

Thank you!

from certificate-transparency.