[100] in Hesiod
Re: Creating a new dns class
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Fri Sep 4 18:52:43 1992
Date: Fri, 4 Sep 92 18:49:07 -0400
From: tytso@Athena.MIT.EDU (Theodore Ts'o)
To: joann@cs.wisc.edu
Cc: hesiod@Athena.MIT.EDU
In-Reply-To: Joann J. Ordille's message of Fri, 4 Sep 92 15:59:03 -0500,
Date: Fri, 4 Sep 92 15:59:03 -0500
From: joann@cs.wisc.edu (Joann J. Ordille)
Could someone summarize the pros and cons of creating the "HS" class for me?
In restrospect, I can not think of a single advantage of having a
separate HS class, and it has several disadvantages. One is that having
several classes stresses the most common implementation of the DNS
around (namely, BIND). It has also made it painful since you need to
have new root servers instead of leveraging off of the existing
hierarchy. (No, I haven't forgotten about doing that; it's just been on
a back burner since I've had many other pressing projects on my mind.)
If it weren't for the fact that we have an large installed base and the
compatibility problems would be a real headache, we would probably
switch back to class IN, type TXT for Hesiod.
- Ted
