[quicwg/base-drafts] ICMP and ICMPv6 (Type: DestinationUnreachable) (#377)
Igor Lubashev <notifications@github.com> Thu, 09 March 2017 05:40 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 8F6291297AA for <quic-issues@ietfa.amsl.com>; Wed, 8 Mar 2017 21:40:10 -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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, 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 tvAjas6a0WA6 for <quic-issues@ietfa.amsl.com>; Wed, 8 Mar 2017 21:40:08 -0800 (PST)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [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 1210E1297AC for <quic-issues@ietf.org>; Wed, 8 Mar 2017 21:40:08 -0800 (PST)
Date: Wed, 08 Mar 2017 21:40:07 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489038007; bh=8eO3xWaunVt+FKTq465Rr/GtFoWWoadnefgkpx3TOsY=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=KoB6RjfiaxxcYhWXzgcRBAn1w6tH8kmq8m11jJYux2WJbcq/S3DMg408DX0JRC+Vf mNQhSLDOqP3+pT9YVJUA9CvgZSodixmu+ashFenEsE7XiRuT8q2G1b4l6q3E7p9ZJa ngsicSc/muvJUYYMarHy1fKwus/+EoePKBgib/e4=
From: Igor Lubashev <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/377@github.com>
Subject: [quicwg/base-drafts] ICMP and ICMPv6 (Type: DestinationUnreachable) (#377)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58c0eab741342_235f3fa62f0bbc3c31737"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/dqPfqo-ZZRQ7jyhWLyoy0O7fuVQ>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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, 09 Mar 2017 05:40:10 -0000
This is related to #353. What would we expect endpoints to do upon the receipt of ICMP (or ICMPv6) Type=DestinationUnreachable? For IPv6, that message has a large chunk of the original packet, proving that a path element sent it. For IPv4, there is very little entropy there (just your src port). Can this be as trusted as PUBLIC_RESET by Clients? For IPv4 the answer is likely to be "no". For ipv6, I am not that sure. But there are real implications for clients that cannot just fall back to tcp. If you ignore ICMP and keep retrying the dead server, you are very likely missing an opportunity to switch the server (switch to another IP offered by DNS). If you do not ignore ICMP (especially ICMPv4) and try reopening the connection (using a different server IP), you are allowing using your client in a highly amplified reflection DDOS attack against the sever. The attacker just needs to send you a slow stream of forged ICMP to get you to keep re-opening/re-negotiating connections and retrying expensive requests. -- 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/377
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Martin Thomson
- [quicwg/base-drafts] ICMP and ICMPv6 (Type: Desti… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Martin Thomson
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Martin Thomson
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Martin Thomson
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… MikkelFJ
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… MikkelFJ
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Igor Lubashev
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Martin Thomson
- Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type: D… Martin Thomson