Re: [quicwg/base-drafts] Authenticating connection IDs (#3439)

David Schinazi <notifications@github.com> Thu, 05 March 2020 06:14 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 A14A93A0DB6 for <quic-issues@ietfa.amsl.com>; Wed, 4 Mar 2020 22:14:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 Lk6FpTk_GtRd for <quic-issues@ietfa.amsl.com>; Wed, 4 Mar 2020 22:14:58 -0800 (PST)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE2EC3A0DB5 for <quic-issues@ietf.org>; Wed, 4 Mar 2020 22:14:57 -0800 (PST)
Received: from github-lowworker-0eea13f.ash1-iad.github.net (github-lowworker-0eea13f.ash1-iad.github.net [10.56.109.26]) by smtp.github.com (Postfix) with ESMTP id 0E463E0F2A for <quic-issues@ietf.org>; Wed, 4 Mar 2020 22:14:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1583388897; bh=OfRb31IWHZNKzc68V+SrHp2YpgUNFx2CUl4g4e0UVeE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QOvH2pHax3j0QubmKAu3hgl/1yHbxEPlBXkTKM+955lgZqng2AXGFMPZnL7h+4Dw0 AkVu8R4YhVphAwzRcOR4CH7n4zsYApMEIrp6ouZynhZCXfvRKm85bY42/EtRAAp2Ay 1NSGnEJ9wJ1h2St75siPBC8RUD7WkTIZwcUc7fg0=
Date: Wed, 04 Mar 2020 22:14:56 -0800
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYMKE3AX6LFJVWGXNF4NR46BEVBNHHCC4LIRI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3439/595047944@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3439@github.com>
References: <quicwg/base-drafts/issues/3439@github.com>
Subject: Re: [quicwg/base-drafts] Authenticating connection IDs (#3439)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e6098e0f26bb_39953fa67aecd96024207d"; 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/YByYJRnYpNJfpHHUjFF9pMit3IQ>
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: Thu, 05 Mar 2020 06:15:00 -0000

In the design of Google QUIC, the client picks a random connection ID, and the server uses that. (BTW that's why it's called a connection ID, it's a unique identifier that has a one-to-one mapping with one connection...) What that means in practice is that the client uses randomness to generate the connection ID, the load balancer maps that to a given server, and using the same connection ID for the duration of the connection makes sure that all packets reach the same server. So far we've kept this design for our implementation of IETF drafts. We understand that some server deployments may want to have the server pick its connection ID, but so far we don't see the value in that outweighing the added complexity. Today we do not yet have a good mechanism for a server to ask the load balancer for more connection IDs that will map to it. We have some hacks that we can perform, but I don't think those hacks will work for the first connection that a server receives. So if this becomes required, we'll have to build the load balancer protocol before we can deploy the new draft.

-- 
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/3439#issuecomment-595047944