Re: [quicwg/base-drafts] Connection ID lengths 1, 2 and 3 bytes can't be encoded (#1570)

MikkelFJ <notifications@github.com> Sun, 15 July 2018 19:26 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 DF042130E60 for <quic-issues@ietfa.amsl.com>; Sun, 15 Jul 2018 12:26:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.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_HI=-5, 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 Wk8sgaTFwJkR for <quic-issues@ietfa.amsl.com>; Sun, 15 Jul 2018 12:26:16 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7BF1130E28 for <quic-issues@ietf.org>; Sun, 15 Jul 2018 12:26:15 -0700 (PDT)
Date: Sun, 15 Jul 2018 12:26:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531682774; bh=ypM66n+lzastOu4sCzNrMKLv05Vw+erPo+doFCN47is=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cuVRDeG2GbRQTOD2yjdIwC2w8q7r8n+EeludQCC9Jon/OfNKAgob6/pdsQ1fTHWwb HAbtUXzga6YlUrcPVzgnzxZzdopHclM/dcnWYVrOGa4IRJJcntyBpfj7an1mgtZCxY DhDQsi/1vZr5jaV2ED9Z5Rk/ft9wIua0nukRO/2Q=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4ff05b035b0cbc846129846cffef765ff3f5efbf92cf00000001176361d692a169ce14587666@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1570/405112346@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1570@github.com>
References: <quicwg/base-drafts/issues/1570@github.com>
Subject: Re: [quicwg/base-drafts] Connection ID lengths 1, 2 and 3 bytes can't be encoded (#1570)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b4b9fd6de32e_543f2b0735640f5c471535"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/7d98-z9ElE1QQR-qrJjftpndn9o>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 15 Jul 2018 19:26:18 -0000

There are also use cases in radio based sensor networks and also wired lightweight protocols that use QUIC without IP/UDP framing. For example an I2C bus or similar microcontroller network might use QUIC for security and routing but really care about keeping individual message frames short. Such use cases might, BTW also opt to truncate the trailing authentication tag.

-- 
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/1570#issuecomment-405112346