IETF Logo Mail Archive

Re: [quicwg/base-drafts] Alternative packet format presentation (#3573)

ekr <notifications@github.com> Fri, 17 April 2020 20:01 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 150C93A0917 for <quic-issues@ietfa.amsl.com>; Fri, 17 Apr 2020 13:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.721
X-Spam-Level:
X-Spam-Status: No, score=-1.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 lcbqV6Mo7ACA for <quic-issues@ietfa.amsl.com>; Fri, 17 Apr 2020 13:01:37 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF3FF3A0927 for <quic-issues@ietf.org>; Fri, 17 Apr 2020 13:01:36 -0700 (PDT)
Received: from github-lowworker-39ac79b.ac4-iad.github.net (github-lowworker-39ac79b.ac4-iad.github.net [10.52.18.15]) by smtp.github.com (Postfix) with ESMTP id A15F46A1EBD for <quic-issues@ietf.org>; Fri, 17 Apr 2020 13:01:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1587153694; bh=04Nh/SRNE5Cz6iQzAdZ8NxA0DY2IjZ0haJLBB93a/vA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pSp5t7Q5/x8W9rAo2jOw0ljOMhkd2RJ8Pt/bZ/fGUmKmkLgun/g3As0JYqzQ5lVOz 5ECnNy/wjKCupKIg3X3wEeO6K4jqeb9GyGlN5ltlqIVzOhcKVFg2vFehrhg3e/JE8F 3nNQgfD7JrbqUz7bxZcx8zUDG3EYxhnk3yRF5hBw=
Date: Fri, 17 Apr 2020 13:01:34 -0700
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3HNELMUKMUUZKXX354UXWB5EVBNHHCHFHWFE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3573/c615438704@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3573@github.com>
References: <quicwg/base-drafts/pull/3573@github.com>
Subject: Re: [quicwg/base-drafts] Alternative packet format presentation (#3573)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e9a0b1e91109_68133fcf448cd964160827"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/00sXG52J0SSESTa9giLBmMd-X-U>
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, 17 Apr 2020 20:01:39 -0000

I definitely like this general structure better. 

As far as the question of whether we should import the TLS language, you would need some extensions, but I suspect that you could get pretty far with the following three:

uintX == unsigned integer of size X
uintv == varint
opaque x[lower..upper] == opaque vector without a header (TLS uses <> to mean that it has a header) and opaque x[y..] means "to end of the container and minimum size y]

I believe we've already done uintv for MLS and @bifurcation has been thinking about a generalized an a "TLS spec language" 


-- 
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/pull/3573#issuecomment-615438704

v2.23.0 | Report a Bug | By Email