[quicwg/base-drafts] 0-RTT flow control lmits can't be increased (#2360)
Martin Thomson <notifications@github.com> Tue, 22 January 2019 21:42 UTC
Return-Path: <noreply@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 42FD7131147 for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 13:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level:
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 zUje6ItsqQH5 for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 13:42:39 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE23313110B for <quic-issues@ietf.org>; Tue, 22 Jan 2019 13:42:39 -0800 (PST)
Date: Tue, 22 Jan 2019 13:42:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548193358; bh=1PtyQ9ePyTQknaMTIs3vFi451OqXTq+mslsbXDfFPjA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=xascJDEh1jEC1VAuQZaFMrd3pu5OwIsd7OArwdcgXNHrUd7h/6cEtBllZjatEUc1Q 3naCTa9s+2lQH8NJwhCeXhHOiRCwld4X3oYke/Hf1w9rWedyb0H68/CQRrJ0f2LlbY bdT5PSwmDSUZaad9mbPdMo+J+BHB/IvbKfTEWrEI=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcdb6e8085d031fce58f77e30dc492861d0375f7092cf00000001185f504e92a169ce17f58684@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2360@github.com>
Subject: [quicwg/base-drafts] 0-RTT flow control lmits can't be increased (#2360)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c478e4ee4ad5_46bb3f85beed45bc4191dd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/s7DvqsmNT4jrE6ssfefAPl6nehI>
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: Tue, 22 Jan 2019 21:42:41 -0000
In #2344, we discuss what can be sent in 0-RTT. We realized that while in theory the client should not be accepting 1-RTT packets from the server and then sending 0-RTT, there is nothing to prevent that. The proposed defense is to prohibit the client from using increased limits (on flow control or streams) that it might have learned from 1-RTT packets. This ensures that 0-RTT - the parts of the connection that might be replayed - are strictly limited to the initial limits. Like many other things, we would require the client not to exceed this limits and merely allow the server to enforce that, in case the server was not inclined to do so. -- 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/issues/2360
- [quicwg/base-drafts] 0-RTT flow control lmits can… Martin Thomson
- Re: [quicwg/base-drafts] 0-RTT flow control limit… Kazuho Oku
- Re: [quicwg/base-drafts] 0-RTT flow control limit… Martin Thomson
- Re: [quicwg/base-drafts] 0-RTT flow control limit… Mark Nottingham
- Re: [quicwg/base-drafts] 0-RTT flow control limit… Mark Nottingham
- Re: [quicwg/base-drafts] 0-RTT flow control limit… Mike Bishop
- Re: [quicwg/base-drafts] 0-RTT flow control limit… Jana Iyengar