IETF Logo Mail Archive

Re: [quicwg/base-drafts] Detectable Stateless Resets (#3032)

martinduke <notifications@github.com> Thu, 19 September 2019 17:02 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 3966A12081A for <quic-issues@ietfa.amsl.com>; Thu, 19 Sep 2019 10:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 wgDlVlA2PXeq for <quic-issues@ietfa.amsl.com>; Thu, 19 Sep 2019 10:02:10 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B46C1202A0 for <quic-issues@ietf.org>; Thu, 19 Sep 2019 10:02:10 -0700 (PDT)
Date: Thu, 19 Sep 2019 10:02:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1568912529; bh=A7IL6Mr7WYs879oL2lWoHNujMuwDrgNSyaheDMF5kKE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XsJ2I2ct9TLh9VaG8hZHKebaPAS8ccyq/zfsyH2e2tRM1+5K1IIRk2SKWuQWOtYTt 6Aot4Xei7sYUiY45fCqV3wnZNFZyxbMsUFQjgDGcjTxmy1ML1gognPtssfGsZI7cnx tBhKWEU+35RiORnc6ovKuj4w0bGwCEPFSKI+yDEo=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4BOXT2YUW6PSF6S5N3SD2SDEVBNHHB22URPQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3032/533221421@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3032@github.com>
References: <quicwg/base-drafts/issues/3032@github.com>
Subject: Re: [quicwg/base-drafts] Detectable Stateless Resets (#3032)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d83b491808a6_5e6e3f953b4cd96014267f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/_LZjfk0a4Hjy5pjQjlZZN6Jh7Uw>
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, 19 Sep 2019 17:02:12 -0000

I guess the embedded assumption is that the following scenario does not become prevalent in the internet:
- Server infrastructures generally do not support migration, meaning a 4-tuple based architecture is satisfactory;
- As CIDs are irrelevant to switching, servers choose short CIDs, specifically to enable stateless reset; and
- Clients generally do not take care to pad their small packets

It's hard to predict the future, but if the internet evolves this way we'll have enabled some bad outcomes. I'm disinclined to change the spec at this time, but we should aware of the implications of this evolution if it occurs.

Unless I've gotten someone more concerned than I am, I believe it's OK to close this issue. I'll do so in a couple of days if no one pipes up.

-- 
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/3032#issuecomment-533221421

v2.23.0 | Report a Bug | By Email