Thank you Rus,
I will correct it.
Mounira
- Mail original -
De: "housley"
À: "Mounira Msahli"
Cc: "tls"
Envoyé: Mardi 2 Octobre 2018 11:23:07
Objet: Re: [TLS] TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2
certificates
The docum
Hi Ilari,
>> - The construction looks like it mixes different kinds of structures:
1609.2 Data of type signed versus TLS 1.3 signature. I do not think
this is cryptographically kosher. In fact, I think the call for
"extreme care" for certain kinds of modifications from TLS 1.3
specificatio
The document says:
/* Managed by IANA */
enum {
X509(0),
RawPublicKey(2),
1609Dot2(?), /* Number 3 will be requested for 1609.2 */
(255)
103097(?), /* Number 4 will be requested for 103097 */
(255)
} CertificateType;
Two
On Wed, Sep 26, 2018 at 05:57:28PM +0200, Mounira Msahli wrote:
> Hi all,
>
> Please find attached a new version of the draft. We took account of
> pevious TLS group comments. William, editor of 1609.2, proposes to
> add the section certificate verify (section 4.3 in the draft).
> It concerns t
Hi all,
Please find attached a new version of the draft. We took account of pevious TLS
group comments.
William, editor of 1609.2, proposes to add the section certificate verify
(section 4.3 in the draft).
It concerns the addition of IEEE 1609.2 signature for the the Certificate
verify.
We
ari Liusvaara" com>
Envoyé: Lundi 27 Août 2018 19:39:12
Objet: Re: [TLS] TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2
certificates
On Monday, 27 August 2018 19:24:34 CEST Mounira Msahli wrote:
> One could abbrevate the handshake traces to just show the relevant
> parts (which
On Monday, 27 August 2018 19:24:34 CEST Mounira Msahli wrote:
> One could abbrevate the handshake traces to just show the relevant
> parts (which could also cut some clutter)? I think the relevant
> messages always occur in the same order (clienthello, serverhello/
> encryptedextensions, certificat
"
Envoyé: Lundi 27 Août 2018 18:37:50
Objet: Re: [TLS] TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2
certificates
On Mon, Aug 27, 2018, 8:21 AM Mounira Msahli < [
mailto:mounira.msa...@telecom-paristech.fr |
mounira.msa...@telecom-paristech.fr ] > wrote:
Hi Huber
.
I agree with you about the rest of comments.
Cheers
Mounira
- Mail original -
De: "Ilari Liusvaara"
À: "Mounira Msahli"
Cc: "tls"
Envoyé: Lundi 27 Août 2018 18:34:05
Objet: Re: [TLS] TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2
ce
ards
> Mounira
>
>
>
> - Mail original -
> De: "Hubert Kario"
> À: "tls"
> Cc: "Mounira Msahli" , "Ilari
> Liusvaara"
> Envoyé: Lundi 27 Août 2018 16:39:56
> Objet: Re: [TLS] TLS 1.3 Authentication using ETSI TS 103 097 and
On Mon, Aug 27, 2018 at 06:21:15PM +0200, Mounira Msahli wrote:
> Hi Hubert,
>
> I can do the exercise but the result will be two sections totally
> decorrelated: one for TLS 1.3 and one for TLS 1.2. Two drafts in
> one document.
The certificate message might be bit annoying as it has different
uses
extension defined in [RFC7250].
Kind Regards
Mounira
- Mail original -
De: "Hubert Kario"
À: "tls"
Cc: "Mounira Msahli" , "Ilari Liusvaara"
Envoyé: Lundi 27 Août 2018 16:39:56
Objet: Re: [TLS] TLS 1.3 Authentication using ETSI TS 1
On Friday, 24 August 2018 19:44:36 CEST Mounira Msahli wrote:
> - You should also specify use in TLS 1.2 in the same draft (or say that
> is prohibited). This is so one only needs one reference for the
> codepoint allocation.
>
> >>> It is not prohibited, for TLS 1.2 the extension is already speci
ificate, the other is the implicit
> certificate.
>
> So for you draft submitted, you plan support both types of certificates or
> just one of them, i.e. the X.509 certificate.
>
> Best regards.
>
> Haiguang
>
> -Original Message-----
> From: TLS [mailto:tls-boun...@ie
Best regards.
Haiguang
-Original Message-
From: TLS [mailto:tls-boun...@ietf.org] On Behalf Of Mounira Msahli
Sent: Saturday, August 25, 2018 1:45 AM
To: Ilari Liusvaara
Cc: tls
Subject: Re: [TLS] TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2
certificates
Thank yo
Behalf Of Mounira Msahli
Sent: Saturday, August 25, 2018 1:45 AM
To: Ilari Liusvaara
Cc: tls
Subject: Re: [TLS] TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2
certificates
Thank you Ilari,
In response to your comments below:
- I did not see requirements where to place the e
t quite hard to read due to various editorial
issues.
>> We will update the draft
Kind Regards
Mounira
- Mail original -
De: "Ilari Liusvaara"
À: "Mounira Msahli"
Cc: "tls"
Envoyé: Vendredi 24 Août 2018 17:50:38
Objet: Re: [TLS] TLS 1.3 Authentica
t quite hard to read due to various editorial
issues.
>> We will update the draft
Kind Regards
Mounira
- Mail original -
De: "Ilari Liusvaara"
À: "Mounira Msahli"
Cc: "tls"
Envoyé: Vendredi 24 Août 2018 17:50:38
Objet: Re: [TLS] TLS 1.3 Authentica
Hi William,
Thank you for these details.
And we welcome your comments .
Cheers
Mounira
- Mail original -
De: "William Whyte"
À: "Mounira Msahli"
Cc: "tls"
Envoyé: Vendredi 24 Août 2018 17:16:00
Objet: Re: [TLS] TLS 1.3 Authentication using E
On Fri, Aug 24, 2018 at 04:09:43PM +0200, Mounira Msahli wrote:
> Hi all,
>
>
> The draft: TLS 1.3 Authentication using IEEE 1609.2/ETSI TS 103097
> certificates is updated in accordance with TLS 1.3:
> https://tools.ietf.org/html/draft-tls-certieee1609-01
>
> This document describes the use o
Hi all -- as editor of 1609.2 (and a contributor to 103 097) I'd like to
recommend that the WG moves forward with consideration of this draft. There
are a number of initiatives in the connected vehicle space that need TLS
with 1609.2 certificates, and in particular ISO 21177, which is currently
in
21 matches
Mail list logo
