Fast Local Internet Protocol: Difference between revisions

Content deleted Content added
MaD70 (talk | contribs)
Clarified RPC acronym and more refinements
Properties: hyphen missing from compound modifier
 
(4 intermediate revisions by 2 users not shown)
Line 2:
 
The '''Fast Local Internet Protocol''' ('''FLIP''') is a [[communication protocol]] for [[Local area network |LAN]] and [[wide area network |WAN]], conceived for [[distributed computing |distributed applications]]. FLIP was designed at the [[Vrije Universiteit Amsterdam]] to support [[remote procedure call |remote procedure call (RPC)]] in the [[Amoeba (operating system)|Amoeba]] [[distributed operating system]].<ref name="FLIP">[[M. Frans Kaashoek]], Robbert van Renesse, Hans van Staveren, and [[Andrew S. Tanenbaum]]. 1993. FLIP: an internetwork protocol for supporting distributed systems. ACM Trans. Comput. Syst. 11, 1 (Feb. 1993), 73–106. https://doi.org/10.1145/151250.151253</ref>
 
==Comparison to TCP/IP==
In the [[OSI model]], FLIP occupies the [[Network layer |network layer (3)]], thus replacing [[Internet Protocol|IP]], but it also obviates the need for a [[Transport layer |transport layer (4)]] protocol like [[Transmission Control Protocol|TCP]].
{| class="wikitable"
Line 21 ⟶ 23:
| 1 || Physical || E.g., Coaxial cable || E.g., Coaxial cable
|}
FLIP is a connectionless protocol designed to support transparency (with respect to the underlying network layers of the OSI model: 2. data link and 1. physical), efficient RPC, group communication, secure communication and easy network management. The following FLIP properties helps to achieve the requirements distributed computing:<ref name="FLIP"/>
 
==Properties==
# FLIP identifies entities with a ___location-independent 64-bit identifier called ''network service access points'' (NSAPs). An entity can, for example, be a [[Process (computing) |process]]; contrary to the IP protocol where an [[IP address]] identify a [[Host (network) |host]].
FLIP is a [[Connectionless communication |connectionless]] protocol designed to support transparency (with respect to the underlying network layers of the OSI model: 2. data link and 1. physical), efficient RPC, group communication, secure communication and easy network management. The following FLIP properties helps to achieve the requirements of distributed computing:<ref name="FLIP"/>
# FLIP uses a one way mapping between the “private” address, used to register an endpoint of a network connection, and the “public” address used to advertise the endpoint.
 
# FLIP identifies entities with a ___location-independent 64-bit identifier called ''networkNetwork serviceService accessAccess pointsPoints'' (NSAPs). An entity can, for example, be a [[Process (computing) |process]]; contrary to the IP protocol where an [[IP address]] identifyidentifies a [[Host (network) |host]].
# FLIP uses a one -way mapping between the “private” address, used to register an endpoint of a network connection, and the “public” address used to advertise the endpoint.
# FLIP routes messages based on NSAP (transparency).
# FLIP discovers routes on demand.