As per Relevance of the word copyright, we have this rfc below:
Network Working Group R.
Request for Comments: 3109
Category: Informational R.
J.
AT&
May 2001
Request to Move STD 39 to Historic
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This memo changes the status of STD 39, BBN Report 1822,
"Specification of the Interconnection of a Host and an IMP",
Standard to Historic
1.
The Internet design grew out of the pioneering packet-
network called the ARPAnet. The ARPAnet was a mostly-US
network built of mini-computer packet switches, called
Message Processors (IMPs), that were linked by 56kbps
telephone lines. The IMPs were designed and built by Bolt, Beranek
and Neumann (BBN) under contract with ARPA, beginning in 1968.
of BBN's first tasks was to define the standard hardware
between a host and a colocated IMP. This interface was described
BBN Report 1822 [BBN1822], which was a bible for the
of the many different hosts that connected to the ARPAnet
The BBN Report 1822 host/IMP hardware interface was bit-serial
asynchronous. In 1968, the 8-bit byte had not yet been adopted as
industry standard, so the interface had to cope with word-
machines with arbitrary word length -- some common word lengths
8, 12, 16, 24, 36, and 60, but there were others. From the
viewpoint, Report 1822 defined what would today be called the link
layer access protocol for the ARPAnet
Braden, et al. Informational [Page 1]
RFC 3109 Request to Move STD 39 to Historic Status May 2001
In 1983 the US DoD moved the ARPAnet technology to TCP/IP and
off parts of the ARPAnet to form a production facility called MILNET
The DoD mandated a byte-oriented, X.25-based interface for the
IMPs. However, the machines on the research-oriented
continued to use the 1822 interface under the new Internet
suite. Therefore, BBN Report 1822 was made an Internet Standard,
39, although the report was not republished as an RFC
2.
Since the ARPAnet technology and the BBN 1822 interface are no
in use, the IESG is moving BBN Report 1822 from Standard to
status. The STD number 39 is retired
3. Security
Moving STD 39 to historic has no known effect on the security of
Internet
4.
[BBN1822] STD 39 is BBN Report 1822 "Specification for
Interconnection of a Host and an IMP". This can be
from Bolt, Beranek, and Newman, 10 Moulton Street
Cambridge, MA 02138.
Braden, et al. Informational [Page 2]
RFC 3109 Request to Move STD 39 to Historic Status May 2001
5. Authors'
Robert
USC/Information Sciences
4676 Admiralty
Marina del Rey, CA 90292-6695
Phone: +1 310-822-1511
EMail: braden@isi.
Randy
5147 Crystal
Bainbridge Island, WA US-98110
Phone: +1 206-780-0431
EMail: randy@psg.
John C.
1770 Massachusetts Ave, Suite 322
Cambridge, MA 02140,
EMail: klensin@jck.
Braden, et al. Informational [Page 3]
RFC 3109 Request to Move STD 39 to Historic Status May 2001
6. Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Braden, et al. Informational [Page 4]
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
