Re: [TLS] Data volume limits

Eric Rescorla <ekr@rtfm.com> Tue, 15 December 2015 22:08 UTC

Return-Path: <ekr@rtfm.com>
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 6AACB1B2B9D for <tls@ietfa.amsl.com>; Tue, 15 Dec 2015 14:08:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=no
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 0UpfB9uajJSu for <tls@ietfa.amsl.com>; Tue, 15 Dec 2015 14:08:44 -0800 (PST)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25EED1B2B94 for <tls@ietf.org>; Tue, 15 Dec 2015 14:08:43 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id t125so36441690qkh.3 for <tls@ietf.org>; Tue, 15 Dec 2015 14:08:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=PIL+FjZXHOuhIEy6mCEUEZZVBQI2rsxUMUXnWY+1Ivc=; b=O2aDRZGnjewpP9cA0vbVsgj4jIE3DttcryQx3H68Vl9I+5BVXpHPbzpCRoY95wmNnV tF4LOwGFpajRmiAiDtIePO/5cyUXsEGTYhXT2FfedD1tjUMDPJrzMY7EznoYEcVzq+GS HmUZoFhwNSc1jM95LEhHXOOb2jjvhQzCZ8nMNSIfTkhlwlRGRgn8WAH32vG8orxeRbNA +vDF2W02C5gSU2ldRsL11hWcDmEskV3ODWO34iE96T5FJA9ZOatfF4+dZPloVi1Mg3Tq Bt4Lh1+6PlZYiJOSp7thM/IP8ysmGob0BWpYGgBnrkDAdpneZYnDCx8u4MyF0IvQx5Ni KPWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=PIL+FjZXHOuhIEy6mCEUEZZVBQI2rsxUMUXnWY+1Ivc=; b=XQiKe85woLL5dNvpRDAlw54ixOBes3hfT/pCPqLfNyRCM7SfQ+PoT0QfQLKvjZwXeI VsOBaU0jiOwV7PjvsqapWZ7vtPNDwWI1cLs92pzQBLxtkPt7cvUwc4V1B3mYxfL1nmAJ 4GdMb0O5awVtnO2cn39+nvc8zp7vHF1NlJizxbqiTM9OLbmXuz2SF9Jo7vqd9+jKlgHV ZQ/TeOC4z8Hor55P4YcpnVQkylVtLOMq5zAAasSvKnRkXDhb19JfaHSAB6ssJhYzgGrm AsnYNLW3l64xU/EEcJ5NbLdG6WzI7j66GKeko6mUC4iVbm6K4Av8r+07KgIcz2RPJhP0 nlhg==
X-Gm-Message-State: ALoCoQmDYbMIQPP45PjcyylOiVTH3dK5aydYObBJnB1ul0SMZazzT10ugSvMeqwf1c/wtNLhhd2MSBEwAcWJ0SQSRp+JdhNWzA==
X-Received: by 10.129.46.84 with SMTP id u81mr24650179ywu.129.1450217322310; Tue, 15 Dec 2015 14:08:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.13.249.197 with HTTP; Tue, 15 Dec 2015 14:08:02 -0800 (PST)
In-Reply-To: <e007baa2f53249d49917e6023e578bc0@XCH-RTP-006.cisco.com>
References: <CABcZeBNR76DqPo0Mukf5L2G-WBSC+RCZKhVGqBZq=tJYfEHLUg@mail.gmail.com> <e007baa2f53249d49917e6023e578bc0@XCH-RTP-006.cisco.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 15 Dec 2015 14:08:02 -0800
Message-ID: <CABcZeBPu23N69u0AsiLRswN2uHJhMQ-CaVF1x7gFe87h_sa9GQ@mail.gmail.com>
To: "Scott Fluhrer (sfluhrer)" <sfluhrer@cisco.com>
Content-Type: multipart/alternative; boundary=001a11409380581cbf0526f7087a
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/75KVJn6oNNXY_dyS02NLpgoKMIE>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Data volume limits
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: Tue, 15 Dec 2015 22:08:45 -0000

On Tue, Dec 15, 2015 at 2:01 PM, Scott Fluhrer (sfluhrer) <
sfluhrer@cisco.com> wrote:

> Might I enquire about the cryptographical reason behind such a limit?
>
>
>
> Is this the limit on the size of a single record?  GCM does have a limit
> approximately there on the size of a single plaintext it can encrypt.  For
> TLS, it encrypts a record as a single plaintext, and so this would apply to
> extremely huge records.
>
>
>
> Or is this a limit on the total amount of traffic that can go through a
> connection over multiple records?  If this is the issue, what is the
> security concern that you would have if that limit is exceeded?
>

Watson provided these, so perhaps he can elaborate.

It would be good to have a value we all agree on.

Thanks,
-Ekr


>
> Thank you.
>
>
>
> *From:* TLS [mailto:tls-bounces@ietf.org] *On Behalf Of *Eric Rescorla
> *Sent:* Tuesday, December 15, 2015 4:15 PM
> *To:* tls@ietf.org
> *Subject:* [TLS] Data volume limits
>
>
>
> Watson kindly prepared some text that described the limits on what's safe
>
> for AES-GCM and restricting all algorithms with TLS 1.3 to that lower
>
> limit (2^{36} bytes), even though ChaCha doesn't have the same
>
> restriction.
>
>
>
> I wanted to get people's opinions on whether that's actually what we want
>
> or whether we should (as is my instinct) allow people to use ChaCha
>
> for longer periods.
>
>
>
> -Ekr
>
>
>