IETF Logo Mail Archive

[quicwg/base-drafts] Why ignore MAX_STREAM_DATA or MAX_DATA that don't increase the flow control limits (#2082)

ekr <notifications@github.com> Sat, 01 December 2018 02:04 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 6B9971293FB for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 IeNNrOCBMESv for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:04:52 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA6FF129C6A for <quic-issues@ietf.org>; Fri, 30 Nov 2018 18:04:51 -0800 (PST)
Date: Fri, 30 Nov 2018 18:04:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543629891; bh=qISr7JV5q6QWD97IWGLMPSLguLIqpLvZiNDwSq1ucY8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=UQc2of8BmQUlENFhiVBCaOpN+6fWQorXsFqw6QeB5hBLK5tTA0jgLheuKuuxzOasz 3p3i7pvcN76oBCwMB7JyUQC/ozuJRhJltJ4xGoRYe9VhmfYpPCAwAQ0wejwl8ijFsI Zn8sXgn/+awp98D5+QGdRUS21prP2dUKfuzMwhPc=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe85b4443d8caaba6545c22536b21009409dacc1092cf000000011819ae4392a169ce17082871@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2082@github.com>
Subject: [quicwg/base-drafts] Why ignore MAX_STREAM_DATA or MAX_DATA that don't increase the flow control limits (#2082)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c01ec432d3e0_76583f8004ed45b84396b3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/8jlfsJyV8IGqZg9Zpb_2emSNSmQ>
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: Sat, 01 Dec 2018 02:04:53 -0000

S 4.1. says:

```
A receiver can advertise a larger offset by sending MAX_STREAM_DATA or MAX_DATA
frames at any time during the connection.  A receiver cannot renege on an
advertisement however.  That is, once a receiver advertises an offset,
advertising a smaller offset has no effect.  A sender MUST therefore ignore any
MAX_STREAM_DATA or MAX_DATA frames that do not increase flow control limits.
```

It seems like it would be more helpful if implementations were to remember the PN of the last advertisement and generate an error in this case. I get that this would be more work, but why is this prohibited?

-- 
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/2082

v2.23.0 | Report a Bug | By Email