[quicwg/base-drafts] Method for associating stateless resets with connections is unclear (#2591)
Benjamin Saunders <notifications@github.com> Mon, 08 April 2019 01:43 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 3B1921201C9 for <quic-issues@ietfa.amsl.com>; Sun, 7 Apr 2019 18:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 esxeHRK5i7HO for <quic-issues@ietfa.amsl.com>; Sun, 7 Apr 2019 18:43:45 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 109941201C2 for <quic-issues@ietf.org>; Sun, 7 Apr 2019 18:43:45 -0700 (PDT)
Date: Sun, 07 Apr 2019 18:43:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554687823; bh=rhBxUj0Vb5niiP/4TvZekI+OrN01Vea2cWKZKIk+z8E=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=HeQ/WU3wNP5meXjIFORi/PD0u18B2psI1/BIIcU9R/pNObLK0ImgTWgvH9QZF2KUY gcVkEzEgBHugGIZ590/ccCnmKXPT1Rdx7ew1lHnJg0vqKbrsBNWH2mT1AAM4HsCFbq +Hez8bBY3gJdHV4f9YiwPWBPftOkgXXNsdoCjovE=
From: Benjamin Saunders <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab213b6278b47d3c4f84ab2cc4d7f299d54fdbb4a692cf0000000118c2694f92a169ce19a4a73d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2591@github.com>
Subject: [quicwg/base-drafts] Method for associating stateless resets with connections is unclear (#2591)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5caaa74f912b0_67403fbff74d45bc32825a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: Ralith
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/zhiQHd9Kwx7TwXvmipx2rqfwx_U>
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: Mon, 08 Apr 2019 01:43:47 -0000
Relevant sections: [§10.4](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#stateless-reset): > An endpoint that receives a packet where removal of packet protection fails MUST check the last 16 bytes of that packet [§10.4.1](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#detecting-a-stateless-reset) > An endpoint detects a potential stateless reset when a incoming packet with a short header either cannot be associated with a connection, cannot be decrypted, or is marked as a duplicate packet. The endpoint then compares the last 16 bytes of the packet with the Stateless Reset Token provided by its peer There is no single token that a packet which cannot be associated with a connection can be compared against, and although §10.4 could be read as a suggestion that decryption should be attempted first, this is impossible if the associated connection is unknown. Connections with non-zero-length IDs cannot be identified by remote address, as multiple connections may share the same remote address. The obvious approach here is to maintain a look-up table mapping stateless reset tokens to connections, and consult it on receipt of a packet that cannot be associated with a connection, perhaps after first ensuring that the packet originates from a known remote address. Should this be made explicit? -- 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/2591
- Re: [quicwg/base-drafts] Method for associating s… Benjamin Saunders
- Re: [quicwg/base-drafts] Method for associating s… Benjamin Saunders
- Re: [quicwg/base-drafts] Method for associating s… Kazuho Oku
- Re: [quicwg/base-drafts] Method for associating s… Martin Thomson
- [quicwg/base-drafts] Method for associating state… Benjamin Saunders
- Re: [quicwg/base-drafts] Method for associating s… Martin Thomson
- Re: [quicwg/base-drafts] Method for associating s… Lars Eggert