2016 06-10-ieee-sdn (1)

Dr. Sven van der MeerNM Lab, [email protected]

what about the Network?How to manage multi-layer Networks

Autonomic Networks - Challenges in closing the loop | Commercial in confidence | IEEE SDN Pre-Industrial Workshop | 2016-06-16 |

Adaptive AutomationPattern & Adaptive Policy

Model-based Everything

› Models

› Supporting A, P, COM

› For semantic

interoperability

› Catalogs

› For detailed information

and history

› Solutions sets

› For easy DEVOPS

› Other Information

› Context, context, and

context


Adaptive AutomationPattern & Adaptive Policy

Separation of concern

› A: Lift Analyze Process

› Lift data into loop

› Recognize and match

› Generate insights

› P: Decide, Recommend

› Automate decisions

› Requires adaptivity

› COM: Validate, Apply

› Semantic, (non-)

functional validation

› Translate to target

› Commit

One More Problem –The network Architecture

TCP as well as ePC


The Problem with IP

• Functional layers organized for modularity, each layer

provides a different service to each other

– As the RM is applied to the real world, it proofs to beincomplete. As a consequence, new layers are patched into

the reference model as needed (layers 2.5, VLANs, VPNs,

virtual network overlays, tunnels, MAC-in-MAC, etc.)

(Theory) (Practice)


Commonality is Key

• Commonality and consistency in RINA greatly simplifiesmanagement models, opening the door to increased

automation in multi-layer networks– Reduce opex, network downtime, speed-up network service delivery,

reduce components that need to be standardised

From managing a set of layers, each

with its own protocols, concepts and

definitions …

… to managing a common, repeating

structure of two protocols and different

policies


RINA Macro StructureSingle Layer Type, Repeated, Programmable Policies

Host

Border

router

Interior

Router

DIF

DIF DIF

Border

router

DIFDIF

DIF (Distributed IPC Facility)

Host

App

A

App

B

Consiste

nt API

through

layers

IPC API

Data Transfer Data Transfer

Control

Layer Management

SDU

Delimiting

Data Transfer

Relaying and

Multiplexing

SDU

Protection

Retransmissio

n Control

Flow Control

RIB

Daemo

n

RIB

CDAP

Parser/Genera

tor

CACEP

Enrollment

Flow

Allocation

Resource

Allocation

Routing

Authenticati

on

Sta

te

Ve

cto

rS

tate

Ve

cto

rS

tate

Ve

cto

r

Data Transfer Data Transfer

Retransmissio

n ControlRetransmissio

n Control

Flow ControlFlow Control

Increasing timescale (functions performed less often) and complexity

Namespace

Management

Security

Management


Example: DCN

• Large-scale DCN connects around 100k servers, how to realize and manage the DCN with RINA and IP?


Example: DCN w/TCP

• Data plane (up), control plane (down). L3-only fabric

9

ToR ToRFabric Spine Fabric

Server ServerIPv4 or IPv6 (Fabric layer)

UDPVM VM

Ethernet Ethernet Ethernet Ethernet

VXLAN802.1Q802.3 802.1Q

IPv4 or IPv6 (tenant overlay)

TCP or UDP or SCTP, … (transport layer)

802.3

Protocol conversion, Local bridging

ToR ToRFabric Spine FabricServerServer

IPv4 or IPv6 (Fabric layer)

TCP

Ethernet Ethernet Ethernet Ethernet

LACP

Ethernet

LACP

Ethernet

TCP

eBGP eBGP

TCP TCP

eBGP eBGP

TCP

eBGP

TCP

eBGP


Example: DCN w/RINA

• Overall design (up), Fabric addressing plan (down)

Simplifying multi-layer network management with RINA 10

PtP DIF PtP DIF PtP DIF PtP DIF

PtP DIF PtP DIFPtP DIFPtP DIFDC Fabric DIF

Tenant DIF

ToR ToR

VM Server Server VM

FabricFabric Spine


DCN Models: IP vs. RINAConcept IP RINA

InterfacesIPv4 interfaces, need IP address (one per

interface), unique in the layer. Port-ids to N-1 flows, just need port-id

(locally –device- unique identifier)

Data Transfer protocol syntax

IPv4 syntax, TCP syntax (TCP is used by the control plane)

EFCP (length of fields). Need address (one per device in the layer), unique in

the layer

Forwarding entity Router, one per device in the layer, has FIB entries (forwarding table)

Relaying and Multiplexing Task (RMT), one per device in the layer, has

forwarding table entries.

Forwarding strategy Longest prefix matching, ECMP Longest prefix matching, ECMP

Scheduling strategy FIFO (needs max-queue size) FIFO (needs max-queue size)

Routing protocol BGP with different routing policies. Needs AS numbers, router-id (IP address),

neighbours’ IP addresses and AS numbers.

CDAP with link-state routing policy and topological addressing

Directory protocol - CDAP with centralized directory policy.

Mgmt protocol NETCONF CDAP

Mgmt models yang-common-types, yang-interfaces, yang-ip, yang-routing , yang-bgp

daf-common-mom, dif-common-mom, dif-default-policies


DCN Models: IP vs. RINAConcept IP RINA

Routing protocol BGP with multi-protocol extensions. Needs route distinguisher and VPN targets. .

CDAP with link-state routing policy and topological addressing

Directory protocol DNS (resolve domain names of apps executing in the tenant DIF to IP @s)

CDAP with distributed directory policy. Maintains Directory Forwarding Table

Redundancy protocol Link Aggregation Control Protocol – needs local Ethernet interface addresses

-

Mgmt protocol NETCONF CDAP

Mgmt models yang-common-types, yang-interfaces, yang-ip, yang-bridging, yang-routing, yang-bgp,

yang-vxlan, yang-evpn, yang-lacp

daf-common-mom, dif-common-mom, dif-default-policies

Concept # (IP) # (RINA)

Interface types 4 1

DT protocol syntaxes 5 1 (2 different field lengths)

Types of forwarding entities 3 1

Layer mgmt/control plane protocols 3 1 (with 4 policies)


Example: SP & RINA (Email)

Access

router

PtP DIF

Cel l Tower (eNodeB)

Mobi le Edge Service Router

MAN P.E MAN P. E.

MAN Access DIF

MAN Core DIF

PtP DIF

PtP DIF

PtP DIF PtP DIF

MAN P

Cell DIF

Mobi le Host

(or border router)

Core Backbone DIF

PtP DIF

Core router Core router e-mall AccessRouter

E-mall Border Router

Service Prov. 1 network

Access Aggregation Service Edge Core Internet Edge

PtP DIF PtP DIF PtP DIF

Service Provider Top Level DIF

E-mall 1 DIF

PtP DIF

E-mall 2 DIF

Mobile Access DIF

Internet ( e-mall) eXchange Point

Core PoP, ci ty BCore PoP, ci ty A

City A MANCity A Cabinets

Cel l sites


RINAResearch, Open Source, Standards

• Current research projects

– FP7 PRISTINE (2014-2016) http://ict-pristine-eu

– H2020 ARCFIRE (2016-2017) http://ict-arcfire.eu

– Norwegian project OCARINA(2016-2021)

– BU RINA team http://csr.bu.edu/rina

• Open source implementations

– IRATI (Linux OS, C/C++, kernel components, policy framework, RINAover X) http://github.com/irati/stack

– RINASim (RINA simulator, OMNeT++)

– ProtoRINA (Java, RINA over UDP, quick prototyping)

• Key RINA standardization activities

– Pouzin Society (experimental specs) http://pouzinsociety.org

– ISO SC6 WG7 (2 new projects: Future Network – Architectures, FutureNetwork- Protocols)

– ETSI Next Generation Protocols ISG

1

2

3

4

1

2

3

1

2

3

http://ict-pristine-eu

http://ict-arcfire.eu

http://csr.bu.edu/rina

http://github.com/irati/stack

http://pouzinsociety.org