Technical data

protocol stack
The set of functions, one at each layer of the protocol stack, that work together to
form a set of network services; each layer of the protocol stack uses the services of
themodulebeneathit.
proxy
The mechanism whereby one system acts on behalf of another system in responding
to protocol requests. uses a proxy mechanism to provide an OpenVMS identity
(account) for each UNIX client by adding the name and identification codes of
the client to a proxy database.
proxy ARP
The technique in which one machine, usually a router, answers Address Resolution
Protocol (ARP) requests intended for another machine. By "faking" its identity, the
router accepts responsibility for routing packets to the "real" destination. Proxy
ARPallowsasitetouseasingleIPaddresswithtwophysicalnetworks.Normally,
creating a subnet is a better solution.
proxy database
The database that provides OpenVMS identities for remote NFS clients and
UNIX-style identities for local NFS client users; provides proxy accounts for
remote processes.
pseudodevice
A software device used to implement special-purpose transports and not directly
associated with hardware.
pseudointerface
A method of extending subnet routing using a network interface. Each network
interface has one name and at most nine pseudointerface names. Each network
interface and pseudointerface has its own IP address, network mask, and broadcast
mask.
public domain
Intellectual property available to users that does not require payment of a fee.
quality of service (QoS)
The OSI equivalent of TOS.
RARP
See Reverse Address Resolution Protocol.
RCD
See RMT/RCD.
RCP
See remote copy program.
reachable node
The node to which the local node has a usable communications path.
read access
The access right that grants the ability to view data.
reassembly
The process of piecing together datagram fragments to reproduce the original
datagram based on the fragmentation data in the IP header of the datagram.
Glossary–36