HDTenEightyP/NetNews huggingface dataset:
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: locality abbreviations (was Re: What is this group for?)
Organization: Wimsey Information Services
Distribution: can
Date: Sun, 3 Jan 1993 08:36:55 GMT

In article <1993Jan03.040438.7309@xenitec.on.ca> eah@xenitec.on.ca (Ed Hew) writes:
>[In the message "Re: What is this group for?", Stuart Lynne <sl@wimsey.bc.ca writes... ]
>I've always had an aversion to making names longer than absolutely
>necessary.  We went around the "what is a proper city name" merry-
>go-round at some length this last spring in committee.  Unfortunately,
>no one could find any "official city abbreviation list", so city
>abbreviations were disallowed.  If anyone is aware of such a list,
>please forward this info to me so that I can present it to the
>committee.  The topic was revived in committee last week, and I
>hope that we'll have a reasonable locality abbreviation policy
>incorporated into the guidelines in short order.  If we could find
>a list pre-prepared by some government agency, the task would be
>much simpler.

RFC1386 mentions Western Union list. It probably covers Canada as well. It
also mentions that it is not that great. E.g. the names are not always
mnemonic.

Don't forget that the Post Office already has a well documented list
of Canadian cities. In fact characterized right down to individual blocks
in most cases. It qualifies as a government agency. It's prepared and
ready for pickup at your local post office or library. Just ask for
the Postal Code book.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: Domain naming conventions
Organization: Wimsey Information Services
Date: Sun, 3 Jan 1993 01:31:15 GMT

In article <1993Jan2.234428.886@cs.UAlberta.CA> cdshaw@cs.UAlberta.CA (Chris Shaw) writes:
>In article <C08zs2.4uG@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:

>Look. When I started using EMail in 1982, there weren't a lot of sites, and
>long site names seemed dumb. Now that there are one hundred thousand or 
>so distinct domains (or whatever it is), it's foolish to demand 6 letter site

Maybe 10,000. There are about 500 in .US. About 450 in .CA. About 5500 in .Com.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: eah@xenitec.on.ca (Ed Hew)
Subject: locality abbreviations (was Re: What is this group for?)
Organization: XeniTec Consulting, Kitchener, Ontario, CANADA
Distribution: can
Date: Sun, 03 Jan 1993 04:04:38 GMT

[In the message "Re: What is this group for?", Stuart Lynne <sl@wimsey.bc.ca writes... ]
} CA guidelines allow xxx.ca, xxx.prov.ca or xxx.municp.prov.ca depending on
} the size and scope of your business/organization etc.
} 
} My personal opinion is that this approach leads to domain names that are
} too long. 	[...]

I've always had an aversion to making names longer than absolutely
necessary.  We went around the "what is a proper city name" merry-
go-round at some length this last spring in committee.  Unfortunately,
no one could find any "official city abbreviation list", so city
abbreviations were disallowed.  If anyone is aware of such a list,
please forward this info to me so that I can present it to the
committee.  The topic was revived in committee last week, and I
hope that we'll have a reasonable locality abbreviation policy
incorporated into the guidelines in short order.  If we could find
a list pre-prepared by some government agency, the task would be
much simpler.

I really don't want to see registrations like foo.niagara-on-the-lake.on.ca.

		--ed
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: Domain naming conventions
Organization: Wimsey Information Services
Date: Sun, 3 Jan 1993 01:32:51 GMT

In article <1993Jan2.234428.886@cs.UAlberta.CA> cdshaw@cs.UAlberta.CA (Chris Shaw) writes:
>Thousands of studies of human memory performance bear this out. Postal
>codes (and other seemingly random strings of letters and digits) are harder 
>to remember than place names.

You will of course give us some journal references so we can check out this
assertion.

>cdshaw@cs.UAlberta.ca    CatchPhrase: Bogus as HELL !

I can agree with that...


-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: can.domain
Organization: Wimsey Information Services
Distribution: can
Date: Sat, 2 Jan 1993 21:14:52 GMT

In article <C08H06.6xB@uunet.ca> smd@uunet.ca (Sean Doran) writes:
>sl@wimsey.bc.ca (Stuart Lynne) writes:
>
>>In article <C07r77.4ut@uunet.ca> smd@uunet.ca (Sean Doran) writes:
>>>lyndon@unbc.edu (Lyndon Nerenberg) writes:
>
>>You can't get registered in .com or .us unless someone is willing to
>>support an MX for you.

>>But policy should be created by the users.
>
>Possibly.  But then we would have to fight about who the users are,
>and who among them gets to define policy.  The issues are not simple.

I still like the IETF working group concept. Membership is open to anyone
willing to participate.

>Can.domain is perhaps a useful vehicle for public bickering.  A
>semipublic/semiprivate mailing list might be useful for some more
>detailed (and less heated) discussions about policy.  However, neither

I'll agree with that. It helps sort out those who are interested in
working out a solution and those who are just wandering through on a 
slow news day.

>be considered a policy-making body.  Policy should be made by the
>person who controls the nameservers for the top-level-domain. 

Don't agree with that. He should implement policy. Not create it.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: eah@xenitec.on.ca (Ed Hew)
Subject: Re: Domain naming conventions
Organization: XeniTec Consulting, Kitchener, Ontario, CANADA
Date: Mon, 04 Jan 1993 03:07:03 GMT

In article <C099vF.np@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>Assuming John Demco delagated authority to my machine for v3h.ca and
>port-moody.bc.ca I would be able to act as generic forwarder for all
>sites in port-moody and in the area delineated by v3h.

There are already a number of registered "domain parks" with authority
granted in just such a manner.  The only difference is that one is not
_forced_ to belong to a domain park, but may register their own
subdomain.  One good example might be .wimsey.bc.ca. :-)

>The US domain is using distributed servers at this level. RFC1386 lists
>a number of existing zones that have been delagated in this fashion (for
>forwarding to city.state.us, they do not have the concept of using the
>postal code). For example TUCSON.AZ.US is delagated to leonard.arizona.edu.

It's my understanding that such granting of authority for provincial
subdomains may indeed happen once the necessary framework is in place.

                --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>
Newsgroups: can.domain
From: rahardj@ccu.umanitoba.ca (Budi Rahardjo)
Subject: Re: Domain naming conventions
Organization: University of Manitoba, Winnipeg, Canada
Date: Sun, 3 Jan 1993 05:47:13 GMT

In <C098As.KF1@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:

>In article <1993Jan2.234428.886@cs.UAlberta.CA> cdshaw@cs.UAlberta.CA (Chris Shaw) writes:
>>Thousands of studies of human memory performance bear this out. Postal
>>codes (and other seemingly random strings of letters and digits) are harder 
>>to remember than place names.

>You will of course give us some journal references so we can check out this
>assertion.

I can't point to a particular reference, but I do maintain some mailing lists.
And from my experience it's easier to remember userid/domain with 
longer-but-readable words than series of 'random' letter and digit. 
I have to look more carefully when dealing with 'random' letters and numbers 
(hey, sometimes an 'l' looks like a '1').

IMHO, 'budi@bison.mb.ca' is easier to remember than '4w9@r3t.mb.ca'.
If there is a typo, say 'bison' -> 'nison', you'll get bounced mail, but
when 'r3t' -> 'r4t', you'll get somebody else's account :-)


-- budi
-- 
Budi Rahardjo <Budi_Rahardjo@UManitoba.Ca>
Unix Support - Computer Services - University of Manitoba
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: registration -vs- forwarder policy
Organization: Wimsey Information Services
Distribution: can
Date: Sun, 3 Jan 1993 09:27:49 GMT

In article <1993Jan3.003445.2159@becker.GTS.ORG> bdb@becker.GTS.ORG (Bruce Becker) writes:
>
>	I'm wondering whether the .CA domain people
>	do anything at all vis-a-vis the DNS, & if
>	so, what system is by default authorative
>	for new registrations when they are approved?

Not by default. The root server for .ca is relay.cdnnet.ca. But they
do not automatically add an SOA or MX. They have in the past been very
supportive if you asked nicely though.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: cdshaw@cs.UAlberta.CA (Chris Shaw)
Subject: Re: Domain naming conventions
Organization: University of Alberta
Date: Sat, 2 Jan 1993 23:44:28 GMT

In article <C08zs2.4uG@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>>It's a *lot* easier to remember that "The company is TDK Consulting 
>>Services, he's in the Region/City of Waterloo, in Ontario, Canada" 
>>and associate that with timk@tdkcs.waterloo.on.ca than to associate 
>>it with "timk@tdkcs.n2j.on.ca" 
>
>Well actually I would suggest that timk@tdkcs.n2j.ca is sufficent. And is 
>
>	timk@tdkcs.waterloo.on.ca
>	timk@tdkcs.n2j.ca
>
>eight characters less to remember or type.

The issue here is not number of characters, but cognitive load. The first
three digits of the postal code are three random characters for which the 
user must learn a place-name association. Both the characters themselves 
and their association with the appropriate place name is demonstrably 
more difficult to learn than an abbreviated place name.

Thousands of studies of human memory performance bear this out. Postal
codes (and other seemingly random strings of letters and digits) are harder 
to remember than place names.

>Phone the post office. Look at your correspondents business card. Give them
>a phone call. 

Oh, I see. To EMail something, I have to telephone the post office or my
corresponent. Why don't I just ditch EMail altogether & use the phone?

>For example how do you specifiy Portage la Prairie?

portage-la-prairie

Was that so hard? Oh I know, it was hard to type. Also a little hard to 
spell. So to save a few characters at the keyboard, I should telephone my 
post office to find an unambiguous postal code, so that I can save 15 or 
so characters.

Look. When I started using EMail in 1982, there weren't a lot of sites, and
long site names seemed dumb. Now that there are one hundred thousand or 
so distinct domains (or whatever it is), it's foolish to demand 6 letter site
names at the expense of everything else. EMail is no longer the cozy village
it once was, but is instead a multi-lingual international metropolis of
more than one million inhabitants.

>I am also of the opinion that it will be impossible to satisfy everyone
>with *one* way of doing things. 

False, in this instance. Canada Post mandates one correct addressing method,
and it works. The same can be true in this instance, although I don't think
that the number of domain names warrants a normative scheme just yet.
Maybe in the USA this is not the case.

>Is there any technical problem with 
>supporting some small number of different ways to select a name. I.e. you
>get your choice of tdkcs.waterloo.on.ca OR tdkcs.n2j.ca OR some other
>scheme that doesn't clash and is desired by some large body of users. 

The only problem is to make sure everyone implements it. I'd be willing to bet
that the place-name format (eg waterloo.on.ca) will be the method of choice
for 98% of users, however. 

>For another example....
Ridiculous emotional appeal deleted.

>Stuart Lynne <sl@wimsey.com> 


--
Chris Shaw               University of Alberta
cdshaw@cs.UAlberta.ca    CatchPhrase: Bogus as HELL !
Newsgroups: can.domain
From: gerrys@sun.com (Gerry Singleton - OpCom Consultant)
Subject: Re: What is this group for?
Reply-To: gerrys@sun.com
Organization: Sun Microsystems, Inc.
Date: Tue, 29 Dec 1992 17:57:46 GMT

In article 8277@julian.uwo.ca, wlsmith@valve.heart.rri.uwo.ca (Wayne Smith) writes:
|>Well?
|>


The purpose and goals of the the group have been discussed thoroughly in
can.uucp, to which I subscribe, and possibly others.  I suggest you examine
the pertinent articles therein.

Happy reading
---
--
G. Roderick Singleton, OPCOM Solaris 2.0 Migration Support Centre
{ gerrys@canada.sun.com | gerry@nexus.yorku.ca | gerry@eclectic.uucp }
Voice: 1-800-363-6200 (Canada and U.S.A.)

Newsgroups: can.domain
From: smd@uunet.ca (Sean Doran)
Subject: Re: Candian Domain Information, By Gopher!
Organization: UUNET Canada
Date: Sun, 3 Jan 1993 08:13:20 GMT

daniel@nstn.ns.ca (Daniel MacKay) writes:

>Point your gopher at [...]

And for those of you without gopher, the CA-DOM types make information
available at various places for anonymous ftp, including:

ftp.cs.ubc.ca:/ca-domain
ftp.cs.toronto.edu:/ca-domain
ftp.uunet.ca:/ca-domain
ftp.crim.ca:/CAnet/ca-domain

	Sean.
Newsgroups: can.domain
From: lyndon@unbc.edu (Lyndon Nerenberg)
Newsgroups: can.domain
Subject: Re: can.domain
Date: 2 Jan 93 00:37:49 GMT
Distribution: can
Organization: University of Northern B.C.


 smd@uunet.ca (Sean Doran) writes:

> Whether this group should or should not be elected, and should or
> should not represent organizations like CA*Net, NetNorth and DRENet,
> or should involve the people who run the primary and secondary
> nameservers for the CA Domain, is something that is probably very
> moot.  I think the important qualifications, though, are visibility,
> responsibility and professionalism.  

> I'm not sure that people elected at a conference will be particularly
> professional and non-political.  I'm almost certain that further
> politicizing the CA domain will slow the applications process to the
> point of near uselessness.

Are you saying that the Net/XX conference attendees are not professional?
Hmmm ... did you attend last year?  After making such a statement will
you attend *this* year? :-)

Given the highly political nature of the *current* .ca old boys club,
how could an openly elected group be any *worse* ???

> The current committee and system, with a bit of Glasnost (e.g., public
> discussion about difficult issues like the namespace rules) and
> a bunch of pragmatism, should do what needs to be done quite effectively.  

No.  If we're going to start clean we have to start clean.  Off with their
heads and let's start over from scratch.
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: What is this group for?
Organization: Wimsey Information Services
Date: Sat, 2 Jan 1993 10:39:08 GMT

In article <1992Dec29.175746.13732@newscan.canada.sun.com> gerrys@sun.com writes:
>In article 8277@julian.uwo.ca, wlsmith@valve.heart.rri.uwo.ca (Wayne Smith) writes:
>|>Well?
>|>
>
>
>The purpose and goals of the the group have been discussed thoroughly in
>can.uucp, to which I subscribe, and possibly others.  I suggest you examine
>the pertinent articles therein.

Anyone interested in domain name topics should probably look at the new
RFC-1386 titled "The US Domain" by A. Cooper and J. Postel. 

The current approach to use of the US domain is similiar to what the CA-domain
committee is moving too. Assigning names based on political geography. It is
implemented a bit differently and possibly a bit more consistently. For example
it does not appear to allow ibm.us but would require ibm.armonk.ny.us. 

CA guidelines allow xxx.ca, xxx.prov.ca or xxx.municp.prov.ca depending on
the size and scope of your business/organization etc.

My personal opinion is that this approach leads to domain names that are
too long. Which leads to problems with use due to being incorrectly transcribed.
I would like to see a solution that requires at most three tokens and a minimum
of characters for the non-organization part. 

Some examples:
  
   New guidelines:
	xxx.municp.prov.ca	wimsey.port-moody.bc.ca

   Just keep it to provinces:
	xxx.prov.ca		wimsey.bc.ca

   Or use first three digits of postal code:
	xxx.postal-code.ca	wimsey.v3h.ca

The reason I would like to keep it to three tokens and minimum char's at this
level is that we tend to add more tokens to the left when in use. For example
on vanbc:

  XXXX.wimsey.bc.ca			questor.wimsey.bc.ca
  XXXX.wimsey.v3h.ca			questor.wimsey.v3h.ca
  XXXX.wimsey.port-moody.bc.ca		questor.port-moody.wimsey.bc.ca

where XXXX is a uucp neighbour will get delivered properly. If those hosts
wish to further sub-divide their namespace:


  YYY.XXX.wimsey.bc.ca			sun.questor.wimsey.bc.ca
  YYY.XXX.wimsey.v3h.ca			sun.questor.wimsey.v3h.ca
  YYY.XXX.wimsey.port-moody-bc.ca	sun.questor.wimsey.port-moody-bc.ca

And don't forget we need to add a user name:

  user@YYY.XXX.wimsey.bc.ca		John_Doe@sun.questor.wimsey.bc.ca
  user@YYY.XXX.wimsey.v3h.ca		John_Doe@sun.questor.wimsey.v3h.ca
  user@YYY.XXX.wimsey.port-moody-bc.ca	John_Doe@sun.questor.wimsey.port-moody.bc.ca


-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: registration -vs- forwarder policy
Organization: Wimsey Information Services
Distribution: can
Date: Sun, 3 Jan 1993 01:44:09 GMT

In article <1993Jan2.232231.16077@sol.UVic.CA> klassen@sol.UVic.CA (Melvin Klassen) writes:
>In article <C08yy0.3qJ@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>>
>>Now nslookup -type=soa gov.coquitlam.bc.ca.
>>    *** (name-server) can't find gov.coquitlam.bc.ca.: Non-existent domain
>
>That's the "correct" answer.  When you try:
>
>     nslookup -type=soa     coquitlam.bc.ca.
>and
>     nslookup -type=soa           gov.bc.ca.
>
>you do get useful information.  
>

Well coquitlam.bc.ca doesn't give you anything for above.  Neither does bc.ca.

The point is that there *is* a registered domain called gov.coquitlam.bc.ca:

    Subdomain:      Gov.Coquitlam.BC.CA
    Date-Received:  1992/10/15
    Date-Approved:  1992/10/23
    Organization:   District of Coquitlam
    Type:           Municipal Government
    Description:    District of Coquitlam's municipal goverment.
    Tech-Mailbox:   JTaylor@Gov.Coquitlam.BC.CA

Not only is there no SOA, and no MX, the domain registration lists information 
that is not usable (the mailbox addresses).

By comparison RFC1386 specifically states:

	The key people must have electronic mailboxes (that work).
and
	The technical contact should have a valid working e-mail address.
	This is necessary in case something goes wrong.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
From: demco@cs.ubc.ca (John Demco)
Newsgroups: can.domain
Subject: Re: can.domain
Date: 2 Jan 1993 15:00:13 -0800
Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
Distribution: can
NNTP-Posting-Host: grolsch.cs.ubc.ca

Presently I'm working on a revision of the Introduction document.
I'll post it as soon as possible.  Work is also proceeding on a FAQ
list.  Perhaps in time it will supercede the Introduction document.

Cheers,
John Demco, CA Domain Registrar    E-mail: demco@cs.ubc.ca
Department of Computer Science        Tel: +1 (604) 822 6724
University of British Columbia        Fax: +1 (604) 822 5485
Vancouver, BC, Canada  V6T 1Z2
Newsgroups: can.domain
From: bdb@becker.GTS.ORG (Bruce Becker)
Subject: Re: registration -vs- forwarder policy
Organization: G. T. S., Toronto, Ontario
Distribution: can
Date: Sun, 3 Jan 1993 00:34:45 GMT

In article <davecb.725998930@yorku.ca> davecb@nexus.yorku.ca (David Collier-Brown) writes:
|  As I understand it, and organization with a discontinuous net (ie,
|no internet mail forwarder) in Canada can register a domain name.  In
|the United States this is untrue.  There you can have an IP network
|number allocated, but you cannot have a domain name without a mail
|forwarder (and someone to hold your MX records, as a practicality
|issue).
|
|  The U.S. position has been criticized because a company cannot
|``reserve'' their domain name.  The Canadian position has been
|criticized because the domain is unreachable.
|
|  Is this an either-or situation?  Is there a middle ground?  Is there
|a necessary relationship with the allocation of an IP address?
|  Does the .ca domain registrar actually place the domain entry into a
|DNS server without any A or MX records? What effect does this have on
|email?
|
|  Ok folks, lets have at it (:-))


	There are several sites in North America
	that have been providing free MX-service
	on request for a while now.


	I'm wondering whether the .CA domain people
	do anything at all vis-a-vis the DNS, & if
	so, what system is by default authorative
	for new registrations when they are approved?


-- 
  ,u,	 Bruce Becker			Toronto, Ontario
a /i/	 Internet: bdb@becker.gts.org	Uucp: ...!web!becker!bdb
 `\o\-e  "...symbolising Excitement and Fun."		
 _< /_		-- Disneyland North investment brochure
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: What is this group for?
Organization: Wimsey Information Services
Date: Thu, 31 Dec 1992 23:05:11 GMT

In article <1992Dec29.175746.13732@newscan.canada.sun.com> gerrys@sun.com writes:
>In article 8277@julian.uwo.ca, wlsmith@valve.heart.rri.uwo.ca (Wayne Smith) writes:
>|>Well?
>|>
>
>
>The purpose and goals of the the group have been discussed thoroughly in
>can.uucp, to which I subscribe, and possibly others.  I suggest you examine
>the pertinent articles therein.

We'll repost the charter next week. Didn't make much sense to do it this
week. Would probably expire before most people got back from vacation.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain