PLNOG 13: Jeff Tantsura: Programmable and Application aware IP/MPLS networking

Slide title 44 pt

Text and bullet level 1 minimum 24 pt

Bullets level 2-5 minimum 20 pt

Characters for Embedded font: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz|~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș−≤≥fifl

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ

Do not add objects or text in the footer area

1

SDN with SR - evolution rather than revolution

Programmable & Application aware multilayer networking with Segment Routing Jeff Tantsura

Slide title 44 pt







2

You are here…

Slide title 44 pt







3

Is this the future?

SDN Falls

Slide title 44 pt







4

Decentralized

Centralized

Decentralized

Slide title 44 pt







5

Slide title 44 pt







6

You are here

Slide title 44 pt







7

Where do we

go from here?

Slide title 44 pt







8

SDN ambitions service provider expectations(2012)

Slide title 44 pt







9

SDN ambitions service provider expectations(2013/14)

Slide title 44 pt







10

Open flow and unicorns in networking

NFV possibilities

•  Switching •  Routing

•  Identity / AAA

•  Policy

•  Firewalls / Security Gateways

•  WAN Optimization •  Email / Email Security •  DNS •  IP Address Management •  Wireless Lan Controllers

•  Load Balancers •  Network Analysis •  WAF •  Route Reflectors

Slide title 44 pt







11

C≤1/R

Impossible!

There is no Silver Bullet for Complexity

Slide title 44 pt







12

We need to separate policy from reachability

!=

Slide title 44 pt







13

“If you can’t explain it simply, you don’t understand it well enough ” Albert Einstein

Logically centralized, physically distributed !

Slide title 44 pt







14

› Faster TTM, simplification – Programmability and Application awareness

› OPEX reduction – Removes complexity from the network, no LDP/RSVP, state is in the

packet, fully automatic 100% IP FRR coverage, native IPv6

› CAPEX optimization –  Investment protection - can be used with the existing equipment, only

SW upgrade needed (HW on ingress in some cases)

› Packet/Opto integration – Coherent multilayer resource provisioning and dynamic reoptimization – On demand bandwidth and admission control – Connection-oriented connectivity, carrier grade OAM

SR addresses operator’s needs & makes SDN promises true

Slide title 44 pt







15

Sr Is Real and happening! › Excellent endorsement and leadership from SP and Entreprise operators

›  IETF: Multi-vendor consensus and collaboration: – Stefano Previdi - Cisco –  Jeff Tantsura - Ericsson – Wim Hendericks - ALU – Hannes Gredler - Juniper

› We have submitted detailed IETF drafts: – Architecture – Use-cases –  ISIS extensions – OSPF extensions – BGP extensions – PCEP extensions – FRR with 100% coverage

IS-IS for IP Internets S. Previdi, Ed.Internet-Draft C. FilsfilsIntended status: Standards Track A. BashandyExpires: December 20, 2014 Cisco Systems, Inc. H. Gredler Juniper Networks, Inc. S. Litkowski B. Decraene Orange J. Tantsura Ericsson June 18, 2014

IS-IS Extensions for Segment Routing draft-ietf-isis-segment-routing-extensions-02

Abstract

Segment Routing (SR) allows for a flexible definition of end-to-end paths within IGP topologies by encoding paths as sequences of topological sub-paths, called "segments". These segments are advertised by the link-state routing protocols (IS-IS and OSPF).

This draft describes the necessary IS-IS extensions that need to be introduced for Segment Routing.

Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

Previdi, et al. Expires December 20, 2014 [Page 1]

Slide title 44 pt







16

Abstract Routing Model

draft-filsfils-rtgwg-segment-routing

Slide title 44 pt







17

Segment Routing

› Segment Routing (SR) leverages the source routing and tunneling paradigms.

› A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header.

› A segment can represent any instruction, topological or service-based.

Slide title 44 pt







18

IGP Node Segment

›  Z advertises its global node segment –  simple ISIS sub-TLV extension –  simple OSPF Opaque sub-TLV extension

›  All remote nodes install the node segment to Z in the SR dataplane along the shortest path to Z

A packet injected anywhere with active segment 65 will reach Z via ecmp-aware shortest-path

A

B C

N O

Z

D

P

65

draft-ietf-isis-segment-routing-extensions draft-psenak-ospf-segment-routing-extensions

Slide title 44 pt







19

IGP Adjacency Segment

›  C allocates a local segment for its datalink adjacency CO ›  C advertises the adjacency segment in the IGP

– Simple ISIS sub-TLV extension –  simple OSPF Opaque sub-TLV extension

›  C is the only node to install the adjacency segment in SR dataplane

A B C

M N O

Z

D

P

9003

A packet injected at node C with active segment 9003 is forced through the link C->O

65

draft-ietf-isis-segment-routing-extensions draft-psenak-ospf-segment-routing-extensions

Slide title 44 pt







20

A path with Adjacency Segments

› Source routing along any explicit path –  stack of adjacency labels

› SR provides for entire path control

B C

N O

Z

D

P

A

9101

9105 9107

9103 9105

9101

9105

9107

9103

9105

9105

9107

9103

9105

9107

9103

9105

9103

9105 9105

Slide title 44 pt







21

Combining Segments

› Source Routing › ABCOPZ is expressed as 72, 9003, 65

A B C

M N O

Z

D

P

9003

72 72

65

65

Slide title 44 pt







22

Cross domain controller segmented and hierarchical

Cross Domain Orchestration

Inter domain

AAA PCRF

SDN CTL

SDN CTL

Edge DC Fabric

DC Compute

DC Orch.

Service Level – Inter-domain

Hierarchical

Residential

SDN CTL

Router

SDN CTL

Router

Inter Area

IP/MPLS Transport Service Edge DataCenter

3G/LTE

DSL GPON

Business

CE

PE

Sites Subscribers Services VM’s

Router Router

Segment routing domain in focus today

BGP-LS-SR

Slide title 44 pt







23

Slide title 44 pt







24

OpenDaylight Project Goals

§ Code: To create a robust, extensible, open source code base that covers the major common components required to build an SDN solution and create a solid foundation for Network Functions Virtualization (NFV) § Acceptance: To get broad industry acceptance amongst vendors and users

§ Community: To have a thriving and growing technical community contributing to the code base, using the code in commercial products, and adding value above, below and around.

24

Slide title 44 pt







25

OpenDaylight Momentum

Slide title 44 pt







26

How Does This Compare?

Slide title 44 pt







27

Broad Industry Support for OpenDaylight

27

Slide title 44 pt







28

ODL: BGP processing

Controller

MD-SAL

BGP-LS-SR

RESTCONF

/operational

BGP-‐RIB

/operational

Topology

BGP-LS Topology Exporter

MD-SAL Set

MD-SAL Notification MD-SAL Set MD-SAL Get

Application (Topology Consumer)

BGP-LS-SR speaker (RR)

draft-ietf-idr-ls-distribution draft-gredler-idr-bgp-ls-segment-routing-extension

Slide title 44 pt







29

ODL: PCEP processing

Controller

MD-SAL

PCEP

RESTCONF

/operational /operational

Topology

PCE

MD-SAL Set

MD-SAL Notification MD-SAL Set MD-SAL Get

Applications (topology/constrains/feedback)

PCEP speaker (ingress)

H-PCE

I2RS/OF/other SBI’s

draft-sivabalan-pce-segment-routing draft-ietf-pce-stateful-pce draft-ietf-pce-pce-initiated-lsp

Slide title 44 pt







30

I want a path from A to F

Min link BW=10G Min link delay < 10ms

Link BW Delay A->B 10G 10ms B->D 200G(SRLG) 15ms D->F 10G 10ms

Link BW Delay A->C 10G 5ms C->E 100G 10ms E->F 10G 10ms

A->F Topology A->B->D->F A->C->E->F S

R

PC

EP

->C->E->F

SDN Orchestration

Slide title 44 pt







31

I want a non-constrained path

from A to F Optimize BW use

== UCMP




R

PC

EP

->B,C->F

SDN Orchestration

Slide title 44 pt







32

My link towards F is overloaded




R

PC

EP

->B->D->F

SDN Orchestration: analytics realtime feedback reoptimization

Slide title 44 pt







33 Segment routing domain

Glue between OF & IP/Mpls networks

RR

App App App

Base Network Service Functions

OpenDaylight APIs (REST)

Service Abstraction Layer (MD-SAL)

SR logic

BGP

Stateful PCE L3

App App App Ericsson SDN Controller

OFx.x NETCONF

OF1 R3

OF2

OF3 R1 R2

BG

P-LS

/ PC

EP

L1 L2 L3 L12 L11 L13

I want a path from OF1 to R3 for FEC “XYZ”

SR OF (OF1-L1, OF2-L2 OF3-L3)

PCEP

OF

SW

AP

L13

by L

13

LFIB SWAP L13 by L13

SW

AP

L13

by L

13

LFIB SWAP L13 by L13 LFIB

POP L13

ISIS/OSPF OF

MATCH FEC XYZ

Slide title 44 pt







34

IP MPLS

IP MPLS

IP MPLS

IP MPLS

ROADM

ROADM ROADM

ROADM

Segment routing domain

IP MPLS

OPTO PATH

RR

App App App

Base Network Service Functions

OpenDaylight APIs (REST)

Service Abstraction Layer (MD-SAL)

VNTM Manager

BGP PCEP

Stateful PCE L3

App App App Ericsson/Ciena SDN Controller

OFx.x NETCONF FUTURE

Stateful PCE

L0-L2

IP MPLS

IP MPLS

ROADM ROADM

TL1

IP/MPLS + Optical interworking brings connection-oriented transport into connectionless IP/MLPL world

Netconf

Slide title 44 pt







35

Edge SDN

IP Core

IP Core

IP Core

IP Core

ROADM

ROADM ROADM

ROADM

MLWC RR

BG

P-LS

MP-BGP(LS,RFC3107)

Segment routing domain

Core MLWC CNC

IP Core

Edge SDN

Silver LSP

US tier 1: SR Core SDN + OF Edge use case

CNC MLWC

Cross Domain Orchestration

DC DC

MP-BGP(LS,RFC3107)

Slide title 44 pt







36

More information

›  IETF WG covering Segment Routing – SPRING - http://tools.ietf.org/wg/spring/

› Relevant protocol extensions are defined in OSPF and ISIS WG:

– https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/

– http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-extensions-02

– https://datatracker.ietf.org/doc/draft-psenak-ospf-segment-routing-ospfv3-extension/

Slide title 44 pt







37

Q&A?

Slide title 44 pt







38