Re: [quicwg/base-drafts] does version negotiation packet format need to be locked across versions (#569)

mirjak <notifications@github.com> Sat, 03 June 2017 14:45 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 0D5171292D3 for <quic-issues@ietfa.amsl.com>; Sat, 3 Jun 2017 07:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level:
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-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 AaMqRj5n4KnX for <quic-issues@ietfa.amsl.com>; Sat, 3 Jun 2017 07:45:45 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C66991286CA for <quic-issues@ietf.org>; Sat, 3 Jun 2017 07:45:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Weh5EBydOfafJNJeSEYgQOoALnw=; b=R6qJ16UXEr+kvNk+ raRJEtyxRTCzpWiqoDlHaNG68w7XWfRjBka0IVqNXktDc/TIysJYswL33D2/EEMV Q2qujDB6dDZptvnCML5E6lVnsPr4JzkyrZ9L7Q918QhBtZvjZPzwnHWQmfDVsaOU 3CaiWONczCexDH8MHxwrcOkPMsg=
Received: by filter0971p1mdw1.sendgrid.net with SMTP id filter0971p1mdw1-3966-5932CB97-2A 2017-06-03 14:45:43.442991903 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id Rxze0YNFQxKtkfDZHsjS5g for <quic-issues@ietf.org>; Sat, 03 Jun 2017 14:45:43.482 +0000 (UTC)
Date: Sat, 03 Jun 2017 07:45:43 -0700
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcff26c8db9ec9189b9ce448aaf92c0954720d16492cf00000001154a8d9792a169ce0de8f806@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/569/305979415@github.com>
In-Reply-To: <quicwg/base-drafts/issues/569@github.com>
References: <quicwg/base-drafts/issues/569@github.com>
Subject: Re: [quicwg/base-drafts] does version negotiation packet format need to be locked across versions (#569)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5932cb975e859_19303faa67de5c3c102157"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3blWZYdY+/j5/pIR9Dv8WtCz/v/mvmyTIsQz Iwez1l6zWWB6TR0UeysFR8+QdJQ4NILoRzWuGfmnlATdkgY9Fcr1m2HIOA3gW8idk+uLj+YS0/O8H9 II/K2U5d3khRCceGrPGxw7fxaJrD3kparD5W+SPTJ0TL8HVhCHgaKIjp9g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/bLactCmR7Xl-wCp8sk6X7oJ0ers>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 03 Jun 2017 14:45:48 -0000

Yes, I agree that this is still unclear. For version negotiation you need to fix the header format bit, the header type field, the whole version negotiation header incl. it's type and either the version field of the long header or also the client initial packet type and the version field in that header as well as the mechanism that all quic connection have to start with a client initial. But probably it makes sense and is just easier for version negotiation to fix the whole long header (which mean future packets type in new version may extend the long header but all long header packets need to have at least these fields). If you want to make it possible to allow network nodes to use the connection or packet number in short header packets (even if they didn't see the handshake and therefore the used version), you of course also have to fix that in the short header as well. Which basically means all headers are fixed and future version can only add additional information. From my side, i think that's okay.

-- 
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/569#issuecomment-305979415