[34] in North American Network Operators' Group
Re: US Domain -- County Delegations
daemon@ATHENA.MIT.EDU (Mike Lawrie)
Thu Jul 27 05:22:30 1995
From: mlawrie@apies.frd.ac.za (Mike Lawrie)
To: michael@memra.com (Michael Dillon)
Date: Thu, 27 Jul 1995 11:14:48 +0200 (EET)
Cc: paul@vix.com, usdomreg@isi.edu, nanog@merit.edu
In-Reply-To: <Pine.LNX.3.91.950726233455.14544L-100000@okjunc.junction.net> from "Michael Dillon" at Jul 26, 95 11:46:32 pm
Michael Dillon writes:-
> I think the key is to let people choose. The county name system and the
> .FAM system do not give people a choice. If cousin Ned wants to be in the
> .KLINGON domain and Aunt Sarah wants to be in the .SEWMISTRESS domain,
> why not let them? Realistically, in order to keep the root under control
> these should be .KLINGON.ROLE and .SEWMISTRESS.ROLE but maybe Aunt Martha
> is happy with the .SMITH.FAM domain.
Hmm. If you are looking for ideas (who said that they had to be good?
what's good about a geographic/city split anyway?), why not have
<SURNAME>.US, and let the family tree start to hang together. If there
are, say, too many DILLON.US branches of the family, then the Dillons
themselves can split this by whatever method suits them. If there are
strong ties with those Dillons who arrived in 1687, then 1687.DILLON.US
could be used, if the Dillons in Boston form a unit, then
BOSTON.DILLON.US and so what if someone moves out of Boston, they still
have the same family relationship.
Mike
--
Mike Lawrie <mlawrie@apies.frd.ac.za>
Manager: Uninet Ph: +27 12 841 3542
Foundation for Research Development Fx: +27 12 804 2679
P O Box 2600, Pretoria 0001, RSA ^^ +27 12 349-1179 sometime in 1995
