Re: [TLS] Comments on the session ticket format in TLS 1.3

Martin Thomson <martin.thomson@gmail.com> Mon, 13 March 2017 00:09 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 129501293E8 for <tls@ietfa.amsl.com>; Sun, 12 Mar 2017 17:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GkxDRXvO2Ei9 for <tls@ietfa.amsl.com>; Sun, 12 Mar 2017 17:09:24 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::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 6F643126D74 for <TLS@ietf.org>; Sun, 12 Mar 2017 17:09:24 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id y76so212165967qkb.0 for <TLS@ietf.org>; Sun, 12 Mar 2017 17:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=g4T9MT6DArm9YiuKrGbb84mUwZ4Y9Gp4bslaxuBe00k=; b=gXdTKw8h180HtmQDez12+jEOJ6fD5qJdWcR7EhHQpVpyv8l4kPyZAHIlOH54gAVr8d H9XCa8FF/WJfLxedh/WFdRDg5WRrgXn+1WLaVwZUL/NQLsG/KI5xhuBUMrnBq0iiIDEo HAkk/EM79hXVoiJNlmP3374+HPD3x/XTGko5IWlKRr91vVvO0gLxWXnfndCvsO/qt7IJ ADsw0FVnJKKQIjE3fbPvJyZntlMOkH0MS//O4CGoT8Mqqyp1qSKdh0y1TxiYogDEYRMB ra+cBkUWc2QfPhBlnnJBps4fAFG3HYnt4mYJdsbG4HjMCS2sbqZgVjxwgKfbEbyXxmCb N86w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=g4T9MT6DArm9YiuKrGbb84mUwZ4Y9Gp4bslaxuBe00k=; b=tUJUyaYv0fkZBnnJwJhVO+KfzWxMfcXvM6kkyY+3lOajIw1pgYg2+EAaTxuYIdu7h8 4SjIe9WBnL0+y0UQxx1GwekvuEKLHxGQlYKTIzF2gmU8VDQgWpqQUMViSmkF8m9P2Xvi 1tesz9iT4OoUl9NGBO3q+pA4UzbCtVkV0Enzrs9sUgexRQIfBPEyUQP2IcGEhd6W2POc UTtmQvqjEuRw56iP+LFfDyBWOhBEDMt0ewrfBCdPWK8Lo85SEcBnzS7fy+i5lnBXbfCH jl3lxaeFn52toezfVVZG1RRG4gok+ezwOEAahlM8osPLTuoFwJhL4zB3GbUK78jwwQpP d4Uw==
X-Gm-Message-State: AMke39l9b0GMgT3Kgz0nb+4cHKYrMUX0w4G00DYGIUTEW6Z+j+J0ACVm27t7bZntIjUtrI/imLe2CgYEa1FKpg==
X-Received: by 10.233.216.68 with SMTP id u65mr28646474qkf.68.1489363763585; Sun, 12 Mar 2017 17:09:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.194 with HTTP; Sun, 12 Mar 2017 17:09:23 -0700 (PDT)
In-Reply-To: <CAFewVt558LB_QTb56i2hQA+pY5HEM7LCLuzEOsMAhq23sa+EMg@mail.gmail.com>
References: <CANHgQ8EEJeTVvyQH8SosO4M3Ecz2=ZE-UPGndcu=XfB1f+1Zgg@mail.gmail.com> <CAFewVt558LB_QTb56i2hQA+pY5HEM7LCLuzEOsMAhq23sa+EMg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 13 Mar 2017 11:09:23 +1100
Message-ID: <CABkgnnW7fH9D6G=8+dEb4dTDheh2yZkkBickKZhzVzYqXr-hYQ@mail.gmail.com>
To: Brian Smith <brian@briansmith.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/eLIK2sBYfc6hZfA00k_QmbWbHi0>
Cc: "tls@ietf.org" <TLS@ietf.org>
Subject: Re: [TLS] Comments on the session ticket format in TLS 1.3
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 13 Mar 2017 00:09:26 -0000

On 13 March 2017 at 10:55, Brian Smith <brian@briansmith.org> wrote:
>> So, I'd prefer to bring session IDs back, and
>> to arrange things so that they're always server-generated.
>
> Even in earlier versions, session IDs were not required with
> resumption using tickets. The server sends an empty session ID and the
> client may (should, IMO) send an empty session ID in the resumption
> hello.

This is true, but I believe that there are compatibility reasons to
send the session ID anyway.  I don't know the details, but it probably
comes down to the load balancing thing that Ivan is asking about.

All told, this was a mess in previous versions.  Now we at least have
a hope of maintaining unlinkability.