Re: [TLS] Record header size?

Peter Gutmann <pgut001@cs.auckland.ac.nz> Wed, 18 November 2015 01:32 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C452D1B36F4 for <tls@ietfa.amsl.com>; Tue, 17 Nov 2015 17:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.785
X-Spam-Level:
X-Spam-Status: No, score=-4.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VsLcVDH72IVw for <tls@ietfa.amsl.com>; Tue, 17 Nov 2015 17:32:38 -0800 (PST)
Received: from mx4.auckland.ac.nz (mx4.auckland.ac.nz [130.216.125.248]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E246C1B36F2 for <tls@ietf.org>; Tue, 17 Nov 2015 17:32:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1447810358; x=1479346358; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=28gWZrrzZkOT8AbJdOhi+HjFxRPoT3CQjtBEjIJZHXM=; b=nYyHdPC5wS3bkoOVClwUmaIlFhle/Cd4vMSaGPbHqnRDw5w5i57Eqlbz nbpWKQFYMitTEMJC4rtD+Eq0qurLzkBrPMoDYwU0nZ33OUAcKAOFskJCB +kUg2/gPdp5S6OBfDN1/eBBqR5n43CXg/5vUsM6y61429J3sqfacNRpYe 4T6fK0RwprQFhAQfTfrp4J57yl3OM7PHq2jweOL83+IKNQ4mhSfg86BSM /Xz3+5caXwZzP2T9oO2+TbH5nrxkLGcp0EJU+OiDTtQCh7/GAJDix9buC OPpgjv+P8Toytyfv46CWuvWdsE7U9BcY2WsTjbfQSx+d1gUJdg1/h/XDm g==;
X-IronPort-AV: E=Sophos;i="5.20,310,1444647600"; d="scan'208";a="54717195"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.112 - Outgoing - Outgoing
Received: from uxchange10-fe1.uoa.auckland.ac.nz ([130.216.4.112]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 18 Nov 2015 14:32:23 +1300
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.51]) by uxchange10-fe1.UoA.auckland.ac.nz ([130.216.4.112]) with mapi id 14.03.0174.001; Wed, 18 Nov 2015 14:32:23 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Eric Rescorla <ekr@rtfm.com>, "Short, Todd" <tshort@akamai.com>
Thread-Topic: [TLS] Record header size?
Thread-Index: AQHRIUwqo2PzkmG0m02LaFyKO+3dU56fmOsAgAFmVoQ=
Date: Wed, 18 Nov 2015 01:32:22 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4B679E6@uxcn10-5.UoA.auckland.ac.nz>
References: <C5F506DC-F814-4C0B-AFAA-86CF790817A7@akamai.com>, <CABcZeBP5QPQAXKvM_oEAzex0-vrVWMvOW0yZuamvF5hxAHtmtw@mail.gmail.com>
In-Reply-To: <CABcZeBP5QPQAXKvM_oEAzex0-vrVWMvOW0yZuamvF5hxAHtmtw@mail.gmail.com>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/76AY_zHh9NBEz97WAcPvlM4HCKA>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Record header size?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 01:32:42 -0000

Eric Rescorla <ekr@rtfm.com> writes:

>The concern here is backward compatibility with inspection middleboxes which
>expect the length field to be in a particular place.

Given that the rest of TLS 1.3 is going to break compatibility with pretty
much everything everywhere, I can't see this as a big concern, may as well fix
it at the same time as everything else is being changed.

Peter.