Hi,
An open issue for draft-ietf-tls-chacha20-poly1305-00 raised by Eric
Rescorla is that this draft doesn't use the draft-TLS 1.3 mechanism
for setting the nonce per record [0]. Is there any support for
switching these ciphersuites to draft-TLS 1.3 nonce mechanism even for
TLS 1.2? The
On Sat, Jul 25, 2015 at 09:07:49PM +0200, Eric Rescorla wrote:
We agreed on how to do this in Prague. The sticking point was establishing
the cipher suite. I have WIP text on my machine for both of these which I
will be
sending early next week, once I get enough sleep to be able to clean
On Mon, Aug 3, 2015 at 11:51 PM, Ilari Liusvaara
ilari.liusva...@elisanet.fi wrote:
On Sat, Jul 25, 2015 at 09:07:49PM +0200, Eric Rescorla wrote:
We agreed on how to do this in Prague. The sticking point was
establishing
the cipher suite. I have WIP text on my machine for both of
Personally, I would rather see the nonce construction follow the form
defined in the respective TLS version.
Yes, consistency. +1
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
On Tue, Aug 4, 2015 at 12:20 PM Salz, Rich rs...@akamai.com wrote:
Personally, I would rather see the nonce construction follow the form
defined in the respective TLS version. [DB: Adding back in for context:
That means including redundant bytes in TLS 1.2 and only getting the full
On 4 August 2015 at 05:37, Nikos Mavrogiannopoulos n...@redhat.com wrote:
Is there any support for
switching these ciphersuites to draft-TLS 1.3 nonce mechanism even for
TLS 1.2? The alternative is to use the TLS 1.2 mechanism with the
redundant bytes redacted as the draft is now [1].
