IETF Logo Mail Archive

Re: [quicwg/base-drafts] Stream Flow Control on Stream 0 (#1252)

Praveen Balasubramanian <notifications@github.com> Sun, 01 April 2018 01:24 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 1AAC0127137 for <quic-issues@ietfa.amsl.com>; Sat, 31 Mar 2018 18:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.606
X-Spam-Level:
X-Spam-Status: No, score=-0.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 VVH5-KuEtL_v for <quic-issues@ietfa.amsl.com>; Sat, 31 Mar 2018 18:24:50 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 920261200FC for <quic-issues@ietf.org>; Sat, 31 Mar 2018 18:24:50 -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=p0v3aPWCxu5CGZpvIXWEhKQb3NE=; b=eIt3HMjoJwEX2P1q KduGwxF/5dK/PX83l5tdrOw9nPRENc0yU1E0mjUn9NKmyU81btR1dFhHjf26S/hd XIwFTItItgzDAqMBwvyT9S58zTqVEgILl0vunlIibTUW7joBo9G6m/qVFCN9x1sw tWbyPlgcnH7I4mJFKSM0QlraO3w=
Received: by filter0648p1mdw1.sendgrid.net with SMTP id filter0648p1mdw1-6593-5AC034E1-E 2018-04-01 01:24:49.583597391 +0000 UTC
Received: from smtp.github.com (out-2.smtp.github.com [192.30.252.193]) by ismtpd0023p1iad2.sendgrid.net (SG) with ESMTP id 4z2k9keGTvixzuop-qkUuw for <quic-issues@ietf.org>; Sun, 01 Apr 2018 01:24:49.578 +0000 (UTC)
Date: Sun, 01 Apr 2018 01:24:49 +0000
From: Praveen Balasubramanian <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab65d576bef7c1ac76e0e99c97312525b01839ccab92cf0000000116d7f6e192a169ce126ccd37@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1252/377735611@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1252@github.com>
References: <quicwg/base-drafts/issues/1252@github.com>
Subject: Re: [quicwg/base-drafts] Stream Flow Control on Stream 0 (#1252)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ac034e171103_48723f825fe4ef2896155"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pravb
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0B2gvsbtcHnIe5j0cTSE5bYuJg1r2rySJi3a U3P/Wkj1h6BIWE0UR10iGyCYZOh/00XOEXCc1402KIJZwGPL9CJpD6lBgE+SKHPc7+AS/nqEobh+kt BQD5Cubq6ZN30m0byfKhVgQaPContg/JM13XgTedlpSAnpdbRLDZPtnA5u+sHbB9igtiPyBTkYkHrR Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/wz6WrCnO8cNVR7799xdvxpbuFhs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 01 Apr 2018 01:24:52 -0000

If there are reasonable limits that are not communicated or negotiated, should there be an error code to reset the connection if that limit is exceeded? 

I see that the recovery draft talks about a dedicated alarm and retransmissions for handshake data but doesn't explicitly say anything about congestion control for stream 0. Do we need a separate issue for whether congestion control should be applied to stream 0?

-- 
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/1252#issuecomment-377735611

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