IETF Logo Mail Archive

Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)

Mike Bishop <notifications@github.com> Wed, 13 February 2019 22:23 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 443F212F295 for <quic-issues@ietfa.amsl.com>; Wed, 13 Feb 2019 14:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 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, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 k5DJsrGmFTpT for <quic-issues@ietfa.amsl.com>; Wed, 13 Feb 2019 14:23:23 -0800 (PST)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 48823128CF2 for <quic-issues@ietf.org>; Wed, 13 Feb 2019 14:23:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=DFzU/N8WS59I76eDl3sMqa1z/oI=; b=UEw96XYVvecCbl0m rAmZ40qbXA4UcjYEyVtodFPRtM92SD61J0bgDOplFipJrokYKRI1g5hhFvTeqhhJ YxWx/ZS67NUU/1s+SQ4JhLLgpdYvlprncMcIdAtXrgLCgNaBVVLJfuMdVZmcSP0t 6e+q8WBq4rfWbVL/Ug7rdWLnU/E=
Received: by filter0409p1iad2.sendgrid.net with SMTP id filter0409p1iad2-7216-5C6498DA-C 2019-02-13 22:23:22.180599136 +0000 UTC m=+698408.037817487
Received: from github-lowworker-e55e3e3.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id qBKI0qRNQMe-0C7Mlni1Qg for <quic-issues@ietf.org>; Wed, 13 Feb 2019 22:23:22.074 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e55e3e3.cp1-iad.github.net (Postfix) with ESMTP id 0D2AA1805C1 for <quic-issues@ietf.org>; Wed, 13 Feb 2019 14:23:22 -0800 (PST)
Date: Wed, 13 Feb 2019 22:23:22 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab91ab89e7d402692e28cc049cfc966df4ba110d5192cf00000001187c5ada92a169ce1869fe88@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2461/c463399914@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2461@github.com>
References: <quicwg/base-drafts/pull/2461@github.com>
Subject: Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c6498dab9ae_75f23fa514cd45bc229039"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0nLAcpLRt/88BzRG6Xtnxp71bveZX4xMnp0T hithLzBTTcgLceuu7MQwCQRaAll6L4fNc6mtM7ct5cOcdmJAA0DHYpCtwSavvI6jJNImXY2TXFRuIx cXmo9R1wuw8Ng9nhwOxU2hveNqi2HjBla67zCULeGsKk+U+1XFPPdPAm/JDB+MD1mV/Zk7gMWh3Bit c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ejOXf-pKpxxdGqMxtUFWuQaRWd0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2019 22:23:25 -0000

> * enforce limits based on TP to streams-related frames sent using 0-RTT packets

Actually, enforce limits based on the TP *from last time* which are embedded in the session ticket.  But yes -- the "correct" way of doing this is saying that there is a parallel set of flow control limits which never increase from the initial value, but which only apply during 0-RTT.  If the client always switches to 1-RTT ASAP, this will be the same as regular flow control provided that the client doesn't consume any higher initial flow control values in the transport parameters until the handshake completes.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2461#issuecomment-463399914

v2.23.0 | Report a Bug | By Email