On 18/07/15 00:40, Rob Stradling wrote:
On 17/07/15 14:35, Stephen Kent wrote:
<snip>
If you believe that there are folks who don't track this list and who
rely on GitHub to track CT stuff, then feel free to post there.
GitHub is what the 6962-bis authors are using to collaboratively edit
the document. A GitHub pull request must be created for any proposed
text before that proposed text is reviewed and incorporated into the
document. We welcome pull requests from anyone (it's the most
convenient way for us to accept proposed text), but posting proposed
text to this WG mailing list is also fine.
I've created a pull request and kicked off the review here:
https://github.com/google/certificate-transparency-rfcs/pull/70
Steve, I made some changes to your proposed text to align the syntax
with the TLS Hello Extensions syntax from RFC5246, and I've merged the
text into rfc6962-bis.xml in the GitHub repo.
If you want to review the changes, please browse to the GitHub URLs
quoted in the TRAC ticket.
(BTW, the fact that the TRAC ticket and the pull request are both
numbered 70 is purely coincidental).
--
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
