IETF Logo Mail Archive

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

MikkelFJ <notifications@github.com> Tue, 31 July 2018 16:33 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 85E4E130DEB for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 09:33:56 -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 fLTETjdI4fG6 for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 09:33:54 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 8206E127B92 for <quic-issues@ietf.org>; Tue, 31 Jul 2018 09:33:54 -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=9t5rN3pqap4p2MA3v32gTZctmsI=; b=cfK2riTRGOLz0AVl ag86j743ooNUmJiLlgUJrKWRZbyBoddKoAC0or3lOFWHc35MZb/I3FxKSP1E0C2k bLtXnrNIqXGs8qx/5O6IZJEQBZfsMvpNy6boKts4uGNLxTN5dh39u8UU26nmg1i1 7A/pb0KstlE2vmTVAxz0IE0T7GE=
Received: by filter1101p1las1.sendgrid.net with SMTP id filter1101p1las1-18230-5B608F70-2E 2018-07-31 16:33:53.039919031 +0000 UTC m=+497029.177563519
Received: from github-lowworker-5909e27.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0009p1iad2.sendgrid.net (SG) with ESMTP id myrEH4yyR8aZ7I-wWBQ_eA for <quic-issues@ietf.org>; Tue, 31 Jul 2018 16:33:52.981 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-5909e27.cp1-iad.github.net (Postfix) with ESMTP id E23AB3E094E for <quic-issues@ietf.org>; Tue, 31 Jul 2018 09:33:52 -0700 (PDT)
Date: Tue, 31 Jul 2018 16:33:53 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8075219ddec00024b258c83a29b9263935ba2f0b92cf000000011778517092a169ce149fd7cc@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/409284998@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_5b608f70e03c0_16dd3fcb49ed45b43043af"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3NF0SlIQU18kY14QpRDaxwYYnD0I0LrL+WYa m+42thfZQTdltDkOtEPoC8hPNwjbLNLXPuviFgEoulBX4MKLr0DMOE4384d9JbQNRK7195Vqz4WpFK 7M/zzacQgLwGh84S3OHMYK4BZKdy559I26z1Y5MTz2HdS13yO7rtFzvrkgy9zQp2Vn2vbHTQOfqBMf 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/osptwKL_SKFmW1f--o_EYOHwxrQ>
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 16:33:57 -0000

@siyengar 

> @mikkelfj what do you mean by the ordering not coming from packet number?

I mean that the general principle of QUIC is for packets to vessels of frames that do not carry any semantic such as ordering, except for the connection context itself. I am not saying there is other ordering for MAX_DATA, only that when there is ordering, it should not, and generally does not, derive from packet numbers. For example, streams are ordered by stream offsets, and streams are ordered by stream ID's. Implying a problem because of ordering related to packet numbers is fundamentally against this design.

-- 
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-409284998

v2.23.0 | Report a Bug | By Email