Copyright (c) 1983, 1986, 1993
The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
@(#)f.t 8.1 (Berkeley) 6/8/93
.nr H2 1 .ds RH Acknowledgements
The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
@(#)f.t 8.1 (Berkeley) 6/8/93
.nr H2 1 .ds RH Acknowledgements
\s+2Acknowledgements\s0
The internal structure of the system is patterned
after the Xerox PUP architecture [Boggs79], while in certain
places the Internet
protocol family has had a great deal of influence in the design.
The use of software interrupts for process invocation
is based on similar facilities found in
the VMS operating system.
Many of the
ideas related to protocol modularity, memory management, and network
interfaces are based on Rob Gurwitz's TCP/IP implementation for the
4.1BSD version of UNIX on the VAX [Gurwitz81].
Greg Chesson explained his use of trailer encapsulations in Datakit,
instigating their use in our system.
.ds RH References
.nr H2 1
[Boggs79] 20
Boggs, D. R., J. F. Shoch, E. A. Taft, and R. M. Metcalfe;
PUP: An Internetwork Architecture. Report CSL-79-10.
XEROX Palo Alto Research Center, July 1979.
[BBN78] 20
Bolt Beranek and Newman;
Specification for the Interconnection of Host and IMP.
BBN Technical Report 1822. May 1978.
[Cerf78] 20
Cerf, V. G.; The Catenet Model for Internetworking.
Internet Working Group, IEN 48. July 1978.
[Clark82] 20
Clark, D. D.; Window and Acknowledgement Strategy in TCP, RFC-813.
Network Information Center, SRI International. July 1982.
[DEC80] 20
Digital Equipment Corporation; DECnet DIGITAL Network
Architecture - General Description. Order No.
AA-K179A-TK. October 1980.
[Gurwitz81] 20
Gurwitz, R. F.; VAX-UNIX Networking Support Project - Implementation
Description. Internetwork Working Group, IEN 168.
January 1981.
[ISO81] 20
International Organization for Standardization.
ISO Open Systems Interconnection - Basic Reference Model.
ISO/TC 97/SC 16 N 719. August 1981.
[Joy86] 20
Joy, W.; Fabry, R.; Leffler, S.; McKusick, M.; and Karels, M.;
Berkeley Software Architecture Manual, 4.4BSD Edition.
UNIX Programmer's Supplementary Documents, Vol. 1 (PSD:5).
Computer Systems Research Group,
University of California, Berkeley.
May, 1986.
[Leffler84] 20
Leffler, S.J. and Karels, M.J.; Trailer Encapsulations, RFC-893.
Network Information Center, SRI International.
April 1984.
[Postel80] 20
Postel, J. User Datagram Protocol, RFC-768.
Network Information Center, SRI International. May 1980.
[Postel81a] 20
Postel, J., ed. Internet Protocol, RFC-791.
Network Information Center, SRI International. September 1981.
[Postel81b] 20
Postel, J., ed. Transmission Control Protocol, RFC-793.
Network Information Center, SRI International. September 1981.
[Postel81c] 20
Postel, J. Internet Control Message Protocol, RFC-792.
Network Information Center, SRI International. September 1981.
[Xerox81] 20
Xerox Corporation. Internet Transport Protocols.
Xerox System Integration Standard 028112. December 1981.
[Zimmermann80] 20
Zimmermann, H. OSI Reference Model - The ISO Model of
Architecture for Open Systems Interconnection.
IEEE Transactions on Communications. Com-28(4); 425-432.
April 1980.