IETF Logo Mail Archive

Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432)

Ryan Hamilton <notifications@github.com> Fri, 03 August 2018 19:51 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 4672F1310B4 for <quic-issues@ietfa.amsl.com>; Fri, 3 Aug 2018 12:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 TOFaIJf-G_6z for <quic-issues@ietfa.amsl.com>; Fri, 3 Aug 2018 12:51:23 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C72A130DC8 for <quic-issues@ietf.org>; Fri, 3 Aug 2018 12:51:23 -0700 (PDT)
Date: Fri, 03 Aug 2018 12:51:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533325882; bh=a0b1siVlNpQp2DBhbznY3y6Srwrn247n6JrnXBbT7KA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=17HZl3EPpXYzRbixdA9qXhPrzDO6R9/5smjNxb9ws1YX2cUJygYhOicIFa6+R5Jmk Cs1yztQHPLOEJgg0Ip+vV2pqb40AwgugUVHBt7f+14FRFutRwQOty3O+cOuzv7Bl36 NhZ6eTPG0S+lMljOn1vyusJ7yPJA4CA7c8uoV8+E=
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4d974223021acd91373705da81fe9016af7b99e592cf00000001177c743a92a169ce13b52edd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1432/410358827@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1432@github.com>
References: <quicwg/base-drafts/issues/1432@github.com>
Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b64b23a35277_36543fae638d45b8828c3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
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/EF0wa6Y9XAjjPoDSmbHtblyAOb8>
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: Fri, 03 Aug 2018 19:51:25 -0000

That's a good point. The receive buffer *exists* to re-assemble data in order. The receive buffer is *sized* to allow the pipe to be filled by the sender in the face of packet loss and receiver application jitter. (If a full CWND worth of data is sent, but the first packet is lost, we don't want to have to wait for the retransmission of that data to be received before we can send new data. We also don't want to have to stop sending after a full CWND just because the app got swapped out temporarily, or is waiting for a seek, for example). It does not exist as an alternative to application data storage and any attempt to treat it as such is fraught with peril. 

-- 
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/1432#issuecomment-410358827

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