Re: RFC 2119 section 6
"D. J. Bernstein" <djb@cr.yp.to> Wed, 11 July 2001 01:28 UTC
Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA02718 for <dnsext-archive@lists.ietf.org>; Tue, 10 Jul 2001 21:28:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1) id 15K8Yt-000IXm-00 for namedroppers-data@psg.com; Tue, 10 Jul 2001 18:13:07 -0700
Received: from mpfg.attlabs.net ([12.106.35.2] helo=roam.psg.com) by psg.com with esmtp (Exim 3.31 #1) id 15K8Ys-000IWP-00 for namedroppers@ops.ietf.org; Tue, 10 Jul 2001 18:13:06 -0700
Received: from randy by roam.psg.com with local (Exim 3.30 #1) id 15K8YT-000H9q-00 for namedroppers@ops.ietf.org; Tue, 10 Jul 2001 18:12:41 -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: Re: RFC 2119 section 6
References: <E15HsNZ-0002Ru-00@psg.com> <E15I6RE-0008P8-00@psg.com> <E15IDD0-000J0d-00@psg.com> <E15IEZl-000LJv-00@psg.com> <E15IMxJ-000ACJ-00@psg.com> <E15Ie0n-000H8P-00@psg.com> <E15Ikad-0003j0-00@psg.com> <E15JxhS-000Kro-00@psg.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Message-Id: <E15K8Yt-000IXm-00@psg.com>
Date: Tue, 10 Jul 2001 18:13:07 -0700
Content-Transfer-Encoding: 7bit
Kevin Darcy writes: > TSIG and EDNS0 are already with us, and as far as I know it is legal > for either or both to be transmitted in an AXFR response Only by bilateral agreement. > are you seriously suggesting that we already need 2 new port > assignments, with more to be obtained as new extensions are adopted? Of course not. You could easily squeeze the entire OSI protocol suite into a protocol running on a single TCP port. You have to be careful, however, if you want to use port 25, or port 80, or port 53. You have to maintain compatibility with the installed base. That's why protocol designers often use new ports. Terrified of new ports? Fine. Use a new EXFR query type. This is not rocket science. > you have IMO fallen far short of demonstrating that > "section-agnosticism" has any practical value I have thousands of sites whose adminitsrators don't want to be forced to upgrade their working DNS software. If you don't think compatibility has ``practical value,'' you're an idiot. ---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.
- 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