![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to ns-6 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10dc / doc / csnet|
Return to ns-6 CVS log | Up to [Research Unix] / researchv10dc / doc / csnet |
1.1 root 1: From research!mtune!rutgers!SH.CS.NET!cic Thu Oct 1 01:45:12 1987
2: Received: by mtune.ATT.COM (smail2.5)
3: id AA21359; 1 Oct 87 01:45:12 EDT (Thu)
4: Received: by RUTGERS.EDU (5.54/1.14)
5: id AA00008; Thu, 1 Oct 87 01:30:56 EDT
6: Message-Id: <[email protected]>
7: Received: by SH.CS.NET id ak10308; 29 Sep 87 15:26 EDT
8: Date: Tue, 29 Sep 87 14:25:27 EDT
9: Subject: ns-6 REGISTER by Mail
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-6
16: Document Updated: 28 Jul 87
17: Subject: Register by Electronic Mail
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: REGISTER BY ELECTRONIC MAIL
25:
26: If no host computer at the CSNET member site runs the Local Agent
27: Software, the CSNET Technical Liaison can arrange to have the
28: registrations performed by the CSNET Coordination and Information
29: Center (CIC) by sending a message to [email protected], or telephoning the
30: CIC at 617/497-2777.
31:
32: The information for users to be registered should be sent in a message
33: addressed to [email protected]. Tables ns-6.1 and ns-6.2 show sample
34: registrations for multiple names. The field names, such as "Account",
35: "MBox", etc., should start in column 1 of the body of the message.
36: The field contents should start in column 2. The User Name Server
37: will turn the space in column 1 into a tab, so lines should be no more
38: than 72 characters long.
39:
40: You may put as many registrations as you wish in a message -- just
41: separate them with a row of hyphens or some other marker.
42:
43: The tables show the MBox (MailBox) addresses for sites with
44: domain-style names. All Internet now have domain-style names, and
45: CSNET PhoneNet sites have either converted to the domain system, or
46: are in the process of doing so. (For more information about
47: domain-style names, see REFERENCES at the end of this document.)
48:
49: The purpose of the Account string is to provide a unique identifier
50: for each person registered in the User Name Server. It has the form
51:
52: user,host,site
53:
54: Before the Internet domain name system was adopted, the designers of
55: the User Name Server, intended the "host" string to be the name of
56: the user's host computer, and the "site" string to be a unique name
57: assigned by CSNET to the CSNET member organization.
58:
59: Now that the Internet domain name system assigns unique hierarchical
60: names, the Account string should incorporate the domain names in some
61: reasonable way.
62:
63: "User", "host" and "site" are just strings of characters, as far as
64: the User Name Server is concerned. As long as we don't end up with
65: duplicate Account strings, the exact scheme used to form the Account
66: string doesn't matter very much. Here are some suggestions:
67:
68: 1. The "user" string should be the user's login name, or the
69: name under which he or she receives mail.
70:
71: 2. The domain name assigned to an entire organization consists
72: of a second-level domain unique to the organization, followed
73: by one of the top-level domains such as ".edu" or "com".
74: For example, AAA College might have the domain name
75: "aaa.edu".
76:
77: If outsiders can send mail to anyone at the site, for example,
78: "aaa.edu" by using the address "[email protected]", the Account
79: string can be
80:
81: user,aaa.edu,aaa.edu
82:
83: 3. If outsiders must know the name of a lower-level domain --
84: which might be the name of a department within the
85: organization -- the lower-level domain can be placed in the
86: "host" string, and the domain for the organization should be
87: in the "site" string. For example, a user in the Computer
88: Science Department of ZZZ University might have the Account:
89:
90: user,cs.zzz.edu,zzz.edu
91:
92: But if addresses must be specified down to the name of an
93: individual host computer, you can use hostnames, too. You
94: might include the full domain name of the computer:
95:
96: user,zebra.cs.zzz.edu,zzz.edu
97:
98: Or, if you can guarantee that there is no other "zebra" in
99: "zzz.edu", you might use just the host name as it is used on
100: the internal network:
101:
102: user,zebra,zzz.edu
103:
104:
105: TABLE ns-6.1. SAMPLE MESSAGE FOR USERS AT SITE AAA.EDU
106: +--------------------------------------------------------------------+
107: |HEADER FIELDS |
108: +--------------------------------------------------------------------+
109: |To: [email protected] |
110: |Subject: User Name Server registrations for aaa.edu |
111: +--------------------------------------------------------------------+
112: |BODY OF MESSAGE |
113: +--------------------------------------------------------------------+
114: |Account |
115: | alice,aaa.edu,aaa.edu |
116: |MBox |
117: | [email protected] |
118: |CsnPass |
119: | abc123 |
120: |FullName |
121: | Alice A. Amherst |
122: |Address |
123: | office: AAA College home: 456 Something St. |
124: | Computer Science Dept. Somewhere, MA 00000 |
125: | 123 Anything St. |
126: | Anywhere, MA 00000 |
127: |Phone |
128: | office: 617/123-4567 x89 home: 617/765-4321 |
129: |Misc |
130: | tcp 1 local area networks amhearst, amerst |
131: |- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
132: |Account |
133: | albert,aaa,aaa |
134: |MBox |
135: | [email protected] |
136: |CsnPass |
137: | efghij |
138: |FullName |
139: | Albert B. Carlson |
140: |Address |
141: | office: AAA College home: 2728 Denver Avenue ... |
142: +--------------------------------------------------------------------+
143:
144:
145: TABLE ns-6. SAMPLE MESSAGE FOR THE CS DEPARTMENT OF ZZZ.EDU
146: +--------------------------------------------------------------------+
147: |HEADER FIELDS |
148: +--------------------------------------------------------------------+
149: |To: [email protected] |
150: |Subject: User Name Server registrations for cs.zzz.edu |
151: +--------------------------------------------------------------------+
152: |BODY OF MESSAGE |
153: +--------------------------------------------------------------------+
154: fi/adr-2|Account |
155: | zack,zebra.cs.zzz.edu,zzz.edu |
156: |MBox |
157: | [email protected] |
158: |CsnPass |
159: | xyz321 |
160: |FullName |
161: | Zack Z. Zimmerman |
162: |Address |
163: | office: ZZZ University ... (etc.) ... |
164: +--------------------------------------------------------------------+
165:
166: -------------------------------------------------------
167:
168: REFERENCES (Available from the CSNET Info Server):
169:
170: Topics under Request: info
171:
172: adr-1 CSNET Addresses and the Domain System
173: adr-2 Transition to Domains
174:
175: Topics under Request: rfc
176:
177: RFC733 "Standard for the Format of ARPA Network Text Messages", David H.
178: Crocker (The Rand Corporation), John J. Vittal (Bolt Beranek and
179: Newman Inc.), Kenneth T. Pogran (Massachusetts Institute of
180: Technology), D. Austin Henderson, Jr.(Bolt Beranek and Newman Inc.) 21
181: November 1977.
182:
183: RFC822 "Standard for the Format of ARPA Internet Text Messages", David H.
184: Crocker (University of Delaware), August 1982.
185:
186: RFC882 "Domain Names - Concepts and Facilities", P. Mockapetris
187: (Information Sciences Institute, University of Southern California),
188: November 1983.
189:
190: RFC883 "Domain Names - Implementation and Specification", P. Mockapetris
191: (Information Sciences Institute, University of Southern California),
192: November 1983.
193:
194: RFC920 "Domain Requirements", J. Postel and J. Reynolds (Information
195: Sciences Institute, University of Southern California), October 1984.
196:
197: RFC921 "Domain Names System Implementation Schedule - Revised", Jon Postel
198: (Information Sciences Institute, University of Southern California),
199: October 1984.
200:
201: RFC973 "Domain System Changes and Observations", Paul Mockapetris
202: (Information Sciences Institute, University of Southern California),
203: January 1983. Supplements RFC 883.
204:
205: RFC974 "Mail Routing and the Domain System", Craig Partridge (CSNET CIC,
206: BBN Laboratories, Inc.), January 1986.
207:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.