User:ConorMcD1/Recursive Inter-Network Architecture (RINA)
The Recursive InterNetwork Architecture (RINA) is a computer network architecture that unifies distributed computing and telecommunications. RINA's fundamental principle is that computer networking is just Inter-Process Communication or IPC. RINA reconstructs the overall structure of the Internet, forming a model that comprises a single repeating layer, the DIF (Distributed IPC Facility), which is the minimal set of components required to allow distributed IPC between application processes. RINA supports inherently and without the need of extra mechanisms mobility, multi-homing and Quality of Service, provides a secure and programmable environment, motivates for a more competitive marketplace and allows for a seamless adoption.
History and Motivation
The principles behind RINA, were first presented by John_Day_(computer_scientist) in his book “Patterns in Network Architecture: A return to Fundamentals” [1]. This work is a start afresh, taking into account lessons learned in the 35 years of TCP/IP’s existence, as well as the lessons of OSI’s failure and the lessons of other network technologies of the past few decades, such as CYCLADES, DECnet or Xerox Network Systems.
From the early days of telephony to the present, the telecommunications and computing industries have evolved significantly. However, they have been following separate paths, without achieving full integration that can optimally support distributed computing; the paradigm shift from telephony to distributed applications is still not complete. Telecoms have been focusing on connecting devices, perpetuating the telephony model where devices and applications are the same. A look at the current Internet protocol suite shows many symptoms of this thinking [2]:
- The network routes data between interfaces of computers, as the public switched telephone network switched calls between phone terminals. However, it is not the source and destination interfaces that wish to communicate, but the distributed applications.
- Applications have no way of expressing their desired service characteristics to the network, other than choosing a reliable (TCP) or unreliable (UDP) type of transport. The network assumes that applications are homogeneous by providing only a single quality of service.
- The network has no notion of application names, and has to use a combination of the interface address and transport layer port number to identify different applications. In other words, the network uses information on “where” an application is located to identify “which” application this is. Every time the application changes its point of attachment, it seems different to the network, greatly complicating multi-homing, mobility, and security
A theory for a new internet architecture by John_Day_(computer_scientist).
Networking is IPC and only IPC
It is IPC if and only if Maximum Packet Lifetime can be bounded.
If MPL can’t be bounded, it is remote storage.
Two protocols: DTP/DTCP for unreliable/reliable data transfer; one for management.
Terminology
IAP: IPC Access Protocol - protocol to carry application names and access control information.
EFPC: Protocol for Error and Flow Control - maintain shared state (synchronization) about the communication between two processes. Detect errors and provide flow control. Port-ids for identifying.
Mux: Multiplexing of messages, scheduling for QoS. One Mux per physical interface.
Dir: Used by IAP to determine which interface to use to find app.
Res Alloc:
AE: Application Entity - that part of the application concerned with communication, i.e. shared state with its peer. An app can have multiple AEs
RIB: Resource Information Base
RMT: Relaying and Multiplexing Task
CAP: ?Common Application Process - ACSE, Authentication, CMIP
SDU:
DIF: Distributed IPC Facility
DAF: Distributed Application Facility
References
References
Patterns in Network Architecture: A Return to Fundamentals, John Day (2008), Prentice Hall, ISBN-13: 978-0132252423
Distributed IPC Facility Development
Recursive InterNetwork Architecture prototype
Eleni Trouva, Eduard Grasa, John Day, Ibrahim Matta, Lubomir T. Chitkushev, Steve Bunch, Miguel Ponce de Leon, Patrick Phelan, Xavier Hesselbach-Serra (2011). Transport over Heterogeneous Networks Using the RINA Architecture WWIC, Vol. 6649, Springer, p. 297-308
J. Touch, I. Baldine, R. Dutta., G. Finn, B. Ford, S. Jordan, D. Massey, A. Matta., C. Papadopoulos, P. Reiher, G. Rouskas (2011). A Dynamic Recursive Unified Internet Design (DRUID). Computer Networks, Volume 55, Issue 4, Pages 919-935
Richard Bennett (2011) Remaking the Internet: Taking Network Architecture to the Next Level Information Technology and Innovation Foundation
Richard Bennett (2009) Designed for Change: End-to-End Arguments,Internet Innovation, and the Net Neutrality Debate Information Technology and Innovation Foundation
DeforaOS wiki: Clean Slate Internet design
R. Watson (1981). Timer-Based Mechanisms in Reliable Transport Protocol Connection Management Computer Networks, 5:47–56.