IETF Logo Mail Archive

Re: [quicwg/base-drafts] PING is reliably delivered (#2068)

Christian Huitema <notifications@github.com> Sun, 02 December 2018 06:28 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 837DA1276D0 for <quic-issues@ietfa.amsl.com>; Sat, 1 Dec 2018 22:28:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 sFU0ueNevUm2 for <quic-issues@ietfa.amsl.com>; Sat, 1 Dec 2018 22:28:06 -0800 (PST)
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 90B24126BED for <quic-issues@ietf.org>; Sat, 1 Dec 2018 22:28:06 -0800 (PST)
Date: Sat, 01 Dec 2018 22:28:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543732085; bh=zpG4KaeIqy4+S6RmJMvmae2iHylRAmW6POhA7q2tyXs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KrUCyB6en41jNTT076ftc/8tx/2iRPwWWfD6JzQCoLV/+8Tdd5gkE4TjThMn2h9/d 4jkMkdO7m20aGg4/cRN1Out97oAyRGlikOjQV1/fr3BPieIsTkMgfHa4Ngi168jwDp rqloMRfPFWJbje7VRa+d22VTnSmgBj+F992oLi50=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abac89ccc3efc44d7a6a476ce2c985abb3327262ba92cf00000001181b3d7592a169ce16fae0fe@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2068/c443485146@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2068@github.com>
References: <quicwg/base-drafts/pull/2068@github.com>
Subject: Re: [quicwg/base-drafts] PING is reliably delivered (#2068)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c037b756747b_607f3fc32c6d45b4393468"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/mwH16gDjEASSB4f8JYFNrienxYU>
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: Sun, 02 Dec 2018 06:28:08 -0000

Wait a minute. I have currently an implementation of PMTU discovery. To test a possible PMTU value, I send a packet of that length, full of PING and PAD, just like the text says. I do expect the packet to be acknowledged if it is received. If the packet is not acknowledged, I will probably not resend it as is. I may or may not try a different PMTU. I may wait for some time. I am definitely not going to automatically retransmit "the PING frame".

For me, the PING frame is a transport level construct, just like ACK or PAD. I don't think that the application API should specify "send a PING frame". It should most probably be something like "test whether the connection is still up, and tell me in not less than 3 RTT". Or something like that. And then the transport logic implements that however they see fit.

-- 
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/pull/2068#issuecomment-443485146

v2.23.0 | Report a Bug | By Email