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

Nicolas Kuhn <> Mon, 04 November 2019 20:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 870AC120998 for <>; Mon, 4 Nov 2019 12:22:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nh5JoseOJo_n for <>; Mon, 4 Nov 2019 12:22:29 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 95B07120A3E for <>; Mon, 4 Nov 2019 12:22:29 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id AC274C60596 for <>; Mon, 4 Nov 2019 12:22:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572898948; bh=icaH9DUauzRorUEvH4n5FYAPSiriQkMIKkzDeiMgBTU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T4uZevadmLzR6MRcOZUAfibqqkztHon87DsWveZj+0ZFAAu7wIN0deelFAjRxaAs7 pZC2BYaOmh/0FIw6G4r/uw1E21mSUre9oIaik0mNSvxY6jah6QIstEUmItokQJmsV4 2o+twk561tsFLbo/fov2ApZZ+qe/QRXdLVot8Cqg=
Date: Mon, 04 Nov 2019 12:22:28 -0800
From: Nicolas Kuhn <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3189/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] QUIC lacks on-path exposure of packet loss (#3189)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc088849c96d_ce43fc210ccd96014563f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: NicoKos
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Nov 2019 20:22:36 -0000

We have experimented the proposed solution. It helped us identify losses occuring before a satellite gateway. Operating a network involves dealing with different equipment providers proposing specific management API and with 'old' equipment with specific management API. This solution is a real helper when it comes to identify the faulty segment in a network composed of various equipment. 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: