Re: [quicwg/base-drafts] Are random packet number skips still relevant for opportunistic ACK protection? (#1030)
janaiyengar <notifications@github.com> Fri, 12 January 2018 22:16 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 57BC4127444 for <quic-issues@ietfa.amsl.com>; Fri, 12 Jan 2018 14:16:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, 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 rVoAoZ27kWtA for <quic-issues@ietfa.amsl.com>; Fri, 12 Jan 2018 14:16:30 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [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 16D89120721 for <quic-issues@ietf.org>; Fri, 12 Jan 2018 14:16:30 -0800 (PST)
Date: Fri, 12 Jan 2018 14:16:29 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1515795389; bh=Z5RSwIhQnvFD7Zv3GcgrGVw0eCqvaoLLKrZaVmekl+M=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vl6kRkQlYod22WJgNZzhQWMheC0XHWU3s8tsV3/HkVm/+nKjbtB3l9UVfhO/CoX/x fCSEZxbQOGz4HNQ0j8H+b8pskHjbI2trrLa7hgaULe/DaEK9aFSpepZ+fYa9Fj7Mmd fUyXGypvzFbhzGeHk8YXYwZlDTrV6/i8HqweE6jY=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abdb911bc204f8bf7f248203e33073605e6b9a4f7d92cf000000011670f5bd92a169ce10eae4f0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1030/357369666@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1030@github.com>
References: <quicwg/base-drafts/issues/1030@github.com>
Subject: Re: [quicwg/base-drafts] Are random packet number skips still relevant for opportunistic ACK protection? (#1030)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a5933bd6cfb2_2be43ff5bd1aef305657e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/P2y-rTZTBn1JZekotebnPafO61A>
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: Fri, 12 Jan 2018 22:16:32 -0000
@marten-seemann : This optimistic ack attack was one of the motivating reasons for entropy in the old GQUIC. We eventually agreed internally that this wasn't an interesting attack... looking through past work and asking around made it clear that this potential vector, which is present in TCP as well, wasn't interesting enough to be exploited. But, as you note, a sender can always skip a packet number just to test. This doesn't have to be co-ordinated with the receiver, and it needs skipping only a single packet number. -- 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/1030#issuecomment-357369666
- [quicwg/base-drafts] Are random packet number ski… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… Marten Seemann
- Re: [quicwg/base-drafts] Are random packet number… Martin Thomson
- Re: [quicwg/base-drafts] Are random packet number… Marten Seemann
- Re: [quicwg/base-drafts] Are random packet number… Martin Thomson
- Re: [quicwg/base-drafts] Are random packet number… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… Marten Seemann
- Re: [quicwg/base-drafts] Are random packet number… Martin Thomson
- Re: [quicwg/base-drafts] Are random packet number… Marten Seemann
- Re: [quicwg/base-drafts] Are random packet number… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… Marten Seemann
- Re: [quicwg/base-drafts] Are random packet number… janaiyengar
- Re: [quicwg/base-drafts] Are random packet number… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… janaiyengar
- Re: [quicwg/base-drafts] Are random packet number… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… Nick Banks
- Re: [quicwg/base-drafts] Are random packet number… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… ianswett
- Re: [quicwg/base-drafts] Are random packet number… janaiyengar
- Re: [quicwg/base-drafts] Are random packet number… MikkelFJ
- Re: [quicwg/base-drafts] Are random packet number… ianswett
- Re: [quicwg/base-drafts] Are random packet number… ianswett