IETF Logo Mail Archive

Re: Increasing QUIC connection ID size

Victor Vasiliev <vasilvv@google.com> Tue, 16 January 2018 06:02 UTC

Return-Path: <vasilvv@google.com>
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 1CE5D126C2F for <quic@ietfa.amsl.com>; Mon, 15 Jan 2018 22:02:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 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_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 G3rt-kfEDQ1s for <quic@ietfa.amsl.com>; Mon, 15 Jan 2018 22:02:41 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 B2C2B124D68 for <quic@ietf.org>; Mon, 15 Jan 2018 22:02:40 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id i1so97709qtj.8 for <quic@ietf.org>; Mon, 15 Jan 2018 22:02:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8idVlZ4PMuizF34le8ExvD02PyogG0RzqDCxc5JyTRI=; b=p5cNm/mDW1NgwXcDXH/cPdMI0KZnKztZk32i6Px4nzwvtsMiexH4pmhSzTPJmbmYiF ybk/miSZRjxyAtStIKybPwEE9o3zetEOYT1ptenvdrASxAQbMVzBeC7wqNsJkwG4NthS V+ENM353L00Ic8LfG4z/2MxLn9WVGlUVuw4/VBOvOFhH0iifFn72ru5G4pqpJlB2Qh9T w+yG5FoksFJDYXqD6ONGFQ7ijZR1m5QiKmAplB0X1PdRO728DOBgH8SrpIn0prCuQbqe 8D89C5MFbqpXCMDoFEr986spHSMl5A2FGFl1kEGUhYXpms6XYkO+vIJSW9xHeBgNKZ9v VDqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8idVlZ4PMuizF34le8ExvD02PyogG0RzqDCxc5JyTRI=; b=qCjKydWj31nN39tnyTDKcsvMr8Gy2HVhAcnE7eKaeSBEHz18BWRzQJj3vWbR/w3wMG sDFbAj+5+PfWmPkgA5fI1X0CCUWcuJJZpY7FTGRgCQm3Cy/Fn2+M8ltvcwLiE0u+8NaG 2GM2AmLVSHhJ7BHYBML6PX5h2mmxhL9dHDIxscE0iZG9kew275L1K0GzrL4YnwCkLU2h YEvLRTyEbJmaqWA8B8M1wVfcfbJ9Fa4GWq17GCjevDB+blBSdAeyTWl8fSCSLnvZwClr WEwOTU8L2Uh5wpPsNOlV9s8GMe69jvgGf8jnBWUr3Vi1kcJGr9WrjKXWjqk77wC5p8kM VKUg==
X-Gm-Message-State: AKwxytcidCCtQPieXIdtRbanWGfalAFk2Xh0GzckSA38cYNWz/jdFtaK pC5XqgPnswiFMzsn4mhpQmRJMIiG1eU5a9KuR+TFbV2N
X-Google-Smtp-Source: ACJfBos5uxm8NNanobKFSd5G880pnEoVDFlSRl+E4SmXhyej0aikIZk5982lliVDiuvG7GC7U7hPhJDuLSwB1J4Y3OE=
X-Received: by 10.200.18.136 with SMTP id y8mr21372345qti.175.1516082559549; Mon, 15 Jan 2018 22:02:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.55.156.209 with HTTP; Mon, 15 Jan 2018 22:02:38 -0800 (PST)
In-Reply-To: <CAOYVs2oRveLXNhBDdNZ2PL7VOuiC7K4mza1JkNCUjumwLCvzAw@mail.gmail.com>
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> <1142e1ee-ae7b-b0be-625a-4136c6085c08@huitema.net> <CAAZdMaf2RCHHzmuFbN_EV1ohqc=EutgQ0SO8innLLuyoy+YK=A@mail.gmail.com> <CAGD1bZZ=e0egn9M9JUmvbzAx+xF7csu1m4kNkrsSEqiLOt9oWA@mail.gmail.com> <38830ad8-b6d7-1539-56d2-ccf8be3483bf@huitema.net> <CAOYVs2oRveLXNhBDdNZ2PL7VOuiC7K4mza1JkNCUjumwLCvzAw@mail.gmail.com>
From: Victor Vasiliev <vasilvv@google.com>
Date: Tue, 16 Jan 2018 01:02:38 -0500
Message-ID: <CAAZdMafFJRKJpsNaVVo9uqcRiHhvEzjLbvz8gn9-C0BHJ0giYQ@mail.gmail.com>
Subject: Re: Increasing QUIC connection ID size
To: Marten Seemann <martenseemann@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, IETF QUIC WG <quic@ietf.org>, Jana Iyengar <jri@google.com>
Content-Type: multipart/alternative; boundary="089e08289ffc6a31a40562de7a52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HqoInk-ADvnemFG_hDkDrgC9LXY>
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: Tue, 16 Jan 2018 06:02:42 -0000

On Fri, Jan 12, 2018 at 11:53 PM, Marten Seemann <martenseemann@gmail.com>
wrote:

> I’m corcerned about the overhead. In the p2p use case, there’s no need for
> encoding any routing information into the connection ID, and since every
> node just handles a small number of connections, even 4 bytes would be more
> than enough to distinguish between connections.
> I can see the use case for 128 bit connection IDs, but in order to reduce
> the overhead for other applications, we should either do some kind of
> negotiation or a varlen encoding.
>

We already vary the CID length in header (0 bits vs 64 bits), so if we
decide to make a 64/128 switch, I would consider that to be more of just
adding another length option.

v2.23.0 | Report a Bug | By Email