Layer Discovery in RINA Networksrina.tssg.org/docs/CAMAD-slides.pdfLayer Discovery in RINA Networks...
Transcript of Layer Discovery in RINA Networksrina.tssg.org/docs/CAMAD-slides.pdfLayer Discovery in RINA Networks...
Layer Discovery in RINA Networks E. Trouva, E. Grasa, J. Day. S. Bunch
International Workshop on Computer-Aided Modeling Analysis and Design of Communication Links and Networks (CAMAD)
September 19th, 2012
Eleni Trouva PhD Researcher @ DANA
i2CAT Foundation
Outline
Application discovery in networks
Quick introduction to RINA
The Inter-DIF Directory (IDD)
An example of the IDD
Implications
What’s a layer? Although the term “layer” has been extensively used in
networking, the concept itself has not been clearly defined
In its origin layers were adopted from its use in operating systems, but in operating systems, using layers is a choice, whereas using layers in networks is a necessity because of the distributed shared state of different scopes
We can describe a layer as the collection of application processes that maintain shared state over a scope
Physical
Data Link
Network
Transport
Application
Host or End System
Router
Less Scope
More Scope
3
Application discovery in networks
host H2 router R2 router R3
host H1
Layer 1
web server application
B
web browser
application A
router R4
router R1
host H4
Layer 3 Layer 2 Layer 4
Layer 6
Layer 5
router R5
host H3
web server application
C
4
Instead...
host H2 router R2 router R3
host H1
IP
web server application
B
web browser
application A
router R4
router R1
host H4
IP
IP
router R5
host H3
public Internet private network
web server application
C
ctx.i2cat.net 84.88.32.6
DNS
myweb.com 192.168.1.1
hosts file
5
Directory Service A database that maintains mappings between two
name spaces
Mappings of application names to list of supporting layers
A framework that involves individual sub-topics: Information stored Structure Search mechanism Replication / caching strategy Strategy for the creation / choice of the supporting
layer 6
Outline
Application discovery in networks
Quick introduction to RINA
The Inter-DIF Directory (IDD)
An example of the IDD
Implications
Recursive InterNetwork Architecture (RINA)
A network architecture proposed by John Day, professor of BU, in his book “Patterns in Network Architecture: A return to fundamentals”
Fundamental principle: Networking is IPC (Inter Process Communication) and only IPC
A structure of recursive layers that provide IPC services to the applications on top
There’s a single type of layer that repeats as many times as required by the network designer
8
All layers have the same functions, with different scope and range (separation of mechanism from policy)
A layer is a distributed application that performs and manages IPC, a Distributed IPC Facility (DIF)
9
Recursive InterNetwork Architecture (RINA)
Outline
Application discovery in networks
Quick introduction to RINA
The Inter-DIF Directory (IDD)
An example of the IDD
Implications
The InterDIF Directory (IDD)
A distributed application, Distributed Application Facility (DAF) as it’s called in RINA, which is a collection of two or more cooperating application processes in one or more processing systems, which exchange information using IPC and maintain shared state
Responsible for two main distinct functions: a) Discovery of the application b) Creation of the supporting DIF
11
A) Discovery of the application IDD-Request
Destination IDD Name, Source IDD Name, Requested Application Process Name, Access Control Information, Quality of Service, Termination Condition
Forwarding of the request between the peer IDDs until the destination application is found or the pre-defined termination condition is met
host H2 router R2 router R3
host H1
web server application
B
web browser
application A
router R4
router R1
host H4
Layer 6
router R5
host H3
...
Layer 1
Layer 3 Layer 2 Layer 4 Layer 5
IDD DAF
web server application
C
12
A) Discovery of the application
Confirmation that the requested application is executing in the destination system and authorization check that the requesting application has the rights to access it
host H2 router R2 router R3
host H1
web server application
B
web browser
application A
router R4
router R1
host H4
Layer 6
router R5
host H3
...
Layer 1
Layer 3 Layer 2 Layer 4 Layer 5
IDD DAF
web server application
C
13
B) Creation of the supporting DIF
A DIF supporting the communication between the two user applications has to be found
This either involves creating a new DIF from scratch or expanding (joining) an existing one so that it spans from the source to the destination system
host H2 router R2 router R3
host H1
web server application
B
web browser
application A
router R4
router R1
host H4
Layer 6
router R5
host H3
...
Layer 1
Layer 3 Layer 2 Layer 4 Layer 5
IDD DAF
web server application
C
14
IDD Information
Naming / synonyms Neighbor Table Search Table Directory
Search Table Application Process Name
List of Peer IDDs Application Process Names Naming Information
IDD Application Process Name
synomyms (optional) Neighbor Table Peer IDD Application Process Name
List of Peers IDDs Application Process Names
Directory Application Process { Name, Access Control Information }
List of supporting DIFs { Name, Access Control Information, supported QoS }
15
Outline
Application discovery in networks
Quick introduction to RINA
The Inter-DIF Directory (IDD)
An example of the IDD
Implications
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
An example
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
- IDD2 - IDD2 ...
* - IDD2 -
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD2 IDD4 - IDD3 ...
* - IDD4 -
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD4 IDD4 - IDD4 ...
- -
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD4 IDD8 - IDD5 IDD6 - IDD6 IDD9 - IDD7
...
.com - IDD8 .edu - IDD6 .org - IDD9
-
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD8 IDD8 - IDD8 ...
- -
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD8 IDD10 - IDD10 IDD13 - IDD11 IDD14 - IDD12
...
.cnn - IDD10 .google - IDD13
.microsoft - IDD14
-
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD13 IDD13 - IDD13 ...
- -
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD13 IDD17 - IDD15 ...
example - IDD17
-
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD17 IDD17 - IDD16 ...
- -
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD17 IDD17 - IDD17 ...
- -
web browser
IDD 1
IDD 4 IDD 6 IDD 17
IDD 8
IDD 9
IDD 10
IDD 11
IDD 12
IDD 15
IDD 16
source
.com
default IDD to ask
.edu
.org
destination
.cnn
.microsoft
IDD 23 IDD 22 IDD 21
IDD 5
IDD 14
IDD 7
IDD 13
IDD 2
root
IDD 3
example.google.com
IDD 20 IDD 19 IDD 18
IDD 24
Destination Neighbor Table
Search Table Directory
IDD17 ... example.google.com - IDD17
example.google.com - list of
supporting DIFs
web browser
Outline
Application discovery in networks
Quick introduction to RINA
The Inter-DIF Directory (IDD)
An example of the IDD
Implications
Implications A real application discovery mechanism is missing from
the Internet today, not just pointers to where to search next as it happens today with DNS
Applications do not have to be on the same layer to discover each other, especially not on the same one layer as it happens now with IP
Elimination of the need for layers with large address spaces
No need for a single application namespace, the largest namespace is defined by the maximum number of applications that need to be discoverable
Greater security by having multiple application namespaces and by better compartmentalization without impairing reachability
30
What? Main goal To advance the state of the art of RINA towards an architecture reference model and
specifications that are closer to enable implementations deployable in production scenarios. The design and implementation of a RINA prototype on top of Ethernet will enable the experimentation and evaluation of RINA in comparison to TCP/IP.
Who? 4 partners
How? Requested 870.000 € funding to the EC to perform 5 activities WP1: Project management WP2: Architecture, Use cases and Requirements WP3: Software Design and Implementation WP4: Deployment into OFELIA testbed, Experimentation and Validation WP5: Dissemination, Standardisation and Exploitation
Project at a glance
Nextworks Interoute
i2CAT
IBBT
Thank you
Contact me: [email protected]
More information about RINA at:
• pouzinsociety.org
• rina.tssg.org
• csr.bu.edu/rina
More information about IRATI at: • irati.eu