detnet control plane – possible...

15
DetNet Control Plane Possible Future November 11, 2018 Bangkok, Thailand 1 DetNet - TSN Workshop

Upload: others

Post on 28-May-2020

3 views

Category:

Documents


0 download

TRANSCRIPT

DetNetControl Plane –Possible Future

November 11, 2018Bangkok, Thailand

1DetNet - TSN Workshop

DetNet and Control Plane• Direct work on Control Plane functions is currently out of scopeo This can be revisited once work deliverables are complete

• Indirect / supporting work, including implications and requirements, is in scopeo Flow information modelo Data plane solutions documentso YANG models

• Future work will leverage existing RFCs and drafts in development of other Working Groupso Some work likely to move to protocol owning WG, with DetNet WG defining

requirementso Objective of this talk is identify those other WGs and their technologies

• For more information see tutorial from IETF 103: An IETF Traffic Engineering Overviewhttps://datatracker.ietf.org/meeting/103/materials/slides-103-edu-sessk-an-ietf-traffic-engineering-overview

DetNet - TSN Workshop 2

Related IETF Technologies• MPLS-TE: MPLS with traffic engineeringo Includes: Data Plane, Routing (OSPF-TE, ISIS-TE), Signaling (RSVP-TE)oMPLS-SR (segment routing) with Traffic Engineering possible future

• GMPLS: Distributed Multi-layer transport network control• PWs: Service adaptation via Pseudo Wires and EVPN control• PCE: Centralized path computation and control• ACTN/SDN-TE: An approach to delivering TE orchestration and

control• TE YANG Models: for monitoring and north/south controloCan be used with centralized, decentralized or hybrid control approaches

DetNet - TSN Workshop 3

MPLS-TE Service

Service may be:• Unidirectional

Point-to-point (P2P) or Point-to-multipoint (P2MP)

• Bidirectional P2P o Co-routed or associated o Symmetric or asymmetric

bandwidth• Multiple recovery options

MPLS TP Services

P2P P2MP

Uni-directional

Bi-directional

Asymmetric Bandwidth

SymmetricBandwidth

Co-routed Associated

TE ServiceAttachment

CircuitAttachment

CircuitTE NetworkCE1 CE2PE1 PE2

Traffic Engineered Tunnels Between Endpoints

DetNet - TSN Workshop 4

Data flow47

GMPLS

DetNet - TSN Workshop 5Source: An IETF Traffic Engineering Overview

GMPLS: Example Multi-Layer Configuration

DetNet - TSN Workshop 6

• Ethernet service: End to end with mid-stage grooming

• TDM - OTU/ODU services: Independent between Ethernet processing nodes

• Lambda services: Independent across WDM networks

OTN Switchingand TransportLambda

Ethernet X

XX X

Layer

DetNet - TSN Workshop 7

MPLS-TE and GMPLS Control Protocols

MPLS Control PlanePrefix LSP Signaling

LDP (and BGP)

Tunnel LSP SignalingRSVP-TE, CR-LDP

TE-RoutingOSPF-TE, IS-IS-TE

GMPLS extensionsGMPLS-Routing

OSPF-TE, IS-IS-TEGMPLS-Signaling

RSVP-TE, CR-LDP

Link ManagementLMP, LMP-WDM,LMP-SONET

• Some implementations use centralized control – more on this later

PseudoWires

• Transports layer 1, 2 or 3 data over packet networkso For example TDM, Ethernet or ATM over MPLS

• PW Control Word used to o Differentiate traffic types (IP vs PW)o Enable PW client related processingo Supports PW OAM

• BGP-Based EVPN is current preferred L2VPN control protocol

PW ServiceAttachment

CircuitAttachment

CircuitMPLS NetworkCE CEP S-PE

Any L1/L2/L3* PWoLSP Any

L1/L2/L3

T-PE T-PE

PWoLSP

LSP Label S=0

PW Label S=1

PW Control

Client data

PW Headers

8DetNet - TSN Workshop

PCE

DetNet - TSN Workshop 9

Source: An IETF Traffic Engineering Overview

PCE

DetNet - TSN Workshop 10

Source: An IETF Traffic Engineering Overview

ACTN/SDN-TE

DetNet - TSN Workshop 11

• TEAS WG ACTN provides a framework for SDN control of traffic engineered networks

• Useful reference architectureoController-based solutions

need not adhere to ACTN• North-south interfaces are

generally applicableoTo non-ACTN controllers

and even distributed control planes

oDefined using YANG

Source: An IETF Traffic Engineering Overview

PCE as a Controller• Non-ACTN SDN-TE Controller Example

DetNet - TSN Workshop 12Source: An IETF Traffic Engineering Overview

TE-YANG• Multiple YANG models

supporting TE existoDefined in multiple WGsoDifferent stages of

process• Reminder: ACTN is a

reference model for SDN-TE, not a required implementation

DetNet - TSN Workshop 13

Source: An IETF Traffic Engineering Overview

Segment Routing

DetNet - TSN Workshop 14

• SR-TE work is on-goingoCurrently path steering is defined via policy (Path Engineering only)oSome individual proposals include resource control

Sour

ce: A

n IE

TF T

raffi

c En

gine

erin

g O

verv

iew

Related IETF Working Groups• TEAS: Traffic Engineering Architectures and GMPLS/RSVP-TE• MPLS: MPLS data plane, LDP, MPLS specific control• PCE: PCE protocol, servers• LSR: Link state routing protocols (ISIS, OSPF)• CCAMP: Non-Packet technology-specific control• BESS: EVPN• PALS: PWs• SPRING: Segment Routing• NetMod: YANG Language, core modules• NetConf: YANG encoding and transport, some core modules

DetNet - TSN Workshop 15