Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Recursive Internetwork Architecture
open-in-new
<p>The Recursive InterNetwork Architecture (RINA) is a new computer <a href="/facts/Network_architecture/b9IWEJIU">network architecture</a> proposed as an alternative to the architecture of the currently mainstream <a href="/facts/Internet_protocol_suite/KNkxtSpw">Internet protocol suite</a>. The principles behind RINA were first presented by <a href="/facts/John_Day_(computer_scientist)/77GdQLXB">John Day</a> in his 2008 book <i>Patterns in Network Architecture: A return to Fundamentals</i>. This work is a fresh start, taking into account lessons learned in the 35 years of <a href="/facts/TCP/IP/KNkxtSpw">TCP/IP</a>’s existence, as well as the lessons of <a href="/facts/OSI_model/oxN9Xhjz">OSI</a>’s failure and the lessons of other network technologies of the past few decades, such as <a href="/facts/CYCLADES/kJX66P6D">CYCLADES</a>, <a href="/facts/DECnet/9wnFzPvn">DECnet</a>, and <a href="/facts/Xerox_Network_Systems/2pfVfFgY">Xerox Network Systems</a>. RINA's fundamental principles are that <a href="/facts/Computer_network/3w5RM99p">computer networking</a> is just <a href="/facts/Inter-Process_Communication/cIQYyT6y">Inter-Process Communication</a> or IPC, and that layering should be done based on scope/scale, with a single recurring set of protocols, rather than based on function, with specialized protocols. The protocol instances in one layer interface with the protocol instances on higher and lower layers via new concepts and entities that effectively <a href="/facts/Reification_(computer_science)/bWHmLPs5">reify</a> networking functions currently specific to protocols like <a href="/facts/BGP/XfYgBzW3">BGP</a>, <a href="/facts/OSPF/PACpGUHb">OSPF</a> and <a href="/facts/Address_Resolution_Protocol/1QyKybkn">ARP</a>. In this way, RINA claims to support features like mobility, <a href="/facts/Multihoming/s3FK7EM7">multihoming</a> and <a href="/facts/Quality_of_service/joz9VkUm">quality of service</a> without the need for additional specialized protocols like <a href="/facts/Real-time_Transport_Protocol/YKQK1RK2">RTP</a> and <a href="/facts/User_Datagram_Protocol/dxLU0D6q">UDP</a>, as well as to allow simplified network administration without the need for concepts like <a href="/facts/Autonomous_system_(Internet)/zIVqxPX1">autonomous systems</a> and <a href="/facts/Network_address_translation/nFweFNfN">NAT</a>. </p>