Re: [quicwg/base-drafts] Remove the discussion about when to use long header (#1550)

Martin Thomson <notifications@github.com> Thu, 12 July 2018 00:19 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 65DDE130F0B for <quic-issues@ietfa.amsl.com>; Wed, 11 Jul 2018 17:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, 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 yfKnIUUDJjbf for <quic-issues@ietfa.amsl.com>; Wed, 11 Jul 2018 17:19:55 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 551FF130EAE for <quic-issues@ietf.org>; Wed, 11 Jul 2018 17:19:55 -0700 (PDT)
Date: Wed, 11 Jul 2018 17:19:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531354794; bh=bRgkoLgNm6C6TgZz6LgfJMehrY0Mjgfbk9E0FCaV9b0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2XlCzj5rezEXRBTIsKDPVtC7D3a/JJZJOqdqouX39Gs0MqP57XtCE9yAZ/qftN4QN C7KnjvwlqEyXpB7BUfXk5ot7/JUsKZpZFZWgy2mgcRNW8Z2JLFBIDHUrzb9OAQzSiz MbWKRWgfB5GwP5YFQbOZ9hbDzkZA4OIYI+ynpxMI=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab164304ad3feeceeff9205c89a680d18a6b8cdf2f92cf00000001175e60aa92a169ce144ab75c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1550/c404350173@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1550@github.com>
References: <quicwg/base-drafts/pull/1550@github.com>
Subject: Re: [quicwg/base-drafts] Remove the discussion about when to use long header (#1550)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b469eaaace0f_2c422b150861af6054595"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/W3FtqNg6w-99WC71O_-lNLG-PBY>
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: Thu, 12 Jul 2018 00:19:58 -0000

While the text is correct in the sense that you can't do version negotiation without packets that use the long header, I see your point here.  This is more consistent with the minimalist nature of the doc, which avoids implying basically anything about what use of any of these packets implies.

My natural inclination would have been to address this sort of concern with an example in the appendix along the lines of:

* the first packets exchanged in a flow use the long header

Do you think that we should add that as well?

-- 
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/1550#issuecomment-404350173