Subject: Re: [Trans] [trans] #143 (rfc6962-bis): Putting TLS server guidance in one place

From: "trans issue tracker" <[email-masked]>
Date: Mon, 01 Feb 2016 17:26:53 -0000

#143: Putting TLS server guidance in one place

Changes (by [email-masked]):

 * owner:  [email-masked] =>
            [email-masked]
 * status:  new => assigned

-- 
--------------------------+-----------------------------------
 Reporter:  [email-masked]  |       Owner:  [email-masked]
     Type:  defect        |      Status:  assigned
 Priority:  minor         |   Milestone:
Component:  rfc6962-bis   |     Version:
 Severity:  -             |  Resolution:
 Keywords:                |
--------------------------+-----------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/143#comment:1>
trans <https://tools.ietf.org/trans/>

---

From: "trans issue tracker" <[email-masked]>
Date: Wed, 17 Feb 2016 12:50:27 -0000

* status:  assigned => closed
 * resolution:   => fixed

Comment:

 This was fixed a while ago in https://github.com/google/certificate-
 transparency-rfcs/commit/e3d53bbd748878f4a641e572c5a42b1c3e3e5383
 but wan't marked as fixed here -- doing so now.

-- 
--------------------------+-----------------------------------
 Reporter:  [email-masked]  |       Owner:  [email-masked]
     Type:  defect        |      Status:  closed
 Priority:  minor         |   Milestone:
Component:  rfc6962-bis   |     Version:
 Severity:  -             |  Resolution:  fixed
 Keywords:                |
--------------------------+-----------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/143#comment:2>
trans <https://tools.ietf.org/trans/>