home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: can.domain
- Path: sparky!uunet!van-bc!sl
- 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
- Message-ID: <C08wCs.LDI@wimsey.bc.ca>
- References: <C07r77.4ut@uunet.ca> <C081rA.Eu3@wimsey.bc.ca> <C08H06.6xB@uunet.ca>
- Lines: 35
-
- 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
-