IETF Logo Mail Archive

Re: [quicwg/base-drafts] are flow control frames really idempotent? (#1612)

Dmitri Tikhonov <notifications@github.com> Tue, 31 July 2018 17:42 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 5ED6E130E5B for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 10:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level:
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 SVG8RF14o8hL for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 10:42:06 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 C8921130DC6 for <quic-issues@ietf.org>; Tue, 31 Jul 2018 10:42:05 -0700 (PDT)
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=zgPfDjuWUWvf3EdcuiIHsqRJZnI=; b=nLLOEe4suCsQih48 N5r0MO2ejJgZHigMkWVasWG09zk86WXyPM8s9+sZIYYdRhqMol4gaD4yIeoR4To7 qNR1WHga8RobS+PHx/xdxrdJRFx0JvC5mAFJYLgzkrkuoapOfJ/m0SMqGwjm3hCw TvCm83pxHb94mZ+YMfI6Qn3ZM9E=
Received: by filter1751p1mdw1.sendgrid.net with SMTP id filter1751p1mdw1-25478-5B609F6B-1B 2018-07-31 17:42:03.696069216 +0000 UTC m=+501982.902252458
Received: from github-lowworker-f6df7df.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0024p1iad2.sendgrid.net (SG) with ESMTP id aZP7dm-FQQmYiAbxiuxr5Q for <quic-issues@ietf.org>; Tue, 31 Jul 2018 17:42:03.566 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-f6df7df.cp1-iad.github.net (Postfix) with ESMTP id 84E313E17CC for <quic-issues@ietf.org>; Tue, 31 Jul 2018 10:42:03 -0700 (PDT)
Date: Tue, 31 Jul 2018 17:42:03 +0000
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd9f3f812f221d5d7e2dbd210604db75f7cfc8f8192cf000000011778616b92a169ce149fd7cc@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1612/409306881@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1612@github.com>
References: <quicwg/base-drafts/issues/1612@github.com>
Subject: Re: [quicwg/base-drafts] are flow control frames really idempotent? (#1612)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b609f6b8328a_7b093fa36dcd45c41454fb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak178FgrjKt3AhuyNFiR9kgF05924jR5bC6T73 ughuReJWIhWRxTSRZ60ggXNShY0fiDGwNbFpl+/V3hh69IZSGeVVIWU6AoAYngtgpp2xqvrj/f4dpB pZm/fSM7NIQgcpUd0ywidKmMdfpY590FkB2Z46s8ZFcA9EIaZtNVBqx99P2uWHNhnC/7B2J6vureGJ s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/K-xpNH1lCzIvX60uL-Attr8qquw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 31 Jul 2018 17:42:09 -0000

@siyengar writes:
> I think a receiver should be allowed to verify that this happens, it is just not required to do so, and we should also allow for implementations that don't verify this check. So if an implementation does send a frame pattern like this, it should be aware that it will not interoperate against some implementations.

In practice, it will mean that all sender implementations will make sure not to send such frame pattern.  When I see that something _MAY result in an error_ (we have some other instances in the other QUIC drafts), it always strikes me as odd:  Surely, if something MAY result in an error, it forces the peer's hand; it is effectively a MUST.

-- 
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/1612#issuecomment-409306881

v2.31.3 | Report a Bug | By Email | System Status