Subject: Re: [Trans] [Public Notary Transparency Wiki] #164: Incorporate new protocol mechanisms into TLS Client section

From: "trans issue tracker" <[email-masked]>
Date: Fri, 12 May 2017 10:32:09 -0000

#164: Incorporate new protocol mechanisms into TLS Client section
-------------------------+-----------------------
 Reporter:  rlb@…        |       Owner:  eranm@…
     Type:  defect       |      Status:  assigned
 Priority:  major        |   Milestone:
Component:  rfc6962-bis  |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-----------------------
Changes (by eranm@…):

 * owner:  draft-ietf-trans-rfc6962-bis@… => eranm@…
 * status:  new => assigned
 * component:  to-be-decided => rfc6962-bis

Comment:

 Re-reading the "TLS Clients" section (now 8.1) It seems to me this is
 covered pretty well.
 There's some repetition there, which I've fixed in this PR:

 https://github.com/google/certificate-transparency-rfcs/pull/258

--
Ticket URL: <https://trac.ietf.org/trac/trans/ticket/164#comment:2>
Public Notary Transparency  Wiki <https://trac.ietf.org/trac/trans>
My example project