[TLS] ALPS and TLS 1.3 half-RTT data

David Benjamin <davidben@chromium.org> Thu, 03 December 2020 21:55 UTC

Return-Path: <davidben@google.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 677803A0D17 for <tls@ietfa.amsl.com>; Thu, 3 Dec 2020 13:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.25
X-Spam-Level:
X-Spam-Status: No, score=-9.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=chromium.org
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 V-CDOtQDD5vA for <tls@ietfa.amsl.com>; Thu, 3 Dec 2020 13:55:40 -0800 (PST)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (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 067753A0D03 for <tls@ietf.org>; Thu, 3 Dec 2020 13:55:40 -0800 (PST)
Received: by mail-pj1-x102a.google.com with SMTP id f14so1863524pju.4 for <tls@ietf.org>; Thu, 03 Dec 2020 13:55:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S1afFZaBB78FxIHUH2DdYcY7+iHQ0XL1lhsjiZacAVw=; b=TS4VXCjcOEWKzNu7tXKAL+Sl07Zr0IgLsxMCUuRYyZUPibH/ccVOcMPkio/eW7tI2K 7OFHQWV0LQwSCpJwyT7I8H118G4X12qbHifLDEVJFVmOhx5IE8mmYoU/5XKNEZd15JzT w0hplUcHJYh1qnYiQvIc8e0oM+wv+7//aa6ag=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=S1afFZaBB78FxIHUH2DdYcY7+iHQ0XL1lhsjiZacAVw=; b=EBgIFMcZ5GoPQ3QNXfzau3av6mcXrSyRx0ge5qN/kS0cIC++6HRzphEDaUrlbvrtpR bmfnlit5pOCxNHHAZCA6pr+QDKTyn4QhAIt3HvokH3CZn4JrSyK7V779lAohlgDwe8WB eRrf5ElpyiwySzag3JxqWjSL/9pQIhefgoQs3JRXQVw7+sudAvxGx7DKqZLF0IKG+4rp QFdPEzsUmo0mzx7U6ZejTIJP9kE5vN0URl/s3N3veUj2Zdlga66dWFLJblREW2H9Cyq/ tZgOFJbBbYPqWLBqRxGwHFIzy9JcOADEzt8IA1gep9/uGi/Mjfyeqvnbz3ZsEytP5HRO b0hw==
X-Gm-Message-State: AOAM531CnDm/JjrnBI0vAldd7nSfkgXPt+QseBCvhb2tNbtpID4sN/KI pIwXMOg8bzFwtCzhZxF1OBE7zBJ+UlQf6WVD2XfpPzglhQ==
X-Google-Smtp-Source: ABdhPJwGiJolN7juVjXKdmq/Vg/VpCsE4kF2KGhoYC/oz64jKbtVGAhw3LWssdbLdJPKXyiTDEOre88wViFiouxQAR8=
X-Received: by 2002:a17:90a:6346:: with SMTP id v6mr1082983pjs.162.1607032539084; Thu, 03 Dec 2020 13:55:39 -0800 (PST)
MIME-Version: 1.0
References: <160703055132.9234.3055845983488231389@ietfa.amsl.com>
In-Reply-To: <160703055132.9234.3055845983488231389@ietfa.amsl.com>
From: David Benjamin <davidben@chromium.org>
Date: Thu, 3 Dec 2020 16:55:23 -0500
Message-ID: <CAF8qwaAUE4H2-JxCyQJSWW680=Xp9pkUOQdOQpbLhd-HjYaVcA@mail.gmail.com>
To: "<tls@ietf.org>" <tls@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000a2ed4305b5966b7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/mpPCqxRg9p3YkTHJjNhXZmXzF7I>
Subject: [TLS] ALPS and TLS 1.3 half-RTT data
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Dec 2020 21:55:41 -0000

Hi TLS and HTTP friends,

At the last HTTPWG interim, there was a question of why one would want
something like ALPS (draft-vvv-tls-alps) for HTTP SETTINGS
(draft-vvv-httpbis-alps) over TLS 1.3 half-RTT data. I know we've also had
some discussion on this topic in the TLSWG as well. At the HTTP meeting,
folks suggested writing up what a half-RTT-based mechanism might look like,
so I put together an I-D below. I hope it helps clarify some of our
thinking.

(The I-D is not meant for adoption or publication or anything. I figured an
I-D was probably the most familiar format for folks.)

David

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Thu, Dec 3, 2020 at 4:22 PM
Subject: New Version Notification for
draft-davidben-tls-alps-half-rtt-00.txt
To: David Benjamin <davidben@google.com>



A new version of I-D, draft-davidben-tls-alps-half-rtt-00.txt
has been successfully submitted by David Benjamin and posted to the
IETF repository.

Name:           draft-davidben-tls-alps-half-rtt
Revision:       00
Title:          Comparing ALPS and Half-RTT Data
Document date:  2020-12-03
Group:          Individual Submission
Pages:          11
URL:
https://www.ietf.org/archive/id/draft-davidben-tls-alps-half-rtt-00.txt
Status:
https://datatracker.ietf.org/doc/draft-davidben-tls-alps-half-rtt/
Html:
https://www.ietf.org/archive/id/draft-davidben-tls-alps-half-rtt-00.html
Htmlized:
https://tools.ietf.org/html/draft-davidben-tls-alps-half-rtt-00


Abstract:
   This document compares the Application Layer Protocols Settings
   extension with the half-RTT feature in TLS 1.3.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat