|
|
1.1 root 1: From research!mtune!rutgers!SH.CS.NET!cic Thu Oct 1 06:36:01 1987
2: Received: by mtune.ATT.COM (smail2.5)
3: id AA14518; 1 Oct 87 06:36:01 EDT (Thu)
4: Received: by RUTGERS.EDU (5.54/1.14)
5: id AA29788; Thu, 1 Oct 87 01:26:28 EDT
6: Message-Id: <[email protected]>
7: Received: by SH.CS.NET id ai10308; 29 Sep 87 15:26 EDT
8: Date: Tue, 29 Sep 87 14:25:18 EDT
9: Subject: ns-1 USER NAME SERVER 3.1
10: Reply-To: rutgers!SH.CS.NET!cic
11: From: CSNET INFO SERVER <rutgers!SH.CS.NET!info>
12: To: [email protected]
13:
14: Request: info
15: Topic: ns-1
16: Document Updated: 4 Dec 86
17: Subject: User Name Server: Introduction
18: ==============================================================================
19: CSNET Coordination and Information Center (CIC) Hotline: 617/497-2777
20: 10 Moulton Street Email: [email protected]
21: Cambridge, MA 02238 Info-Server requests to: [email protected]
22: ==============================================================================
23:
24: +-------------------------------- NOTE ------------------------------+
25: | CSNET Service Host: csnet-sh = csnet-sh.arpa = sh.cs.net |
26: | CSNET Relay Host: csnet-relay = csnet-relay.arpa = relay.cs.net |
27: | CSNET Info-Server: [email protected] = [email protected] |
28: +--------------------------------------------------------------------+
29:
30: USER NAME SERVER: INTRODUCTION
31:
32: NS 3.1 .................... 9 HOW-TO MESSAGES ........... 46
33: WHO CAN REGISTER? ......... 30 End ....................... 122
34:
35:
36: NS 3.1
37:
38: The central CSNET User Name Server, Version 3.1, on the service host,
39: SH.CS.NET, is a directory database of users and hosts.
40:
41: Any CSNET host that runs the UNIX operating system (BSD 4.1 or 4.2)
42: may receive "Local Agent" software for the User Name Server, at no
43: extra charge. Version 3.1 of the Local Agent Software, initially
44: available only for 4.2, was released in September 1985. This version
45: combines the "nicknames" and "mail forwarding" enhancements previously
46: announced as Phase II and Phase III.
47:
48: On sites with Local Agent software, the 'ns' command runs the User
49: Name Server, which allows you to compose queries or register new users
50: interactively. Requests are sent to the central Name Server on
51: SH.CS.NET by electronic mail, and the responses are automatically
52: mailed back. On X25Net or Arpanet hosts, the 'ns' program on the
53: local host connects directly to the central User Name Server, and
54: response is immediate.
55:
56:
57: WHO CAN REGISTER?
58:
59: A CSNET host is a host computer at a CSNET site (i.e., a CSNET member
60: organization) which is able to send mail to the CSNET. Each CSNET
61: site has one, or at most two, CSNET hosts which have been designated
62: as official CSNET hosts. On Phonenet sites, the offical CSNET hosts
63: are the only hosts with direct access to the CSNET. The official
64: hosts may act as gateways between the CSNET and other host computers
65: within the member organization. This is particularly important when
66: none of the other hosts is on the X25Net or Arpanet.
67:
68: Only the official CSNET hosts are registered as "site entries" in the
69: Name Server, but all users at any CSNET host are eligible to register
70: in the CSNET User Name Server.
71:
72:
73: HOW-TO MESSAGES
74:
75: CSNET Info Documents ns-2 through ns-7 explain how you can query the
76: User Name Server, register yourself as a new user, and edit your entry
77: from different types of hosts. Document ns-8 briefly describes the
78: new features of Version 3.1.
79:
80:
81: ns-2. QUERY with Local Agent or TELNET (Arpanet/X25Net)
82:
83: If you are at an X25Net or Arpanet site, you can query the
84: central User Name Server interactively through Local Agent
85: Software or by direct TELNET connection. If you are at a
86: PHONENET site, you can use the Local Agent Software
87: interactively; responses from the central User Name Server are
88: returned by electronic mail.
89:
90: ns-3. QUERY by Electronic Mail.
91:
92: If your CSNET site has no Local Agent Software and no TELNET
93: access you can send and receive queries by electronic mail.
94: You can use this technique on any X25Net or Arpanet site when
95: you want the results of your queries in message form.
96:
97: ns-4. REGISTER on Hosts with Local Agent Software.
98:
99: Automatic registration requires the use of Local Agent
100: Software so that you can be authenticated by your login
101: identity. Although you can query the central User Name Server
102: over a direct TELNET connection, you cannot register yourself
103: as a new user. This is a matter of both policy and technical
104: considerations.
105:
106: ns-5. REGISTER Non-Local Users with Local Agent Software.
107:
108: If your host does not run the Local Agent Software but the the
109: software is installed on another CSNET host at your site, your
110: local Technical Liaison can register you.
111:
112: ns-6. REGISTER by Electronic Mail.
113:
114: If none of the hosts at your CSNET site run the Local Agent
115: software, your Technical Liaison can send User Name Server
116: registrations by electronic mail to the CIC@CSNET-CIC.
117:
118: ns-7. EDIT Your Registration, MOVE to Another Host.
119:
120: You can edit your registration using Local Agent Software on
121: the original host at any time. Your CSNET password allows you
122: to edit your entry on any host that has Local Agent Software,
123: or by telnetting to the central User Name Server, on SH.CS.NET
124: and using the 'ns' login. If your move to another host, you
125: can use your CSNET password to move your User Name Server
126: identity. This is important if you use the nickname feature.
127:
128: ns-8. Nicknames and Mail Forwarding
129:
130: With Local Agent Software, you can define personal "nicknames"
131: for addresses or lists, with the Local Agent Software. If you
132: define nicknames for people, and if those people transfer
133: their accounts to other CSNET hosts and use the MOVE command
134: to change their NS entries, the Local Agent Software will
135: automatically forward messages to them.
136:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.