Re: [quicwg/base-drafts] Should QUIC provides PING interface for upper layer? (#3567)
Lucas Pardue <notifications@github.com> Thu, 09 April 2020 16: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 7571C3A0B5D for <quic-issues@ietfa.amsl.com>; Thu, 9 Apr 2020 09:10:53 -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 nxsutAhrVGtg for <quic-issues@ietfa.amsl.com>; Thu, 9 Apr 2020 09:10:52 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32B723A0C0C for <quic-issues@ietf.org>; Thu, 9 Apr 2020 09:10:52 -0700 (PDT)
Date: Thu, 09 Apr 2020 09:10:51 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1586448651; bh=leB59nm7PH4KvliOqXlv9ykA508Tkou1p2qtrzLFwzs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nl7duq+ZtwRvIU9IhV70ze4zVFF5dkPkGdJF1E1hIW9TkzjF1XAd++g9Fe5BB81nf ykm+sMEDFD9rJxmiMCBBB+TAJXELMmBfVS2Zd1bvNDzgfCzs/N8bysVp5N02EVizkd souPipuW628nRnd3b45J6CNSoCzhqqQ/PIsopWGQ=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5XBIZTMAQEZ3O7QWN4TMVAXEVBNHHCHCTWCE@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/611613556@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_5e8f490b6cc7c_43ca3f803fccd9643225c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/9tF431x7VP0lT1mYg9jCWoR5Alg>
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 16:10:53 -0000
I'm not seeing the issue here. The QUIC transport provides the capability to send PING and measure the time until it is ACK'd. It seems like you are using this and it works for you? The HTTP/3 mapping can use all transport features, it doesn't need to redefine them. So as Mike says, the discussion becomes one about implementation API and how an HTTP/3 implementation might choose to expose transport layer features. That is not something the QUIC WG needs to consider in the specification(s) IMO. -- 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-611613556
- Re: [quicwg/base-drafts] Should QUIC provides PIN… stormlin
- [quicwg/base-drafts] Should QUIC provides PING in… stormlin
- Re: [quicwg/base-drafts] Should QUIC provides PIN… David Schinazi
- Re: [quicwg/base-drafts] Should QUIC provides PIN… Mike Bishop
- Re: [quicwg/base-drafts] Should QUIC provides PIN… Lucas Pardue
- Re: [quicwg/base-drafts] Should QUIC provides PIN… stormlin
- Re: [quicwg/base-drafts] Should QUIC provides PIN… stormlin