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

ianswett <> Tue, 06 August 2019 21:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E1EC2120723 for <>; Tue, 6 Aug 2019 14:36:17 -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 8WTxIit7-XjO for <>; Tue, 6 Aug 2019 14:36:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AAA57120703 for <>; Tue, 6 Aug 2019 14:36:14 -0700 (PDT)
Date: Tue, 06 Aug 2019 14:36:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1565127373; bh=KR98XKFDGpOTq1XUO9LSbRIz4+0AUBqYUYCvUBaAsvw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xFiXQBdzeP/EsAAoKoYW96+IXUWYNP1s1/Ttd8Kf82PYq7RaRqq3qs3SO6ogU+KFu VbVqpVHWmtQJJmh+4lusgi6lm1O4bHQKF+2KKEBa7ThknIEPgBFtOcrfY/d4N9tyHm nR8sjzkRGVFz6wHogyKKWtN+5F2I1nyUwIfWIy2w=
From: ianswett <>
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_5d49f2cd8bd65_297c3fac070cd9681182f7"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Tue, 06 Aug 2019 21:36:28 -0000

ianswett commented on this pull request.

> @@ -1101,6 +1132,41 @@ suggested structure:
+## Required Operations on Connections
+There are certain operations which an application MUST be able to perform when
+interacting with the QUIC transport.  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 connection.
+When implementing the client role, applications need to be able to:
+- open a connection, which begins the exchange described in {{handshake}};
+- enable 0-RTT; and
+- be informed when 0-RTT has been accepted or rejected by a server.

Good point.  I still think the client needs to know when 1-RTT data can be sent, because it may want to send some data in 0-RTT but not other data.

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