Re: [quicwg/base-drafts] QUIC lacks on-path exposure of packet loss (#3189)

MikkelFJ <notifications@github.com> Tue, 05 November 2019 08:25 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 DF00F1200F9 for <quic-issues@ietfa.amsl.com>; Tue, 5 Nov 2019 00:25:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 895P9ji2854m for <quic-issues@ietfa.amsl.com>; Tue, 5 Nov 2019 00:25:15 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F6D6120103 for <quic-issues@ietf.org>; Tue, 5 Nov 2019 00:25:15 -0800 (PST)
Received: from github-lowworker-45eca55.ac4-iad.github.net (github-lowworker-45eca55.ac4-iad.github.net [10.52.25.70]) by smtp.github.com (Postfix) with ESMTP id 92B6E660551 for <quic-issues@ietf.org>; Tue, 5 Nov 2019 00:25:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572942314; bh=anurkbhdRvcVEz2a4fFPGLjVN0ZvCZs4X/oB503YUpk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ll5NOFaNmYSwVUICgp54dRXTH9ACZJNX96vwFkt0HOwfKPaZ4g1yNLJF7CwynDhRp E2Ki0TLAZ+JG6j8sLp8dzsnX9jqS1gCXGYjsl/lzFjfA9mmvwePP0nwyyS45NhsT8t MGPVMgX3fehNevXn9vepCqQg7NZByhoGE+qoYxx4=
Date: Tue, 05 Nov 2019 00:25:14 -0800
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK23HP44LVOLYICKSNN3ZZSGVEVBNHHB5VOOHI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3189/549714684@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3189@github.com>
References: <quicwg/base-drafts/issues/3189@github.com>
Subject: Re: [quicwg/base-drafts] QUIC lacks on-path exposure of packet loss (#3189)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc131ea84c30_32d43fa8d56cd96041211d"; 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/FioCC2y6WR1dJUamWko_kTQLmNg>
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: Tue, 05 Nov 2019 08:25:19 -0000

If it works, if it is tested, and if it is easy to implement, there are great benefits to having it in version 1 because then equipment can monitor all QUIC traffic without exceptions.

But if there is the slightest doubt that the design is absolutely right it definitely would be premature to introduce this now.

-- 
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/3189#issuecomment-549714684