🚀 go-pugleaf

In article <13055@ember.UUCP> pacolley@ember.UUCP (Paul Colley) writes:
>But I find it annoying:  I intend to move!  When I moved from
>Waterloo to Kingston, my email address of "pacolley@ember.uucp"
>didn't change and I didn't get any reports of mail problems from
>people.  This is the way it should be, IMHO.

It however doesn't mean that you're easily findeable by distant
Internet hosts unless you have someone hold an MX record for you.

>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?  Not all of them stay in Canada either, let alone
>Ontario.

The .CA domain namespace is intended to provide a geographically
oriented namespace to stable organizations, companies, and
institutions.  The odd time one of them requires an ammendment
to their registration, it's easily forthcoming.

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.

>Somebody told me to make up a company name and register under
>"*.com".  Which seems silly, but is perhaps the best answer.  Do
>they allow individuals to register under .com?  Is it as cheap as
>under a geographic name?

Don't quote me, but I recall when it was the same fee.  I have no
idea what it may be for .com right at the moment, but it's still
likely to be nominal.

As for which domain to register under...perhaps your best choice
may be .org, and then register under .CA when your location
stabilizes.  Remember, there's nothing to preclude having more
than one registration.  There's lots of precedence, {.edu,.ca},
{.com,.ca}, {.org,.ca}, to name a few known combinations.

>Anyways, I'm hoping somebody has some good advice.
>
>- Paul Colley
>University:  colley@qucis.queensu.ca
>Home:        pacolley@ember.uucp   watmath!ember!pacolley  +1 613 545 3807

Hope this helps.

                --ed            (Ed Hew)
--
        Canadian UUCP Map Coordinator           <path@cs.toronto.edu>
        UUCP liason to .CA Domain Registry	<registry@cs.toronto.edu>
   ==>  XeniTec Consulting Services             <edhew@xenitec.on.ca>

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 
<<<----+---------+-----+--------------+-----+---------------------------+-->>>

In article <1992Oct08.210936.9251@tdkcs.waterloo.on.ca> timk@tdkcs.waterloo.on.ca (Tim Kuehn) writes:
>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:

And what you outline is precisely what a domain park is supposed
to accomodate.  It gives you a .CA subdomain registration, and
the authority to determine routing within that subdomain, which
is one of the reasons I suggested it in the first place.  It works,
just look at .ocunix.on.ca.  There's no reason why there can't be
a .kwuug.on.ca.

		--ed

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?  Not all of them stay in Canada either, let alone
>Ontario.

UUCP site names are not for laptop computers. And definitely
not for transients. Think of it like a post office. It's supposed
to stay in one place.

I'm the only undergrad I know with a UUCP connection. I'm
not in co-op. No reasonable co-op would try what you're suggesting.

Ice()

In article <1992Oct09.224733.1591@skynet.uucp> ice@skynet.uucp (Ice) 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?  Not all of them stay in Canada either, let alone
>>Ontario.
>UUCP site names are not for laptop computers. And definitely
>not for transients. Think of it like a post office. It's supposed
>to stay in one place.

Humbug. The only consideration when you have a .uucp name registered is 
that (1) it's unique, and (2) mail can reliably be gotten to it.  Want 
to move and you have a .uucp registration? Make your connection with the 
new site, send in an updated map entry, and have your prior and current 
site send in a map update, and the deed's done. Pathalias'll or other 
appropriate mail routing technology will figure out the rest.

If you had a central system that took care of processing mail under that 
domain, then moving around would be that much easier since all you'd 
have to do would be have the forwarding host update it's local map entries
to reflect the change in connectivity. Simplicity itself.

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