IETF Logo Mail Archive

Re: [quicwg/base-drafts] why require in order delivery? (#252)

mirjak <notifications@github.com> Tue, 14 March 2017 08:11 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 23AE41293F2 for <quic-issues@ietfa.amsl.com>; Tue, 14 Mar 2017 01:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.597
X-Spam-Level:
X-Spam-Status: No, score=-5.597 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_HI=-5, RCVD_IN_MSPIKE_H2=-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 xhDvqy1b1has for <quic-issues@ietfa.amsl.com>; Tue, 14 Mar 2017 01:11:28 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9879B120725 for <quic-issues@ietf.org>; Tue, 14 Mar 2017 01:11:28 -0700 (PDT)
Date: Tue, 14 Mar 2017 01:11:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489479088; bh=gNXlpwVg6FpIUFNNTtVZmrduuizLfE4404cENrDARqI=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EDmRK43+RC+FwL50XzBkhtvPIjndXTlWvuQa4UcbTkUT40uYvTN7TtocCW80+VwFi NV/4vOschKH+sfSK/4+Morn6bbRZ5sGmDpBlK6g/Sh7lvsKSWVWzoLeuxuEt6E4gvs bzrFLok/ujYteBpCObgb7U8BoQCyHYBtAQsCVdaI=
From: mirjak <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/252/286350008@github.com>
In-Reply-To: <quicwg/base-drafts/issues/252@github.com>
References: <quicwg/base-drafts/issues/252@github.com>
Subject: Re: [quicwg/base-drafts] why require in order delivery? (#252)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58c7a5aff2385_274b3fe9c2869c3c95697"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/7OWmaUbk1m4VmYf4l1zAOyaSit4>
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, 14 Mar 2017 08:11:30 -0000

This sounds like you want streams with partial reliability which is in the charter for later.

Regarding the low latency case: I guess you could open a second connection and use a lower-than-best-effort congestion control for that one. However, I think we should not do this within one connection. My understanding really is that a quic connection is one flow for the network and therefore all packets of a quic flow should operate under the same congestion control domain.

-- 
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/252#issuecomment-286350008

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