Hi,
On Fri, Jul 24, 2015 at 9:38 PM, Jason Greene wrote:
> The truth is that there is a gap between the current capabilities of TLS
> stacks and what the specs are trying to achieve. Ultimately the desired
> semantic the specs are trying to achieve is that every ALPN protocol can have
> its ow
Am Fri, 24 Jul 2015 14:38:36 -0500
schrieb Jason Greene :
> The truth is that there is a gap between the current capabilities of
> TLS stacks and what the specs are trying to achieve. Ultimately the
> desired semantic the specs are trying to achieve is that every ALPN
> protocol can have its own TL
> On Jul 9, 2015, at 12:02 PM, Bradford Wetmore oracle.com> wrote:
>
> Ok, I'll check with the HTTP/2 group tomorrow. It appears the proper
> list is:
Hi Brad,
Your post to the H2 group got my attention, so I thought as a user of JSSE for
an H2 implementation I should reply additionally he
Ok, I'll check with the HTTP/2 group tomorrow. It appears the proper
list is:
ietf-http...@w3.org
Is that correct?
Brad
On 7/9/2015 8:29 AM, Simone Bordet wrote:
Hi,
On Thu, Jul 9, 2015 at 1:42 AM, Bradford Wetmore
wrote:
SSLParameters is a configuration class which is used to conf
Hi,
On Thu, Jul 9, 2015 at 1:42 AM, Bradford Wetmore
wrote:
> SSLParameters is a configuration class which is used to configure
> SSLSockets/SSLEngines. SSLSession/ExtendedSSLSession is a class which holds
> negotiated Session values. getReceivedApplicationProtocols() represents the
> Applicati
On 7/9/2015 7:42 AM, Bradford Wetmore wrote:
> Xuelei/Simone wrote:
>>> Per my understanding, application protocol should be negotiated before
>>> cipher suite and protocol version negotiated.
>>
>> This is not possible for HTTP/2.
>> Application protocol negotiation MUST happen *after* the TLS pro
