IETF Logo Mail Archive

Re: [quicwg/base-drafts] Priority in QUIC Transport (#104)

Victor Vasiliev <notifications@github.com> Tue, 24 January 2017 02:48 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 B21AB129561 for <quic-issues@ietfa.amsl.com>; Mon, 23 Jan 2017 18:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.251
X-Spam-Level:
X-Spam-Status: No, score=-7.251 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-1.156, RP_MATCHES_RCVD=-3.199, 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 gPAM1Nb7p8CF for <quic-issues@ietfa.amsl.com>; Mon, 23 Jan 2017 18:48:07 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 7ABFC129548 for <quic-issues@ietf.org>; Mon, 23 Jan 2017 18:48:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=axUHjHZjGzkgdEUdrg8k+RVqJZY=; b=GoFonTm66EM1f7LX I1zqRoS3uwZwFIB0TrXmeN8zc8VjgFo0xiSvJTCqrO4dC3HmcgKuKKH0292zOQAo TCDoIdXTWrVOh/TGPRviyW0t9OBsUmxIl1/UGzToHMQ6gXfH+13nxcBxirGHyLyb FF1zvwbaen3QEHX04jRCR0o6iRo=
Received: by filter0950p1mdw1.sendgrid.net with SMTP id filter0950p1mdw1-14038-5886C066-43 2017-01-24 02:48:06.715688423 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 0EK3L_lqSv2NNujWA3Lcrw for <quic-issues@ietf.org>; Tue, 24 Jan 2017 02:48:06.620 +0000 (UTC)
Date: Mon, 23 Jan 2017 18:48:06 -0800
From: Victor Vasiliev <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/104/274686151@github.com>
In-Reply-To: <quicwg/base-drafts/issues/104@github.com>
References: <quicwg/base-drafts/issues/104@github.com>
Subject: Re: [quicwg/base-drafts] Priority in QUIC Transport (#104)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5886c0667ceea_60493ff7a384f14012686b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: vasilvv
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2bcnDfKGBk1qKW2ppo8CUTbizjWH7Wz00t6q IWi5gijnhKzTDeCnU7o3/fTbh2G5sNXlpHR17GtX4PJ0kKvxtWUt136auWHwlSZjVvsBsYfo60rLML Q4ZAiWWDB5irQGUgWx57bVeAVFpRJg5IBmbXGKSp9ARzQEu/eNUD9oI3FC+kBiGkAbqNtqI02C1OHk g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/_QRIp4_x0PQpuAu_09YxwZlrk80>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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, 24 Jan 2017 02:48:08 -0000

I would like to note here that stream scheduling is just like congestion control -- your QUIC implementation *will* have logic to schedule streams, it's just it might be trivial logic.

Unlike congestion control, there are two issues here (from the discussion at the interim): (1) prioritization heavily depends on the interface between the application and transport, and (2) we might not have enough prior experience to draw on in order to provide guidance to the implementations at this point.

-- 
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/104#issuecomment-274686151

v2.39.1 | Report a Bug | By Email | System Status