RINAS IM : Y OUR R ECURSIVE I NTER N ETWORK Intro RINASim A - - PowerPoint PPT Presentation

rinas im
SMART_READER_LITE
LIVE PREVIEW

RINAS IM : Y OUR R ECURSIVE I NTER N ETWORK Intro RINASim A - - PowerPoint PPT Presentation

S KIP T HIS P APER RINAS IM : Y OUR R ECURSIVE I NTER N ETWORK Intro RINASim A RCHITECTURE S IMULATOR Outro Vladimr VESEL , Marcel MAREK, Tom HYKEL, Ondej RYAV 2 ND OMN E T++ S UMMIT 3 RD -4 TH S EPTEMBER 2015, Z RICH , S


slide-1
SLIDE 1

Intro RINASim Outro

1

SKIP THIS PAPER RINASIM: YOUR RECURSIVE INTERNETWORK ARCHITECTURE SIMULATOR

Vladimír VESELÝ,

Marcel MAREK, Tomáš HYKEL, Ondřej RYŠAVÝ

2ND OMNET++ SUMMIT 3RD-4TH SEPTEMBER 2015, ZÜRICH, SWITZERLAND

slide-2
SLIDE 2

Intro RINASim Outro

2

THEORY

 Your teachers told you about this…

 1978 – 1994

Intro

Application Presentation Session Transport Network Data-link Physical

ISO-OSI RM

slide-3
SLIDE 3

Intro RINASim Outro

3

THEORY

 …or this…

 1983

Intro

Application Transport Internet Link

TCP/IP RM

slide-4
SLIDE 4

Intro RINASim Outro

4

THEORY

 …or that!

Intro

Application Transport Internet Link Physical

TCP/IP RM

medium abstraction adjacent communication logical communication data transfer services network part of each application

slide-5
SLIDE 5

Intro RINASim Outro

5

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Transport Internet Link Physical

TCP/IP RM

DWDM

slide-6
SLIDE 6

Intro RINASim Outro

6

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Transport Internet Link

TCP/IP RM

802.1q

slide-7
SLIDE 7

Intro RINASim Outro

7

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Transport Internet Link Physical

TCP/IP RM

DWDM 802.1q Q-in-Q

slide-8
SLIDE 8

Intro RINASim Outro

8

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Transport Link Physical

TCP/IP RM

DWDM 802.1q Q-in-Q IPsec

slide-9
SLIDE 9

Intro RINASim Outro

9

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Link Physical

TCP/IP RM

DWDM 802.1q Q-in-Q IPsec TLS/SSL

slide-10
SLIDE 10

Intro RINASim Outro

10 10

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Physical

TCP/IP RM

DWDM 802.1q Q-in-Q IPsec MPLS TLS/SSL

slide-11
SLIDE 11

Intro RINASim Outro

11 11

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Physical

TCP/IP RM

DWDM 802.1q Q-in-Q TLS/SSL MPLS GRE or VPNs IPsec

slide-12
SLIDE 12

Intro RINASim Outro

12 12

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Physical

TCP/IP RM

DWDM 802.1q Q-in-Q TLS/SSL MPLS GRE or VPNs IPsec LISP or ILNS

slide-13
SLIDE 13

Intro RINASim Outro

13 13

THEORY

 Have you noticed clash of theory and practice?

Intro

Application Physical

TCP/IP RM

DWDM 802.1q Q-in-Q TLS/SSL MPLS GRE or VPNs IPsec LISP or ILNS Tunnel across HTTP(s)

slide-14
SLIDE 14

Intro RINASim Outro

14 14

PROBLEMS

 Open problems of nowadays Internet

 Multi-homing  Identity  Mobility  Default-free Zone growth

WiFi 10.0.1.11 HSPDA 20.0.2.22 What is unique address???

IPv4 IPv6

Intro

slide-15
SLIDE 15

Intro RINASim Outro

15 15

RECURSIVE INTERNETWORK ARCHITECTURE

 One generic layer (called DIF, Distributed IPC Facilty) that limits scope 1) Data transfer with soft-state timer-based synchronization 2) Complete addressing and naming scheme 3) Split between mechanism (fixed) and policy (flexible) 4) Single generic application protocol

Application Transport Internet Link Physical Layer Layer0 Layer1 Layer2 Intro

slide-16
SLIDE 16

Intro RINASim Outro

16 16

HISTORY

 In 2007 book Patterns in Network Architecture: A Return to Fundamentals by John Day

Intro

slide-17
SLIDE 17

Intro RINASim Outro

17 17

1) SOFT-STATE TRANSPORT PROTOCOL

 Hard-state = explicit synchronization prior to communication using special messages (i.e., TCP flags and 3-way handshake)  Data Transfer Protocol (DTP) based on Richard Wattson’s transport protocol Delta-t from 1984

 Proves that hard-state is unnecessary IFF

Maximum Packet Lifetime denotes upper bound time (value 𝑁𝑄𝑀) that a packet can

exists in a network

Retransmission-timer specifies maximum period (value 𝑆) that a sender is willing to

retransmit its unacknowledged messages;

Acknowledgment-timer defines maximum delay (value 𝐵) that the receiver of data can

wait before sending acknowledgment.

∆𝑢 = 𝑁𝑄𝑀 + 𝑆 + 𝐵

 All connections exist all the time

Decoupling of port allocation from synchronization After period of 2-3 ∆𝑢 of no traffic, all synchronization state should be discarded, which effectively resets the connection

 Both reliable and unreliable transfer based on employment of sequence numbers

Intro

slide-18
SLIDE 18

Intro RINASim Outro

18 18

2) COMPLETE ADDRESSING

 Logical vs. Physical addresses  Variable addresses  Reflects scope (size) and usage (flat vs. hierarchical)

Application Namespace Node Namespace PoA Namespace MAC address IP address Port number Route Path

Application Namespace Node Namespace PoA Namespace Route Path Directory

src CEP-id dst CEP-id

Ports with port-ids EFCPIs with CEP-ids Connection-id Structured IPCP address

src CEP-id dst CEP-id QoS-id

Port allocation State synchronization

Connection Flow N-PDU has

Intro

slide-19
SLIDE 19

Intro RINASim Outro

19 19

3) MECHANISM VS. POLICY

 i.e., error-checking (fixed) employing CRC (flexible)  Programmable behavior using well-defined APIs

State Vector Tightly-bound DTP Loosely-bound DTCP

EFCP instance

data traffic control traffic State Vector Relaying & Multiplexing Task RIB Daemon Flow Allocator Resource Allocator Common Distributed Application Protocol Delimiting Data Transfer SDU Protection RIB Flow Control Error Control

a) Data Transfer c) Management

Time and functional complexity increases

b) Data Transfer Control

Enrollment

Intro

slide-20
SLIDE 20

Intro RINASim Outro

20 20

4) CDAP

 Common Distributed Application Protocol (CDAP)

 All application protocols are stateless, the state is in the application  DTP modify state internal to the protocol and CDAP modify state external to the protocol

CDAP encapsulated into DTP

 Request-response scheme with feedback

 Primitive operations governing objects (i.e., files)

 Read / Write  Create / Delete  Start / Stop

 Subcomponents

 CACE – connection establishment  Auth – authentication  CDAppP – protocol operation 6 messages × 2 directions = 12 message types

Intro

slide-21
SLIDE 21

Intro RINASim Outro

21 21

NODE TYPES

Border Router Interior Router Border Router Host (N)-DIF (N+1)-DIF (N-1)-DIF Host Physical medium Relaying RMT Multiplexing RMTs Physical medium

RINASim

slide-22
SLIDE 22

Intro RINASim Outro

22 22

DIF COMPONENTS

slide-23
SLIDE 23

Intro RINASim Outro

23 23

RINASim

LIVE DEMONSTRATION

HostA HostB Switch

Interior Router (N-1)-DIF (N)-DIF Host Host 1 3 2 DAF 4 5

slide-24
SLIDE 24

Intro RINASim Outro

24 24

CONCLUSION

 RINASim is full-fledged RINA simulating framework

 Independent on other libraries (such as INET)  105 899 SLOC and getting bigger

including *.h, *.cc, *.msg, *.ned, *.ini, *.xml excluding comments and empty lines

 Complete recursive stack implementation

 Generic CDAP socket-like APIs  Data transfer protocol  Routing protocol policies  Flow lifecycle

RINASim

Outro

slide-25
SLIDE 25

Intro RINASim Outro

25 25

THE END

 Thank you! Feel free to ask any question…  https://github.com/kvetak/RINA

 Expecting first research papers to be accepted  Work more on Enrollment, EFCP  Develop a new routing protocols with load-balancing features  4th International RINA Workshop in April 2016 hosted in Brno

 https://github.com/kvetak/ANSA

 Submit a new INET3.0 contributions

EIGRP LISP VRRP TRILL and IS-IS

Outro