IETF Logo Mail Archive

Re: [quicwg/base-drafts] No normative language for connection/stream operations (#3935)

ianswett <notifications@github.com> Wed, 22 July 2020 00:20 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 8BA123A0889 for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 17:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 kQptL6WIECLl for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 17:20:46 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 352613A0888 for <quic-issues@ietf.org>; Tue, 21 Jul 2020 17:20:46 -0700 (PDT)
Received: from github-lowworker-45eca55.ac4-iad.github.net (github-lowworker-45eca55.ac4-iad.github.net [10.52.25.70]) by smtp.github.com (Postfix) with ESMTP id 404AB6A1213 for <quic-issues@ietf.org>; Tue, 21 Jul 2020 17:20:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595377245; bh=HOyhFet9xcx2D0eM/ySzgBl2nwV/iaBHZvcyCAlsXrs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xOuBLOg+2UfP5NEWbe/CA48AiVDCRiXHznyjNSfY7UKYnK8GkIfDp+N+HLN1K8voz WL5BkcHnd45h59uVveImMe1Lclhvz+o/PT8wQIQLkZ5ZGnFYrMEDR3572L1CMGJ8BR YUkBozReeOJYpo6qXbumUBwf/6VafnlZH/97KkvY=
Date: Tue, 21 Jul 2020 17:20:45 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK37JUEV2A2LNAQ4RNF5ENTV3EVBNHHCPCSANM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3935/review/452913735@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3935@github.com>
References: <quicwg/base-drafts/pull/3935@github.com>
Subject: Re: [quicwg/base-drafts] No normative language for connection/stream operations (#3935)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f17865d31414_11e63f9a854cd95c76199"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/87qnvrIXJSgVx3614Oj_7JCO88g>
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: Wed, 22 Jul 2020 00:20:49 -0000

@ianswett approved this pull request.



>  
-There are certain operations that 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.
+This document does not define an API for QUIC, but instead defines a set of
+functions on streams that application protocols can rely upon.  An application
+protocol can assume that an implementation of QUIC provides an interface that

```suggestion
protocol can assume that a complete implementation of QUIC provides an interface that
```

-- 
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/pull/3935#pullrequestreview-452913735

v2.23.0 | Report a Bug | By Email