IETF Logo Mail Archive

Re: [quicwg/base-drafts] QUIC Version Ossification (#2496)

Christian Huitema <notifications@github.com> Thu, 23 May 2019 10:20 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 320E812002F for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 03:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 LXTmt6xwFmkq for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 03:20:36 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDCB4120045 for <quic-issues@ietf.org>; Thu, 23 May 2019 03:20:35 -0700 (PDT)
Date: Thu, 23 May 2019 03:20:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558606834; bh=EOVORAe0iJFy8iPerDLeV0znfntKqmFe/RyNUp5CqAg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=v3ZbNO3zCGvXh+2nMbE+S7aN7wkWLbtydAkUTtacZ2qZHyYin/rd87P0akRP/CPPQ ZADmM7dqnd4nSJqkLFm1C+xP9IjP1AqjWwelufgKRXjyGtXjeg/MQINjn1k3pmz3Po HMg77VWBPrTwUUAYOak0ThswkCQbdM8odJiLXacA=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYTGTG5UCSF5ZSP65N26OTHFEVBNHHBRWZGVA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2496/495159944@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2496@github.com>
References: <quicwg/base-drafts/issues/2496@github.com>
Subject: Re: [quicwg/base-drafts] QUIC Version Ossification (#2496)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce673f2af746_53fc3fa813ccd9682390a6"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/o6i5Odd4-zMPecNIwcW9iRsEipc>
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, 23 May 2019 10:20:37 -0000

I am trying to summarize the set of version obfuscation proposals. I believe we have:

1) Natural versions. Just define a version 2, maybe 1bis, very quickly, and actually use version negotiation.

2) Server specific version aliases,as specified in #2573

3) Version based obfuscation and trial decryption, as proposed by David Benjamin and explained on this thread

4) Introduce a "QUIC Version" TLS extension, sent either in the clear or passed as an encrypted extension to the ESNI content.

There are pros and cons to each of those:

proposal | Pros | Cons 
--- | --- | ---
Natural version | Very little code required | Still risk of ossification
Server defined aliases | Robust prevention | Does not protect 1st packet; Requires caching code; May enable tracing
Version based obfuscation | Robust prevention | Requires trial decryption
TLS extension | Can be encrypted | Requires ESNI


-- 
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/2496#issuecomment-495159944

v2.14.0 | Report a Bug | By Email