TKEY compatibility problems

"D. J. Bernstein" <djb@cr.yp.to> Thu, 12 July 2001 23:33 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA12660 for <dnsext-archive@lists.ietf.org>; Thu, 12 Jul 2001 19:33:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1) id 15KpfA-000ISO-00 for namedroppers-data@psg.com; Thu, 12 Jul 2001 16:14:28 -0700
Received: from rip.psg.com ([147.28.0.39] ident=exim) by psg.com with esmtp (Exim 3.31 #1) id 15KpfA-000ISI-00 for namedroppers@ops.ietf.org; Thu, 12 Jul 2001 16:14:28 -0700
Received: from randy by rip.psg.com with local (Exim 3.30 #1) id 15KpfA-0001UF-00 for namedroppers@ops.ietf.org; Thu, 12 Jul 2001 16:14:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: "D. J. Bernstein" <djb@cr.yp.to>
To: namedroppers@ops.ietf.org
Subject: TKEY compatibility problems
References: <E15KlKU-000DVy-00@psg.com> <E15KnUL-000Fe0-00@psg.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Message-Id: <E15KpfA-000ISO-00@psg.com>
Date: Thu, 12 Jul 2001 16:14:28 -0700
Content-Transfer-Encoding: 7bit

Brian Wellington writes:
> I'm saying that your server will cache the
> records, which could lead to strange results in the future.

I don't know what you mean by ``strange.'' Is there a problem, or not?
Will a TKEY-aware client have trouble if I forward it a copy of a TKEY
record that someone else spontaneously sent me?

If so, the TKEY extension is broken. You said that TKEY servers could
spontaneously send TKEY records. Forwarding the records---treating them
as zone data---is indisputably correct behavior for my cache. See RFC
1123 section 6.1.3.5. See also http://cr.yp.to/djbdns/newtypes.html.

If, on the other hand, there is no problem, then why did you claim that
my AXFR client shouldn't forward the records?

---Dan


to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.