IETF Logo Mail Archive

Re: [DNSOP] Priming query transport selection

Jaap Akkerhuis <jaap@NLnetLabs.nl> Wed, 13 January 2010 22:02 UTC

Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8D473A6890 for <dnsop@core3.amsl.com>; Wed, 13 Jan 2010 14:02:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 847CfsDqxnj1 for <dnsop@core3.amsl.com>; Wed, 13 Jan 2010 14:02:18 -0800 (PST)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by core3.amsl.com (Postfix) with ESMTP id D6D4B3A683C for <dnsop@ietf.org>; Wed, 13 Jan 2010 14:02:17 -0800 (PST)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.3/8.14.3) with ESMTP id o0DM2ASq022539; Wed, 13 Jan 2010 23:02:10 +0100 (CET) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201001132202.o0DM2ASq022539@bartok.nlnetlabs.nl>
To: Edward Lewis <Ed.Lewis@neustar.biz>
In-reply-to: <a06240801c773e8e88485@[10.31.201.49]>
References: <201001131823.o0DINxYv068180@stora.ogud.com> <a06240801c773e8e88485@[10.31.201.49]>
Comments: In-reply-to Edward Lewis <Ed.Lewis@neustar.biz> message dated "Wed, 13 Jan 2010 16:33:50 -0500."
Date: Wed, 13 Jan 2010 23:02:10 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (bartok.nlnetlabs.nl [127.0.0.1]); Wed, 13 Jan 2010 23:02:10 +0100 (CET)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Priming query transport selection
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 13 Jan 2010 22:02:18 -0000

    
    What does a DNSSEC-protected priming query gain you?

I was about to ask the same question.
    
    Accepting any old priming query and having a root SEP configured, if 
    the query is right all things work.  If the query is wrong/forged you 
    won't get anywhere any how.  (Without going into the weeds here - 
    what if one IP address were forged, what if it were 6, 16, or all of 
    them?)
    
    (13 name servers => 13 A records + 7 AAAA records last check)
    
    Besides the warm and fuzzy feeling, what do you gain? (Keep in mind 
    all of the TCP traffic it would take to get warm and fuzzy.)

I think that this is also discussed in Koch's priming draft.

	jaap

v2.15.0 | Report a Bug | By Email