[quicwg/base-drafts] Stream Send State Machine is Confusing (#2357)
martinduke <notifications@github.com> Tue, 22 January 2019 16:55 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 C7EA8130F3C for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 08:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.935
X-Spam-Level:
X-Spam-Status: No, score=-5.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 liyll12tLZ4e for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 08:55:22 -0800 (PST)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 D3849126CC7 for <quic-issues@ietf.org>; Tue, 22 Jan 2019 08:55:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=GazBekuxScuvrnHxtEW6TmRMfbs=; b=kWLCLNUL+rDRNxsD 5/VA0JeETOmlywnFnVNgjdznXAiEJ00nZocW6niTQhhcaeA78gtWvDY1WG5BfbC6 cDB4FkQXGfeAuZkQc6o18oXcPdYcZAfMNRAFFIGupwm3fhlDODNrbO6vKlWVb83o djxT8qQfIQJH5reuFy+tlmAMnH8=
Received: by filter1403p1mdw1.sendgrid.net with SMTP id filter1403p1mdw1-25342-5C474AF8-14 2019-01-22 16:55:20.572220191 +0000 UTC m=+654780.673111475
Received: from github-lowworker-dcc078e.cp1-iad.github.net (unknown [192.30.252.44]) by ismtpd0024p1iad2.sendgrid.net (SG) with ESMTP id RNt_tVgNR2qVUn5Boae6fw for <quic-issues@ietf.org>; Tue, 22 Jan 2019 16:55:20.777 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-dcc078e.cp1-iad.github.net (Postfix) with ESMTP id 8DCE32C06B1 for <quic-issues@ietf.org>; Tue, 22 Jan 2019 08:55:20 -0800 (PST)
Date: Tue, 22 Jan 2019 16:55:20 +0000
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd64f98f02471831a46f7952d54a86e61fd3c93eb92cf00000001185f0cf892a169ce17f3e339@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2357@github.com>
Subject: [quicwg/base-drafts] Stream Send State Machine is Confusing (#2357)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c474af88b1d8_11203fe76fcd45c4129864"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3A4dxt++6ME36PbGfRwAESLRcEvcIla9g24+ 8UPV02vBWEt7qeoTUvJrcO22ADzSf+lDW/vgwU8Lym2MjgIcGKoA0w3mtabxhSw9J5ylRCMRkcnh4C RUb4/kT7RU5N1NaQ5Coi3PAnu0hxBuB0OBkdjTHiXf4lmIL2fFCg8C1A/uz6ZIsY/v44lrcXiQ5DSR w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/kBYGdIUuIVzbTqXmy6WvYIgqCPg>
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: Tue, 22 Jan 2019 16:55:25 -0000
The send state machine diagram says that if the "Peer Creates Bidirectional Stream" it should transition to READY and then to SEND. The text says ""a bidrectional stream initiated by a peer... enters the 'Ready' state then immediately transitions to the 'Send' state if the receiving part enters the 'Recv' state." This seems unnecessarily indirect and opaque. I suggest that instead we say that if a host receives STREAM, STREAM_DATA_BLOCKED, RESET_STREAM, MAX_STREAM_DATA, or STOP_SENDING on an unopened, peer-initiated bidirectional stream, it transitions directly to the "Send" state. If people agree, I'll file a PR. -- 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/2357
- [quicwg/base-drafts] Stream Send State Machine is… martinduke
- Re: [quicwg/base-drafts] Stream Send State Machin… martinduke
- Re: [quicwg/base-drafts] Stream Send State Machin… Martin Thomson
- Re: [quicwg/base-drafts] Stream Send State Machin… martinduke
- Re: [quicwg/base-drafts] Stream Send State Machin… martinduke
- Re: [quicwg/base-drafts] Stream Send State Machin… martinduke