change serialized 'TLS' structure to serialized 'SCT' structure

[GoogleCodeExporter]

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?]

Original issue reported on code.google.com by c...@cem.me on 19 May 2014 at 3:45

Attachments:

• rfc6962-bis.xml.patch

[GoogleCodeExporter]

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).

Original comment by c...@cem.me on 21 May 2014 at 1:10

[GoogleCodeExporter]

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.

Original comment by pphaneuf@google.com on 21 May 2014 at 2:47

[GoogleCodeExporter]

This has been pushed here:

https://github.com/google/certificate-transparency-rfcs/commit/bb088033239b74e21
05292d356c47305b5e08a3c

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/discussio
n

Thank you!

Original comment by pphaneuf@google.com on 23 May 2014 at 10:19

• Changed state: Fixed