[jira] [Closed] (PROTON-136) Add support for SSL session resumption

["Ken Giusti (JIRA)" <ji...@apache.org>]

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

Ken Giusti closed PROTON-136.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 0.3

Feature merged in from task branch kgiusti-proton-136:

http://svn.apache.org/viewvc?view=revision&revision=1423617
                
> Add support for SSL session resumption
> --------------------------------------
>
>                 Key: PROTON-136
>                 URL: https://issues.apache.org/jira/browse/PROTON-136
>             Project: Qpid Proton
>          Issue Type: New Feature
>          Components: proton-c
>    Affects Versions: 0.3
>            Reporter: Affan Dar
>            Assignee: Philip Harvey
>              Labels: ssl, sslContext, sslresume
>             Fix For: 0.3
>
>         Attachments: PROTON-136-initial-Java-and-Python.tgz, ssl-patches-20121212.tar.gz
>
>
> Open SSL supports resumption of SSL sessions which by-pass the heavy SSL handshake process. This is critical for scenarios involving low powered devices especially on cellular data networks where bandwidth is precious.
> It would be great if Proton exposes this ssl resume feature to users. .
> From: rhs [mailto:rschloming@gmail.com] 
> Sent: Tuesday, November 13, 2012 11:34 AM
> To: Affan Dar
> Cc: David Ingham
> Subject: Re: SSL session resumption
> On Tue, Nov 13, 2012 at 8:05 PM, Affan Dar <af...@microsoft.com> wrote:
> >>Serializing/restoring the whole session state for the messenger will work for the scenario I think.
> Ok, let's start with this step then. I'm open to providing something finer grained if there is a need, but my preference is to keep it simple for the moment.
>    
> >>One more thing, RFC 5077 has another flavor of session resumption which openssl supports (original >>implemented as RFC 4057 back in 2007 I think). This allows us to resume sessions without carrying state >>on the server side which as you can imagine is a big deal for service vendors. Probably there is no API >>level impact if messenger handles the session state itself but just wanted to put this on your radar.
> Ok, good to know.
> Could one of you file a JIRA for this upstream? I'm trying to get things a little more organized on the process front and keep everything centralized in JIRA. ;-)
> --Rafael

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira