As per Relevance of the word internet, we have this rfc below:
Network Working Group J.
Request for Comments: 902 J.
July 1984
ARPA-Internet Protocol
Status of this
This memo is a policy statement on how protocols become
standards for the ARPA-Internet and the DARPA research community
This is an official policy statement of the ICCB and the DARPA
Distribution of this memo is unlimited
The purpose of this memo is to explain how protocol standards
adopted for the ARPA-Internet and the DARPA research community
There are three important aspects to be discussed: the process,
authority, and the complex relationship between the DARPA
and the DDN community. To do this some background must be given
some of the players described
DARPA = Defense Advanced Research Projects
DDN = Defense Data
The DARPA
The DARPA world is headed up by the DARPA office. DARPA
research on many subjects with a number of contractors. This set
contractors is called the "DARPA research community".
typically casts its research efforts into "programs" that
work by several contractors. One program is the "Internet Program",
which is researching computer communications issues and
experimental communication systems. When the experiments
successful, the results are often put into use to support
work in the Internet Program and other DARPA research programs.
this way, DARPA developed the ARPANET, SATNET, Packet Radio Networks
and the Internet
In 1981 DARPA established the Internet Configuration Control
(ICCB) to help manage the DARPA Internet Program
Postel & Reynolds [Page 1]
RFC 902 July 1984
DARPA Internet Protocol
The
The concerns of the ICCB fall into two categories
Short Term Issues
Keeping the Internet operating as an on-going resource, i.e.,
dealing with problems that arise due to the growth in the
of the system and the level of use of the system.
this suggests research on new procedures and algorithms,
suggests changes to the existing protocols and procedures
Sometimes the results of long range research become
and their introduction into the current system becomes a
term concern
Long Term Issues
The ICCB also considers communication problems related to
Internet more abstractly. The ICCB suggests to DARPA
research topics and experiments. The ICCB may act as
sounding board for ideas suggested by others
DARPA has delegated some aspects of the management of the
Program and operation of the (experimental) ARPA-Internet for
DARPA research community to the ICCB
The members of ICCB were chosen to represent a spectrum of
and viewpoints. The ICCB members are from different organizations
their individual backgrounds specialize in different
systems and their viewpoints on computer communication issues
diverse
The chairman of the ICCB is also the "Internet Architect", and
assistant chairman is the "Deputy Internet Architect". The
currently has 12 members. The Internet Architect is Dave Clark
MIT, and the Deputy Internet Architect is Jon Postel of ISI
The DDN
The DDN is a communication system for DoD operational use.
integrates many networks and communication systems now used
planned within the DoD. One part of the DDN system is networks
are also part of the Internet, specifically MILNET and the
connected to it
The DDN is managed by the DDN Program Management Office (DDN-PMO).
The DDN-PMO sets policy for the use of DDN facilities and
protocol standards established for use in the DDN networks
Postel & Reynolds [Page 2]
RFC 902 July 1984
DARPA Internet Protocol
Within the DoD, there are three protocol committees: the
Standard Steering Group (PSSG), the Protocol Standard Technical
(PSTP), and the Protocol Configuration Control Board (PCCB).
committees have members that represent most elements of the DoD
Generally, they develop and recommend guidelines for
standardization and usage to the DDN-PMO, and to all of the DoD.
PSSG is a policy setting committee for all of DoD on matters
protocols standards
The Relationship between the DARPA World and the DDN
There is cooperation between DDN-PMO and DARPA about the Internet.
few people serve on both the DoD committees (PSSG, PSTP, or PCCB)
the DARPA committee (ICCB). There are good working
between the key people in the DARPA office and the DDN-PMO,
between the technical people in both worlds at lower levels
For example, the ICCB may decide that a certain protocol is to
used in the ARPA-Internet, and develop an implementation plan
schedule. The DDN-PMO would separately consider the issue. It
decide to require that protocol to be implemented in DDN on the
schedule, or it may decide to wait for some results from the
experiment with that protocol before committing to a schedule, or
may decide that that protocol is not required in the DDN
There are two documents that specify TCP. RFC-793 is the
specification of the DARPA research community. Military
1778 is the official specification of the DDN community. The
documents specify the same protocol
Organizations that are connected to the Internet through
derived from DARPA follow the rules set by the ICCB and DARPA
Organizations that are connected to the Internet through
derived from DDN-PMO follow the rules set by the DDN-PMO
DARPA Official Protocol
Official protocols for the ARPA-Internet and DARPA research
are specified in RFCs and should have that designation indicated
the first few paragraphs of the defining RFC. That is, the
defining an official protocol should have a policy statement
says
"This RFC specifies a standard for the DARPA community. Hosts
the ARPA-Internet are expected to adopt and implement
standard.",
Postel & Reynolds [Page 3]
RFC 902 July 1984
DARPA Internet Protocol
or something quite similar
Also, there is a memo titled "Official Protocols". This document
issued occasionally as an RFC that describes all the
protocols of the ARPA-Internet. This document provides
on each protocol; its status (experimental, required, etc.),
specification, additional comments, other references, dependencies
and the person to contact. The most recent issue is RFC-901.
RFCs are coordinated by the RFC Editor and distributed by the
Information Center (NIC). The RFC documents are stored as
files in the NIC's computer. Announcements of new RFCs are sent to
mailing list of interested people. The RFC Editor is Jon Postel
The Normal Development of an DARPA Protocol
There probably never has been a "normal" case. In most
some exception or another has been made to the following procedure
The Typical Chain of
The development of a protocol starts with some discussion
random people in messages and meetings over an idea of a
protocol and the form it ought to take
Someone writes a draft and proposes this draft to a group
people who are interested in the problem. They suggest
and iterate the discussion. Eventually, they may decide that
have a reasonable definition of the new protocol and then
this definition on to the RFC Editor
The next step is that the RFC Editor sends a draft to other
who might also be interested in the problem. These people
number just a few, or be part of a large mailing list.
upon the results from this selected informal group, the draft
be revised and rewritten several times
When this process stabilizes, the protocol draft is sent out as
RFC, identified as a draft proposal of a protocol that may
an official protocol. The RFC is sent to the ARPA-Internet
at large
After a certain amount of time, if only a few comments are
back, some people may try to implement the draft protocol
Test implementation of a protocol is a difficult management issue
Postel & Reynolds [Page 4]
RFC 902 July 1984
DARPA Internet Protocol
Experiments must be done with a small number of participants
to the difficulty in changing many implementations at the
time if changes in the protocol are necessary
In cases where the ICCB deems it necessary, a set of
implementations will be done. A few participants are
(typically 5 or fewer) for such experiments. This may lead
revision of the protocol before further implementations
encouraged or before the protocol is made official
If no problems arise, a new RFC is issued containing the
definition of the protocol, and that the protocol is an
protocol of the ARPA-Internet and DARPA research community
In general, lower level protocols are more critically judged
higher level protocols (for example, a protocol like TCP would
subject to more careful study than an application like the
protocol).
The Bottom
For the ARPA-Internet and the DARPA research community, DARPA is
charge. DARPA delegates the authority for protocol standards to
ICCB. The ICCB delegates the actual administration of the
standards to the Deputy Internet Architect
For the DoD in general, the PSSG is in charge. The PSSG
the authority for the day to day management of protocol standards
the DDN to the DDN-PMO
Postel & Reynolds [Page 5]
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
