done.
Thanks for the review!
Yours
Daniel
On Tue, Nov 8, 2016 at 1:07 AM, Ilari Liusvaara
wrote:
> On Mon, Nov 07, 2016 at 10:16:13PM -0500, Daniel Migault wrote:
> > Hi,
> >
> > The current draft is only considering TLS1.2. TLS1.3 is only mentioned
> for
> > advocating AEAD.
> >
> > Do you t
On Mon, Nov 07, 2016 at 10:16:13PM -0500, Daniel Migault wrote:
> Hi,
>
> The current draft is only considering TLS1.2. TLS1.3 is only mentioned for
> advocating AEAD.
>
> Do you think we should add text that details how to proceed with TLS1.3 ?
> If so what do you think of the following text ?
Hi,
The current draft is only considering TLS1.2. TLS1.3 is only mentioned for
advocating AEAD.
Do you think we should add text that details how to proceed with TLS1.3 ?
If so what do you think of the following text ?
Comments are welcome!
Yours,
Daniel
The assigned code points are only ex
On Tue, Oct 18, 2016 at 04:22:59PM +, Xiaoyin Liu wrote:
> Why does this draft normatively depend on TLS 1.3, even if the
> cipher suites defined in this draft use the old syntax, which
> TLS 1.3 no longer uses?
I don't see any reason why it would normatively depend.
If it claims to be so, IM
niel.miga...@ericsson.com>
Cc: tls@ietf.org<mailto:tls@ietf.org>
Subject: Re: [TLS] early IANA code point assignment request for
draft-ietf-tls-ecdhe-psk-aead
I think there might be consensus to ask for code points but not early. This
draft can’t really proceed any faster than the TLS1.3 and 44
I think there might be consensus to ask for code points but not early. This
draft can’t really proceed any faster than the TLS1.3 and 4492bis drafts.
spt
> On Oct 17, 2016, at 12:03, Daniel Migault wrote:
>
> Hi,
>
> I am not clear what the consensus is for the following points. Is there an
Hi,
We are discussing in the TLS wg assignment points for TLS PSK
authentication. We would like to understand if there is a specific interest
of the IoT community for the following suites.
TLS_ECDHE_PSK_WITH_AES_128_CCM_8_SHA256 = {0xTBD; 0xTBD} {0xD0,0x03};
TLS_ECDHE_PSK_WITH_AES_256_CCM_8_SHA38
I would like to see these included:
> TLS_ECDHE_PSK_WITH_AES_128_GCM_SHA256 = {0xTBD; 0xTBD} {0xD0,0x01};
> TLS_ECDHE_PSK_WITH_AES_256_GCM_SHA384 = {0xTBD; 0xTBD} {0xD0,0x02};
I am fine with including these as well if someone wants to use them:
> TLS_ECDHE_PSK_WITH_AES_128_CCM_SHA256 = {0x
Hi,
I am not clear what the consensus is for the following points. Is there any
consensus for requesting the following ones?
BR,
Daniel
TLS_ECDHE_PSK_WITH_AES_128_GCM_SHA256 = {0xTBD; 0xTBD} {0xD0,0x01};
TLS_ECDHE_PSK_WITH_AES_256_GCM_SHA384 = {0xTBD; 0xTBD} {0xD0,0x02};
TLS_ECDHE_PSK_WITH_A
I'm mainly just looking to economize on different configurations.
On 9 October 2016 at 16:32, John Mattsson wrote:
> Hi Martin,
>
>
> AES_256_CCM_8 was not in the first versions of the draft but added later
> after request from IoT people (probably afraid of quantum computers).
>
>
> While I thin
Hi Martin,
AES_256_CCM_8 was not in the first versions of the draft but added later
after request from IoT people (probably afraid of quantum computers).
While I think it makes very much sense to have short tags in wireless
radio, I do not know how large need there is for AES-256 in IoT for
c
Speaking of early assignments for code points, it'd be about time for one
for TLS-LTS as well, otherwise it'll end up with the de facto 0x42 hard-
coded into various implementations. So could I get an IANA early assignment
for that?
Peter.
___
TLS maili
Looking at those emails, I am prompted to wonder if anyone can justify
the existence of a ciphersuite with a double-sized key and half-sized
authentication tag. RFC 6655 doesn't really explain how that is a
useful thing.
On 10 August 2016 at 19:33, Nikos Mavrogiannopoulos wrote:
> On Tue, 2016-0
On Tue, 2016-08-09 at 14:45 -0400, Sean Turner wrote:
> All,
>
> We've received a request for early IANA assignments for the 6 cipher
> suites listed in https://datatracker.ietf.org/doc/draft-ietf-tls-ecdh
> e-psk-aead/. Please respond before August 23rd if you have concerns
> about early code po
On 10 August 2016 at 04:45, Sean Turner wrote:
> We've received a request for early IANA assignments for the 6 cipher suites
> listed in https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/.
> Please respond before August 23rd if you have concerns about early code point
> assignment
All,
We've received a request for early IANA assignments for the 6 cipher suites
listed in https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/.
Please respond before August 23rd if you have concerns about early code point
assignment for these cipher suites.
J&S
__
16 matches
Mail list logo
