IETF Logo Mail Archive

[quicwg/base-drafts] Optional packet length field in the short header? (#1831)

Lars Eggert <notifications@github.com> Thu, 04 October 2018 06:05 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 21CF9130DDF for <quic-issues@ietfa.amsl.com>; Wed, 3 Oct 2018 23:05:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Level:
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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 KW4phWWyrhoX for <quic-issues@ietfa.amsl.com>; Wed, 3 Oct 2018 23:05:02 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B1EF130DE7 for <quic-issues@ietf.org>; Wed, 3 Oct 2018 23:05:02 -0700 (PDT)
Date: Wed, 03 Oct 2018 23:05:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538633100; bh=tcAL286EzWo1qGO76KALqwtRjB5drX6WlODzd8lJqyk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=rwTc/b+tivCXiZ9+Zxz5f8bhUu2oirXeDi5ouQGle0jgGabFDEU2j9t4cgp16qfTr QsBhpK/KAc6+tku+RB3WonpJkIkJhv4KufHjdyKB7iBQ5Yr1rtirViVtSL36rio4Vt Mr0P+radeOxowRcYl4BMv+IhqC2cMR/4YryAXtM0=
From: Lars Eggert <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb5c9b983435892bff72dde55a76b0f60320b2e0292cf0000000117cd6f8c92a169ce15da6710@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1831@github.com>
Subject: [quicwg/base-drafts] Optional packet length field in the short header? (#1831)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bb5ad8c2d68d_6f2f3fbcc32d45b4187267"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: larseggert
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/ITQUyWXzcuoneH-VC-KOavnUP9Q>
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: Thu, 04 Oct 2018 06:05:04 -0000

I'm wondering if it would be useful to optionally allow SH packets to carry a packet length field, as LH packets do. This would allow SH packets to be coalesced behind SH packets, which might be useful?

We could burn a flag bit to indicate the presence of said packet length field, but before doing a more detailed design I'd like to understand if coalescing of SH packets behind SH packets is something that anyone cares about?

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

v2.23.0 | Report a Bug | By Email