Re: [quicwg/base-drafts] Clarify whether QUIC packets with no payload are acceptable (#1745)
MikkelFJ <notifications@github.com> Fri, 14 September 2018 19: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 C3B7A130F28 for <quic-issues@ietfa.amsl.com>; Fri, 14 Sep 2018 12:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.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_NONE=-0.0001, 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 N4UzsnlZD0IU for <quic-issues@ietfa.amsl.com>; Fri, 14 Sep 2018 12:10:40 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 69CB1130F05 for <quic-issues@ietf.org>; Fri, 14 Sep 2018 12:10:40 -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=xrYpuUt5l31SDidAOnubtfkirUE=; b=Pf0yJ8Rs4RdgGPaW VtDFKDAt27C+qVVoOeIAK+XbQmRqs0psBZal4to1544IL5xl10fyn0U4x2r7XSz9 uToLvjILAMhE7WROXVf4bHzAwiAS1E8cVvtkP+qX3Y0TB4fzA2u7O/d7c4/gozhR UE3WW1cNldmUDe9OTSa/xjdLeXI=
Received: by filter1857p1mdw1.sendgrid.net with SMTP id filter1857p1mdw1-1012-5B9C07AA-1B 2018-09-14 19:10:34.646512607 +0000 UTC m=+684194.596822535
Received: from github-lowworker-417c549.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0016p1iad2.sendgrid.net (SG) with ESMTP id 6S0EU9AcQ1C7D0y6PG5O6g for <quic-issues@ietf.org>; Fri, 14 Sep 2018 19:10:34.518 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-417c549.cp1-iad.github.net (Postfix) with ESMTP id 47322C41E5C for <quic-issues@ietf.org>; Fri, 14 Sep 2018 12:10:34 -0700 (PDT)
Date: Fri, 14 Sep 2018 19:10:34 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd7dfdee3ab8dfd6c313f35644e22ca136631f59d92cf0000000117b3c9aa92a169ce157b79fc@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1745/421456612@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1745@github.com>
References: <quicwg/base-drafts/issues/1745@github.com>
Subject: Re: [quicwg/base-drafts] Clarify whether QUIC packets with no payload are acceptable (#1745)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b9c07aa451bc_1d343fb3912d45b82144ba"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0jx305QqKFr7DaMFaflveUjmyhued0VbPu4L 9KBOALn80gzMu7hzwBW1jjEYMJCgGM2v5h9FyK8Q5y2eHaPVXsJ20gt5vYcMi9IYxRMnUruhlPNGG0 gpD2Hq1JD7sgEhvh3l9YH99/nMWdw8A/7YnuHU90sNIJflFCFW6xrz9S4g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/J2k59IP4DOOs6u3YfSP_N_DB6oo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 19:10:56 -0000
If you forbid empty, you must also consider padding only. And then you must consider if keep alive only happens with ping, which is extra load on the connection. What can go wrong with empty? Bandwidth abuse? That can happen by other means. -- 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/1745#issuecomment-421456612
- [quicwg/base-drafts] Clarify whether QUIC packets… ianswett
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Nick Banks
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Marten Seemann
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… ianswett
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Ryan Hamilton
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Marten Seemann
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… MikkelFJ
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Ryan Hamilton
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… ianswett
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… MikkelFJ
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Martin Thomson
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Martin Thomson
- Re: [quicwg/base-drafts] Clarify whether QUIC pac… Igor Lubashev