IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clarify PADDING vs PING frames (#838)

Martin Thomson <notifications@github.com> Mon, 04 June 2018 14:11 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 A4A2F12D964 for <quic-issues@ietfa.amsl.com>; Mon, 4 Jun 2018 07:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 KQKT88OqBTX5 for <quic-issues@ietfa.amsl.com>; Mon, 4 Jun 2018 07:11:40 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53169127058 for <quic-issues@ietf.org>; Mon, 4 Jun 2018 07:11:40 -0700 (PDT)
Date: Mon, 04 Jun 2018 07:11:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528121499; bh=HzCjwMVXPNuzH40ijBgz7934bzSANW1T/q6GUoFH1HM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BUUyJ+N7tk91bPme/HXld3Snuf+SYN15lR5cplVoExqsm96LD/fU5MT9YV0uVQoUy aeyO0I685GexAiltVxzOYeKDt58A5YdatdoCEQi+RNX5lvAgHeMgaVYQwAZ9pGNGE7 LOw9/Y3oE9uz+N+nVZQM4A8MmqeUm5G5kawvPFo8=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab967f08016d76ea288417c5bd405a6e34365ed07992cf00000001172d0a9b92a169ce0fb03aff@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/838/394368550@github.com>
In-Reply-To: <quicwg/base-drafts/issues/838@github.com>
References: <quicwg/base-drafts/issues/838@github.com>
Subject: Re: [quicwg/base-drafts] Clarify PADDING vs PING frames (#838)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b15489b96be4_42ae2b0be6a52f5430521d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/lxsdxMmMMFwhXz9SemYByxUr-vg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 04 Jun 2018 14:11:42 -0000

PADDING doesn't elicit ACK.  PING does.

A packet containing only ACK and PADDING counts towards bytes-in-flight.  But that means that you will consume bytes-in-flight by sending these, and maybe never an ACK.  So, send a PING sometimes, and you get your bytes-in-flight back.

-- 
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/838#issuecomment-394368550

v2.30.2 | Report a Bug | By Email | System Status