As per Relevance of the word technical, we have this rfc below:
Network Working Group J.
Request for Comments: 920 J.
October 1984
Domain
Status of this
This memo is a policy statement on the requirements of establishing
new domain in the ARPA-Internet and the DARPA research community
This is an official policy statement of the IAB and the DARPA
Distribution of this memo is unlimited
This memo restates and refines the requirements on establishing
Domain first described in RFC-881 [1]. It adds considerable
to that discussion, and introduces the limited set of top
domains
The Purpose of
Domains are administrative entities. The purpose and expected use
domains is to divide the name management required of a
administration and assign it to sub-administrations. There are
geographical, topological, or technological constraints on a domain
The hosts in a domain need not have common hardware or software,
even common protocols. Most of the requirements and limitations
domains are designed to ensure responsible administration
The domain system is a tree-structured global name space that has
few top level domains. The top level domains are subdivided
second level domains. The second level domains may be
into third level domains, and so on
The administration of a domain requires controlling the assignment
names within that domain and providing access to the names and
related information (such as addresses) to users both inside
outside the domain
Postel & Reynolds [Page 1]
RFC 920 October 1984
Domain
General Purpose
While the initial domain name "ARPA" arises from the history of
development of this system and environment, in the future most of
top level names will be very general categories like "government",
"education", or "commercial". The motivation is to provide
organization name that is free of undesirable semantics
After a short period of initial experimentation, all
ARPA-Internet hosts will select some domain other than ARPA for
future use. The use of ARPA as a top level domain will
cease
Initial Set of Top Level
The initial top level domain names are
ARPA = The current ARPA-Internet hosts
GOV = Government, any government related domains meeting
second level requirements
EDU = Education, any education related domains meeting
second level requirements
COM = Commercial, any commercial related domains meeting
second level requirements
MIL = Military, any military related domains meeting
second level requirements
ORG = Organization, any other domains meeting the
level requirements
The English two letter code (alpha-2) identifying a
according the the ISO Standard for "Codes for
Representation of Names of Countries" [5].
Postel & Reynolds [Page 2]
RFC 920 October 1984
Domain
A multiorganization may be a top level domain if it is large
and is composed of other organizations; particularly if
multiorganization can not be easily classified into one of
categories and is international in scope
Possible Examples of
The following examples are fictions of the authors' creation,
similarity to the real world is coincidental
The UC
It might be that a large state wide university with, say,
campuses and several laboratories may want to form a domain.
campus or major off-campus laboratory might then be a subdomain
and within each subdomain, each department could be
distinguished. This university might be a second level domain
the education category
One might see domain style names for hosts in this domain
these
LOCUS.CS.LA.UC.
CCN.OAC.LA.UC.
ERNIE.CS.CAL.UC.
A.S1.LLNL.UC.
A.LAND.LANL.UC.
NMM.LBL.CAL.UC.
The MIT
Another large university may have many hosts using a variety
machine types, some even using several families of protocols
However, the administrators at this university may see no need
the outside world to be aware of these internal differences.
university might be a second level domain in the
category
One might see domain style names for hosts in this domain
these
APIARY-1.MIT.
BABY-BLUE.MIT.
CEZANNE.MIT.
DASH.MIT.
Postel & Reynolds [Page 3]
RFC 920 October 1984
Domain
MULTICS.MIT.
TAC.MIT.
XX.MIT.
The CSNET
There may be a consortium of universities and industry
laboratories called, say, "CSNET". This CSNET is not a
per se, but rather a computer mail exchange using a variety
protocols and network systems. Therefore, CSNET is not a
in the sense of the ARPANET, or an Ethernet, or even
ARPA-Internet, but rather a community. Yet it does, in fact,
the key property needed to form a domain; it has a
administration. This consortium might be large enough and
have membership that cuts across the categories in such a way
it qualifies under the "multiorganization rule" to be a top
domain
One might see domain style names for hosts in this domain
these
CIC.
EMORY.
GATECH.
HP-LABS.
SJ.IBM.
UDEL.
UWISC.
General Requirements on a
There are several requirements that must be met to establish
domain. In general, it must be responsibly managed. There must be
responsible person to serve as an authoritative coordinator
domain related questions. There must be a robust domain name
service, it must be of at least a minimum size, and the domain
be registered with the central domain administrator (the
Information Center (NIC) Domain Registrar).
Responsible Person
An individual must be identified who has authority for
administration of the names within the domain, and who
takes on the responsibility for the behavior of the hosts in
domain, plus their interactions with hosts outside the domain
This person must have some technical expertise and the
within the domain to see that problems are fixed
Postel & Reynolds [Page 4]
RFC 920 October 1984
Domain
If a host in a given domain somehow misbehaves in its
with hosts outside the domain (e.g., consistently
protocols), the responsible person for the domain must
competent and available to receive reports of problems,
action on the reported problems, and follow through to
the problems
Domain Servers
A robust and reliable domain server must be provided. One way
meeting this requirement is to provide at least two
domain servers for the domain. The database can, of course,
the same. The database can be prepared and copied to each
server. But, the servers should be in separate machines
independent power supplies, et cetera; basically as
independent as can be. They should have no common point
failure
Some domains may find that providing a robust domain service
most easily be done by cooperating with another domain where
domain provides an additional server for the other
In other situations, it may be desirable for a domain to
for domain service to be provided by a third party, perhaps
hosts located outside the domain
One of the difficult problems in operating a domain server is
acquisition and maintenance of the data. In this case, the
are the host names and addresses. In some environments
information changes fairly rapidly and keeping up-to-date data
be difficult. This is one motivation for sub-domains. One
wish to create sub-domains until the rate of change of the data
a sub-domain domain server database is easily managed
In the technical language of the domain server implementation
data is divided into zones. Domains and zones are not
one-to-one. It may be reasonable for two or more domains
combine their data in a single zone
The responsible person or an identified technical assistant
understand in detail the procedures for operating a domain server
including the management of master files and zones
The operation of a domain server should not be taken on lightly
There are some difficult problems in providing an
service, primarily the problems in keeping the database up
date, and keeping the service operating
Postel & Reynolds [Page 5]
RFC 920 October 1984
Domain
The concepts and implementation details of the domain server
given in RFC-882 [2] and RFC-883 [3].
Minimum Size
The domain must be of at least a minimum size. There is
requirement to form a domain because some set of hosts is
the minimum size
Top level domains must be specially authorized. In general,
will only be authorized for domains expected to have over 500
hosts
The general guideline for a second level domain is that it
over 50 hosts. This is a very soft "requirement". It makes
that any major organization, such as a university or corporation
be allowed as a second level domain -- even if it has just a
hosts
Registration
Top level domains must be specially authorized and registered
the NIC domain registrar
The administrator of a level N domain must register with
registrar (or responsible person) of the level N-1 domain.
upper level authority must be satisfied that the requirements
met before authorization for the domain is granted
The registration procedure involves answering specific
about the prospective domain. A prototype of what the NIC
Registrar may ask for the registration of a second level domain
shown below. These questions may change from time to time. It
the responsibility of domain administrators to keep
information current
The administrator of a domain is required to make sure that
and sub-domain names within that jurisdiction conform to
standard name conventions and are unique within that domain
If sub-domains are set up, the administrator may wish to
along some of his authority and responsibility to a sub-
administrator. Even if sub-domains are established,
responsible person for the top-level domain is
responsible for the whole tree of sub-domains and hosts
This does not mean that a domain administrator has to know
Postel & Reynolds [Page 6]
RFC 920 October 1984
Domain
details of all the sub-domains and hosts to the Nth degree,
simply that if a problem occurs he can get it fixed by calling
the administrator of the sub-domain containing the problem
Top Level Domain
There are very few top level domains, each of these may have
second level domains
An initial set of top level names has been identified. Each of
has an administrator and an agent
The top level domains
ARPA = The ARPA-Internet *** TEMPORARY ***
Administrator:
Agent: The Network Information
Mailbox: HOSTMASTER@SRI-NIC.
GOV =
Administrator:
Agent: The Network Information
Mailbox: HOSTMASTER@SRI-NIC.
EDU =
Administrator:
Agent: The Network Information
Mailbox: HOSTMASTER@SRI-NIC.
COM =
Administrator:
Agent: The Network Information
Mailbox: HOSTMASTER@SRI-NIC.
MIL =
Administrator: DDN-
Agent: The Network Information
Mailbox: HOSTMASTER@SRI-NIC.
Postel & Reynolds [Page 7]
RFC 920 October 1984
Domain
ORG =
Administrator:
Agent: The Network Information
Mailbox: HOSTMASTER@SRI-NIC.
The English two letter code (alpha-2) identifying a
according the the ISO Standard for "Codes for
Representation of Names of Countries" [5].
As yet no country domains have been established. As they
established information about the administrators and
will be made public, and will be listed in subsequent
of this memo
A multiorganization may be a top level domain if it is large
and is composed of other organizations; particularly if
multiorganization can not be easily classified into one of
categories and is international in scope
As yet no multiorganization domains have been established.
they are established information about the administrators
agents will be made public, and will be listed in
editions of this memo
Note: The NIC is listed as the agent and registrar for all
currently allowed top level domains. If there are other
that would be more appropriate agents and registrars for some
all of these domains then it would be desirable to reassign
responsibility
Second Level Domain
Each top level domain may have many second level domains.
second level domain must meet the general requirements on a
specified above, and be registered with a top level
administrator
Postel & Reynolds [Page 8]
RFC 920 October 1984
Domain
Third through Nth Level Domain
Each second level domain may have many third level domains, etc
Every third level domain (through Nth level domain) must meet
requirements set by the administrator of the immediately higher
domain. Note that these may be more or less strict than the
requirements. One would expect the minimum size requirements
decrease at each level
The ARPA
At the time the implementation of the domain concept was begun it
thought that the set of hosts under the administrative authority
DARPA would make up a domain. Thus the initial domain selected
called ARPA. Now it is seen that there is no strong motivation
there to be a top level ARPA domain. The plan is for the
ARPA domain to go out of business as soon as possible. Hosts
are currently members of the ARPA domain should make arrangements
join another domain. It is likely that for experimental
there will be a second level domain called ARPA in the ORG
(i.e., there will probably be an ARPA.ORG domain).
The DDN
DDN hosts that do not desire to participate in this domain
system will continue to use the HOSTS.TXT data file maintained by
NIC for name to address translations. This file will be kept up
date for the DDN hosts. However, all DDN hosts will change
names from "host.ARPA" to (for example) "host.DDN.MIL" some time
the future. The schedule for changes required in DDN hosts will
established by the DDN-PMO
Impact on
What is a host administrator to do about all this
For existing hosts already operating in the ARPA-Internet,
best advice is to sit tight for now. Take a few months
consider the options, then select a domain to join.
carefully for the impact that changing your host name will have
both your local users and on their remote correspondents
For a new host, careful thought should be given (as
below). Some guidance can be obtained by comparing notes on
other hosts with similar administrative properties have done
The owner of a host may decide which domain to join, and
Postel & Reynolds [Page 9]
RFC 920 October 1984
Domain
administrator of a domain may decide which hosts to accept into
domain. Thus the owner of a host and a domain administrator
come to an understanding about the host being in the domain. This
the foundation of responsible administration
For example, a host "XYZ" at MIT might possible be considered as
candidate for becoming any of XYZ.ARPA.ORG, XYZ.CSNET,
XYZ.MIT.EDU
The owner of host XYZ may choose which domain to join
depending on which domain administrators are willing to
him
The domain is part of the host name. Thus if USC-ISIA.ARPA
its domain affiliation to DDN.MIL to become USC-ISIA.DDN.MIL, it
changed its name. This means that any previous references
USC-ISIA.ARPA are now out of date. Such old references may
private host name to address tables, and any recorded
about mailboxes such as mailing lists, the headers of old messages
printed directories, and peoples' memories
The experience of the DARPA community suggests that changing the
of a host is somewhat painful. It is recommended that
thought be given to choosing a new name for a host - which
selecting its place in the domain hierarchy
The Roles of the Network Information
The NIC plays two types of roles in the administration of domains
First, the NIC is the registrar of all top level domains.
the NIC is the administrator of several top level domains (and
registrar for second level domains in these).
Top Level Domain
As the registrar for top level domains, the NIC is the
point for investigating the possibility of establishing a new
level domain
Top Level Domain
For the top level domains designated so far, the NIC is
administrator of each of these domains. This means the NIC
responsible for the management of these domains and
registration of the second level domains or hosts (if at
second level) in these domains
Postel & Reynolds [Page 10]
RFC 920 October 1984
Domain
It may be reasonable for the administration of some of
domains to be taken on by other authorities in the future. It
certainly not desired that the NIC be the administrator of all
level domains forever
Prototypical
To establish a domain, the following information must be provided
the NIC Domain Registrar (HOSTMASTER@SRI-NIC.ARPA):
Note: The key people must have computer mail mailboxes
NIC-Idents. If they do not at present, please remedy
situation at once. A NIC-Ident may be established by
NIC@SRI-NIC.ARPA
1) The name of the top level domain to join
For example:
2) The name, title, mailing address, phone number, and
of the administrative head of the organization. This is the
point for administrative and policy questions about the domain.
the case of a research project, this should be the
Investigator. The online mailbox and NIC-Ident of this person
also be included
For example
Organization USC/Information Sciences
Name Keith
Title Executive
Mail Address USC/
4676 Admiralty Way, Suite 1001
Marina del Rey, CA. 90292-6695
Phone Number 213-822-1511
Net Mailbox Uncapher@USC-ISIB.
NIC-Ident
3) The name, title, mailing address, phone number, and
of the domain technical contact. The online mailbox and NIC-Ident
the domain technical contact should also be included. This is
contact point for problems with the domain and for
information about the domain. Also, the domain technical contact
be responsible for hosts in this domain
Postel & Reynolds [Page 11]
RFC 920 October 1984
Domain
For example
Technical
Organization USC/Information Sciences
Name Craig Milo
Title
Mail Address USC/
4676 Admiralty Way, Suite 1001
Marina del Rey, CA. 90292-6695
Phone Number 213-822-1511
Net Mailbox Rogers@USC-ISIB.
NIC-Ident
4) The name, title, mailing address, phone number, and
of the zone technical contact. The online mailbox and NIC-Ident
the zone technical contact should also be included. This is
contact point for problems with the zone and for updating
about the zone. In many cases the zone technical contact and
domain technical contact will be the same person
For example
Technical
Organization USC/Information Sciences
Name Craig Milo
Title
Mail Address USC/
4676 Admiralty Way, Suite 1001
Marina del Rey, CA. 90292-6695
Phone Number 213-822-1511
Net Mailbox Rogers@USC-ISIB.
NIC-Ident
5) The name of the domain (up to 12 characters). This is the
that will be used in tables and lists associating the domain and
domain server addresses. [While technically domain names can
quite long (programmers beware), shorter names are easier for
to cope with.]
For example: ALPHA-
6) A description of the servers that provides the domain service
translating name to address for hosts in this domain, and the
they will be operational
Postel & Reynolds [Page 12]
RFC 920 October 1984
Domain
A good way to answer this question is to say "Our server
supplied by person or company X and does whatever their
issue server does".
For example: Our server is a copy of the server operated
the NIC, and will be installed and made operational
1-November-84.
7) A description of the server machines, including
(a) hardware and software (using keywords from the
Numbers
(b) addresses (what host on what net for each connected net
For example
(a) hardware and
VAX-11/750 and UNIX,
IBM-PC and MS-DOS,
DEC-1090 and TOPS-20
(b)
10.9.0.193 on
8) An estimate of the number of hosts that will be in the domain
(a) initially
(b) within one year
(c) two years,
(d) five years
For example
(a) initially = 50
(b) one year = 100
(c) two years = 200
(d) five years = 500
Postel & Reynolds [Page 13]
RFC 920 October 1984
Domain
We would like to thank the many people who contributed to this memo
including the participants in the Namedroppers Group, the ICCB,
PCCB, and especially the staff of the Network Information Center
particularly J. Feinler and K. Harrenstien
[1] Postel, J., "The Domain Names Plan and Schedule", RFC-881,
Information Sciences Institute, November 1983.
[2] Mockapetris, P., "Domain Names - Concepts and Facilities",
RFC-882, USC Information Sciences Institute, November 1983.
[3] Mockapetris, P., "Domain Names - Implementation
Specification", RFC-883, USC Information Sciences Institute
November 1983.
[4] Postel, J., "Domain Name System Implementation Schedule",
RFC-897, USC Information Sciences Institute, February 1984.
[5] ISO, "Codes for the Representation of Names of Countries",
ISO-3166, International Standards Organization, May 1981.
[6] Postel, J., "Domain Name System Implementation Schedule -
Revised", RFC-921, USC Information Sciences Institute,
1984.
[7] Mockapetris, P., "The Domain Name System", Proceedings of
IFIP 6.5 Working Conference on Computer Message Services
Nottingham, England, May 1984. Also as ISI/RS-84-133,
June 1984.
[8] Mockapetris, P., J. Postel, and P. Kirton, "Name Server
for Distributed Systems", Proceedings of the
International Conference on Computer Communication, October 30
to November 3 1984, Sidney, Australia. Also as ISI/RS-84-132,
June 1984.
Postel & Reynolds [Page 14]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
