Content deleted Content added
Clarified the role of network service access points (NSAPs) used for transparency; added more links to articles |
→Properties: hyphen missing from compound modifier |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1:
{{More citations needed|date=February 2013}}
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 [[OSI model]], FLIP occupies [[Network layer|layer 3]], thus replacing [[Internet Protocol|IP]], but it also obviates the need for a transport-level protocol like [[Transmission Control Protocol|TCP]].▼
==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
{| class="wikitable"
|+ Layers of functionality in OSI, TCP/IP, and FLIP.<ref name="FLIP"/>
!
|-
| 7 || Application || User-defined || User-defined
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), group communication, secure communication and easy network management. The following FLIP properties helps to achieve the efficiency requirements:▼
==Properties==
▲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
*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 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]] identifies a [[Host (network) |host]].
*FLIP uses a bit in the message header to request transmission of sensitive messages across trusted networks.▼
▲
# FLIP discovers routes on demand.
▲
==See also==
|