Return-Path: 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 313411200F6 for ; Wed, 5 Feb 2020 07:07:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.682 X-Spam-Level: X-Spam-Status: No, score=-3.682 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 r57ehNgW9K5n for ; Wed, 5 Feb 2020 07:07:31 -0800 (PST) Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C45901200C7 for ; Wed, 5 Feb 2020 07:07:31 -0800 (PST) Date: Wed, 05 Feb 2020 07:07:30 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1580915251; bh=isLdPCbffkA/diYNXTKbhUJ93vGNef+bLES97D9Weyc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zpteBqPTC+X51vmnUaf0XTygDGwIZZZjUoYAduJAqJErKUCH0RtdaKdE8cUJModFm DuI3Kwwa7EOONINB62ffXB1MJ7f8u9h1dmw+D8g+fNScfRMZtsU3BAiMKhv8xspQiB LHwjEMAvWVbXrpea6Os47CFzhGG7ErSI7NvBxHKw= From: Marten Seemann Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Remember active_connection_id_limit for 0-RTT (#3425) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e3ada32e9a2f_67f93f97262cd95c768b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: marten-seemann X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2020 15:07:33 -0000 ----==_mimepart_5e3ada32e9a2f_67f93f97262cd95c768b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This is a bigger design change than it might look like from the diff.=0D =0D Our design principle was to only remember things for 0-RTT that are actua= lly needed to make 0-RTT work. This means that we need the flow control l= imits as well as the stream number limits, because obviously the client n= eeds to be able to send application data in 0-RTT. =0D This saves state on the client side (because the client only needs to rem= ember those 6 parameters) as well as in the session ticket (because that=E2= =80=99s how the server stores that state). A reasonable implementation st= rategy on the server is to reject 0-RTT if those parameters changed / wer= e reduced, so keeping the number of things to remember small increases th= e probability that 0-RTT is not rejected. =0D =0D -- =0D You are receiving this because you are subscribed to this thread.=0D Reply to this email directly or view it on GitHub:=0D https://github.com/quicwg/base-drafts/pull/3425#issuecomment-582451625= ----==_mimepart_5e3ada32e9a2f_67f93f97262cd95c768b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This is a bigger design change than it might look like from the diff.<= /p>=0D

Our design principle was to only remember things for 0-RTT that are ac= tually needed to make 0-RTT work. This means that we need the flow contro= l limits as well as the stream number limits, because obviously the clien= t needs to be able to send application data in 0-RTT.
=0D This saves state on the client side (because the client only needs to rem= ember those 6 parameters) as well as in the session ticket (because that=E2= =80=99s how the server stores that state). A reasonable implementation st= rategy on the server is to reject 0-RTT if those parameters changed / wer= e reduced, so keeping the number of things to remember small increases th= e probability that 0-RTT is not rejected.

=0D =0D

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on = GitHub, or unsubscribe.3D""

=0D = ----==_mimepart_5e3ada32e9a2f_67f93f97262cd95c768b9--