IETF Logo Mail Archive

Re: [quicwg/base-drafts] Should QUIC provides PING interface for upper layer? (#3567)

stormlin <notifications@github.com> Thu, 09 April 2020 15:53 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 A63EB3A0ADA for <quic-issues@ietfa.amsl.com>; Thu, 9 Apr 2020 08:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.721
X-Spam-Level:
X-Spam-Status: No, score=-1.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 S0hkHa1JWv4o for <quic-issues@ietfa.amsl.com>; Thu, 9 Apr 2020 08:53:02 -0700 (PDT)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B7783A0AD8 for <quic-issues@ietf.org>; Thu, 9 Apr 2020 08:53:02 -0700 (PDT)
Date: Thu, 09 Apr 2020 08:53:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1586447581; bh=JqBi1+CxWxK3O8hiYSz14ucfvNP38+uBHkMe2/PPflE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WSq/qQRHn1r9vPRl4oyHH+OABIH8TzhxsCy+/ZlOZg6p91xRGADaZv/0hNsUOr4Ab z267B7+yl+q04+pJ2I5qkQEOg8eZuW5SDbfVllQAnNaCLgy2NIPY1ivHJRKEtS/b9l ukeZx3HASxCwSXUfwwdESjHVdXvaDK+Z386oRjRo=
From: stormlin <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7GHB7OM2XCGTGRD554TMS53EVBNHHCHCTWCE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3567/611603998@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3567@github.com>
References: <quicwg/base-drafts/issues/3567@github.com>
Subject: Re: [quicwg/base-drafts] Should QUIC provides PING interface for upper layer? (#3567)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e8f44dd7fce4_3ac03fa35d2cd964105290"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: K9A2
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/jx8lno0ApmE7gvxL_8DOJr8yY6Q>
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: Thu, 09 Apr 2020 15:53:04 -0000

Actually, I am doing some research on H3 request schedule mechanism using HTTP/3 connection level delay partly. Yet neither the spec of H3 nor QUIC provides an interface to fetch delay from H3 connection or QUIC connection. Workarounds do exists, if I use ICMP PING Frame, or calculate TTFB when I send H3 request as result, or get it directly from QUIC congestion control module. But none of these workarounds fit my purpose on pro-actively retrieving the dealy of H3 connection or QUIC connection. At last, I end up implementing by pro-actively send QUIC PING Frame and wait my peer
acknowledges the QUIC packet contains it.

I found another research doing the similar thing as I do. Their paper is "MP-H2: A Client-only Multipath Solution for HTTP/2". They just use the H2 PING and corresponding ack to get H2-level delay.

This is all I am thinking about.

-- 
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/3567#issuecomment-611603998

v2.23.0 | Report a Bug | By Email