Re: [DNSOP] Priming query transport selection

Edward Lewis <Ed.Lewis@neustar.biz> Wed, 13 January 2010 21:36 UTC

Return-Path: <Ed.Lewis@neustar.biz>
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 855F33A683C for <dnsop@core3.amsl.com>; Wed, 13 Jan 2010 13:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.67
X-Spam-Level:
X-Spam-Status: No, score=-3.67 tagged_above=-999 required=5 tests=[AWL=-2.929, BAYES_20=-0.74]
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 S7f4+ghdpnVV for <dnsop@core3.amsl.com>; Wed, 13 Jan 2010 13:36:24 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 77C793A679C for <dnsop@ietf.org>; Wed, 13 Jan 2010 13:36:24 -0800 (PST)
Received: from [10.31.201.49] (ns.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o0DLem9E070187; Wed, 13 Jan 2010 16:40:49 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a06240801c773e8e88485@[10.31.201.49]>
In-Reply-To: <201001131823.o0DINxYv068180@stora.ogud.com>
References: <201001131823.o0DINxYv068180@stora.ogud.com>
Date: Wed, 13 Jan 2010 16:33:50 -0500
To: dnsop@ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 66.92.146.20
Cc: ed.lewis@neustar.biz
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 21:36:25 -0000

At 13:19 -0500 1/13/10, Olafur Gudmundsson wrote:

>The benefit is that a single query can retrieve the signed root NS set
>and all the signed glue records.

I am not certain that the cost of doing TCP for this is worth the 
benefit of getting a signed priming response.  I agree with section 
2.4 - no DO bit.

What does a DNSSEC-protected priming query gain you?

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.)

At 16:05 -0500 1/13/10, Olafur Gudmundsson wrote:

>Why not ask for signatures ?

Same reason it is no longer fashionable to include keys in signed 
responses - signatures are a big load.  Yes, you'll know sooner if a 
server's IP address is a problem, but you'd figure it out before it 
mattered anyway (if you ever use that server).
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.