From: timk@tdkcs.waterloo.on.ca (Tim Kuehn)
Subject: Re: Choice of domain
Organization: TDK Consulting Services
Distribution: kw
Date: Thu, 08 Oct 1992 21:09:36 GMT

In article <1992Oct08.032122.29500@xenitec.on.ca> eah@xenitec.on.ca (Ed Hew) writes:
>In article <13055@ember.UUCP> pacolley@ember.UUCP (Paul Colley) writes:
>>What's the point of a domain name if I'm going to have change
>>domains every few years?  What about co-op students that move 
>>every four months?  

>The .CA domain namespace is intended to provide a geographically
>oriented namespace to stable organizations, companies, and
>institutions. [...] It wasn't designed to provide registrations 
>for private individuals, hence unless you declare yourself to be 
>a company or equivalent, you're out of luck here.  Co-op students 
>were never in the plan, so are not provided for.

>I suppose you could make a case that there _should_ be provision
>for such.  I'll leave that to you to decide.

Hmmmm.... maybe there'd be a market for a centralized email forwarding
service similar along the lines of the "domain park" we keep talking 
about?. People who move a lot (like co-op students) could register with 
the machine that runs that domain park/mail forwarding service for a small 
fee. All mail to that person would be sent to an address at that machine, 
which would then forward it to the machine wherever the person actually is.

This way, the only thing that would have to be changed when someone 
changes where they tie into the net to a new upstream site would be:

- the forwarding address in the domain park machine

- update the local map entry on the machine they are hooking up to show
  the new connection

- update the old machine they used to talk to reflect the lost connection


-----

For example, say .tdkcs.waterloo.on.ca provided the domain park services, 
and ember became a sub-domain of that, ie

ember.tdkcs.waterloo.on.ca

Now in reality, ember's out in Kingston attached to a machine with the
domain name upstream1.on.ca. Upstream1 would make a map entry local to
their machine like so:

ember	= ember.upstream1.on.ca
upstream1	ember.upstream1.on.ca(DIRECT)

Back at tdkcs, a set of local to tdkcs map entries would be made:

ember.upstream1.on.a	= ember.tdkcs.waterloo.on.ca
upstream1	ember.upstream1.on.ca(DIRECT)

-----

No updated map entries would need to be sent in, which would 
help alleviate matters in that area (as well as decrease the 
work required of the map maintainer, and enhance reliable email 
connectivity).

Assuming that the domain park machine would generate full "!" paths 
to the target site, and no intermediate sites decided try to re-route 
it, this might work.

WARNING! I haven't tried this yet to see what would happen, but this, 
or something along similar lines should (conceivably) be doable. This 
also assumes pathalias generated maps when implimenting this. I'm not 
certain how sendmail could be used to impliment this idea.

With that disclaimer, thoughts, anyone? :-)

<<<----+---------+-----+--------------+-----+---------------------------+-->>>
    +	Tim Kuehn   + 	TDK Consulting   +    (519)-888-0766	
    +	<><         + 	Services         +    timk@tdkcs.waterloo.on.ca 
<<<----+---------+-----+--------------+-----+---------------------------+-->>>