Re: [dnsext] Fwd: RFC 2308 & RFC 4035

Edward Lewis <Ed.Lewis@neustar.biz> Sat, 26 February 2011 15:50 UTC

Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B05783A6924 for <dnsext@core3.amsl.com>; Sat, 26 Feb 2011 07:50:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 N91KJCWIVfAB for <dnsext@core3.amsl.com>; Sat, 26 Feb 2011 07:50:41 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id BC9693A682C for <dnsext@ietf.org>; Sat, 26 Feb 2011 07:50:40 -0800 (PST)
Received: from Work-Laptop-2.local (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p1QFpSHc063532; Sat, 26 Feb 2011 10:51:29 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [192.168.1.103] by Work-Laptop-2.local (PGP Universal service); Sat, 26 Feb 2011 10:51:34 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Sat, 26 Feb 2011 10:51:34 -0500
Mime-Version: 1.0
Message-Id: <a06240800c98ed0f7a8c5@[10.31.200.114]>
In-Reply-To: <20110226003214.0E1BFAFA28D@drugs.dv.isc.org>
References: <a06240805c98db61801c2@[10.31.200.114]> <20110226003214.0E1BFAFA28D@drugs.dv.isc.org>
Date: Sat, 26 Feb 2011 10:50:32 -0500
To: Mark Andrews <marka@isc.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, dnsext@ietf.org
Subject: Re: [dnsext] Fwd: RFC 2308 & RFC 4035
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Feb 2011 15:50:42 -0000

At 11:32 +1100 2/26/11, Mark Andrews wrote:
>Nothing worse than having asked for the AAAA record at 10:00 am.
>The zone administrator has to assume that AAAA queries will have
>been made prior to adding the AAAA records.  This will almost
>certainly be the case if there were A queries.

I think my question wasn't understood.

Do cache implementers use the fact that the proof of no A record 
coincidently shows there is also no AAAA record when processing a 
subsequent AAAA query.  (Meaning, there's no other entry for the AAAA 
alredy in the cache.)

If a cache does do this kind of proof by inference, what does the 
implementer think about the situation in which there is a "race 
condition" - that the proof of non-existence has been obviated by 
actions outside of it's sphere?  (Like the subsequent adding of the 
AAAA set in the authority.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Me to infant son: "Waah! Waah! Is that all you can say?  Waah?"
Son: "Waah!"