IETF Logo Mail Archive

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

Patrick McManus <notifications@github.com> Wed, 04 January 2017 18:27 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 934311296BF for <quic-issues@ietfa.amsl.com>; Wed, 4 Jan 2017 10:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level:
X-Spam-Status: No, score=-7.419 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, 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 nv6TFv0s94g3 for <quic-issues@ietfa.amsl.com>; Wed, 4 Jan 2017 10:27:58 -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 18A9B126D74 for <quic-issues@ietf.org>; Wed, 4 Jan 2017 10:27:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=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=z0sIz54u+gZnuFqk76oQNbAauP4=; b=p1FCQfkovqG7dIiH +4iLKM9bdWou+7pOQiyerptU6heBfE2g/SL5eOTmaioWtfwz2UmDksu26EhBmIne Vz2rPB9itUTDqF6W4rYruUEWs9gGlXIoL8OC04/0qBNOqxlNfHQaHOhu1vB5oGOB N9YjjQSDBINWZKaoXRHVdumE8dY=
Received: by filter0627p1mdw1.sendgrid.net with SMTP id filter0627p1mdw1-24159-586D3EAC-35 2017-01-04 18:27:56.938463949 +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 bMlb-pqkT82F4HYNbmWGNQ for <quic-issues@ietf.org>; Wed, 04 Jan 2017 18:27:56.924 +0000 (UTC)
Date: Wed, 04 Jan 2017 10:27:56 -0800
From: Patrick McManus <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/104/270446893@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_586d3eacd0817_7c43fd118a65134179754"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mcmanus
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0ZMEH0dAhhvux8GkT58P2GvvY3/MjTilYF7C pWpsOM+Z3PAV2cRs4vkho0wgNb5Kd1uXlY3sUZnD57YoYfWKl7AsoIhLT9xMHej769t2048RnWK1Qp 4A8KZMLZ/mhlu0u6qs2yPB/UsWrJwPa3MVDSU1MMKEV1jKltP7CUBy28b36wrn87ucsTnReSsdEhh0 g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/do81L2B2wxv--Sa15d7plSFrMfQ>
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: Wed, 04 Jan 2017 18:27:59 -0000

in general moving information down the pipeline as fast as you can without creating a HoL-Blocking problem is a good strategy. The blocking problem is the reason an H2 impl has to hold back data from TCP, and it would seem to correlate somewhat to a congestion controller's desire to not create buffering in the network (via crystal ball).

I think that argues for moving prio to the quic transport layer. mux without pri is indeed lame.. and quic wisely retransmits frames instead of packets, so prio can play a role there if prio is part of the frame otherwise this is all opaque to quic during retransmit.

-- 
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-270446893

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