IETF Logo Mail Archive

Re: [DNSOP] draft-ietf-dnsop-no-response-issue-03

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 25 August 2016 19:20 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F04A712D11C for <dnsop@ietfa.amsl.com>; Thu, 25 Aug 2016 12:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level:
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548] 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 pmZK4QWLZrjR for <dnsop@ietfa.amsl.com>; Thu, 25 Aug 2016 12:20:01 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21BED12B024 for <dnsop@ietf.org>; Thu, 25 Aug 2016 12:20:01 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 24A342806BB; Thu, 25 Aug 2016 21:19:59 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 15F4A2806B4; Thu, 25 Aug 2016 21:19:59 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay2.nic.fr (Postfix) with ESMTP id 11F67B3800C; Thu, 25 Aug 2016 21:19:29 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 01CED406BA; Thu, 25 Aug 2016 21:19:28 +0200 (CEST)
Date: Thu, 25 Aug 2016 21:19:28 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Marek Vavruša <mvavrusa@cloudflare.com>
Message-ID: <20160825191928.mze4bbzypq2ml2uv@nic.fr>
References: <BC3FCB73-3ECA-4374-8AD5-845A452B6835@icann.org> <20160825043551.GP4670@mournblade.imrryr.org> <20160825072545.36iklvmpcfcpqawg@nic.fr> <CACfw2hjDNQcZo1To2wv=oAhDF1avDwJvA1myG4NgyYjRF95zSg@mail.gmail.com> <alpine.DEB.2.11.1608251203310.14525@grey.csi.cam.ac.uk> <CACfw2hguojqbictc0RvLFQiY=1BVdQ+qA0Ot_ztdZEndHUy+Hg@mail.gmail.com> <alpine.DEB.2.11.1608251719360.2933@grey.csi.cam.ac.uk> <CAC=TB12DFHmAndeb3fJNYr1sdS6U4GOrAoKZHZUcMfh7WXmrJA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAC=TB12DFHmAndeb3fJNYr1sdS6U4GOrAoKZHZUcMfh7WXmrJA@mail.gmail.com>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.6.0-1-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.6.2-neo (2016-07-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zmWY1e8GpaNuz4Y232HknXRFVCg>
Cc: Tony Finch <dot@dotat.at>, dnsop <dnsop@ietf.org>, william manning <chinese.apricot@gmail.com>
Subject: Re: [DNSOP] draft-ietf-dnsop-no-response-issue-03
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 19:20:03 -0000

On Thu, Aug 25, 2016 at 11:11:22AM -0700,
 Marek Vavruša <mvavrusa@cloudflare.com> wrote 
 a message of 56 lines which said:

> +1, there are other implications besides performance. For example
> attacker can silence
> the NS for victim (either on path or off path with spoofed source
> subnet). If successful,
> the attacker doesn't have to race NS->victim RTT anymore for
> successful cache poisoning.

Which is exactly the attack explained in the OARC talk I cited a few
emails before.

v2.23.0 | Report a Bug | By Email