Re: [quicwg/base-drafts] minimum payload size requirement creates awkward special case (#2049)

Marten Seemann <notifications@github.com> Sun, 25 November 2018 10: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 C8334129385 for <quic-issues@ietfa.amsl.com>; Sun, 25 Nov 2018 02:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 TsT-Ec7_RxnY for <quic-issues@ietfa.amsl.com>; Sun, 25 Nov 2018 02:17:13 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5E4E128D09 for <quic-issues@ietf.org>; Sun, 25 Nov 2018 02:17:12 -0800 (PST)
Date: Sun, 25 Nov 2018 02:17:11 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543141031; bh=hM+8/WLmzU9WsJf5rijO7772WW0UYLf6SgyqnWInOgQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=teflYM/86MClgO6jXaNdn+n6Onihxe18ZsuyEsM9u7GvNM6q2Qy7oI5E9yZRkOb7Y 5kR9SEVhgv81RWnBvMYE3GaFVHhUbJTp3ccBuOBOpd94PPy+QzPs3wt1nihcXovooR aVWGzGsW39hpE+/+YlWA64JY4xb6kEzS18AdpJXQ=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abce223dd02035284f9b59929f816f445f1ef0e1e292cf00000001181238a792a169ce16e4137a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2049/441429539@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2049@github.com>
References: <quicwg/base-drafts/issues/2049@github.com>
Subject: Re: [quicwg/base-drafts] minimum payload size requirement creates awkward special case (#2049)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bfa76a7aba86_655c3f9ef10d45c4922fd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/NDRnzLWSthUKIHKc5j8w50MTwnY>
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: Sun, 25 Nov 2018 10:17:15 -0000

> What I mean is that when you notice that the length of the streams is below 4 bytes, you can move them backwards and insert PADDING before them. That logic would replace the logic you have, that appends PADDING frames.

Sure, I can think of multiple ways to fix this, and I'm not concerned about performance at all. I'm concerned about correctness and implementation complexity.

My point is: I think the way of packing frames and then adding padding is a common way to pack packets, and many implementations will choose to implement it that way. The corner case I described is **very subtle**, and I expect this to be the source of nasty bugs in the future. I think we could save ourselves a lot of trouble by reverting #2030.

-- 
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/2049#issuecomment-441429539