IETF Logo Mail Archive

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

Igor Lubashev <notifications@github.com> Thu, 05 October 2017 17:36 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 2BF7B134300 for <quic-issues@ietfa.amsl.com>; Thu, 5 Oct 2017 10:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.182
X-Spam-Level:
X-Spam-Status: No, score=-8.182 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, 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 DGkEEX361B80 for <quic-issues@ietfa.amsl.com>; Thu, 5 Oct 2017 10:36:34 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F1C61342F3 for <quic-issues@ietf.org>; Thu, 5 Oct 2017 10:36:34 -0700 (PDT)
Date: Thu, 05 Oct 2017 10:36:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1507224993; bh=MBIiTHb7n7rdeUwv26clm0DHeiA47/vx8fSOWmHSVQA=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=v00mYJj5D7CqACdrq7DWQXOaE2UvG2vNkgs2Uz8ksqI6AkjiwWDvLhheyOMcYGBBM bhnOwrGlccVyHMmN4SHd/UO8bfqZgl39SgGkMy+FWXrgjKCh41JnbitG4S6jFs9WXS 7Pd4pgzt+L55cem2G6KKv/utAFrYAtWg+BKisWLM=
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc85b61a3a3a07e2c400036a9deeb346c854c40a592cf0000000115ee2fa192a169ce0fb03aff@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@github.com>
Subject: [quicwg/base-drafts] Clarify PADDING vs PING frames (#838)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59d66da1d1e26_1a5b3fb3290d4f28302b8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/JMPYEYMorn8xJ-UBwQakR9bv1YY>
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: Thu, 05 Oct 2017 17:36:36 -0000

At this point, it looks like the semantics of PADDING and PING frames are identical -- both take exactly 1 byte, both cause ACKs, both count for congestion control, both have no other effect on transport.  Are there any differences (like PING must be ACKed immediately, while PADDING can be ACKed after a delay)?

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

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