Re: [dnsext] need new flag bit in EDNS, "do me no favours" (DMNF)

David Conrad <drc@virtualized.org> Mon, 25 October 2010 20:39 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DB6F3A6897; Mon, 25 Oct 2010 13:39:27 -0700 (PDT)
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 GcjavW1VU5hV; Mon, 25 Oct 2010 13:39:23 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 74D703A6B65; Mon, 25 Oct 2010 13:39:04 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1PATjF-000Axi-PD for namedroppers-data0@psg.com; Mon, 25 Oct 2010 20:33:13 +0000
Received: from trantor.virtualized.org ([204.152.189.190] helo=virtualized.org) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <drc@virtualized.org>) id 1PATjB-000Awn-Tv for namedroppers@ops.ietf.org; Mon, 25 Oct 2010 20:33:10 +0000
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id 40124EE17A7; Mon, 25 Oct 2010 13:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83nAsmporq1Y; Mon, 25 Oct 2010 13:33:05 -0700 (PDT)
Received: from [64.9.242.111] (unknown [64.9.242.111]) by virtualized.org (Postfix) with ESMTP id 3E248EE179C; Mon, 25 Oct 2010 13:33:05 -0700 (PDT)
Subject: Re: [dnsext] need new flag bit in EDNS, "do me no favours" (DMNF)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: David Conrad <drc@virtualized.org>
In-Reply-To: <alpine.LFD.1.10.1010251302160.6683@newtla.xelerance.com>
Date: Mon, 25 Oct 2010 13:32:58 -0700
Cc: "namedroppers@ops.ietf.org WG" <namedroppers@ops.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <ED683A32-D4E1-49EA-AC87-7B5E3C1106E1@virtualized.org>
References: <C8EA875A.83BA%roy@nominet.org.uk> <8D01F5E3-F863-4873-BB0E-654FA89983F7@virtualized.org> <alpine.LFD.1.10.1010251302160.6683@newtla.xelerance.com>
To: Paul Wouters <paul@xelerance.com>
X-Mailer: Apple Mail (2.1081)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

Paul,

On Oct 25, 2010, at 10:05 AM, Paul Wouters wrote:
> unbound already supports a changing forwarder statement via unbound-control, and

> even deals with the forwarder changing between DNSSEC (in)capable forwarders. And
> it also detects stripped DNSSEC data.

Wouldn't this mean the application has to know that it is behind a forwarder?  If it isn't (or it can't figure out if it is), it'll have to implement the full iterative resolver goop.  As such, I'd think the safe approach for application developers would be to link in the full iterative resolver library into the application.  

Regards,
-drc