Re: TKEY compatibility problems
Brian Wellington <Brian.Wellington@nominum.com> Sat, 14 July 2001 01:44 UTC
Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA15274 for <dnsext-archive@lists.ietf.org>; Fri, 13 Jul 2001 21:44:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1) id 15LDdz-0002Xy-00 for namedroppers-data@psg.com; Fri, 13 Jul 2001 17:50:51 -0700
Received: from rip.psg.com ([147.28.0.39] ident=exim) by psg.com with esmtp (Exim 3.31 #1) id 15LDdz-0002Xs-00 for namedroppers@ops.ietf.org; Fri, 13 Jul 2001 17:50:51 -0700
Received: from randy by rip.psg.com with local (Exim 3.31 #1) id 15LDdz-000BEZ-00 for namedroppers@ops.ietf.org; Fri, 13 Jul 2001 17:50:51 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: Brian Wellington <Brian.Wellington@nominum.com>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: namedroppers@ops.ietf.org
Subject: Re: TKEY compatibility problems
In-Reply-To: <E15KpfA-000ISO-00@psg.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Message-Id: <E15LDdz-0002Xy-00@psg.com>
Date: Fri, 13 Jul 2001 17:50:51 -0700
Content-Transfer-Encoding: 7bit
On Thu, 12 Jul 2001, D. J. Bernstein wrote: > 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? There would be a problem if a client was sanity checking the response of an ANY query, and saw a TKEY record in the answer section. Seeing a meta-type where it's not expected is bad. > 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. A spontaneous TKEY will only be in the additional section, which means that it shouldn't be treated as zone data. If it was in the answer section, I'd agree that it would be zone data, and that it is a broken extension. > If, on the other hand, there is no problem, then why did you claim that > my AXFR client shouldn't forward the records? Because they're not part of the zone, as indicated by the fact that they're in the additional section. Brian to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body.
- Re: RFC 2119 section 6 Alan Barrett
- Re: RFC 2119 section 6 D. J. Bernstein
- Re: RFC 2119 section 6 Brian Wellington
- Re: RFC 2119 section 6 Brian Wellington
- TKEY compatibility problems D. J. Bernstein
- Re: TKEY compatibility problems D. J. Bernstein
- Re: RFC 2119 section 6 Kevin Darcy
- Re: RFC 2119 section 6 Brian Wellington
- Re: TKEY compatibility problems Andreas Gustafsson
- Re: RFC 2119 section 6 D. J. Bernstein
- Re: TKEY compatibility problems D. J. Bernstein
- Re: RFC 2119 section 6 Kevin Darcy
- Re: TKEY compatibility problems Robert Elz
- Re: RFC 2119 section 6 Kevin Darcy
- Re: RFC 2119 section 6 Kevin Darcy
- Re: TKEY compatibility problems Robert Elz
- Re: TKEY compatibility problems Brian Wellington
- Re: TKEY compatibility problems Kevin Darcy
- Re: RFC 2119 section 6 D. J. Bernstein
- Re: TKEY compatibility problems D. J. Bernstein
- Re: TKEY compatibility problems Kevin Darcy
- Re: TKEY compatibility problems D. J. Bernstein
- Re: TKEY compatibility problems D. J. Bernstein
- Re: TKEY compatibility problems D. J. Bernstein
- Re: TKEY compatibility problems Kevin Darcy
- AXFR extensibility Andreas Gustafsson
- Re: RFC 2119 section 6 Robert Elz