You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/12/16 18:55:46 UTC

[jira] [Updated] (TS-3138) Implement/Verify Downstream (origin) TLS False Start

     [ https://issues.apache.org/jira/browse/TS-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-3138:
------------------------------
    Fix Version/s:     (was: 6.1.0)
                   sometime

> Implement/Verify Downstream (origin) TLS False Start
> ----------------------------------------------------
>
>                 Key: TS-3138
>                 URL: https://issues.apache.org/jira/browse/TS-3138
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Core, SSL
>            Reporter: Brian Geffon
>             Fix For: sometime
>
>         Attachments: disabled_tls_falsestart_ats.png, enabled_tls_falsestart_ats.png
>
>
> TLS false start can really reduce latency by allowing data to be transmitted before the CipherChange has been completed. For more information see: 
> http://chimera.labs.oreilly.com/books/1230000000545/ch04.html#TLS_FALSE_START and http://tools.ietf.org/html/draft-bmoeller-tls-falsestart-00
> We need to 1) verify that Traffic Server correctly reads data that was transmitted as false start before the hand shake is "officially complete." and 2) if it's not then determine why the read is not happening earlier.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)