[quicwg/base-drafts] New packet format used before it is defined (#3673)
David Schinazi <notifications@github.com> Wed, 20 May 2020 02:00 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 57CD33A08D3 for <quic-issues@ietfa.amsl.com>; Tue, 19 May 2020 19:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level:
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 pZekYxaPIf0i for <quic-issues@ietfa.amsl.com>; Tue, 19 May 2020 19:00:07 -0700 (PDT)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A11D3A08D2 for <quic-issues@ietf.org>; Tue, 19 May 2020 19:00:07 -0700 (PDT)
Received: from github-lowworker-52827f8.ash1-iad.github.net (github-lowworker-52827f8.ash1-iad.github.net [10.56.108.24]) by smtp.github.com (Postfix) with ESMTP id B4A1C8C0BF6 for <quic-issues@ietf.org>; Tue, 19 May 2020 19:00:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1589940005; bh=0fvU2kaa28RexOMfXPJE/xv4vvxkUSPHLpxZRCHRyjA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=rnZxnmSq4ocn4kSVjAL8ojR9wwUMjxJGa5gFRj1t2xpy2fBodJPEAp0LrCLyKxqmZ as2YbeYHGX9qgeaoRGjR84wzYWnA3VbcHwQ4y6v8HP0RcmSfp8kZAt5I87686IAuQY yaceHnbwtCmRWwqJhtQxbOW6xT03chyLjNGATCpc=
Date: Tue, 19 May 2020 19:00:05 -0700
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK44XN56XRWVFWWZS7V42BYCLEVBNHHCKCOUQQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3673@github.com>
Subject: [quicwg/base-drafts] New packet format used before it is defined (#3673)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ec48f25a49ef_3c83fe8662cd95c2711ea"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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/lnDCnnmTSw41M01_3vN5ys7ENeI>
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: Wed, 20 May 2020 02:00:10 -0000
#3573 introduced a new bespoke packet format. I don't have issues with the format itself, but as I reviewed [draft-ietf-quic-invariants-08](https://tools.ietf.org/html/draft-ietf-quic-invariants-08) I was surprised to see it used there without any explanation as to how to decipher it. I think it would be nicer if each document that uses this format either: - References the "Notational Conventions" section from draft-ietf-quic-transport - Has a "Notational Conventions" section of its own explaining this format -- 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/3673
- [quicwg/base-drafts] New packet format used befor… David Schinazi
- Re: [quicwg/base-drafts] New packet format used b… Martin Thomson
- Re: [quicwg/base-drafts] New packet format used b… Mike Bishop
- Re: [quicwg/base-drafts] New packet format used b… Martin Thomson