IETF Logo Mail Archive

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

Lucas Pardue <notifications@github.com> Fri, 06 October 2017 22:48 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 36ABF1330B0 for <quic-issues@ietfa.amsl.com>; Fri, 6 Oct 2017 15:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.615
X-Spam-Level:
X-Spam-Status: No, score=-5.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 TXhYC2TCNgJ4 for <quic-issues@ietfa.amsl.com>; Fri, 6 Oct 2017 15:48:38 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7E92132F7C for <quic-issues@ietf.org>; Fri, 6 Oct 2017 15:48:38 -0700 (PDT)
Date: Fri, 06 Oct 2017 15:48:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1507330117; bh=Ahvf5eiv61XP1J9aPFYLm0mO57mPa3ALJayCzGVjVBY=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jDqAdaJoewN8vjMo1xc0din89hAHi/JKhTOccm5DtHDTCpws/NrzggYn4T3NnBE4Q gNVGkWicFCAdk0nssUQmsGSgbDkAn9MoEzJ+VrKu+L4cMx1heQC/hPypex02FDKMg0 3jgCQLEj3Sr5nD4uKl/dICqpAYMbZfoS9UlA2TdA=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2591fa6c76fce69e01d3b7e348313d361fcc348992cf0000000115efca4592a169ce0fb03aff@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/334887739@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_59d80845cf3d3_2d353fa47393ef348679d"; 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/p_yURv3lmHKPTE0R7kYe3Nraacg>
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: Fri, 06 Oct 2017 22:48:40 -0000

I'd like to keep PADDING distinct from ACK, for applications where ACK is harder to do (i.e. unidirectional flows). Unless I'm misunderstanding and the suggestion is to send ACK for padding when it is not really acking anything.

As to PING vs PADDING, I think I remember some old text, where PING solicited a response PING (aka PONG). That could make it distinct from PADDING but the current text doesn't include that concept. 

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

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