Re: [quicwg/base-drafts] Recommend algorithm for packet scheduler, rather than implementation (#3122)

MikkelFJ <notifications@github.com> Sat, 22 February 2020 11:38 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 05976120074 for <quic-issues@ietfa.amsl.com>; Sat, 22 Feb 2020 03:38:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, 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: 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 6uHJvoT9tDwX for <quic-issues@ietfa.amsl.com>; Sat, 22 Feb 2020 03:38:45 -0800 (PST)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75AB9120052 for <quic-issues@ietf.org>; Sat, 22 Feb 2020 03:38:45 -0800 (PST)
Received: from github-lowworker-c53a806.ac4-iad.github.net (github-lowworker-c53a806.ac4-iad.github.net [10.52.23.45]) by smtp.github.com (Postfix) with ESMTP id CBF4F26158E for <quic-issues@ietf.org>; Sat, 22 Feb 2020 03:38:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582371524; bh=KOtwbxecWWusMzV9dC3SvMoeUBOUYKwk2x8BrUWQbGo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WFo6a8Wtw7yFejYybYaKdRoSbj0FQnJN5Ra7nZIaZhZL2Aj29wwc2ok3Dqr0UDNtR lIsGZOMS4aAvymA9ejzMAdDfNicsbx96f9QOcF2xSmLR1CuaQIYa7QBrtfpzwxKh3u Ko0asD57P1kPJsQeAA3lbJ2syj5EJLBuD6QmpPJs=
Date: Sat, 22 Feb 2020 03:38:44 -0800
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5ABY4IZDXGRYPGZI54LZCUJEVBNHHB4VEL2Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3122/589947874@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3122@github.com>
References: <quicwg/base-drafts/issues/3122@github.com>
Subject: Re: [quicwg/base-drafts] Recommend algorithm for packet scheduler, rather than implementation (#3122)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e5112c4866a7_4f6f3fa660ecd95c208563"; 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: <https://mailarchive.ietf.org/arch/msg/quic-issues/4LDMGuYAUIwrgs_dZPv-9l3dorY>
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: Sat, 22 Feb 2020 11:38:47 -0000

@martinthomson I think it is good to have a clear definition of what pacing means when QUIC has that as a requirement for one operational mode. I'm not sure it is really helpful by itself in guiding the user towards queueing disciplines such as deficit round robin. I'd prefer at least a mention of such an algorithm as one way to achieve the desired behaviour rather then referring to qdisc. Such a name can searched and Wikipedia will answer.

-- 
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/3122#issuecomment-589947874