Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An Internetwork Architecture," XEROX Palo Alto Research Center, CSL-79-10, July 1979. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Routing Information Protocol - Hedrick Rutgers University (1999) (178 citations) (Correct)
....algorithm presented here, as well as a number of other related algorithms. The basic algorithms described in this protocol were used in computer routing as early as 1969 in the ARPANET. However, the specific ancestry of this protocol is within the Xerox network protocols. The PUP protocols (see [4]) used the Gateway Information Protocol to exchange routing information. A somewhat updated version of this protocol was adopted for the Xerox Network Systems (XNS) architecture, with the name Routing Information Protocol. See [7] Berkeley s routed is largely the same as the Routing Information ....
Boggs, D. R., Shoch, J. F., Taft, E. A., and Metcalfe, R. M., "Pup: An Internetwork Architecture", IEEE Transactions on Communications, April 1980.
Advanced Distributed Simulation through the Aggregate.. - Richard Weatherly.. (1996) (3 citations) (Correct)
....management, 3) a programmable message filtering scheme used to define the information of interest to an actor, and (4) a mechanism for providing intelligent message distribution. 3.3. 1 Inter component communications model The AIS employs a persistent connection communications model (see Boggs [8]) to provide the inter component communications for the AIS. The transport layer interface used to provide inter component communications is dictated by actor ACM ABE ABE ACM Object Time Time Object Time Management Actor 2 Protocol (Peer Level) Actor 1 Connection Protocol Actor ACM ....
Boggs, D.R. Shoch, J.F., Taft, E.A., and Metcalfe, R.M. (1979). "PUP: An Internetwork Architecture," Report CSL-79-10, XEROX Palo Alto Research Center, July.
A Caching File System for a Programmer's Workstation - Schroeder, Gifford, Needham (1985) (28 citations) (Correct)
....features available at the CFS client interface, we outline the services provided by these file servers. Each file server provides a shared hierarchical directory. Access control mechanisms define which authenticated users are able to access and manipulate each file. Using a file transfer protocol [3], new files can be stored and existing files can be read, renamed and deleted. These operations are on whole files. File names include version numbers and when a new version of a file is stored the file server automatically generates a new version number for its name. The file servers also allow ....
Boggs, D.R. et al., "PUP: an Internetwork Architecture," IEEE Trans. on Comm. 28, 4 (Apr 1980), pp. 612--634.
Experience with Processes and Monitors in Mesa - Lampson, Redell (1980) (85 citations) (Correct)
....a single monitor containing an array of representative states and a single condition variable. 6. 3 Gateway: An internetwork forwarder Another substantial application program that has been implemented in Mesa using the process and monitor facilities is an internetwork gateway for packet networks [2]. The gateway is attached to two or more networks and serves as the connection point between them, passing packets across network boundaries as required. To perform this task efficiently requires rather heavy use of concurrency. At the lowest level, the gateway contains a set of device drivers, ....
Boggs, D.R. et al. Pup: An internetwork architecture. IEEE Trans. on Communications 28, 4 (April 1980).
Hints for Computer System Design - Lampson (1983) (97 citations) (Correct)
....case, and attempts to obey it lead to many complications and inefficiencies even in the normal case. Furthermore, the client does not benefit, since it still has to deal with packets lost by host or network failure (see section 4 on end to end) Eventually the rule was abandoned. The Pup internet [3], faced with a much more variable set of transport facilities, has always ruthlessly discarded packets at the first sign of congestion. 4. Fault tolerance The unavoidable price of reliability is simplicity. C. Hoare) Making a system reliable is not really hard, if you know how to go about it. ....
Boggs, D.R. et al. Pup: An internetwork architecture. IEEE Trans. Communications COM-28, 4, April 1980, pp 612-624.
Network Working Group J. Postel Request for Comments: 762 .. - Obsoletes Iens Assigned (Correct)
No context found.
Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An Internetwork Architecture," XEROX Palo Alto Research Center, CSL-79-10, July 1979.
Unknown - (Correct)
No context found.
D.R. Boggs, J.F. Shoch, E.A. Taft, and R.M. Metcalfe. "Pup: An Internetwork Architecture." IEEE Transactions on Communications COM-28, 4, pp612-624, April 1980.
Network Working Group G. Malkin Request for Comments: 2080.. - Status Of This (Correct)
No context found.
Boggs, D. R., Shoch, J. F., Taft, E. A., and Metcalfe, R. M., "Pup: An Internetwork Architecture", IEEE Transactions on Communications, April 1980.
Network Working Group J. Saltzer Request for Comments: 1498.. - Status Of This (Correct)
No context found.
Boggs, D. R., Shoch, J. F., Taft, E. A., and Metcalfe, R. M., "PUP: An Internetwork Architecture", IEEE Trans. on Comm. 28, 4 (April, 1980) pp. 612-623.
Unknown - (Correct)
No context found.
Boggs, D. R., Shoch, J. F., Taft, E. A., and Metcalfe, R. M., "Pup: An Internetwork Architecture", IEEE Transactions on Communications, April 1980.
Network Working Group G. Malkin Request for Comments.. - Category Standards Track (Correct)
No context found.
Boggs, D. R., Shoch, J. F., Taft, E. A., and Metcalfe, R. M., "Pup: An Internetwork Architecture", IEEE Transactions on Communications, April 1980.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC