[10] in Hesiod
Re: question about HS class
daemon@ATHENA.MIT.EDU (pma%hpcndm@hplabs.HP.COM)
Thu Oct 27 10:27:32 1988
To: Win Treese <treese@ATHENA.MIT.EDU>
Cc: hesiod%ATHENA.MIT.EDU%hplabs@hplabs.HP.COM
In-Reply-To: Your message of Wed, 26 Oct 88 23:23:35 -0400.
Date: Thu, 27 Oct 88 08:04:18 MST
From: pma%hpcndm@hplabs.HP.COM
> Technically, the distinction is not strictly
> necessary.
> The second reason is pragmatic. At MIT, normal name resolution (such as
> host addresses) is handled by name servers maintained by MIT Telecommunicatio
ns,
> not by Project Athena. We do not currently maintain Athena hosts in an
> ATHENA.MIT.EDU subdomain of MIT.EDU.
While creating a new class facilitated the development of a new way of
using the name server, it will probably make the general acceptance
much slower. I would expect it to be more common that the name server
administrators maintain TXT data (password entries for instance) than
separate groups maintain TXT data. Since our administrators are
handling more and more machines without more manpower, we have to make
maintenance and set up as simple as possible. I expect it will be hard to
convince them to take the time and effort to set up a new class for
aesthetic reasons.
Don't get me wrong. The name server use provided by the hesiod work is
very very useful. I would like to see it in general use and the easier
it is to set up, the more people will who will use it.
paul
