From: tonyd@ssc60.sbwk.nj.us (Tony DeBari)
Newsgroups: comp.bbs.waffle,comp.mail.uucp
Subject: Re: Mixed format addresses
Date: Sun, 20 Dec 92 02:25:58 EST
Organization: Lost In Space

dan@dribble.c-mols.siu.edu (Dan Ellison) writes:

> In <lgXLrA1BBh107h@ssc60.sbwk.nj.us> tonyd@ssc60.sbwk.nj.us (Tony DeBari) wri
> >Ok, but consider my site, ssc60.sbwk.nj.us, a few-user Waffle iron owned
> >and operated by a private individual (i.e. me).
> 
> >It's not an "organization" per se.
> >It's not a company or other type of commercial site.
> >It's not an educational institution.
> >It's not international (is that what .INT is for?)
> 
> >The only real domain left is .<MyCountry> (.US), which is based on a
> >geographic hierarchy.  If I move out of South BrunsWicK, NJ, I have 
> >to register a new domain name.  Yes, it's free and easy, but I'd rather
> >not have to do it more than once.  And I'm fortunate in that my account
> >with UUNET means not having to find another forwarder.
> 
> Yes, but you still have to submit a new map entry describing you path
> for receiving mail after a move.  IMHO, this is more work that sending
> a piece of email to the MX record site requesting that they change 
> the delivery host (when using the .us domain that is....)
 
I'm not sure I follow you here.  Right now I'm registered as
ssc60.sbwk.nj.us, with uunet.uu.net (or one of their machines) as my
MX forwarder.  UUNET is the only site I talk to.  If I move to 
Phoenix tomorrow, I have to (or should, anyway) send a new registration
to ISI chaning my name to ssc60.phx.az.us, and UUNET would still be
my forwarder.  However, if I were registered (somewhere) as ssc60.pri,
I could move to anywhere without having to update any DNS records so
long as UUNET remained my forwarder.  Either way, I'm in the DNS, so
a UUCP map entry is no longer necessary.

> >What would be wrong with a .PRI domain for unaffiliated, private sites?
> >Everyone has at least an MX record in the DNS, it doesn't imply a specific
> >transfer protocol like .UUCP, and there is no geographic hierarchy so a
> >site can be physically moved without having to re-register its domain name.
> 
> This could easily become unmanagable.  By using the geographical domain
> hierchy, you can at least get a clue as to where it is you might be
> sending your packets.  

A clue that could be very misleading.  I could be asking a person in
Tasmania what he thinks of Da Bears. :-)

> Fact is, that with the methods in use today,
> when you make a move, you have to let somebody know where and how to
> deliver packets.  The farther the move the more things need to be
> adjusted (domain, MX info, uucp neighbor etc.)  

True.  That's why I have a UUNET account.  No matter where I go, they
will always be my UUCP neighbor and MX forwarder.  Registering a new
domain name under .us would be the only change I would need to make,
and that would be avoided with a non-geographic domain hierarchy.

> Fortunately, it's
> pretty easy to do, just take a few days to be final.  Oh well, it
> sure works well!

Yes, it does!  It might sound like I'm complaining, but I'm really
not.  As you said, moving a site sometimes requires a lot of work to 
keep the connection going.  I'd just like to make it easier by 
eliminating the need to re-register a domain name solely because the 
site has moved.

--
Tony DeBari          FQDN: tonyd@ssc60.sbwk.nj.us     CI$: 73117,452
                     UUCP: ...!uunet!ssc60!tonyd      *P*: GHRW14B

a.k.a. Skip Bowler, captain of USENET Fantasy Bowling League Team 9.