[quicwg/base-drafts] Handling of duplicate packets (#1405)
Magnus Westerlund <notifications@github.com> Thu, 31 May 2018 08:03 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 B4CEA12EAE0 for <quic-issues@ietfa.amsl.com>; Thu, 31 May 2018 01:03:58 -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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 PHG--cZpFwZ1 for <quic-issues@ietfa.amsl.com>; Thu, 31 May 2018 01:03:56 -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 D8E3412E046 for <quic-issues@ietf.org>; Thu, 31 May 2018 01:03:55 -0700 (PDT)
Date: Thu, 31 May 2018 01:03:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527753834; bh=BsiOjf0jer5snAZ0hxxCodfdfWM99lQP5UZvODOdFc0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=cAo+EUQWWsbpmft0wVmYPLbSJBAMpCEk5eoM9X79I1D75SP8Jab5HljdXhdm6lL+i cC9HkWWg6g+JT0KpLmFMH7HylAB0/dHV0tYk9PxAQTKNCV7UIqP3AkbrGl3HZ2nRu7 LISBSlYC2PHQwulRSAQXtM9HpVha/KIDhXw2ZjbY=
From: Magnus Westerlund <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab086f34c138f466f99b6fc362448227a1c6c2b2b992cf0000000117276e6a92a169ce138d6870@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1405@github.com>
Subject: [quicwg/base-drafts] Handling of duplicate packets (#1405)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b0fac6a16d5e_29623f8ea08d6f80116273"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gloinul
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/Z1jlyslB7Vpg7Q1dEG8L3CTKfjo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 31 May 2018 08:03:59 -0000
Packet duplication sometimes occur and it has a potential for affecting the ECN counter for what markings that arrive within a connection. Thus, it would be good if the requirements on how a QUIC implementation handle packets that are detected as duplicates. There also appear that there are current text in the transport draft that makes assumption about handling of duplicate packets: 6.10.4.1. Detecting a Stateless Reset A client detects a potential stateless reset when a packet with a short header either cannot be decrypted or is marked as a duplicate packet. The other mention of packet duplication, also pointing to an action that is this: 6.8.3.2. Handling Address Spoofing by an On-path Attacker An on-path attacker could cause a spurious connection migration by copying and forwarding a packet with a spoofed address such that it arrives before the original packet. The packet with the spoofed address will be seen to come from a migrating connection, and the original packet will be seen as a duplicate and dropped. These two pieces appear to indicate that packet duplicates should: 1. Be detected by receiver, at least within the window of PN between highest seen and some window into the past. 2. The packet marked as duplicate 3. Duplicate are dropped, but only after having been somewhat processed (see 6.10.4.1). To my understanding the smallest window a receiver could have for tracking packets, is what is in ACKs that hasn't been ACKed yet. But that could be extremely short into the past, which could be short in time, compared to the expected re-ordering or packet life time in the network. Independently of window size, if a packet would arrive with a PN that is prior to the current window the receiver have, the receiver has discard the state for the packet number, and thus can't determine if it was ACKed or not, and thus needs to be discarded without further processing. Is that correctly assumed. Thus, it would be good if these assumptions and needed functionality was collected in its own paragraphs somewhere in the specification. >From an ECN perspective, the current thinking is that the ECN marking of a duplicate will simply be ignored. We want to avoid adding duplicates in the counter, as it will increase the uncertainty of the validation of the correct marking. -- 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/1405
- Re: [quicwg/base-drafts] Handling of duplicate pa… Kazuho Oku
- Re: [quicwg/base-drafts] Handling of duplicate pa… Magnus Westerlund
- Re: [quicwg/base-drafts] Handling of duplicate pa… Magnus Westerlund
- Re: [quicwg/base-drafts] Handling of duplicate pa… Kazuho Oku
- Re: [quicwg/base-drafts] Handling of duplicate pa… MikkelFJ
- Re: [quicwg/base-drafts] Handling of duplicate pa… MikkelFJ
- Re: [quicwg/base-drafts] Handling of duplicate pa… Magnus Westerlund
- Re: [quicwg/base-drafts] Handling of duplicate pa… MikkelFJ
- Re: [quicwg/base-drafts] Handling of duplicate pa… Magnus Westerlund
- Re: [quicwg/base-drafts] Handling of duplicate pa… Kazuho Oku
- Re: [quicwg/base-drafts] Handling of duplicate pa… Christian Huitema
- [quicwg/base-drafts] Handling of duplicate packet… Magnus Westerlund
- Re: [quicwg/base-drafts] Handling of duplicate pa… Mike Bishop
- Re: [quicwg/base-drafts] Handling of duplicate pa… Mike Bishop
- Re: [quicwg/base-drafts] Handling of duplicate pa… ianswett
- Re: [quicwg/base-drafts] Handling of duplicate pa… Martin Thomson
- Re: [quicwg/base-drafts] Handling of duplicate pa… Kazuho Oku
- Re: [quicwg/base-drafts] Handling of duplicate pa… Martin Thomson
- Re: [quicwg/base-drafts] Handling of duplicate pa… Kazuho Oku
- Re: [quicwg/base-drafts] Handling of duplicate pa… Magnus Westerlund
- Re: [quicwg/base-drafts] Handling of duplicate pa… Kazuho Oku
- Re: [quicwg/base-drafts] Handling of duplicate pa… Martin Thomson