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

Igor Lubashev <notifications@github.com> Wed, 06 November 2019 04:10 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 6078B12006F for <quic-issues@ietfa.amsl.com>; Tue, 5 Nov 2019 20:10:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 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_32=0.001, 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 GU8sxvNaoyRU for <quic-issues@ietfa.amsl.com>; Tue, 5 Nov 2019 20:10:48 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0E2F120C0F for <quic-issues@ietf.org>; Tue, 5 Nov 2019 20:10:46 -0800 (PST)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id D19892C323B for <quic-issues@ietf.org>; Tue, 5 Nov 2019 20:10:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573013445; bh=UVBXgp+wgdtBF5GjgX+liv0dDH1ZhfnyuVeiiNN4Qao=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cxrYlZcIj7dfcfkztOaSw7j1Z4HybY41W2Y9MpkaczklrsMMQL7d5XE+XPYjEszYq 9D2jLIF8pYw5NO8k17W2VD6BdG36jMTdk0EeE34pEeYMDUVLESFk6RdcQMGbHaocrD vBWnwrG3QC5kUJhU/S9W2zEtc2rVu/XWxFsuZf1s=
Date: Tue, 05 Nov 2019 20:10:45 -0800
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYWDOP7Y6TXCEF4RGN3Z55ELEVBNHHB5VOOHI@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/550134604@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_5dc247c5c1ba0_49743fc2eb6cd96c35012d"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/mHeBR5ul6Mc_VfTckernJWdUp_Q>
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: Wed, 06 Nov 2019 04:10:49 -0000

@mnot, @larseggert I am sure this is not an easy call, and it is late in the process. While this is not a straightforward "draft has an interop [between QUIC implementations] problem" it is a potential "draft has an interop with Internet ops problem" issue. This could be a stretch of what interoperability 
impact means, or not; please use your best Hat of Wisdom here.

P.S. In the IETF105 timeframe, while the draft I was presenting was, indeed, not targeting QUIC WG specifically, I did ask for the consideration of the topic by QUIC WG: "if the WG is interested, we are happy to have a quick QUIC-specific presentation on this". But you are correct that I could had been much more forceful in the request. In any case, we [got a rejection](https://mailarchive.ietf.org/arch/msg/quic/wsVao34--oHbH6Qtf9V0h8SVCSo) (and, as you said, we later [presented this in other WGs and held a side meeting](https://mailarchive.ietf.org/arch/msg/quic/UMcte0FnHGUSHs7lnVpZ0tGX_Vw)).

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