[TLS] Updates on the "Transport parameters for 0-RTT connections" draft

Kuhn Nicolas <Nicolas.Kuhn@cnes.fr> Tue, 21 May 2019 13:48 UTC

Return-Path: <Nicolas.Kuhn@cnes.fr>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E1C35120043; Tue, 21 May 2019 06:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 97nPPaqa8FUS; Tue, 21 May 2019 06:48:38 -0700 (PDT)
Received: from mx1.cnes.fr (mx1.cnes.fr []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22C67120041; Tue, 21 May 2019 06:48:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.60,495,1549929600"; d="scan'208,217";a="7936522"
X-URL-LookUp-ScanningError: 1
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, IETF QUIC WG <quic@ietf.org>, "'tls@ietf.org'" <tls@ietf.org>
CC: "'emile.stephan@orange.com'" <emile.stephan@orange.com>, "'gorry@erg.abdn.ac.uk'" <gorry@erg.abdn.ac.uk>, Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
Thread-Topic: Updates on the "Transport parameters for 0-RTT connections" draft
Thread-Index: AdUP24Zg+1VIa8FMRoKfDVG/fwUlTg==
Date: Tue, 21 May 2019 13:47:28 +0000
Deferred-Delivery: Tue, 21 May 2019 13:48:27 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF1EBEEF69@TW-MBX-P03.cnesnet.ad.cnes.fr>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-tm-as-product-ver: SMEX-
x-tm-as-result: No--19.463400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_F3B0A07CFD358240926B78A680E166FF1EBEEF69TWMBXP03cnesnet_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/d4841frqbZzWyUCxqNidmMCylQY>
Subject: [TLS] Updates on the "Transport parameters for 0-RTT connections" draft
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: Tue, 21 May 2019 13:48:41 -0000

Dear all,

Following the different feedbacks on this draft, we have proposed an updated version on the "Transport parameters for 0-RTT connections".

The draft proposes a solution where path characteristics are shared between the peers to improve the ingress traffic for 0-RTT connections.

The difference with version 01 are mainly based on the received feedback.
In short, we now a BDP_metadata structure so that various path parameters can be exposed to the client (MTU, RTT, bandwidth, loss-rate).
We have also added a section to discuss what happens when BDP is used incorrectly.

Let us know if we have any views or interest in this proposal.


Nico for the authors