Re: [quicwg/base-drafts] Define terms for application actions (#2857)

Mike Bishop <> Mon, 28 October 2019 20:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6781F120096 for <>; Mon, 28 Oct 2019 13:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XizV8bVSEdoQ for <>; Mon, 28 Oct 2019 13:19:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 080151200F1 for <>; Mon, 28 Oct 2019 13:19:11 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 212D49603C8 for <>; Mon, 28 Oct 2019 13:19:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572293950; bh=zrotNRxa986ZZ6kDMV3ElJDvFwPkM092W42rXmoWmPE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VauxDyTeJ9YPAQbi6W5TpkwHjpL2nZ6ovlnYi9AvqVguI4DJ1aFZvfXxbPmhzFgRk iXSLOVWOQGmfKnCKM/QyWXwXIMuYBMNj7Ol0zba7XKIojNFQndAZYeZRbQl6Es2epQ ukqr6I4fxtOqWsK7e6Vw5nPeSZ5QOrGJLrMKfykg=
Date: Mon, 28 Oct 2019 13:19:10 -0700
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2857/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Define terms for application actions (#2857)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db74d3e10b3b_5bf23fe5da2cd968130317"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 28 Oct 2019 20:19:12 -0000

MikeBishop commented on this pull request.

> +## Required Operations on Streams
+There are certain operations which an application MUST be able to perform when
+interacting with QUIC streams.  This document does not specify an API, but
+any implementation of this version of QUIC MUST expose the ability to perform
+the operations described in this section on a QUIC stream.
+On the sending part of a stream, application protocols need to be able to:
+- write data, understanding when stream flow control credit
+  ({{data-flow-control}}) has successfully been reserved to send the written
+  data
+- end the stream (clean termination), resulting in a STREAM frame
+  ({{frame-stream}}) with the FIN bit set; and
+- reset the stream (abrupt termination), resulting in a RESET_STREAM frame
+  ({{frame-reset-stream}}), even if the stream was already ended.

Rather than having this discussion on a closed PR, let's open a separate issue.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: