Re: [Coin] TR: New Version Notification for draft-kuhn-quic-0rtt-bdp-03.txt - implications for COINRG and NWCRG

Marie-Jose Montpetit <marie@mjmontpetit.com> Tue, 09 July 2019 15:17 UTC

Return-Path: <marie@mjmontpetit.com>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C64CF1205FB for <coin@ietfa.amsl.com>; Tue, 9 Jul 2019 08:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level:
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.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 vjIFnyII4tUi for <coin@ietfa.amsl.com>; Tue, 9 Jul 2019 08:17:48 -0700 (PDT)
Received: from mail-io1-xd41.google.com (mail-io1-xd41.google.com [IPv6:2607:f8b0:4864:20::d41]) (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 9E00B120610 for <coin@irtf.org>; Tue, 9 Jul 2019 08:17:48 -0700 (PDT)
Received: by mail-io1-xd41.google.com with SMTP id k8so44041306iot.1 for <coin@irtf.org>; Tue, 09 Jul 2019 08:17:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=GCl2BRc5P5x93ZYTHwgn/tvkOgWYu2AJ7u8VPr0NGVY=; b=Nt75Oi9Fp4/Hu/70eiN2D5koUJOz2Qq4d228+NFP75IoIO3VsNEyEbq5GAD5G13VDX X2bNIgS18+K7sOJRhetIhzShAdMQpBnVQwCVB1b8mos2ZKBpKFiBMlQGjcW+10MKE0Of yrmRYvf+/vJYE+HTTsxEhiQf3lxHmhgqXeQOEsoXcAV4apCMZLCilNh4WE10TAqLmPi5 oGAo7ST28113fC3nCUhG2Y2L/mCm9WuUK68BkAGeBL7wf0tRmMLSE9IebpWyqKVij9LZ 83viueMp+vtxN4KOq3Qihomi6gtkE2gTD/wSCTfl4uO7sTXxN+cdVXg3y2ENjFHWibj7 QKoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=GCl2BRc5P5x93ZYTHwgn/tvkOgWYu2AJ7u8VPr0NGVY=; b=suAoDxcvRF1V64yt21vyCotKn3a3k/84ju4DsrU5Pjd4d7D+hCdRLNHLm04CGSKMlD fVXs7WH1KtyRaqL0z1W+4UeYBa6WxIydyFDPtVjSIwJwfgrxRzpijXpIwewkc1YCOFJR a7GVpqbtwMHdGmnpi1HYi7z4X0l573jHIO1AS/jIvi4zWoCrQ3Yy3+8xHFwBUF/uk5eU jf2SdSvV4MwK0wYd4dLooSZn9t/vjVWUSWn/lG74/5Pj3D/DIUnBIj+l1Tio8XTrARnt tzBEOT2QuQvBGONiEIToP+p7ohvZsokEh7MebwO+emzi8bCp4sqv3FFSTUPCBdXcPM5C ZBYA==
X-Gm-Message-State: APjAAAUtO/SoHCo/ut7ZtUvuquRfD9hXEGRynh8N5IGsVCzC/1tjJNIV 7FJUhzWbjjH/cDuvCWIDmLJrLFzo51/vGFb01vNxom2G
X-Google-Smtp-Source: APXvYqzskDqo7WcKQJmP58fA9d6gBRbfpBV7YeLPor3ZhT5RejWtwQgJeQFAEuqEnk2GYZWk00H14/V7puC5edFjFI0=
X-Received: by 2002:a02:8814:: with SMTP id r20mr29894123jai.115.1562685466313; Tue, 09 Jul 2019 08:17:46 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 9 Jul 2019 08:17:45 -0700
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF1EC1D36C@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <156257274331.734.4411179632617138188.idtracker@ietfa.amsl.com> <F3B0A07CFD358240926B78A680E166FF1EC1C3C1@TW-MBX-P03.cnesnet.ad.cnes.fr> <F3B0A07CFD358240926B78A680E166FF1EC1D36C@TW-MBX-P03.cnesnet.ad.cnes.fr>
MIME-Version: 1.0
Date: Tue, 9 Jul 2019 08:17:45 -0700
Message-ID: <CAPjWiCSYDB0bEzH87kkf4EZHAYw0FVES-yOdRtv-hqgNF3ObSQ@mail.gmail.com>
To: coin@irtf.org, "nwcrg@irtf.org" <nwcrg@irtf.org>
Cc: Kuhn Nicolas <nicolas.kuhn@cnes.fr>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, emile.stephan@orange.com, LOCHIN Emmanuel <emmanuel.lochin@isae-supaero.fr>, Ian Swett <ianswett@google.com>, Lars Eggert <lars@eggert.org>, "Schooler, Eve M" <eve.m.schooler@intel.com>, Hejianfei <jeffrey.he@huawei.com>
Content-Type: multipart/alternative; boundary="0000000000001da11b058d411014"
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/xzMZcYhrC2nVk3W5CLyDUc7q8nI>
X-Mailman-Approved-At: Tue, 09 Jul 2019 08:18:48 -0700
Subject: Re: [Coin] TR: New Version Notification for draft-kuhn-quic-0rtt-bdp-03.txt - implications for COINRG and NWCRG
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2019 15:17:51 -0000

Me the dual hat person again:

Hi the draft below could have interest to both the nwcrg and the coinrg as:
1. nwcrg: there is already work on QUIC and NC that wants to be adaptive
and negotiated; this is very much in line with the protocol part of the work
2. coinrg: as we deal with the impacts of encryption on computing in the
network and the potential use of QUIC proxies negations will also be
important. We have a milestone on how to link coin

I did not send this message to the QUIC mailing list but if you think it’s
useful I can :)

mjm


-----Message d'origine-----
De : QUIC <quic-bounces@ietf.org> De la part de Kuhn Nicolas
Envoyé : lundi 8 juillet 2019 10:05
À : IETF QUIC WG <quic@ietf.org>
Cc : Gorry Fairhurst <gorry@erg.abdn.ac.uk>uk>; emile.stephan@orange.com
Objet : TR: New Version Notification for draft-kuhn-quic-0rtt-bdp-03.txt

Hi,

We have updated our draft on "Transport parameters for 0-RTT connections".
In short, the proposal of the draft is the following:
While each client and server can have its
dedicated solution to store path parameters, having a standard way of
exchanging this information helps in providing symmetrical control of
the optimisation and reducing protocol ossification. [...]

This memo discusses a solution where the client is informed about
path parameters: both the client and the server can contribute to the
reduction of the time-to-service for subsequent connections. This
would improve symmetrical transmission of data and reduce
ossification of the protocol.

Please let us know if you have any views on this proposal.

Cheers,

Nico


-----Message d'origine-----
De : internet-drafts@ietf.org <internet-drafts@ietf.org> Envoyé : lundi 8
juillet 2019 09:59 À : Stephan Emile <emile.stephan@orange.com>om>; Emile
Stephan <emile.stephan@orange.com>om>; Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>fr>;
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Objet : New Version Notification for
draft-kuhn-quic-0rtt-bdp-03.txt


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

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

Abstract:
The time-to-service duration depends on both peers and the peer
initiating the connection may not be the peer actually sending data.
Moreover, clients may be resource-limited, behind a low bandwidth or
a long-RTT network and may need adaptations to improve data
transmission or reception. While each client and server can have its
dedicated solution to store path parameters, having a standard way of
exchanging this information helps in providing symmetrical control of
the optimisation and reducing protocol ossification. QUIC may not be
limited to HTTP3: it can be used as a substrate for proxying and
tunneling.

This memo discusses a solution where the client is informed about
path parameters: both the client and the server can contribute to the
reduction of the time-to-service for subsequent connections. This
would improve symmetrical transmission of data and reduce
ossification of the protocol. To improve the time-to-service of
subsequent 0-RTT reconnection the server currently sets in the
early_data extension the maximum volume of egress data the client is
allowed to send when reconnecting. This memo proposes BDP_metadata,
an additional extension, to also inform the client about path
parameters.




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