PARC Universal Packet - Revision history

Jnc: /* Application protocols */ +EFTP

2024-11-16T13:34:08Z

Application protocols: +EFTP

← Older revision		Revision as of 13:34, 16 November 2024
Line 27:		Line 27:
	==Application protocols==		==Application protocols==

	PUP supported a large number of applications. Some of them, such as [[Telnet]] and [[File Transfer Protocol]], were basically the same protocols as used on the [[ARPANET]] (much as occurred with the TCP/IP suite).		PUP supported a large number of applications. Some of them, such as [[Telnet]] and [[File Transfer Protocol]], were basically the same protocols as used on the [[ARPANET]] (much as occurred with the TCP/IP suite). One very early one was [[EFTP]], which provided file transfer functionality in very spare/scant implementation environments.

	Others were novel, including protocols for printer spooling, copying disk packs, page-level remote access to file servers, name lookup, remote management, etc (although some of these capabilities had been seen before, e.g. the ARPANET already made heavy use of remote management for controlling the [[Interface Message Processor]]s which made it up).		Others were novel, including protocols for printer spooling, copying disk packs, page-level remote access to file servers, name lookup, remote management, etc (although some of these capabilities had been seen before, e.g. the ARPANET already made heavy use of remote management for controlling the [[Interface Message Processor]]s which made it up).

Jnc: /* Basic internetwork protocol */ link 'checksum'

2024-11-16T12:30:30Z

Basic internetwork protocol: link 'checksum'

← Older revision		Revision as of 12:30, 16 November 2024
Line 11:		Line 11:
	The main internet layer protocol was PUP, which roughly corresponds to the [[Internet Protocol]] (IP) layer in TCP/IP. A full PUP [[network address]] consisted of an 8-bit network number, an 8-bit host number, and a 16-bit socket number. The network number had a particular special value which meant 'this network', for use by hosts which did not (yet) know their network number.		The main internet layer protocol was PUP, which roughly corresponds to the [[Internet Protocol]] (IP) layer in TCP/IP. A full PUP [[network address]] consisted of an 8-bit network number, an 8-bit host number, and a 16-bit socket number. The network number had a particular special value which meant 'this network', for use by hosts which did not (yet) know their network number.

	Unlike TCP/IP, socket fields were part of the full network address in the PUP [[header]], so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte checksum covered the entire [[packet]].		Unlike TCP/IP, socket fields were part of the full network address in the PUP [[header]], so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte [[checksum]] covered the entire [[packet]].

	PUP packets were up to 554 bytes long (including the 20 byte PUP header), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP [[router]] was required to handle them. Unlike in IP, larger packets could not be fragmented (except locally).		PUP packets were up to 554 bytes long (including the 20 byte PUP header), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP [[router]] was required to handle them. Unlike in IP, larger packets could not be fragmented (except locally).

Jnc: /* External links */ +PUP docs in Xerox PARC archives

2023-05-11T14:27:59Z

External links: +PUP docs in Xerox PARC archives

← Older revision		Revision as of 14:27, 11 May 2023
Line 57:		Line 57:
	* Edward A. Taft, ''Pup Error Protocol'' (Xerox Parc, Palo Alto, July, 1978 and October, 1975)		* Edward A. Taft, ''Pup Error Protocol'' (Xerox Parc, Palo Alto, July, 1978 and October, 1975)
	* Jon A. Hupp, ''Pup Network Constants'' (Xerox Parc, Palo Alto, July, 1979)		* Jon A. Hupp, ''Pup Network Constants'' (Xerox Parc, Palo Alto, July, 1979)

			==External links==

			* [https://xeroxalto.computerhistory.org/_cd8_/pup/.index.html PUP] - Documentation in the Xerox PARC archives

	[[Category: Network Protocols]]		[[Category: Network Protocols]]
	[[Category: Xerox]]		[[Category: Xerox]]

Larsbrinkhoff: Category: Xerox

2022-05-04T13:47:05Z

Category: Xerox

← Older revision		Revision as of 13:47, 4 May 2022
Line 59:		Line 59:

	[[Category: Network Protocols]]		[[Category: Network Protocols]]
			[[Category: Xerox]]

Jnc: /* Basic internetwork protocol */ only local frag

2022-03-25T20:40:53Z

Basic internetwork protocol: only local frag

← Older revision		Revision as of 20:40, 25 March 2022
Line 13:		Line 13:
	Unlike TCP/IP, socket fields were part of the full network address in the PUP [[header]], so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte checksum covered the entire [[packet]].		Unlike TCP/IP, socket fields were part of the full network address in the PUP [[header]], so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte checksum covered the entire [[packet]].

	PUP packets were up to 554 bytes long (including the 20 byte PUP header), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP [[router]] was required to handle them. Unlike in IP, larger packets could be fragmented.		PUP packets were up to 554 bytes long (including the 20 byte PUP header), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP [[router]] was required to handle them. Unlike in IP, larger packets could not be fragmented (except locally).

	A protocol named the ''Gateway Information Protocol'' (a remote ancestor of [[Routing Information Protocol\|RIP]]) was used as both the [[routing protocol]] (the router information-exchange system), and for hosts to discover routers.		A protocol named the ''Gateway Information Protocol'' (a remote ancestor of [[Routing Information Protocol\|RIP]]) was used as both the [[routing protocol]] (the router information-exchange system), and for hosts to discover routers.

Jnc: /* Implementations */ +C Gateway

2022-03-24T00:12:51Z

Implementations: +C Gateway

← Older revision		Revision as of 00:12, 24 March 2022
Line 40:		Line 40:

	* [[Alto]]		* [[Alto]]
	* [[4.2BSD]]
	* [[MINITS]]
	* [[TENEX]]		* [[TENEX]]
	* [[TOPS-20]]		* [[TOPS-20]]
	* [[WAITS]]		* [[WAITS]]
			* [[4.2BSD]]
			* [[MINITS]]
			* [[C Gateway]]

	==Further reading==		==Further reading==

Larsbrinkhoff: /* Implementations */ 4.2BSD.

2022-03-23T18:54:23Z

Implementations: 4.2BSD.

← Older revision		Revision as of 18:54, 23 March 2022
Line 40:		Line 40:

	* [[Alto]]		* [[Alto]]
			* [[4.2BSD]]
			* [[MINITS]]
	* [[TENEX]]		* [[TENEX]]
	* [[TOPS-20]]		* [[TOPS-20]]
	* [[WAITS]]		* [[WAITS]]
	* [[MINITS]]

	==Further reading==		==Further reading==

Larsbrinkhoff: Some implementations.

2022-03-23T18:49:14Z

Some implementations.

← Older revision		Revision as of 18:49, 23 March 2022
Line 36:		Line 36:

	The Gateway Information Protocol's descendant, RIP, (somewhat modified to match the syntax of addresses of other protocol suites), remains in wide use today in other protocol suites. One version of RIP served as one of the initial so-called [[interior gateway protocol]]s for the growing [[Internet]], before the arrival of the more modern [[OSPF]] and [[IS-IS]]. It is still in use as an interior routing protocol, in small sites with simple requirements.		The Gateway Information Protocol's descendant, RIP, (somewhat modified to match the syntax of addresses of other protocol suites), remains in wide use today in other protocol suites. One version of RIP served as one of the initial so-called [[interior gateway protocol]]s for the growing [[Internet]], before the arrival of the more modern [[OSPF]] and [[IS-IS]]. It is still in use as an interior routing protocol, in small sites with simple requirements.

			==Implementations==

			* [[Alto]]
			* [[TENEX]]
			* [[TOPS-20]]
			* [[WAITS]]
			* [[MINITS]]

	==Further reading==		==Further reading==

Jnc: Proper target

2018-11-17T17:15:37Z

Proper target

← Older revision		Revision as of 17:15, 17 November 2018
Line 11:		Line 11:
	The main internet layer protocol was PUP, which roughly corresponds to the [[Internet Protocol]] (IP) layer in TCP/IP. A full PUP [[network address]] consisted of an 8-bit network number, an 8-bit host number, and a 16-bit socket number. The network number had a particular special value which meant 'this network', for use by hosts which did not (yet) know their network number.		The main internet layer protocol was PUP, which roughly corresponds to the [[Internet Protocol]] (IP) layer in TCP/IP. A full PUP [[network address]] consisted of an 8-bit network number, an 8-bit host number, and a 16-bit socket number. The network number had a particular special value which meant 'this network', for use by hosts which did not (yet) know their network number.

	Unlike TCP/IP, socket fields were part of the full network address in the PUP header, so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte checksum covered the entire [[packet]].		Unlike TCP/IP, socket fields were part of the full network address in the PUP [[header]], so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte checksum covered the entire [[packet]].

	PUP packets were up to 554 bytes long (including the 20 byte PUP ~~[[Header (information technology)\|~~header]]), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP [[router]] was required to handle them. Unlike in IP, larger packets could be fragmented.		PUP packets were up to 554 bytes long (including the 20 byte PUP header), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP [[router]] was required to handle them. Unlike in IP, larger packets could be fragmented.

	A protocol named the ''Gateway Information Protocol'' (a remote ancestor of [[Routing Information Protocol\|RIP]]) was used as both the [[routing protocol]] (the router information-exchange system), and for hosts to discover routers.		A protocol named the ''Gateway Information Protocol'' (a remote ancestor of [[Routing Information Protocol\|RIP]]) was used as both the [[routing protocol]] (the router information-exchange system), and for hosts to discover routers.

Jnc: Avoid redirs

2018-11-15T19:57:53Z

Avoid redirs

← Older revision		Revision as of 19:57, 15 November 2018
Line 1:		Line 1:
	The '''PARC Universal Packet''' (commonly abbreviated to '''PUP''', although the original documents usually use '''Pup''') was one of the two earliest [[internetwork\|internetworking]] [[protocol suite]]s; it was created by researchers at [[Xerox PARC]] in the mid-1970s.		The '''PARC Universal Packet''' (commonly abbreviated to '''PUP''', although the original documents usually use '''Pup''') was one of the two earliest [[internetwork\|internetworking]] [[protocol suite]]s; it was created by researchers at [[Xerox PARC]] in the mid-1970s.

	(Technically, the name "PUP" only refers to the [[internetworking layer]] [[protocol]], but it is also applied to the whole protocol suite.) The entire suite provided [[~~routing~~]] and packet delivery, as well as higher level functions such as a [[reliable byte stream]], along with numerous applications.		(Technically, the name "PUP" only refers to the [[internetworking layer]] [[protocol]], but it is also applied to the whole protocol suite.) The entire suite provided [[path selection]] and [[packet]] delivery, as well as higher level functions such as a [[reliable byte stream]], along with numerous applications.

	The origins of the PUP suite lie in two developments; in the same events in the early 1970s as the very earliest stage of the development of [[TCP/IP]], and the creation of the [[Ethernet]] [[local area network]] at PARC. However, the development of PUP split off because Xerox PARC wished to move ahead with implementation, for in-house use. The fundamental design of the PUP suite was substantially complete by 1974.		The origins of the PUP suite lie in two developments; in the same events in the early 1970s as the very earliest stage of the development of [[TCP/IP]], and the creation of the [[Ethernet]] [[local area network]] at PARC. However, the development of PUP split off because Xerox PARC wished to move ahead with implementation, for in-house use. The fundamental design of the PUP suite was substantially complete by 1974.
Line 13:		Line 13:
	Unlike TCP/IP, socket fields were part of the full network address in the PUP header, so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte checksum covered the entire [[packet]].		Unlike TCP/IP, socket fields were part of the full network address in the PUP header, so that upper-layer protocols did not need to implement their own demultiplexing; PUP also supplied packet types (again, unlike IP). Also, an optional 2-byte checksum covered the entire [[packet]].

	PUP packets were up to 554 bytes long (including the 20 byte PUP [[Header (information technology)\|header]]), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP router was required to handle them. Unlike in IP, larger packets could be fragmented.		PUP packets were up to 554 bytes long (including the 20 byte PUP [[Header (information technology)\|header]]), and the checksum. This was a smaller packet size than IP, which requires all hosts to support at least 576 (but supports packets of up to 65K bytes, if the hosts support them); individual PUP host pairs on a particular network might use larger packets, but no PUP [[router]] was required to handle them. Unlike in IP, larger packets could be fragmented.

	A protocol named the ''Gateway Information Protocol'' (a remote ancestor of [[Routing ~~information protocol~~\|RIP]]) was used as both the [[routing protocol]] (the router information-exchange system), and for hosts to discover routers.		A protocol named the ''Gateway Information Protocol'' (a remote ancestor of [[Routing Information Protocol\|RIP]]) was used as both the [[routing protocol]] (the router information-exchange system), and for hosts to discover routers.

	PUP also included a simple echo protocol at the internetwork layer, similar to IP's [[ping]], but operating at a lower level.		PUP also included a simple echo protocol at the internetwork layer, similar to IP's [[ping]], but operating at a lower level.