Re: [quicwg/base-drafts] introduce a version alias mechanism (#2573)

MikkelFJ <> Wed, 10 April 2019 05:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 014F31202AF for <>; Tue, 9 Apr 2019 22:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6sXlJUPmgrao for <>; Tue, 9 Apr 2019 22:47:46 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2D4381202A4 for <>; Tue, 9 Apr 2019 22:47:46 -0700 (PDT)
Date: Tue, 09 Apr 2019 22:47:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1554875265; bh=UfNgBCRUGXmMH1xWkoQnqEJT1aYJu9s4oep6JCvYQuQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M/CWmWxi3fEeGV92K7VD67qEEjbdxrrpJeQZd+AEw/knXTy5rIi7xFGyWsK5o6tE9 1LqZIateevBOdShWBBjcwxcvse+0bqQ+A5Ry7RX52FlICCNVYuxRcHEC58TZXsmkUl QU4TeTpj3Nt1JLwRymu9zOaOf9B6F+HDD4CNJ2WI=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2573/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] introduce a version alias mechanism (#2573)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cad8380cc52f_579b3f99464d45bc1645e7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Apr 2019 05:47:48 -0000

I'm a bit concerned with unbounded amounts of aliases being dumped on the client. If the alias is tied to a token, a client can just drop excess tokens and aliases, but if the design somehow evolves into a many headed alias thing, there could be some abuse/resource issues.

Wouldn't it be reasonable to limit this to a single alias?

A future version linked to downgrade protection and version negotiation could have a more complicated pattern, with more time for analysis and design.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: