Re: [quicwg/base-drafts] What can change in a different version (#55)

martinduke <notifications@github.com> Mon, 12 December 2016 05:29 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 D55F812998A for <quic-issues@ietfa.amsl.com>; Sun, 11 Dec 2016 21:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level:
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 1VY4BW1UmSUv for <quic-issues@ietfa.amsl.com>; Sun, 11 Dec 2016 21:29:06 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EB6C129987 for <quic-issues@ietf.org>; Sun, 11 Dec 2016 21:29:05 -0800 (PST)
Date: Sun, 11 Dec 2016 21:29:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1481520544; bh=3K/mK4jWp/waM/4bWXwa6/w/+4Kb7Eneyy5zgbv2OeU=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pV413dfKNQpQIGzt0zrnvekkpc0FAJIMoZOjIk2lvfHgY7bnq3v5XN4WdIlIzLUEw K7IrMnQxKdUTmP13lUmqb7l6U8tUhS5i5vaSO6PTf8Q2CHIzZvp6IvpUofF1mkn5ij Hhr+Xp4sYvSlCI0DpgSra8HFIiJTx57ADpCB+8yY=
From: martinduke <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/55/266346429@github.com>
In-Reply-To: <quicwg/base-drafts/issues/55@github.com>
References: <quicwg/base-drafts/issues/55@github.com>
Subject: Re: [quicwg/base-drafts] What can change in a different version (#55)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_584e35a0d793f_21983f9ee97ef1402063c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
X-GitHub-Recipient: quic-issues
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Dadd58DutlW6bQt8sxB3oQqBwM8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quicwg/base-drafts <reply+0166e4ab822fe9a2045f2fc120d2eb0d0f9a15f7af4f6ea192cf000000011465f7a092a169ce0b80c9d5@reply.github.com>
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: Mon, 12 Dec 2016 05:29:08 -0000

After thinking about it a bit, I may be willing to fold on putting the version number first.

It's not too onerous to make host use the full 64 bits of the conn-id until the version is negotiated. 

Also, we're looking at quadrillions of connections on a single server before there's much chance of a connection ID collision, and in that case the only consequence is a dropped CHLO. So allowing for > 64 bits in the far future may be a bit too paranoid.

But that means that the "must not change between versions" section I'm proposing should also lock the connection ID length for version negotiation packets.

-- 
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/55#issuecomment-266346429