Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Fast Local Internet Protocol
open-in-new
<h2 id="comparison-to-tcpip">Comparison to TCP/IP</h2> <p>In the <a href="/facts/OSI_model/oxN9Xhjz">OSI model</a>, FLIP occupies the <a href="/facts/Network_layer/L2jAtJzQ">network layer (3)</a>, thus replacing <a href="/facts/Internet_Protocol/Qq6VeEal">IP</a>, but it also obviates the need for a <a href="/facts/Transport_layer/UmIGUCeK">transport layer (4)</a> protocol like <a href="/facts/Transmission_Control_Protocol/WW4sPrt9">TCP</a>. </p> Layers of functionality in OSI, TCP/IP, and FLIP.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a><table><tbody><tr><th>Layer</th><th>OSI</th><th>TCP/IP</th><th>FLIP</th></tr><tr><td>7</td><td>Application</td><td>User-defined</td><td>User-defined</td></tr><tr><td>6</td><td>Presentation</td><td>User-defined</td><td>Amoeba Interface Language (AIL)</td></tr><tr><td>5</td><td>Session</td><td>Not used</td><td>RPC and Group communication</td></tr><tr><td>4</td><td>Transport</td><td>TCP or UDP</td><td>Not needed</td></tr><tr><td>3</td><td>Network</td><td>IP</td><td>FLIP</td></tr><tr><td>2</td><td>Data Link</td><td>E.g., Ethernet</td><td>E.g., Ethernet</td></tr><tr><td>1</td><td>Physical</td><td>E.g., Coaxial cable</td><td>E.g., Coaxial cable</td></tr></tbody></table> <h2 id="properties">Properties</h2> <p>FLIP is a <a href="/facts/Connectionless_communication/MfMys8t7">connectionless</a> 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:<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> </p> <ol><li>FLIP identifies entities with a location-independent 64-bit identifier called <i>Network Service Access Points</i> (NSAPs). An entity can, for example, be a <a href="/facts/Process_(computing)/Vcq7EnUV">process</a>; contrary to the IP protocol where an <a href="/facts/IP_address/z9V22Sw9">IP address</a> identifies a <a href="/facts/Host_(network)/HPNcFXHk">host</a>.</li> <li>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.</li> <li>FLIP routes messages based on NSAP (transparency).</li> <li>FLIP discovers routes on demand.</li> <li>FLIP uses a bit in the message header to request transmission of sensitive messages across trusted networks.</li></ol> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/IL_(network_protocol)/2Tqatafj">IL (network protocol)</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>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 <a href="/wiki/M._Frans_Kaashoek" target="_blank">/wiki/M._Frans_Kaashoek</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>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 <a href="/wiki/M._Frans_Kaashoek" target="_blank">/wiki/M._Frans_Kaashoek</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>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 <a href="/wiki/M._Frans_Kaashoek" target="_blank">/wiki/M._Frans_Kaashoek</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> </ol>