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

martinduke <notifications@github.com> Fri, 13 September 2019 21:26 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 8BB46120846 for <quic-issues@ietfa.amsl.com>; Fri, 13 Sep 2019 14:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level:
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 h8RoF5ZezoPl for <quic-issues@ietfa.amsl.com>; Fri, 13 Sep 2019 14:26:57 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B2C41201DB for <quic-issues@ietf.org>; Fri, 13 Sep 2019 14:26:57 -0700 (PDT)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id 9E78A2C0E3C for <quic-issues@ietf.org>; Fri, 13 Sep 2019 14:26:56 -0700 (PDT)
Date: Fri, 13 Sep 2019 14:26:56 -0700
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2HKQSCHMZVGIZ5I4F3RFFDBEVBNHHB22URPQ@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@github.com>
Subject: [quicwg/base-drafts] Detectable Stateless Resets (#3032)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d7c09a090e45_9493fd63cacd968201f5"; 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/Ncf_W19kbKeCwwFbnOoYOySzmXk>
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: Fri, 13 Sep 2019 21:27:04 -0000

What are the implications of some stateless resets being detectable? The new language explicitly allows a situation where a host chooses not to pad out all its packets to include the length of its own connection ID. In this situation, a small packet could trigger a stateless reset from the peer that is too small to be anything other than a stateless reset.

I don't believe this will happen "all the time", as in general Server CIDL > Client CIDL and in general servers are the ones sending resets. Those are somewhat weak assumptions for reasons we can bracket for now, but I feel confident that the detectable reset will happen in the internet, at least occasionally. What is the threat model we feared when we put in the original rules to block reset detection, and do the concerns apply here?

-- 
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