IETF Logo Mail Archive

Re: [quicwg/base-drafts] Why are stateless reset tokens 16 bytes long? (#2018)

Kazuho Oku <notifications@github.com> Sat, 17 November 2018 08:43 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 D9E91127148 for <quic-issues@ietfa.amsl.com>; Sat, 17 Nov 2018 00:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-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 xK7wtMvfSvUz for <quic-issues@ietfa.amsl.com>; Sat, 17 Nov 2018 00:43:55 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14ECD12008A for <quic-issues@ietf.org>; Sat, 17 Nov 2018 00:43:55 -0800 (PST)
Date: Sat, 17 Nov 2018 00:43:53 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542444233; bh=+s72pgcQlvchs+rVcpUDyCr5fJ8m94TiZpLP4VlsLl4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FCPpHDGJdO+lWf9EhPqrb+rVu2J7k2IKYRsSeRjXf17/nyAqdu73SYl6I5t43QcrA GY+GJyE3OtGPxJ8gIT9iFVv8/Bx9jwtac0MXhHDxnNdvSmlrVCqJ223ydAmYuTPQTq JhV3Ho5IEpZSYAdFo8UpBAyLgXKFF5dsAnzcFmN8=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab24975e52007dd43193282d9f5e462cd2e6a1a65792cf00000001180796c992a169ce16c2396c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2018/439600762@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2018@github.com>
References: <quicwg/base-drafts/issues/2018@github.com>
Subject: Re: [quicwg/base-drafts] Why are stateless reset tokens 16 bytes long? (#2018)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5befd4c9bb6b9_1743fb2a56d45c45754b0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/_sdGODx44YQJf5mTUsS3lssyUIY>
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: Sat, 17 Nov 2018 08:43:57 -0000

If the concern is about the overhead of the Stateless Reset Token field of the NEW_CONNECTION_ID frame, the other option might be to make the field optional. I am not sure why the field is mandatory, even though not all endpoints are required to send Stateless Resets.

Conveniently, once #2006 gets merged, the Length field of the Stateless Reset Token field would be the only field we use a 8-bit encoding for Connection ID Length. We can change it to a 4-bit encoding for consistency, and will have 4 bits to encode flags...

-- 
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/2018#issuecomment-439600762

v2.27.8 | Report a Bug | By Email | System Status