Re: [quicwg/base-drafts] Clarify PADDING vs PING frames (#838)
dkg <notifications@github.com> Fri, 06 October 2017 22:17 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 01BCE1330B0 for <quic-issues@ietfa.amsl.com>; Fri, 6 Oct 2017 15:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.018
X-Spam-Level:
X-Spam-Status: No, score=-7.018 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_32=0.001, 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 Gi_GXQWwho-H for <quic-issues@ietfa.amsl.com>; Fri, 6 Oct 2017 15:17:09 -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 68948133090 for <quic-issues@ietf.org>; Fri, 6 Oct 2017 15:17:09 -0700 (PDT)
Date: Fri, 06 Oct 2017 15:17:08 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1507328228; bh=xwJsQwcquJyrUXdAOvAJVoagAg+nnwGhu6ZoSILWxFY=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WV5iC2IpWxd2LQS7dnSepMdDc/+pCxKbFDhOYdeLWHyau/0ScpAlIEGxI8ia7ZMIs 8yHmJGtSANt26+E3jK4tUAVfNitgAlFq8ZrxkLgXBSLDct4U17/kba3uvW6T/+SZOb NzghhHr/JvVvEIbE7t0rsx5IULqq2I5iwzWrZGvA=
From: dkg <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abac4df59da8a25fea505f7bc48a49a3385a7e5a4e92cf0000000115efc2e492a169ce0fb03aff@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/334883289@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_59d800e44f200_55723fc23de64f301016fc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dkg
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/GkCd13DGoktDc2mQ-m4zebW54ao>
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:17:11 -0000
I lean in the direction of making PADDING not count (and not require an ACK), because i'd like both sides to be able to pad packets that would otherwise be ACK-only without inducing a feedback loop. That would distinguish PADDING from PING as well. Another alternative (voiced by @ekr at the interim, possibly facetiously) was to allow/encourage the use of ACK frames as padding in general. Or, we could allow ACK frames to be arbitrarily large, which would let us use them both as ACK and as PADDING -- that would also let us get rid of PADDING. -- 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-334883289
- [quicwg/base-drafts] Clarify PADDING vs PING fram… Igor Lubashev
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Patrick McManus
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Igor Lubashev
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Martin Thomson
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … ianswett
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Igor Lubashev
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … ianswett
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Igor Lubashev
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … ianswett
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … dkg
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Lucas Pardue
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Igor Lubashev
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Christian Huitema
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … janaiyengar
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Igor Lubashev
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … ianswett
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … ianswett
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … MikkelFJ
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Martin Thomson
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … Igor Lubashev
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … ianswett
- Re: [quicwg/base-drafts] Clarify PADDING vs PING … ianswett