Return-Path: 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 68CD8120342 for ; Tue, 18 Jun 2019 23:32:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 UP62W_tYSr8S for ; Tue, 18 Jun 2019 23:32:37 -0700 (PDT) Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6848E1201E4 for ; Tue, 18 Jun 2019 23:32:37 -0700 (PDT) Date: Tue, 18 Jun 2019 23:32:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560925955; bh=Ez0IZV2G1K+tNkx3q+U9qlXvxdl7hNhDsmAI3/Xqjes=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HujtwNeIsvWjEy8nhGUSjRkBUY0+Ua2MbVmHgEB8AewVm0B1CuXyl98/W/fWloysY pHaxB2sKRjhyao7fW20OYIucusyhmeBKP8RCURAC7UL5l1WCLdELgHbXJuxHrok/ow rxRqG+LDZjEqVew7PVgi3n7AYs0P7YupWt/mT4gM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Editorial suggestions on the Streams section (#2730) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5d09d703e4857_7d473f82188cd960960ad"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org 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: Wed, 19 Jun 2019 06:32:40 -0000 ----==_mimepart_5d09d703e4857_7d473f82188cd960960ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > @@ -335,8 +337,9 @@ the flow control limits set by its peer. Flow control is described in detail in Stream multiplexing can have a significant effect on application performance if resources allocated to streams are correctly prioritized. -QUIC does not provide frames for exchanging prioritization information. Instead -it relies on receiving priority information from the application that uses QUIC. +QUIC does not provide a mechanism for exchanging prioritization information. +Instead it relies on receiving priority information from the application that +uses QUIC. ```suggestion uses QUIC in an implementation specific manner. ``` -- 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/2730#pullrequestreview-251496654 ----==_mimepart_5d09d703e4857_7d473f82188cd960960ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj commented on this pull request.

=0D =0D
=0D =0D

In draft-ietf-quic-transport.md:

=0D 
> @@ -335,8 +337,9 @@ the flow control limit=
s set by its peer.  Flow control is described in detail in=0D
 Stream multiplexing can have a significant effect on application perform=
ance if=0D
 resources allocated to streams are correctly prioritized.=0D
 =0D
-QUIC does not provide frames for exchanging prioritization information. =
 Instead=0D
-it relies on receiving priority information from the application that us=
es QUIC.=0D
+QUIC does not provide a mechanism for exchanging prioritization informat=
ion.=0D
+Instead it relies on receiving priority information from the application=
 that=0D
+uses QUIC.=0D
=0D =E2=AC=87=EF=B8=8F Suggested change=0D 
-uses QUIC.=0D
+uses QUIC in an implementation specific manner.=0D
=0D =0D =0D

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the th= read.3D""=

=0D = ----==_mimepart_5d09d703e4857_7d473f82188cd960960ad--