Re: [TLS] TLS 1.3 comments

Dave Garrett <davemgarrett@gmail.com> Tue, 18 August 2015 00:00 UTC

Return-Path: <davemgarrett@gmail.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 C0D691B2FE2 for <tls@ietfa.amsl.com>; Mon, 17 Aug 2015 17:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 L9tdF8CG2HeE for <tls@ietfa.amsl.com>; Mon, 17 Aug 2015 17:00:38 -0700 (PDT)
Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (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 470961B2FE5 for <tls@ietf.org>; Mon, 17 Aug 2015 17:00:38 -0700 (PDT)
Received: by ykdt205 with SMTP id t205so143005034ykd.1 for <tls@ietf.org>; Mon, 17 Aug 2015 17:00:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=dL/RU6d4v/gknWo0udLpYT9bCJ9Lc8prVyTLUfDA+ME=; b=MA5HFIrIRWBxLE3tVmWwRADJNVL65fmRbuMbGvkTfn87JCC39H5iwj+hOBJ18pWIa2 DDYvB1XEkyK3EjR9hdkPRV/DJhZQAfxI6Q+YSmaV1zqPgdy/wPg7Hrfk9w1J117FTLgQ jC5n+6zaedC55pSgpVGAU/S6gkwZ33+GnsWoxv7p75BG7hJbejFKt8BGg8OaT6MqC4XK F1bT4+IO3ZB0Cp/XUdCL3uqFQ89erl91bWkp38TZsiCcJEjCvXuyFim8m8u+1dojNEAp iKyVvr5vb//dl+NsgY2zY7LwKj/IHkAbGv8SQsXSD30z+nPUkH2tsP518V+8M1N7REcH SRmQ==
X-Received: by 10.170.199.7 with SMTP id q7mr4234772yke.66.1439856037596; Mon, 17 Aug 2015 17:00:37 -0700 (PDT)
Received: from dave-laptop.localnet (pool-108-52-139-147.phlapa.fios.verizon.net. [108.52.139.147]) by smtp.gmail.com with ESMTPSA id d23sm14634439ywb.16.2015.08.17.17.00.36 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 17 Aug 2015 17:00:37 -0700 (PDT)
From: Dave Garrett <davemgarrett@gmail.com>
To: tls@ietf.org
Date: Mon, 17 Aug 2015 20:00:35 -0400
User-Agent: KMail/1.13.5 (Linux/2.6.32-74-generic-pae; KDE/4.4.5; i686; ; )
References: <55D1B5CC.1050005@gmail.com>
In-Reply-To: <55D1B5CC.1050005@gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201508172000.35844.davemgarrett@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/Bn_Y7w9AtJKuG9ULYBMZjdkRYw0>
Subject: Re: [TLS] TLS 1.3 comments
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, 18 Aug 2015 00:00:39 -0000

On Monday, August 17, 2015 06:22:04 am Yaron Sheffer wrote:
> The record length field is limited by encrypted-length+2048. Shouldn't it be 1024? - "Each AEAD cipher MUST NOT produce an expansion of greater than 1024 bytes".

See: https://github.com/tlswg/tls13-spec/issues/55

> Handshake_failure alert seems to be synonymous with insufficient_security (and Sec. 6.2.1 proves it...). Can we clarify the difference, or deprecate one of them?

See: https://github.com/tlswg/tls13-spec/pull/201/commits

A PR for the typos would be appreciated. I'd suggest having the typos in a separate PR from any other proposed changes.


Dave


PS
I recommend against citing sections by number. The numbers can change; the sections can change completely. Cite by draft number & section, or preferably via a link to a section in a page. Also note that there are a few different things that can be considered the "latest" draft, so always specify which one to be clear. (e.g. numbered draft, GitHub current draft, PR drafts, WIP branch drafts, etc.)