![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to domain-1 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 domain-1 CVS log | Up to [Research Unix] / researchv10dc / doc / csnet |
1.1 root 1: From research!mtune!rutgers!SH.CS.NET!cic Tue Sep 29 21:02:53 1987
2: Received: by mtune.ATT.COM (smail2.5)
3: id AA10125; 29 Sep 87 21:02:53 EDT (Tue)
4: Received: by RUTGERS.EDU (5.54/1.14)
5: id AA19280; Tue, 29 Sep 87 18:18:31 EDT
6: Message-Id: <[email protected]>
7: Received: by SH.CS.NET id ae10308; 29 Sep 87 15:25 EDT
8: Date: Tue, 29 Sep 87 14:24:49 EDT
9: Subject: domain-1 Domain Application for CSNET Members
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: domain-1
16: Document Updated: 13 Jul 87
17: Subject: Application for a Second-Level Domain for a CSNET Member
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: Dear CSNET Member:
25:
26: Please complete the application at the end of this message and return
27: the CSNET CIC by U.S. Mail or by EMail to [email protected]. We will send
28: your application to the NIC and notify you when the registration is
29: completed.
30:
31: The name that you choose for your organization should conform to the
32: Domain Naming System adopted by the Defense Data Network (DDN).
33:
34: The DDN is composed of the ARPANET, an experimental research and
35: development network, and the MILNET, an operational military network.
36: The Internet is composed of the DDN, plus other networks that share the
37: same protocols, including the CSNET X25Net and NSFNET Regional Networks.
38:
39: CSNET PhoneNet sites can exchange electronic messages with the Internet
40: through RELAY.CS.NET, which also connects PhoneNet sites to each other,
41: and to other networks, public and private.
42:
43: In the past, the addresses used by the DDN were based upon individual
44: host computers (as were the addresses used by most other multi-computer
45: neworks). The domain system is different -- it sets up the
46: organization, not the physical hardware, as the basic unit. All users
47: at the same organization have addresses in the same domain, regardless
48: of the hardware they use or the route used to deliver their messages.
49:
50: Domain names for organizations must be registered with the Network
51: Information Center (NIC) of the DDN. The CSNET CIC has arranged with
52: the DDN NIC to take care of the registration process for PhoneNet sites.
53:
54: The information that is required to translate domain names into routes
55: between hosts is stored on Internet host computers in dynamic database
56: programs called "domain servers". CSNET PhoneNet sites cannot run their
57: own domain servers, since they do not have direct real-time access to
58: the Internet; instead, they must arrange with Internet hosts to perform
59: this function. The CSNET CIC runs a domain server on RELAY.CS.NET, with
60: a backup on SH.CS.NET, and offers to be the domain server for any
61: PhoneNet site that needs this service.
62:
63: Domain names are organized in a hierarchical tree structure. At the top
64: is a set of top-level domain names chosen and administered by the DDN
65: NIC. The top-level domains for the United States represent classes of
66: organizations:
67:
68: COM Commercial organizations MIL Department of Defense
69: EDU Educational organizations NET Administrative organizations
70: GOV Civilian government for networks, e.g., CSNET.
71: ORG Nonprofit organizations ARPA Temporary top-level domain,
72:
73: Non-US countries have their own top-level domains, named for the
74: 2-letter country codes of the International Standards Organization (ISO
75: standard 3166), for example, AU (Australia), NZ (New Zealand), IL
76: (Israel) and UK (United Kingdom). If your organization is based in a
77: country other than the United States, you should contact the CSNET CIC
78: for information about your top-level domain.
79:
80: Second-level domains represent individual organizations. Hypothetical
81: examples of domains for organizations might be:
82:
83: OXBRIDGE.EDU Oxbridge University
84: WIDGETS.COM Widgets Mfg. Co., Inc.
85: THINKTANK.ORG The Thinktank Institute
86:
87: Each CSNET site should form its domain name by selecting the appropriate
88: top-level domain, and choosing a second-level domain. The CSNET CIC
89: will check the combination to make sure that it is unique.
90:
91: Once your organization has been registered as a second-level domain, you
92: may freely create lower-level domains, according to your needs.
93:
94: The pattern for an electronic mail address is:
95:
96: user@domain
97:
98: where "domain" is a string of words separated by periods. Lower-level
99: domains are arranged left to right in, ascending order of level. The
100: domain ends with a top-level domain. Any number of lower-level domains
101: may be used.
102:
103: A domain may represent a subdivision of an organization (at any level),
104: or an individual host computer.
105:
106: Examples of addresses might be:
107:
108: [email protected] Oxbridge.edu either has no subdomains,
109: or hides its subdomains.
110: [email protected] Engineering Dept within oxbridge.edu.
111: [email protected] AI project in the Computer Science Dept.
112: [email protected] Workstation in the Computer Center.
113:
114: If you have further questions about domains, please send a message to
115: [email protected], or call the CSNET CIC Hotline at (617)497-2777.
116:
117:
118:
119:
120:
121:
122: APPLICATION FOR A SECOND-LEVEL DOMAIN FOR A CSNET MEMBER
123:
124:
125: 1) ORGANIZATION NAME
126:
127: What is your organization's name? _____________________________________
128: Example: "Oxbridge University"
129:
130: ------------------------------------------------------------------------
131:
132: 2) DOMAIN NAME
133:
134: What domain name do you want? _______________________________________
135: Example: "OXBRIDGE.EDU"
136:
137: In general, the NIC strongly encourages you to keep the second-level
138: domain name (e.g., OXBRIDGE) down to 12 characters. Technically, the
139: names can be much longer, but long names are hard to type.
140:
141: ------------------------------------------------------------------------
142:
143: 3) OTHER NETWORKS AT SITE.
144:
145: Is there a local electronic mail
146: network within your organization? ______________________________________
147:
148: Please give the approximate number of host computers. _________________
149:
150: Does your organization have connections to other networks that can
151: access the Internet by electronic mail, such as the ARPANET/MILNET,
152: an NSFNET Regional Network, UUCP, or BITNET? Please give the
153: network, the department of your organization, and the names of the
154: principal host or hosts. Example: Example: "Our computer science
155: department has the UUCP host "oxbridge-vax", and our campus
156: computing center has the BITNET host "OXBRVM".
157:
158:
159: _________________________________________________________________
160:
161: _________________________________________________________________
162:
163: _________________________________________________________________
164:
165: _________________________________________________________________
166:
167: Have you reached an agreement about your domain name with the
168: people in your organization who are concerned with other networks?
169:
170: --------------
171:
172: You should be aware that the NIC will expect the CSNET Administrative
173: and Technical Liaisons at your site to act as domain liaisons for the
174: second-level domain at your organization.
175:
176: ------------------------------------------------------------------------
177:
178: 4) DOMAIN SERVERS
179:
180: Do you want CSNET to run your domain servers for you? ______________
181:
182: If you are a CSNET PhoneNet site, you should answer yes, unless you
183: have already made arrangements with another larger organization.
184: At any time in the future, you can easily change domain servers.
185:
186: If you want to register through CSNET but intend to use a domain
187: server other than RELAY.CS.NET, please include the names of the
188: Internet hosts that have agreed to act as your domain servers.
189:
190: _________________________________________________________________
191:
192: _________________________________________________________________
193:
194: _________________________________________________________________
195:
196:
197: - END -
198:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.