8/13/2019 Mon 2-2 Andersson

1/21

www.isocore.com/mpls2013

Presentation Title

Loa Andersson

Huaweiloa@mail01.Huawei.com/ loa@pi.nu

mailto:loa@mail01.Huawei.commailto:loa@pi.numailto:loa@pi.numailto:loa@mail01.Huawei.com

8/13/2019 Mon 2-2 Andersson

2/21

Once I read a book ...

Well not the entire book ...

just one chapter...

The original affluent society by Marshall D Sahlins

Page 2

8/13/2019 Mon 2-2 Andersson

3/21

Once upon a time

An isolated group of humans...

Hunter / gathers

Stoneage lifestyle

Working hours?

Modern

Tribal

Page 3

8/13/2019 Mon 2-2 Andersson

4/21

Pretty relaxed!

But really isolated!!??

No mail, no Facebook, no Twitter, no Web, no SLA ...

Wait a minute!! Bronislaw Malinowski!

The story of the Kuari shells!

4

8/13/2019 Mon 2-2 Andersson

5/21

Kuari shell!

5

8/13/2019 Mon 2-2 Andersson

6/21

Stoneage networking

The original well-connected society...

Page 6

8/13/2019 Mon 2-2 Andersson

7/21

Interesting (?)

But what has this...

...to do with MPLS and SDN?

Solving an eternal basic problem

Note: Not reinventingthe wheel!

The problems statment involves

defining new and better tools for our

inter-tribal communicatio

At least I hope that this is what we are doing ...

7

8/13/2019 Mon 2-2 Andersson

8/21

From the pespective of an MPLS nerd

Page 8

L3VPN

PCEMPLS-TP

GMPLSL2VPN

PWE3

L1VPN

IPO

MPLS and IP

MPLS-TEVN

MPLS-MCP2MP MPLS

SDNCLOUDSR

SPRINGMS-PWs

BFD

OAMi/f

overlay

SFC

DC

8/13/2019 Mon 2-2 Andersson

9/21

What does the picture say?

The picture is clearly a mish-mash of everything!

Working groups are apples

Solutions are oranges

And does not immidiately compare

Dependencies are there,

but not always apparent.

When we continue to develop the

technology we might find ourselves

in one of four situations

9

8/13/2019 Mon 2-2 Andersson

10/21

Monolith

10

A monolith is impressive! But it just stand there

No developmemt TTL has become 0

8/13/2019 Mon 2-2 Andersson

11/21

8/13/2019 Mon 2-2 Andersson

12/21

One size does not fit all!

12

The strength of MPLS is that

it is adaptable.

A couple of fortunate design

decisions:

EncapsulatonFixed Label

Unaware of payload

Link local Labels Context adaptable

8/13/2019 Mon 2-2 Andersson

13/21

One size does not fit all (II)

13

Scaling issues

We dont know what theyare and where to find them

Until we know what the

problem iswe should avoid

bright ideas

Lucky Luke shooting Irrevocable decissions

8/13/2019 Mon 2-2 Andersson

14/21

Irrevocable Decisions

14

More than one way down!

They are not equal!

One is irrevocableand will justget you wet!

The other will leave you with

both alternatives open!

Irrevocable Decissions!

8/13/2019 Mon 2-2 Andersson

15/21

Or we stay in control!

15

8/13/2019 Mon 2-2 Andersson

16/21

Insert

CompanyLogo Here

What do we need to learn?/ What did we learn?

Design authority is

important

Keep the data plane

intact

Dont play with the

MPLS encapsulation

We need strong OAM

tools BFD

LSP Ping

Coordination

Design decisions for

backwards compatibility

Keep the backdoor open

Control Plane is more

robust Not sure whether that is an

accident or not.

If it is not we credit theauthors of RFC 3031

Page 16

8/13/2019 Mon 2-2 Andersson

17/21

What about the future

The future is not what it used to be, whats more it

never was! (Lee Hayes, base singer in the Weavers)!

The future will come with more and increasingly

intresting challenges. We will carefully have to adapt IP and MPLS to these

challenges

SDN, DC, SR, Service Chaning, MPLS Labeled

Applications, etc; just a step on the road

17

8/13/2019 Mon 2-2 Andersson

18/21

Insert

CompanyLogo Here

Future requirements!

Design authority is

important

Keep the data plane

intact

Dont play with the

MPLS encapsulation

We need strong OAM

tools BFD

LSP Ping

Coordination

Design decisions for

backwards compatibility

Keep the backdoor open

Control Plane is more

robust Not sure whether that is an

accident or not.

If it is not we credit the

authors of RFC 3031

Page 18

8/13/2019 Mon 2-2 Andersson

19/21

Insert

CompanyLogo Here

Future requirments!

Design authority is

important

Coordination

We have 24 different

things to coordinate

If it breaks, it will stay

broken

New applications

MPLS to the (who knows) LSPs with new

characteristics might need

to be set up

Look out for the new

bright ideas

We have probably already

discussed them !

more than once

Design for scale

Design for flexibility

Page 19

8/13/2019 Mon 2-2 Andersson

20/21

Summary

What we have done so far has kept us

on the track; and ...

...in control

We will need to continue to do that! The role on bleading edge testing is important

The role of interoperability testing is important

Meeting place for people knee deep in technologydevelopment outside the marketing events is

important

20

8/13/2019 Mon 2-2 Andersson

21/21

Insert

CompanyLogo Here

Questions?

21