Re: [quicwg/base-drafts] Remove amplification throttle if the server receives Initial that echoes its high entropy SCID. (#3834)

ekr <notifications@github.com> Wed, 08 July 2020 01:33 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 D95753A0CFE for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 18:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 CmJHVpxKZDUd for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 18:33:28 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BFF23A0CF9 for <quic-issues@ietf.org>; Tue, 7 Jul 2020 18:33:28 -0700 (PDT)
Received: from github-lowworker-f1f7af9.ash1-iad.github.net (github-lowworker-f1f7af9.ash1-iad.github.net [10.56.111.13]) by smtp.github.com (Postfix) with ESMTP id 7BC6E6E1198 for <quic-issues@ietf.org>; Tue, 7 Jul 2020 18:33:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594172007; bh=3VODDijFA2v1XxFgpPLGFuKVj1b0Q8W2XfxT+mLSAuU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=abWTbTclYBMekCtFrnRYGTHE1ja2Ks65ZOS3z6cA/6GXnaVjPFLmSDgS9Z5cC22+T +YlI3wJLjOOw1B4paWVdpTy4NM9yZNIimX035fdQGQR2k6pljE3Z1DWbpNCUVLcPlO 4DK5JBcAjCFgOFutF2ezAf4Qb+bdu9g+ahgG4zX8=
Date: Tue, 07 Jul 2020 18:33:27 -0700
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK723BZBGYFEWCAM7WV5CEBWPEVBNHHCN2E4VA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3834/655227174@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3834@github.com>
References: <quicwg/base-drafts/issues/3834@github.com>
Subject: Re: [quicwg/base-drafts] Remove amplification throttle if the server receives Initial that echoes its high entropy SCID. (#3834)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f0522676a719_75ce3fa057acd960294099"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/E76VCpOm0eiNcIt9y2TAFN7i_v0>
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: Wed, 08 Jul 2020 01:33:30 -0000

On Tue, Jul 7, 2020 at 6:26 PM Marten Seemann <notifications@github.com>
wrote:

> This would be conditional on the server choosing a connection ID that has
> enough entropy (we seem to have decided that 64 bits is the benchmark).
> @huitema <https://github.com/huitema> has made the same comment on
> occasion.
>
> How would a client know how what algorithm the server used to generate the
> connection ID?
>
The client doesn't need to know, because it's the server's amplification
limit that is at hand. And right now, the handshake would complete if the
client doesn't do anything, it's just not optimal.

As this seems to be a design issue anyway, here's another proposal: The
> server could send a token in the Initial packet, and the client would then
> use this token on subsequent Initial packets (replacing the token it might
> have used on the packet containing the ClientHello). This way, we'd be
> using a field that's intended to carry a high-entropy value, and not rely
> on a field that the server might not even have control over.
>
I agree that this would work, but it seems like a significantly more
invasive change, especially given the somewhat edge-casey nature of the
issue.


-- 
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/3834#issuecomment-655227174