Re: Increasing QUIC connection ID size

Willy Tarreau <w@1wt.eu> Fri, 12 January 2018 07:30 UTC

Return-Path: <w@1wt.eu>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FDB12D890 for <quic@ietfa.amsl.com>; Thu, 11 Jan 2018 23:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 r7qZX8Z6AL6X for <quic@ietfa.amsl.com>; Thu, 11 Jan 2018 23:30:02 -0800 (PST)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 3BFB812700F for <quic@ietf.org>; Thu, 11 Jan 2018 23:30:00 -0800 (PST)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id w0C7Tnt2015934; Fri, 12 Jan 2018 08:29:49 +0100
Date: Fri, 12 Jan 2018 08:29:49 +0100
From: Willy Tarreau <w@1wt.eu>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Victor Vasiliev <vasilvv@google.com>, Mikkel =?iso-8859-1?Q?Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Roberto Peon <fenix@fb.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Increasing QUIC connection ID size
Message-ID: <20180112072949.GA15927@1wt.eu>
References: <CAAZdMad=YnTyXG-q0ACpT=tyCSX1GgRLvb=8HT3Au=e9_XT5Ag@mail.gmail.com> <d2a6136f93654eb1a5c7970cfb41f7ad@usma1ex-dag1mb5.msg.corp.akamai.com> <CAN1APdf7MqhdQ-+VMOwsNgz_F+OZK-8CzndwWTQq4FPM52ro9Q@mail.gmail.com> <1bf50145082642f1add41595c73ec4a1@usma1ex-dag1mb5.msg.corp.akamai.com> <21333E2A-AA5D-4D99-8315-3468242493DF@fb.com> <20180112055554.GA15873@1wt.eu> <CABkgnnU+QMGD4XW3mgpE1fYRVrceEXV6tu9Psy5m=LV_zPqogg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABkgnnU+QMGD4XW3mgpE1fYRVrceEXV6tu9Psy5m=LV_zPqogg@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9sreAD84GwzrKpn0KT9SexPM1WY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2018 07:30:04 -0000

On Fri, Jan 12, 2018 at 05:18:52PM +1100, Martin Thomson wrote:
> https://tools.ietf.org/html/draft-ietf-tls-dtls-connection-id-00 is
> currently DTLS specific.  Is this something that you feel should be
> more general?

Hmm I don't know yet, this makes me think. I'm realizing that very often
the LB will not decide on the server from the initial packet if it starts
to take certain elements in consideration, so it may be needed to pass the
server identifier later. In the most basic DSR case it will work though.
But above there's provision for changing the connection ID later so that
could possibly work to some extents.

I need more time to think about it and I'm lagging behind on QUIC design,
so I'm mostly focusing on general architectural points that I want to be
sure we don't forget to address.

Willy