As per Relevance of the word standard, we have this rfc below:
Network Working Group
Request for Comments: 945
May 1985
A DoD Statement on the NRC
STATUS OF THIS
This RFC reproduces a letter from the Assistant Secretary of
for Command, Control, Communications, and Intelligence (ASDC3I)
the Director of the Defense Communications Agency (DCA). This
is distributed for information only. Distribution of this memo
unlimited
In December 1978, the Principal Deputy Under Secretary of Defense
Research and Engineering, Gerald P. Dinneen, USDR&E, issued
memorandum mandating the use of TCP/IP for all packet-oriented
networks where there is potential for host-to-host
across network or subnetwork boundaries, and designating the
Communications Agency as the DoD Executive Agent for
communications protocols (see IEN-152).
In April 1980, the Assistant Secretary of Defense for Communications
Command, Control, and Intelligence, Gerald P. Dinneen, ASDC3I,
a memorandum reaffirming the requirement of TCP/IP, confirming
role of DCA as the Executive Agent, and approving a plan for
organization and activities of the Executive Agent (see IEN-152).
In March 1982, Richard D. DeLauer, ASDC3I, issued a
reaffirming the requirement for the use of TCP/IP, and
the role of DCA as Executive Agent (see IEN-207).
However, there is also a DoD policy of long standing to use non-
standards when such standards are available and meet the
requirements. This policy is cited in DeLauer's memorandum
Because questions were raised about the DoD use of TCP/IP as
protocol standard, while the ISO is developing an differing set
standards, and the NBS is working toward establishing the
standards as FIPS, in May 1983 the National Research Council (NRC
was asked jointly by DoD and NBS to study the issues and recommend
course of action. The final report of the NRC committee
published in February 1985 (see RFC-942).
The enclosed letter is from Donald C. Latham (ASDC3I) to
transmitting the NRC report and requesting specific actions
to the recommendations of the report
Postel [Page 1]
RFC 945 DOD Statement on NRC
DEPARTMENT OF DEFENSE April 1985
Assistant Secretary of
Washington, D.C., 20301-3040
Command, Control
MEMORANDUM FOR DIRECTOR, DEFENSE COMMUNICATIONS
SUBJECT: National Research Council Report on Transport Protocols
DoD Data
Attached is the final report on "Transport Protocols for
of Defense Data Networks" from the National Research Council (Board
Telecommunications and Computer Applications, Commission on
and Technical Systems). The report recommends that DoD
adopt the International Standards Organization Transport Protocol (TP-4)
and Internetwork Protocol (IP) as a DoD co-standard to the current
standard Transmission Control Protocol (TCP) and IP and move
toward exclusive use of TP-4.
Whenever international standards are available and can be used
support military requirements, they will be implemented as rapidly
possible to obtain maximum economic and interoperability benefits
However, TP as a proven commercial offering is not available at
time. The progress of TP will be monitored carefully and
commercially available, TP will be tested and evaluated for use
military application
In order to insure that DoD is in a posture to evaluate TP once
is in wider use in the commercial sector, request you initiate
following actions
(1) develop the DoD military requirement specification for TP
insure that industry is aware of DoD needs as TP is
implemented
(2) insure that appropriate advisory representation is provided
commercial standards working groups that are currently
TP under the auspices of the National Bureau of Standards
(3) insure that the DCA protocol test facility can accommodate
testing as required when commercial implementations
available
(4) develop a transition strategy for Option 2 of the report
include estimated resource requirements
(5) evaluate the detailed recommendations presented in the
(pages 61-64) as they apply to Option 2.
Donald C.
Postel [Page 2]
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
