Re: [TLS] Encryption of TLS 1.3 content type

Yoav Nir <ynir.ietf@gmail.com> Fri, 25 July 2014 20:57 UTC

Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <DD255E31-FA87-40CE-AF13-0F43A7DD54CF@cisco.com>
Date: Fri, 25 Jul 2014 16:57:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <578C0CCE-DD3C-41B9-A8D7-19D5B799F643@gmail.com>
References: <DD255E31-FA87-40CE-AF13-0F43A7DD54CF@cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/N3skB7VbwCBZRDu_u_xQE-ggdYw
Cc: "<tls@ietf.org>" <tls@ietf.org>
Subject: Re: [TLS] Encryption of TLS 1.3 content type
Precedence: list

Hi.

I believe that changing the 5-byte record header will cause us trouble. Passive IDS/IPS devices follow TLS streams to detect certain attacks. They will cut connections. I also believe that it is impossible to “run some tests” because there are literally dozens of different such middleboxes, with multiple software/firmware versions available for each type.

I therefore support leaving the 5-byte header as it is, fixing the ContentType value to 23 for all encrypted records, and having another contentType byte within the encrypted record.

Yoav

On Jul 25, 2014, at 1:37 PM, Joseph Salowey (jsalowey) <jsalowey@cisco.com> wrote:

> At the interim meeting on July 20, 2014 there was general consensus to support the encryption of TLS 1.3 content type.  The favored approach was to remove the content type and version from the TLS record layer header and add the content type to the encrypted data.   The proposal is to update the draft to document this approach and try to run some tests to see if this causes much grief with middle boxes.  If you object to this proposal please respond to the list by Friday, August 01, 2014.  
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] Encryption of TLS 1.3 content type Yoav Nir
Re: [TLS] Encryption of TLS 1.3 content type Fabrice Gautier
Re: [TLS] Encryption of TLS 1.3 content type Eric Rescorla
[TLS] Encryption of TLS 1.3 content type Joseph Salowey (jsalowey)
Re: [TLS] Encryption of TLS 1.3 content type Watson Ladd
Re: [TLS] Encryption of TLS 1.3 content type Colm MacCárthaigh
Re: [TLS] Encryption of TLS 1.3 content type Juho Vähä-Herttua
Re: [TLS] Encryption of TLS 1.3 content type Peter Gutmann
Re: [TLS] Encryption of TLS 1.3 content type Yoav Nir
Re: [TLS] Encryption of TLS 1.3 content type Nikos Mavrogiannopoulos
Re: [TLS] Encryption of TLS 1.3 content type Yoav Nir
Re: [TLS] Encryption of TLS 1.3 content type Daniel Kahn Gillmor
Re: [TLS] Encryption of TLS 1.3 content type Martin Rex
Re: [TLS] Encryption of TLS 1.3 content type Colm MacCárthaigh
Re: [TLS] Encryption of TLS 1.3 content type Nikos Mavrogiannopoulos
Re: [TLS] Encryption of TLS 1.3 content type Daniel Kahn Gillmor
Re: [TLS] Encryption of TLS 1.3 content type Nikos Mavrogiannopoulos
Re: [TLS] Encryption of TLS 1.3 content type Viktor Dukhovni
Re: [TLS] Encryption of TLS 1.3 content type Brian Sniffen
Re: [TLS] Encryption of TLS 1.3 content type Stephen Farrell
Re: [TLS] Encryption of TLS 1.3 content type Michael StJohns
Re: [TLS] Encryption of TLS 1.3 content type Yoav Nir
Re: [TLS] Encryption of TLS 1.3 content type Colm MacCárthaigh
Re: [TLS] Encryption of TLS 1.3 content type Eric Rescorla
Re: [TLS] Encryption of TLS 1.3 content type Andy Lutomirski
Re: [TLS] Encryption of TLS 1.3 content type Peter Gutmann
Re: [TLS] Encryption of TLS 1.3 content type Alfredo Pironti
Re: [TLS] Encryption of TLS 1.3 content type Martin Rex
Re: [TLS] Encryption of TLS 1.3 content type Alfredo Pironti