Re: [TLS] PR#28: Converting cTLS to QUIC-style varints

Eric Rescorla <ekr@rtfm.com> Tue, 06 October 2020 03:09 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4D33A0FCA for <tls@ietfa.amsl.com>; Mon, 5 Oct 2020 20:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 4SydTgav7PsS for <tls@ietfa.amsl.com>; Mon, 5 Oct 2020 20:09:33 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 C1F903A0FC7 for <tls@ietf.org>; Mon, 5 Oct 2020 20:09:32 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id m16so7126361ljo.6 for <tls@ietf.org>; Mon, 05 Oct 2020 20:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AAZfwGlc/j156QDH39oB3ZzeBAX9iRm2UmU7bKQzi78=; b=vhYfcj6eHZJV14QLW7tqFw71roA36tloOaguTIvcz9INNPH+Cx8vEVtmA9xRfdbf4o +rSp2u5c2NvdV/lZAQ9D4QSALyG0DojfFdtix4fqApq9PE0CNIcT7ggf77B7tJ6K2mEu mD11ADik5ZJequAqAHc90B5lN4UyAnBucjISlB3NjUIhKD3WQuNedCN7+bLkH0VBBbhD HLMk/i5mYt7yd/6Wzsy1tmn7cSNSLmUDDnX9QDVrf0IJaPxJyUWPjYYEo23bgxBwBlcb E67sRLlFCL9yafhBqoj+2dpKJuMjKrnfHjdj5MW9wM+WFDkcUK1/d1YWERIvQ8Fj1BXL dBNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AAZfwGlc/j156QDH39oB3ZzeBAX9iRm2UmU7bKQzi78=; b=NH5O3ZXbSAC/q4BfpiRxvIHnSdW3Ibr8rJtXBeL9EZ0MQKheNxvFkQbcrFhwgIiXBZ 03GUYQc+POn6/Vwdl1jpt7OpFUXnBWedfxCxknYZC/FKdF2E44wFSXe7cv0inZs7Ewnz kbxsAcldXJ33gbGctpHyZtT+qo0f2xO7zsJqqfdixM8BNgUuVnQZnkx0kOgfwGbAIU2E UpELaSxPYrgA/cHUdMvZZ+GI6fff8GQmYx8R6TKLGVxGiRbc8E0tECfG+/eQXCEQQ4eZ e5bmFpFJ7kLmW/tXtmpMpTV/9yMzhDGeCYpgzZl3cNI19XT7XurFuaqh/1LOlIl21ozP JjyQ==
X-Gm-Message-State: AOAM532uBDcc/THL94/hcS3faSj5jSpFI8noutYb/eI7/i5plVVT3Ed8 FC/uOmS+huPU/6LcFIYsBgLSrVx75Iddv/j89k2ZoQ==
X-Google-Smtp-Source: ABdhPJw4ctyJAYTDDy43QkxvBMZ0duhHysew2k1hRezmYiH/Srpxpjn/dCM9FkOxmdVsXaAHIDqL1tJYzA8aTnWKmKk=
X-Received: by 2002:a2e:b5a2:: with SMTP id f2mr824262ljn.17.1601953770890; Mon, 05 Oct 2020 20:09:30 -0700 (PDT)
MIME-Version: 1.0
References: <CABcZeBPNFhGoLhgqeR9ObwyU68BYq=hXG1PhXcqNsNDNFGGyaw@mail.gmail.com> <CAOYVs2rEDtgJFVpiQkcaaYG2LAyW1hB5Cou4kUoG2_dkxMFTww@mail.gmail.com> <CABcZeBP3BUDEeiV2T-kxYTmC841XE_BrXhPHSoRqfdH0hHd-6w@mail.gmail.com> <BBA456AB-EC42-47DD-A3E3-5FC0E9E7A534@akamai.com> <CAOYVs2r+AiEs0q6sybqT2CbtLtj4KE4onr-3qjr5vZ5RFPiKOQ@mail.gmail.com>
In-Reply-To: <CAOYVs2r+AiEs0q6sybqT2CbtLtj4KE4onr-3qjr5vZ5RFPiKOQ@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 5 Oct 2020 20:08:54 -0700
Message-ID: <CABcZeBNQ3tk-rGpdJ88q0oaUXXq4B7NQWKp8P8uQOyxA7Lwstg@mail.gmail.com>
To: Marten Seemann <martenseemann@gmail.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000075feac05b0f7edfe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/WyhnN6H52nkL1szZru2fbV6c7vc>
Subject: Re: [TLS] PR#28: Converting cTLS to QUIC-style varints
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 03:09:34 -0000

I don't have a strong opinion on whether to require a minimal encoding, but
if we're not going to use QUIC's encoding as-is, then I would rather stick
with the existing scheme, which has twice as large a range for the 1 byte
encoding and is thus more compact for a range of common cases.

-Ekr


On Mon, Oct 5, 2020 at 7:31 PM Marten Seemann <martenseemann@gmail.com>
wrote:

> In that case, why use QUIC's encoding at all? It would just put the burden
> on the receiver to check that the minimal encoding was used.
> Would it instead make more sense to modify QUIC's encoding, such that the
> 2-byte encoding doesn't encode the numbers from 0 to 16383, but the numbers
> from 64 to (16383 + 64), and equivalently for 4 and 8-byte encodings?
>
> On Tue, Oct 6, 2020 at 9:22 AM Salz, Rich <rsalz@akamai.com> wrote:
>
>> Can you just say “QUIC rules but use the minimum possible length”?
>>
>