trans issue tracker | 10 Feb 19:46 2016
Picon

Re: [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension

#113: Add advice about the tls-feature TLS extension

Changes (by melinda.shore <at> gmail.com):

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

--

-- 
--------------------------------------+------------------------------
 Reporter:  rob.stradling <at> comodo.com  |       Owner:  benl <at> google.com
     Type:  enhancement               |      Status:  closed
 Priority:  minor                     |   Milestone:  review
Component:  rfc6962-bis               |     Version:
 Severity:  -                         |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/113#comment:5>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 10 Feb 14:54 2016
Picon

Re: [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension

#113: Add advice about the tls-feature TLS extension

Changes (by rob.stradling <at> comodo.com):

 * milestone:   => review

Comment:

 Fully fixed at https://github.com/google/certificate-transparency-
 rfcs/commit/a24fca772c3b95198cc909fd5aceb04003063ae4

--

-- 
--------------------------------------+------------------------------
 Reporter:  rob.stradling <at> comodo.com  |       Owner:  benl <at> google.com
     Type:  enhancement               |      Status:  new
 Priority:  minor                     |   Milestone:  review
Component:  rfc6962-bis               |     Version:
 Severity:  -                         |  Resolution:
 Keywords:                            |
--------------------------------------+------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/113#comment:4>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 4 Feb 23:55 2016
Picon

Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct

#115: Verify that recommended consistency checking algorithm is correct

Changes (by melinda.shore <at> gmail.com):

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

--

-- 
------------------------------+----------------------------------
 Reporter:  eranm <at> google.com  |       Owner:  katjoyce <at> google.com
     Type:  defect            |      Status:  closed
 Priority:  major             |   Milestone:  review
Component:  rfc6962-bis       |     Version:
 Severity:  -                 |  Resolution:  fixed
 Keywords:                    |
------------------------------+----------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/115#comment:11>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 4 Feb 15:02 2016
Picon

Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct

#115: Verify that recommended consistency checking algorithm is correct

Changes (by katjoyce <at> google.com):

 * milestone:   => review

--

-- 
------------------------------+----------------------------------
 Reporter:  eranm <at> google.com  |       Owner:  katjoyce <at> google.com
     Type:  defect            |      Status:  reopened
 Priority:  major             |   Milestone:  review
Component:  rfc6962-bis       |     Version:
 Severity:  -                 |  Resolution:
 Keywords:                    |
------------------------------+----------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/115#comment:10>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 3 Feb 17:14 2016
Picon

Re: [Trans] [trans] #23 (rfc6962-bis): How can TLS clients match an SCT to a certificate?

#23: How can TLS clients match an SCT to a certificate?

Comment (by eranm <at> google.com):

 Strongly support removing the ItemExtension field.

--

-- 
------------------------------+---------------------------------------
 Reporter:  eranm <at> google.com  |       Owner:  rob.stradling <at> comodo.com
     Type:  defect            |      Status:  new
 Priority:  major             |   Milestone:
Component:  rfc6962-bis       |     Version:
 Severity:  -                 |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/23#comment:10>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 3 Feb 17:14 2016
Picon

Re: [Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension

#112: Consider permitting the status_request_v2 TLS extension

Changes (by melinda.shore <at> gmail.com):

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

--

-- 
--------------------------------------+---------------------------------
 Reporter:  rob.stradling <at> comodo.com  |       Owner:  pphaneuf <at> gmail.com
     Type:  enhancement               |      Status:  closed
 Priority:  minor                     |   Milestone:  review
Component:  rfc6962-bis               |     Version:
 Severity:  -                         |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/112#comment:4>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 3 Feb 17:13 2016
Picon

Re: [Trans] [trans] #121 (rfc6962-bis): log metadata dissemination

#121: log metadata dissemination

Changes (by melinda.shore <at> gmail.com):

 * status:  new => closed
 * resolution:   => wontfix

Comment:

 This will need to be revisited in a different document.

--

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-trans-
  kent <at> bbn.com           |  rfc6962-bis <at> tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:  review
Component:  rfc6962-bis  |     Version:
 Severity:  -            |  Resolution:  wontfix
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/121#comment:4>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 3 Feb 17:12 2016
Picon

Re: [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior

#109: log shutdown timeline and behavior

Changes (by melinda.shore <at> gmail.com):

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

--

-- 
-----------------------------------+-------------------------------
 Reporter:  dkg <at> fifthhorseman.net  |       Owner:  eranm <at> google.com
     Type:  defect                 |      Status:  closed
 Priority:  major                  |   Milestone:  review
Component:  rfc6962-bis            |     Version:
 Severity:  -                      |  Resolution:  fixed
 Keywords:                         |
-----------------------------------+-------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/109#comment:5>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 3 Feb 17:11 2016
Picon

Re: [Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension

#112: Consider permitting the status_request_v2 TLS extension

Changes (by pphaneuf <at> gmail.com):

 * milestone:   => review

Comment:

 Fixed at https://github.com/google/certificate-transparency-
 rfcs/commit/9c921489a544a9538da05328f5f51fc772774fb9

--

-- 
--------------------------------------+---------------------------------
 Reporter:  rob.stradling <at> comodo.com  |       Owner:  pphaneuf <at> gmail.com
     Type:  enhancement               |      Status:  assigned
 Priority:  minor                     |   Milestone:  review
Component:  rfc6962-bis               |     Version:
 Severity:  -                         |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/112#comment:3>
trans <https://tools.ietf.org/trans/>
trans issue tracker | 3 Feb 17:11 2016
Picon

Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct

#115: Verify that recommended consistency checking algorithm is correct

Comment (by katjoyce <at> google.com):

 Changes being reviewed in https://github.com/google/certificate-
 transparency-rfcs/pull/125

--

-- 
------------------------------+----------------------------------
 Reporter:  eranm <at> google.com  |       Owner:  katjoyce <at> google.com
     Type:  defect            |      Status:  reopened
 Priority:  major             |   Milestone:
Component:  rfc6962-bis       |     Version:
 Severity:  -                 |  Resolution:
 Keywords:                    |
------------------------------+----------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/115#comment:9>
trans <https://tools.ietf.org/trans/>
Rob Stradling | 3 Feb 14:43 2016

[Trans] Oh...

http://trac.tools.ietf.org/wg/trans/trac/report/1 currently returns...

"Oops…

Trac detected an internal error:
OperationalError: database or disk is full"

Who can fix this?

--

-- 
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online

_______________________________________________
Trans mailing list
Trans <at> ietf.org
https://www.ietf.org/mailman/listinfo/trans

Gmane