1980
DOI: 10.1109/tcom.1980.1094684
|View full text |Cite
|
Sign up to set email alerts
|

Pup: An Internetwork Architecture

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
54
0

Year Published

1983
1983
1999
1999

Publication Types

Select...
5
3
2

Relationship

0
10

Authors

Journals

citations
Cited by 136 publications
(54 citation statements)
references
References 19 publications
0
54
0
Order By: Relevance
“…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.…”
Section: Give Every Man Thy Ear But Few Thy Voice;mentioning
confidence: 99%
“…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.…”
Section: Give Every Man Thy Ear But Few Thy Voice;mentioning
confidence: 99%
“…However, the specific ancestry of this protocol is within the Xerox network protocols. The PUP protocols [7] 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 [9].…”
Section: Malkin Standards Track [Page 3]mentioning
confidence: 99%
“…Client programs of Grapevine run on various workstation and server computers attached to the internet. Communication among Grapevine servers, and among clients and servers, is built on internet protocols that provide a uniform means for addressing any computer attached to any local network in order to send individual packets or to establish and use byte streams [3,16].…”
Section: Structural Overviewmentioning
confidence: 99%