🚀 go-pugleaf

Mike O'Connor writes:

> Aigh!!  I like mi.org, and its relative flexibility.  I can relocate
> my site within Michigan and not feel compelled to change my name
> 'cause I happen to enter a different city.  The addressing is
> certainly less awkward.

Is this really an issue, though?  How often do most people move?  Or, if it
is the case where a host moves back-and-forth between two cities, for instance,
one could just have two MI.US entries.  Or is this particular example one
where the computer in question is highly mobile?  If so, I'd argue that it
still belongs in MI.US, but perhaps in some sort of domain along the lines
of <host>.MOBILE.MI.US.

> Ahhh...  the three high schools that I see in your DNS seem to be
> under k12.mi.us, rather than some-city.mi.us.  How do the people who
> run .ca feel about a k13.{province}.ca for their high schools?

Right.  The naming scheme is supposed to be <school>.<district>.K12.MI.US.
Right now the ones in Michigan don't have the <district> part, but that
ought to change soon.

> I am not in favor of it.  Of course, I realize that you're doing all
> the work involved -- for our information, how much work IS involved?

Not a whole lot.  I have to add the name to the DNS, and Wes has to add the
name to a list on destroyer.rs.itd.umich.edu in the cases where we provide
the MX host.

I just don't want to see us behind-the-times using something like MI.ORG
when the rest of the country is (slowly) moving towards its respective parts
of the US domain.
-- 
Bryan Beecher, U-M Information Technology Division (+1 313 747 4050)
Domain:	Bryan.Beecher@umich.edu      Path:  ..!uunet!destroyer!bryan