Re: DNSSEXT Yokohama Minutes

Paul Vixie <paul@vix.com> Mon, 16 September 2002 14:24 UTC

Received: from psg.com (smmsp@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06279 for <dnsext-archive@lists.ietf.org>; Mon, 16 Sep 2002 10:24:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 17qwkH-000Bob-00 for namedroppers-data@psg.com; Mon, 16 Sep 2002 07:21:01 -0700
Received: from as.vix.com ([204.152.187.70]) by psg.com with esmtp (Exim 3.36 #1) id 17qwk9-000BoL-00 for namedroppers@ops.ietf.org; Mon, 16 Sep 2002 07:20:53 -0700
Received: from as.vix.com (localhost [127.0.0.1]) by as.vix.com (Postfix) with ESMTP id D886128B01 for <namedroppers@ops.ietf.org>; Mon, 16 Sep 2002 14:20:52 +0000 (GMT)
From: Paul Vixie <paul@vix.com>
To: namedroppers <namedroppers@ops.ietf.org>
Subject: Re: DNSSEXT Yokohama Minutes
In-Reply-To: Message from Edward Lewis <edlewis@arin.net> of "Sat, 14 Sep 2002 10:44:44 -0400." <a05111b07b9a8fa7d4cff@[193.0.9.238]>
X-Mailer: mh-e 6.0; nmh 1.0.4; Emacs 21.2
Date: Mon, 16 Sep 2002 14:20:52 +0000
Message-Id: <20020916142052.D886128B01@as.vix.com>
X-Spam-Status: No, hits=-2.9 required=5.0 tests=IN_REP_TO, TO_LOCALPART_EQ_REAL version=2.31
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

> >it's starting to seem to me that answers containing NXT should include an
> >SOA in the authority section.  (even though that means nonauthoritative
> >servers will have to cache them, which today is illegal.)  when new secure
> >(verified) data arrives with a later SOA.SERIAL, all the older cached data
> >for that zone becomes invalid.
> 
> NXT's are already supposed to only be signed by the zone key.  Isn't 
> that sufficient to identify the authority - or is there something 
> else needed out of the SOA RR RDATA?

if there's enough info in the signature to be able to tell what other cached
data you should preexpire, then no.  however, i don't think that's the case;
all you can know, afaik, is that the records you're holding were signed less
recently than the records you're now receiving.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>