IETF Logo Mail Archive

TR: New Version Notification for draft-kuhn-quic-0rtt-bdp-07.txt

Kuhn Nicolas <Nicolas.Kuhn@cnes.fr> Mon, 18 May 2020 08:17 UTC

Return-Path: <Nicolas.Kuhn@cnes.fr>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 989C33A095E for <quic@ietfa.amsl.com>; Mon, 18 May 2020 01:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 gfmO0h1R5Ojd for <quic@ietfa.amsl.com>; Mon, 18 May 2020 01:17:02 -0700 (PDT)
Received: from mx2.cnes.fr (mx2.cnes.fr [194.199.174.201]) (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 1EFA53A095D for <quic@ietf.org>; Mon, 18 May 2020 01:17:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.73,406,1583193600"; d="scan'208";a="35004500"
X-IPAS-Result: A2HPAgDxQ8Je/wYBeApmHAEBAQEBAQcBARIBAQQEAQFAgUeDBxSBMwqEGqxsCwEBAQEBAQEBASsMBAEBhEQCF4IqOBMCEAEBAQUBAQEBAQUCAQECAoVzTAyGRwIBAyMRQxICARUNAgYgAgICMBUQAgQTCBODDIMLrj12gTIahCQCDkGFLYEOKoFljHeBVIMLgmcBAQIBARiBMRoFM4JaM4ItBJFbhkeabgeBSIELgnSFMoZEiXqBAoFbgQ6HYoRvA40Xmi6VeYF5MxonK4MKCUcYkFYaiGOFQnQCNQIGAQcBAQMJjiuBEAEB
X-URL-LookUp-ScanningError: 1
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: IETF QUIC WG <quic@ietf.org>
Subject: TR: New Version Notification for draft-kuhn-quic-0rtt-bdp-07.txt
Thread-Topic: New Version Notification for draft-kuhn-quic-0rtt-bdp-07.txt
Thread-Index: AQHWLOwCIIql756Bu0mh4ih88RSVJKitfmFA
Date: Mon, 18 May 2020 08:16:58 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF1EDAB042@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <158978951893.22751.4814113172992555805@ietfa.amsl.com>
In-Reply-To: <158978951893.22751.4814113172992555805@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-25426.005
x-tm-as-result: No--19.554700-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sj6xX7no87tGGhWhH2hTBc7Cb7o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 08:17:05 -0000

Hi, 

We have been working on an updated version of the 0-RTT draft. 

In short, the document describes a generic method to exchange path parameters
relating to transport.  The additional transport parameters can help
a connection that continues after an interruption or restarts by
sharing connection properties.  They can be used to increase the
performance for a path with large RTT.

The motivation is described in the document, but here is an extract :
"Currently each side has a proprietary solution to measure and to
   store path characteristics.  Recalling the parameters of a previous
   connection would allow:
   o  Server and client to re-initialise the state from previously
      established parameters (i.e., minRTT, MTU, bottleneck capacity,
      etc.)
   o  The client to prepare the right resources
   o  The server to adapt to non-default path characteristics"

Please let us know if you have any questions/comments. 

Kind regards, 

Nico on the behalf of the authors 


-----Message d'origine-----
De : internet-drafts@ietf.org <internet-drafts@ietf.org> 
Envoyé : lundi 18 mai 2020 10:12
À : Emile Stephan <emile.stephan@orange.com>; Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>; Gorry Fairhurst <gorry@erg.abdn.ac.uk>; Stephan Emile <emile.stephan@orange.com>; Tom Jones <tom@erg.abdn.ac.uk>
Objet : New Version Notification for draft-kuhn-quic-0rtt-bdp-07.txt


A new version of I-D, draft-kuhn-quic-0rtt-bdp-07.txt has been successfully submitted by Nicolas Kuhn and posted to the IETF repository.

Name:		draft-kuhn-quic-0rtt-bdp
Revision:	07
Title:		Transport parameters for 0-RTT connections
Document date:	2020-05-18
Group:		Individual Submission
Pages:		8
URL:            https://www.ietf.org/internet-drafts/draft-kuhn-quic-0rtt-bdp-07.txt
Status:         https://datatracker.ietf.org/doc/draft-kuhn-quic-0rtt-bdp/
Htmlized:       https://tools.ietf.org/html/draft-kuhn-quic-0rtt-bdp-07
Htmlized:       https://datatracker.ietf.org/doc/html/draft-kuhn-quic-0rtt-bdp
Diff:           https://www.ietf.org/rfcdiff?url2=draft-kuhn-quic-0rtt-bdp-07

Abstract:
   0-RTT mechanisms reduce the time it takes for the first bytes of
   application data to be processed in a transport connection and can
   greatly reduce connection latency during setup.  The 0-RTT transport
   features described by quic-transport help clients establish secure
   connections with a minimal number of round-trips.

   This document describes a generic method to exchange path parameters
   relating to transport.  The additional transport parameters can help
   a connection that continues after an interruption or restarts by
   sharing connection properties.  They can be used to increase the
   performance for a path with large RTT.

                                                                                  


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

v2.23.0 | Report a Bug | By Email