IETF Logo Mail Archive

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

Mike Bishop <notifications@github.com> Thu, 29 November 2018 17:20 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 C31C0130E2F for <quic-issues@ietfa.amsl.com>; Thu, 29 Nov 2018 09:20:03 -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 ggrDRIFp8Krx for <quic-issues@ietfa.amsl.com>; Thu, 29 Nov 2018 09:20:01 -0800 (PST)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E32C130E2B for <quic-issues@ietf.org>; Thu, 29 Nov 2018 09:20:01 -0800 (PST)
Date: Thu, 29 Nov 2018 09:20:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543512000; bh=O5xzjspTr7iG1DRrKJITn91FzMvCAW635poL4JQok2k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=khSQoElKvmEnHnM5DAQBjBOsEOuW55XmzpSKl/rsDCl4xK9Xu8KM9wgQ362+n6Do+ buabZlTdql4Vpnnoa1RGujD3KxY0XsFDjVw0GcQa3eVwJ47DfPRuWqN3b62gA2+wdU zaNAdDzrYeEoCHNTN1LcrfkFR8ihO+P/Iq0OcIO0=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf80c6a1723bbbb06bc1e28e4f352a8c7364e051692cf000000011817e1c092a169ce16fae0fe@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/c442918679@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_5c001fc05d7f8_64a03fd96ced45c41309f5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/qRJbyZv_DD2xWffgf0MZki2oxjk>
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, 29 Nov 2018 17:20:04 -0000

We have a separate PROBE frame; it's called PATH_CHALLENGE.

I think we've said previously that PADDING and PING have identical semantics (to wit, none), except that PING forces the packet to be acknowledged regardless of whether there's anything retransmittable in that packet.  Whether we want it to have that property because it's reliably transmitted or because it's not either ACK or PADDING seems like a philosophical discussion akin to how many angels could dance on the head of a pin.

FWIW, it delivers no information when delivered; I see no point in delivering it reliably.  It elicits an ACK if the packet arrives -- that is a sufficient purpose.

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

v2.23.0 | Report a Bug | By Email