IETF Logo Mail Archive

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

Christian Huitema <notifications@github.com> Mon, 09 October 2017 17:10 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 8D5811346EE for <quic-issues@ietfa.amsl.com>; Mon, 9 Oct 2017 10:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level:
X-Spam-Status: No, score=-0.402 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_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 PuiufVLEdEx3 for <quic-issues@ietfa.amsl.com>; Mon, 9 Oct 2017 10:10:45 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 807DD1346C0 for <quic-issues@ietf.org>; Mon, 9 Oct 2017 10:10:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=V2wc4rFMTU94/Nq2I4jPJG91P64=; b=TJnsSgvZ9Avo3gs9 i+2QQhqtL7aE2c4yrl4g0x6aohsBTRgISHmP00oR4cPFObNAf6aFrYvWNTOFTBxw j5HAbXWuEvPWCjin6Rj7ZSHzvS1D3Bd0T1dYVfWkxJf/TedOKdT1VecH+EX8QV5e hqhy/lOe3zMdHUyRzvFe6tM3ofI=
Received: by filter0104p1iad2.sendgrid.net with SMTP id filter0104p1iad2-13605-59DBAD94-C 2017-10-09 17:10:44.300846425 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0022p1iad2.sendgrid.net (SG) with ESMTP id 5BcW1WWYR3KABxd4wdUV4A for <quic-issues@ietf.org>; Mon, 09 Oct 2017 17:10:44.276 +0000 (UTC)
Date: Mon, 09 Oct 2017 17:10:44 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab02384f6e4149aa85142d328a501846c39326368892cf0000000115f36f9392a169ce0fb03aff@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/335221001@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_59dbad9382b48_b393fdb77372f34929bb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1dzNRjnmXgWVGEFNHm2VRFf+vrta6Fo046T4 Mi/ISRjTpzwHI3mBc8OuGwrq4cJFfjA2EBGXHJbEOHP6U/VSj4bUcaRe2DIT7UbZMVfLkzj9qeplmK cY/e4JRi8DjQTvZMRIOVA9uD/aC1WOg+38fIOVx5yex2hde45H85ddF/CM2h5OYDJ9eOk6P60hhQNy w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FCh4g0ahdHzqbvOrqN28Xp_JYyE>
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, 09 Oct 2017 17:10:46 -0000

PADDING should be a no-op as far as ACK strategy is concerned. If the sender wanted the packet to be acked, they could swap one of the PADDING bytes for a PING.

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

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