As per Relevance of the word february, we have this rfc below:
Network Working Group Jon
Request for Comments: 897
February 1984
Updates: RFC 881
Domain Name System Implementation
Status of this
This memo is a policy statement on the implementation of the
Style Naming System in the Internet. This memo is a partial
of RFC 881. This is an official policy statement of the ICCB and
DARPA
The intent of this memo is to detail the schedule for
implementation for the Domain Style Naming System. The
of how this system works is to be found in the references
The Current
Simple
Hosts in the ARPA research and DDN operational communities
currently assigned names in a flat or global name space
character strings. There are some limits on these names.
must start with a letter, end with a letter or digit and have
letters or digits or hyphen as interior characters. Case is
significant
For example: USC-
Every host in the Internet is expected to have a way
translating the name of any other host into its Internet address
By and large, the name to address translation is done by
up the information in a table of all hosts
The maintenance of this table is centralized at the
Information Center (NIC). Each host is expected to obtain
current copy of the table on a timely basis
Interface to the
A great deal of mail moves between the Internet and
"systems" that somehow transport mail among computers. This
currently done by hiding some sort of "other-system"
information in the local-part of the mail address and using
mail-relay host in the host-part of the mailbox
Postel [Page 1]
RFC 897 February 1984
Domain Implementation
For example
OBERST%EDUCOM.MAILNET@MIT-
EDMISTON.CIC@CSNET-
The Future
Hierarchical
Because of the growth of the Internet, structured names (or
style names) will be used. Each element of the structured
will be a character string (with the same constraints
previously applied to the simple names).
For example: F.ISI.USC.
Every host in the Internet will be expected to have a way
translating the name of any other host into its Internet address
By and large, the name to address translation will be done
interacting with a service. There will be a number of
that each hold a portion of the name to address information
The maintenance of the translation data will be subdivided
distributed
There are several stages of implementation for the servers
several levels of development for use of the domain style names
First, there is the simple substitution of the domain style
for the current host names, and the subdivision of these
several domains. At this stage all domain style names
translate to host addresses and all domain style names have
components
For example: USC-ISIF.ARPA or USC-ISIA.
and: Postel@USC-ISIF.ARPA or Kahn@USC-ISIA.
Here we expect that "USC-ISIF.ARPA" is the name of an
host and that we can send mail for "Postel" to the SMTP port
that host. It may be that some backward host can still fake
by ignoring the ".ARPA" and looking up an address
"USC-ISIF".
Postel [Page 2]
RFC 897 February 1984
Domain Implementation
Using the domain name servers (but not the tables)
forwarding may be supported. A domain name server query
say "I want to send mail to ABCDEF.ARPA". The response
be "to send mail to ABCDEF.ARPA send it to the mail
GHIJKL.ARPA at address 123.123.123.123".
Second, there is an extension to more name components
For example: F.ISI.USC.ARPA or A.USC-ISI.
and: Postel@F.ISI.USC.ARPA or Kahn@A.USC-ISI.
Here we expect that "F.ISI.USC.ARPA" is the name of an
host and that we can send mail for "Postel" to the SMTP port
that host. It is unlikely that a backward host can hack
at all
Third, there is an extension to domain style names that
represent only organizations or administrative entities.
a host that represents such entities may require a level
indirection in the search
For example: USC-ISI.ARPA or ARPA.
and: Postel@USC-ISI.ARPA or Kahn@ARPA.
Here we don't count on "USC-ISI.ARPA" being the name of
Internet host. When we want to send mail to "Postel" we
the domain name server about sending mail to "USC-ISI.ARPA".
The server will tell us the name (and address) of a
Internet host that handles mail on this organizations behalf
for example, "F.USC-ISI.ARPA = 10.2.0.52". We then send
for "Postel" to the SMTP port on F.USC-ISI.ARPA
Interface to the
Mail will continue to move between the Internet and
"systems". This may be done by designating some sort
"other-system" representative organization in the domain
data bases that can indirect mail to a mail-relay host
For example
OBERST@EDUCOM.
EDMISTON@CIC.
Postel [Page 3]
RFC 897 February 1984
Domain Implementation
The Transition
Actually, the situation is a bit more complicated, of course.
number of hosts are already using domain style names under
constraint that their domain style name is exactly their old
name with the string ".ARPA" appended. The first transition step
to have all hosts do this, and then to eliminate the user of
style names altogether
Please note carefully that two types of changes are being made
One is a change in the support mechanism for translating a
name to an internet address
that is from using local copies of a full centrally
table to dynamically accessing a distributed set of
each posesing a portion of a data base maintained in
distributed fashion
The other is a change in the host names themselves
from a flat global space of unstructured strings to
hierarchical structure of names
There are four steps to the transition plan
First, change from old names to domain style names
host-name --> host-name.
Second, one domain to a few domains
host-name.ARPA --> host-name.ARPA and host-name.
Third, change from using central tables to using name servers
Fourth, allow many domains
There are two communities that are taking slightly different
in this transition. The ARPA research community is making the
transition. The DDN operational community is making the change
naming on the same schedule, but is not requiring hosts in the
operational community make the change to using servers at the
time (they can if they want to). The DDN PMO will establish
schedule for that change at a later time. The NIC will maintain
central table of all DDN operational hosts
Postel [Page 4]
RFC 897 February 1984
Domain Implementation
Interface to the
The interchange of mail with "other-systems" will have to
pretty much as it does now (except that RELAY-HOST will
RELAY-HOST.ARPA) until organization names can be used.
representative organizations can be designated for
"other-system" in the domain server data bases that will
indirectly specify a mail-relay host
Policy
The names of hosts will be changed to domain style names. Hosts
begin to use domain style names on 14-Mar-84 and the use of old
names will be completely phased out before 2-May-84.
This applies to both the ARPA research hosts and the DDN
hosts
All Hosts Change
The impact of introducing the domain style names is that all
change their names at least once. Hosts that move to new
or subdomains may change their names several times
Hosts have an official (or primary) name and possibly
nicknames. When mail is sent from a host, the official name
used in the mail header address fields
Suppose, that in the old days before domains were thought of,
host changed its name. What is the impact on users of
the name of a host? Suppose one host changed its name from FOO
BAR
Mail that was sent before the name was changed can not
answered using mail program commands that automatically
in the return address. While it may be possible to
special tricks to fix up the "From" or the "To"
addresses, the "Cc" addresses are very difficult to correct
Mail that was sent to JOE@ABC from FRED@FOO can not
answered unless the change of name is known to the user
the mail program an ABC and the host name BAR
for FOO
Postel [Page 5]
RFC 897 February 1984
Domain Implementation
Mail that is sent to JOE@ABC from SAM@DEF with a cc
FRED@FOO can not be answered easily
Mailing
Any mailing lists that have mailboxes on the host
changed names will now have incorrect entries
The point is that while the host that changed names may be able
use special tricks for a while to fix things up for the users,
is difficult for other hosts to do this
A general trick is to make the old name a nickname for the
for some period of time
The introduction of domain style names means that all hosts
their names essentially at the same time
For example, USC-ISIF changes to USC-ISIF.
To lessen the resulting havoc, the initial set of new names has
fixed relationship to the old names. The first set of
style names is exactly the old names with the domain name "ARPA
appended. That is, if a hosts old name was "HOST-NAME", then
new name is "HOST-NAME.ARPA".
To further lessen the havoc, there will be a period of time
both the old and the new names are allowed. That is, the
names will be nicknames for a while
Primary
In to old style names, host have an official or primary names
may have several nicknames. For example
Primary Name
USC-ISIF
ADA-VAX ISI-VAXB AJPO
In any case, the data base in such than given any of the names
a host one can find the address, and given the address one
find the primary name
In the new domain style name system this property must
maintained. That is, given the Internet address of a host
Postel [Page 6]
RFC 897 February 1984
Domain Implementation
must be able to find the primary name of that host. This
for careful management of the distributed database by those
charge of the domains and subdomains
The Time
-- Nov 83 Plan and
At this point the overall plan for the implementation of
style names and name servers, and a schedule of events
published (RFC-881). Also the draft design and specification
the protocol and data base were published (RFC-882, RFC-883).
-- Nov 83 Initial Domain Style Host Name
At this point a version of the host table which includes
domain style names is made available (DHOSTS.TXT).
-- Feb 84 Domain Requirements
At this point the requirements for establishing a new domain
published as an RFC
14 Mar 84 Begin using Domain Style
At this point all hosts should start using their domain
names as their official and primary names. The standard table
host names contains domain style names as the official and
name (DHOSTS.TXT becomes HOSTS.TXT).
04 Apr 84 Server for ARPA
At this point several domain name servers are in operation
supply host name to internet address translations, one of
servers is at the NIC
04 Apr 84 Domain
At this point a master table of top level domain names and
associated servers is established at the NIC
02 May 84 Stop using old style
At this point the use of old style names must be completely
out
Postel [Page 7]
RFC 897 February 1984
Domain Implementation
02 May 84 Certain New
At this point a few new domains may be established, in
the DDN domain
06 Jun 84 General & Multilevel
At this point additional new domains may be established, if
meet the requirements. Domain style names may have more than
segments
18 Jul 84 Organizational
Domain style names may identify organizations. Finding an
for a host may involve a level of indirection
05 Sep 84 Decommission Host
At this point the master host table maintained by the NIC need
longer be complete for the ARPA research community. A full
of the DDN operational hosts will be maintained by the NIC
03 Oct 84 DDN Plan for Domains Name
At this point the DDN PMO will establish a plan for the
support of name to address translations in the DDN community
[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.
Postel [Page 8]
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
