32
Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality in terms of 802.1Q modelling Maarten Vissers 2010-11-08

Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Embed Size (px)

Citation preview

Page 1: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN)

supporting P2P, P2MP, RMP and MP2MP Ethernet Services

An overview of architecture and functionality in terms of 802.1Q modelling

Maarten Vissers2010-11-08

Page 2: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Introduction

E-OTN and PTN are multi domain, traffic engineered transport networks which support P2P, P2MP, RMP and MP2MP Ethernet servicesOTN network contains multiple OTN carrier networksOTN carrier networks contain OTN access, metro and core domainsOTN network contains OTN network termination (NT), electrical switching and optical switching (SW) equipmentOTN equipment at edge of domains is extended with Ethernet Switch functionality

2

Page 3: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN example

OTN Core

OTN Metro

OTN Metro

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XCN-degree ROADM

ODU XC

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XC/ADMN-degree ROADM

ODU XC

OEOOEOOEO

OCH XCN-degree ROADM

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XCN-degree ROADM

ODU XC

OEOOEOOEO

OCH XCN-degree ROADM

OEOOEOOEO

OCH XCN-degree ROADM

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XC/ADMN-degree ROADM

ODU XC

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XC/ADMN-degree ROADM

ODU XC

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XC/ADMN-degree ROADM

ODU XC

OEOOEOOEO

OCH XC/ADMN-degree ROADM

OEOOEOOEO

OCH XC/ADMN-degree ROADM

OEOOEOOEO

OCH XC/ADMN-degree ROADM

OEOOEOOEO

OCH XC/ADMN-degree ROADM

NT

NT

NT

NT

NT

NT

NT

NT

NT

OEOE

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XCN-degree ROADM

ODU XC

Ethernet Switch

OE

OE

OE

OE

OEOE

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XCN-degree ROADM

ODU XC

Ethernet Switch

OE

OE

OE

OE

NT

NT

NT

NT

NT

OEOE

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XCN-degree ROADM

ODU XC

Ethernet Switch

OE

OE

OE

OE

OEOE

OEOOEOOEO

OEOE

OE

OE

OE

OE

OCH XCN-degree ROADM

ODU XC

Ethernet Switch

OE

OE

OE

OE

NT NT NTOTN Network Termination

Ethernet Network Termination

Hybrid Ethernet & OTN Network Termination

OD

UO

DU

OD

U

OD

UO

DU

OD

U

OD

UO

DU

OD

UO

DU

OD

UO

DU

OTN Access

SWOTN/EOTN Switch

MAC Relay functions interconnected via OTN

ODU connections

MAC Relay functions interconnected via OTN

ODU connections

MAC Relay functions are interconnected via OTN ODU connections

MAC Relay functions interconnected via OTN

ODU connections

MAC Relay functions interconnected via OTN

ODU connections

MAC Relay functions are interconnected via OTN ODU connections or S- or I-Tagged LANs

3

Page 4: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN and PBN

EOTN adds one transport VLAN layer on top of its OTN layer stackEOTN can be viewed in this respect as a transport PBN in which the 802.3 physical ports are replaced by G.709/G.7041 physical ports and TPMR type reserved address transparencyEOTN deploys the 802.1Q features complemented by specific transport network features defined in Y.1731, G.8021, G.8031, G.8051 and G.8052

4

Page 5: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

S-VLANComponent

88-a8Table 8-2

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

S-VLANComponent

88-a8Table 8-2

802.1Q Provider (Edge) Bridges(starting point)

C-VLANComponent

81-00Table 8-1

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

Provider Edge Bridge

C-tagged service interfaces(CTSI) S-tagged service interface

(STSI)

Port-based service interface (PBSI)

Provider Bridge

Provider Bridge

Provider Edge Port

Customer Edge Ports

Customer Network Port

Provider Network

Ports

Provider Network Ports

Customer System

C-VLANComponent

81-00Table 8-1

Provider Access Ports

C-tagged service interfaces

Remote customer service interfaces (RCSI)

Port-based service interface

Access Network’sProvider Bridge

Provider Network Ports

S-VLAN Components operating on TPID 88-a8 with S-VLAN Reserved

Address transparency (Table 8-2), IVL and SVL (multi-vid E-Tree), VID

translation, xSTP/xVRP

S-VLANComponent

88-a8Table 8-2

Customer’sProvider Bridge

PNP

5

Page 6: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

802.1Q port types

Many of the 802.1Q port types are variations of a common port which supports

a single VLAN multiplexing instance (clause 6.9) with configurable:

Tag type (TPIDs: 81-00, 88-a8), Acceptable Frames Typeuntagged set member

Up MEPs, Up MIPsDown MIPs, Down MEPsDown MEP below clause 8.5

6

Page 7: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

802.1Q port types

7

CEP PEP CNP port

based

CNP tag’d

PNP RCAP PAP Common Port

Tag type C C S S S S S C/S

Admit Only VLAN-tagged frames Y Y N Y Y Y N Y/N

Admit Only Untagged and Priority-tagged frames

Y N Y N N N Y Y/N

Admit All frames Y Y N ? N ? N Y/N

PVID Y Y Y Y Y Y/N

Enable Ingress Filtering N Y N Y/N

Member of untagged set O O Y N - Y Y/N

Up MEP N N Y Y N N N Y/N

Up MIP Y N N|Y Y Y N N Y/N

Down MIP Y N N|Y Y Y N N Y/N

Down MEP N N N N N N N Y/N

Down MEP below c8.5 Y N N|Y Y Y Y N Y/N

Specific Configurations of Common Port

Page 8: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

S-VLANComponent

88-a8Table 8-2

EOTN (Edge) Bridges(based on provider (edge) bridges)

C-VLANComponent

81-00Table 8-1

VLANComponent

VLANComponent

EOTN Edge Bridge

Transparent Service Interface

Port Based Service Interface

EOTN Bridge

EOTN Bridge

CEP

OTNNetwork

Ports

Customer System

C-VLANComponent

81-00Table 8-1

Customer’sProvider Bridge

CEP PAP

PAP

PEP

PEPCNP

CNP

CNP

CNP

CTSI

CNP

CNP

CNP

PNP

RCAP PNP

PEP

PEP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

EOTN’s VLAN Component deploys:• ONP instead of PNP ports, and

• transport Ethernet specific features

S-VLANComponent

88-a8Table 8-2

Customer’sProvider Bridge

PNP

Individual S-VLAN Service Interface

8

Page 9: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

OTN Network Port functionalityOTN Network Ports combine 802.1Q’s Provider Network Port functionality with an OTN physical layer

Ethernet MEP and MIP functionsIncludes support for Y.1731 Ethernet OAM, G.8021 OAM processing and G.8031 APS OAM

Ethernet to OTN (de)mapping/(de)muxing functions:Support of the EISS Tag insertion/extractionSupport of the ISS by additional technologies GFP-F/OTN

Up MPs (6.17, 19.2, 19.3)

Port filtering entities (8.6.1/2/4/5)

Down MPs (6.17, 19.2, 19.3)

Linktrace Output Multiplexer (19.5)

Queuing entities (8.6.6/7/8)

Support of the EISS

Support of the ISS by additional technologies (6.15)

OTN ODU Down MP

GFP-F

Tagging

Up MPs (6.17, 19.2, 19.3)

Port filtering entities (8.6.1/2/4/5)

Down MPs (6.17, 19.2, 19.3)

Linktrace Output Multiplexer (19.5)

Queuing entities (8.6.6/7/8)

Support of the EISS

Support of the ISS by additional technologies (6.15)

OTN ODU Down MP

Frame filtering (8.6.3)EISS

EISS

EISS

EISS

EISS

EISS

ISS

EISS

EISS

EISS

EISS

EISS

EISS

ISS

OTN other functionsOTN other functions

Supports G.8031 SNC Protection

OTN

NETWORK

PORTs

Supports Y.1731 OAM

9

PNPequivalent

OTNspecific

Page 10: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

MAC SDU

TYPE

PLI GFP Core HeaderGFP Payload Header

DA

MAC FCS

VLAN Tag

PTI=000: Client DataPFI=0: no Payload FCSEXI=000: Null Extension HeaderUPI=0000 0001: Frame Mapped Ethernet

PTI EXIcHEC

PFI UPI tHEC

DA SASA

TPID PCP

DEI VID

ODUk with GFP-F encapsulated Ethernet frames with VLAN Tag

GFP IDLEs

16 3808

4

ODUkbit rates

1.25G2.5G

3.75G5G

6.25G7.5G

8.75G10G

11.25G::

100G

Page 11: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN service set

11

Page 12: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN Requirementshttp://www.ieee802.org/1/files/public/docs2010/liaison-itut-sg15-oLS-197-0710.docx

Transport all MEF (G.8011.x) services over OTNTransport all 802.1 service interfaces over OTNSupport the management of all above services simultaneously using a single forwarding functionTransport by using a unique edge-to-edge layer that is separated from the customer

12

Page 13: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN Edge Bridge – Extended service set

EOTN is required to support any type of Tagged service, including bundled S-Tagged and I-Tagged services, over a single Ethernet (ETH) layerEOTN Edge Bridge can support those services by deploying additional CNPs and CBPs and connecting those to customer PIPs and CBPs as illustrated in the next slide

13

Page 14: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

S-VLANComponent

88-a8Table 8-2

EOTN Edge Bridge – Extended service set

C-VLANComponent

81-00Table 8-1

VLANComponent

VLANComponent

EOTN Edge Bridge

EOTN Bridge

EOTN Bridge

CEP

Customer System

C-VLANComponent

81-00Table 8-1

Customer’sProvider BridgeCEP PAP

PAP

PEP

PEPCNP

CNP

CNP

CNP

CTSI

CNP

CNP

CNP

CNP

RCAP PNP

PNP

PEP

PEP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP bundled S-VLAN service interface

CBPBSI (bundled) service interface

I-Component

Customer’s I-BEB/B-BEB/T-BEB

PIP

B-Component

CBPCBP

CNP

CNP

PNP

PNP

BSI (bundled) service interface

S-VLANComponent

88-a8Table 8-2

Customer’sProvider Bridge

PNP

CBP

PIP

BSI transparent service interface

CNP

CNP

BSI transparent service interface

Reuse of existing CNP and CBP ports on the EEB supports BSI individual and/or bundled services,

transparent services and S-VID/S-PCP/S-DEI

preserving (bundled) S-Tagged services

PNPIndividual S-VLAN Service

Interface

Transparent Service Interface

Port Based Service Interface

T-Component CNPPIP

BSI transparent service interface

CNP

14

Page 15: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN (Edge) Bridges – Transparency

Support of Transparent Services by the EOTN’s Ethernet service (ETH VC) layer requires TPMR type transparency (Table 8-3)S-Tag does not provide such transparencyEOTN should deploy a new VLAN Tag associated with:

TPMR type transparencyTransport network type operation, management and control

15

Page 16: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Choice of Tag in EOTN (Edge) Bridge

Tag choiceNew Transport VLAN Tag with 12-bit T-VID (ETH VC ID) & TPMR Reserved Address transparency (table 8-3/802.1Q)

I-Tag with 24-bit I-SID; UCA-bit deals with T-VLAN (ETH VC) frames with or without network MAC addresses (N-DA, S-DA)

Tag is terminated in the “Support of the EISS” functions in ONP

vlan_identifier parameter represents in EM_UNITDATA the 12-bit T-VLAN ID or 24-bit I-SIDExisting devices already support VLAN Tag with 12-bit ID; EtherType is configurable per portDevices do not support an I-SID based vlan_identifier parameter

VLAN Tag with new “Transport VLAN” type TPID value is best fit

TPID = xx-xx T-VID (ETH VC ID)PCP DE

INew VLAN Tag4-octets

16 3 1 12

TPID = 88-E7 I-SID (ETH VC ID)PCP DE

I

I-Tag18-octets

16 3 1 24

RES2

2

UC

A

1

RE

S1

1

DA

SA

16

Page 17: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN port types(based on provider (edge) bridge ports)

17

CEP PEP CNP port

based

CNP tag’d

PNP RCAP PAP Common Port

ONP

Tag type C C S / T S S S S C/S/T T

Admit Only VLAN-tagged frames Y Y N Y Y Y N Y/N Y

Admit Only Untagged and Priority-tagged frames

Y N Y N N N Y Y/N N

Admit All frames Y Y N ? N ? N Y/N N

PVID Y Y Y Y Y Y/N

Enable Ingress Filtering N Y N Y/N N

Member of untagged set O O Y N - Y Y/N N

Up MEP N N Y Y N N N Y/N N|Y

Up MIP Y N N|Y Y Y N N Y/N Y

Down MIP Y N N|Y Y Y N N Y/N Y

Down MEP N N N N N N N Y/N N|Y

Down MEP below c8.5 Y N N|Y Y Y Y N Y/N N

Same basic set of portsAdditional Tag typeAdditional Port type

Specific Configurations of Common Port

Page 18: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

S-VLANComponent

88-a8Table 8-2

EOTN (Edge) Bridge

C-VLANComponent

81-00Table 8-1

T-VLANComponent

<T-Tag>Table 8-3

T-VLANComponent

<T-Tag>Table 8-3

EOTN Edge Bridge

EOTN Bridge

EOTN Bridge

CEP

Customer System

C-VLANComponent

81-00Table 8-1

Customer’sProvider BridgeCEP PAP

PAP

PEP

PEPCNP

CNP

CNP

CNP

CTSI

CNP

CNP

CNP

CNP

RCAP PNP

PNP

PEP

PEP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

ONP

bundled S-VLAN service interface

CBP

BSI (bundled) service interfaceI-

Component

Customer’s I-BEB/B-BEB/T-BEB

PIP

B-Component

CBPCBP

CNP

CNP

PNP

PNP

BSI (bundled) service interface

S-VLANComponent

88-a8Table 8-2

Customer’sProvider Bridge

PNP

CBP

PIP

BSI transparent service interface

CNP

CNP

BSI transparent service interface

PNPIndividual S-VLAN Service

Interface

Transparent Service Interface

Port Based Service Interface

T-Component CNPPIP

BSI transparent service interface

CNP

18

T-VLAN component is a VLAN type Component

operating on TPID: <T-Tag> with TPMR Reserved

Address transparency (Table 8-3), ONP instead of PNP

ports, IVL and SVL (multi-vid E-Tree/E-LAN),

independent ingress/egress VID translation, disabled

xSTP/xVRP, Y.1731/G.8021 OAM and G.8031 Ethernet

VLAN SNC protection.

Page 19: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

MAC SDU

TYPE

PLI GFP Core HeaderGFP Payload Header

DA

MAC FCS

Transport-VLAN Tag

PTI=000: Client DataPFI=0: no Payload FCSEXI=000: Null Extension HeaderUPI=0000 0001: Frame Mapped Ethernet

PTI EXIcHEC

PFI UPI tHEC

DA SASA

TPID=<T-Tag> PCP

DEI T-VID

ODUk with GFP-F encapsulated Ethernet frames with T-VLAN Tag

GFP IDLEs

16 3808

4

ODUkbit rates1.25G2.5G

3.75G5G

6.25G7.5G

8.75G10G

11.25G::

100G

Page 20: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN summary

20

Page 21: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

EOTN Summary

EOTN requires a minimal extension of 802.1Q functions and ports:

Additional OTN Network Port with a Support of the EISS function which operates on a new T-Tag associated with TPMR Reserved Address transparencyExisting CNPs and CBPs with a Support of the EISS function which operates on a new T-Tag associated with TPMR Reserved Address transparency

21

Page 22: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

PTN

22

Page 23: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Q.9/15 liaison on G.ptneq: “Next Step”http://www.ieee802.org/1/files/public/docs2010/new-itu-1-G-ptneq-IEEE-Final-0510-v1.ppt

PTN VC/VP/VS layers may be supported by the Ethernet technology including ETH OAM(Y.1731,G.8021), ETH protection switching(G.8031,G.8032), ETH connection management (G.8051, G.8052).The use of Ethernet technology in PTN requires an extension of the tagging option defined in 802.1Q to support VC, VP, VS stacking in single and multi-domain scenarios. ITU-T Q9/15 would like to progress this work in cooperation with IEEE 802.1

23

Page 24: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Ethernet PTN

Ethernet PTN network contains a PBN like transport VLAN (ETH VC) layer (same as EOTN)

Those transport VLANs may be transported in P2P server VLANs (ETH VPs)

instead of in P2P ODUs in EOTN, or P2P LSPs in MPLS-TP/VPLS

This requires PTN Network Ports (PTNP) which support 2-stage VLAN multiplexing and optional priority-tagging

24

Customer/Client service Layer

Virtual Channel Layer

Virtual Path Layer (optional)

Virtual Section Layer (optional)

Physical Media (802.3)

GFPCircuit Switching Technology

(OTN, SDH, PDH)

Physical Media (OTM-n, STM-n, DSn/En,

xDSL)

PT

N la

yer

netw

orks

Tra

nsm

issi

on M

edia

Cha

nnel

Pat

h

Page 25: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Linktrace Output Multiplexer (19.5)

Down MPs (6.17, 19.2, 19.3)

Priority Tag (6.13)

Down MPs (6.17,19.2)

PTN Network Port (PTNP)

25

Up MPs (6.17, 19.2, 19.3)

Port filtering entities (8.6.1/2/4/5)

Down MPs (6.17, 19.2, 19.3)

Linktrace Output Multiplexer (19.5)

Support of the EISS (6.9)

Support of the ISS (6.7)

MAC

Frame filtering (8.6.3)EISSEISS

EISS

EISS

EISS

EISS

ISS

PTNP

PTN-Tagged LAN

Linktrace Output Multiplexer (19.5)

Support of the EISS (6.9)EISS

ISS

ISS

EISS

EISS ISS

ISS

EISS

NxISS

ISS

ISS

ISS

ISS

ISS

ISS

ISS

VC Tag

VP Tag

VS Tag

Page 26: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Hierarchy

Multi-stage connection hierarchy is a normal means deployed in the latest generation circuit and packet transport networks to scale these networks

OTN supports up to 4 ODU multiplexing stages (more to follow)

MPLS-TP supports an unrestricted number of LSP multiplexing stages

An Ethernet based PTN should have the capability to support such multi-stage connection hierarchyVLAN Tags should therefore be stackable

VP and VS transport VLANs are P2P VLANs (without MAC based forwarding) set up by transport network management and control systems

26

Page 27: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

VPVS

VPVS

In multi-domain case the layer relationship is relative and the names represent their role in each domain; some examples:

Top Default case, no additional hierarchy

MiddleVP in Domain 1 is VC in Domain 2VP in Domain 2 is VC in Domain 3

BottomVS in Domain 1 is VC in Domain 2 VS in Domain 2 is VC in Domain 3

Each domain operates on the lower three layers and is unaware of the higher layers

VCVPVS

VCVPVS

VCVPVS

Domain 1 Domain 2 Domain 3

Hierarchy for multiple domains

VCVP

VS VCVP

VS VCVPVS

Page 27

VCVPVS

VS

VS

Page 28: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Domain interconnect examplesVLAN Hierarchy Extension

28

Up MPs (6.17, 19.2, 19.3)

Linktrace Output Multiplexer (19.5)

Support of the EISS (6.9)

Linktrace Output Multiplexer (19.5)

Down MPs (6.17, 19.2, 19.3)

Priority Tag (6.13)

Down MPs (6.17,19.2)

Support of the ISS (6.7)

Support of the EISS (6.9)

Linktrace Output Multiplexer (19.5)

Down MPs (6.17, 19.2, 19.3)

Port filtering entities (8.6.1/2/4/5)EISS

EISS

EISS

EISS

ISS

EISS

ISS

ISS

EISS

EISSISS

ISS

EISS

NxISS

ISS

ISS

ISS

ISS

ISS

ISS

ISS

Linktrace Output Multiplexer (19.5)

Down MPs (6.17, 19.2, 19.3)

Priority Tag (6.13)

Down MPs (6.17,19.2)

Up MPs (6.17, 19.2, 19.3)

Port filtering entities (8.6.1/2/4/5)

Down MPs (6.17, 19.2, 19.3)

Linktrace Output Multiplexer (19.5)

Support of the EISS (6.9)

Support of the ISS (6.7)

MAC

Frame filtering (8.6.3)

EISS

EISS

EISS

EISS

EISS

ISS

Linktrace Output Multiplexer (19.5)

Support of the EISS (6.9)EISS

ISS

ISS

EISS

EISS ISS

ISS

EISS

NxISS

ISS

ISS

ISS

ISS

ISS

ISS

ISS

Linktrace Output Multiplexer (19.5)

Down MPs (6.17, 19.2, 19.3)

Priority Tag (6.13)

Down MPs (6.17,19.2)

Up MPs (6.17, 19.2, 19.3)

Port filtering entities (8.6.1/2/4/5)

Down MPs (6.17, 19.2, 19.3)

Linktrace Output Multiplexer (19.5)

Support of the EISS (6.9)

Support of the ISS (6.7)

MAC

EISS

EISS

EISS

EISS

EISS

ISS

Linktrace Output Multiplexer (19.5)

Support of the EISS (6.9)EISS

ISS

ISS

EISS

EISSISS

ISS

EISS

NxISS

ISS

ISS

ISS

ISS

ISS

ISS

ISS

MAC

EISS

DOMAIN A DOMAIN B

VCAVPAVSA=VCBVPBVSB

VCAVPAVSAVPA=VCBVPBVSB

Page 29: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

T-VLANComponent

<T-Tag>Table 8-3

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

S-VLANComponent

88-a8Table 8-2

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

C-VLANComponent

81-00Table 8-1

S-VLANComponent

88-a8Table 8-2

E-PTN (Edge) Bridges(based on eotn (edge) bridges)

C-VLANComponent

81-00Table 8-1

T-VLANComponent

<T-Tag>Table 8-3

E-PTN Edge Bridge

E-PTN Bridge

E-PTN Bridge

CEP

Customer System

C-VLANComponent

81-00Table 8-1

Customer’sProvider BridgeCEP PAP

PAP

PEP

PEPCNP

CNP

CNP

CNP

CTSI

CNP

CNP

CNP

CNP

RCAP PNP

PNP

PEP

PEP

PTNP

PTNP

PTNP

PTNP

PTNP

PTNP

PTNP

PTNP

PTNP

PTNP

S-VLAN bundled service interface

CBPBSI (bundled) service interface

I-Component

Customer’sI-BEB/B-BEB/T-BEB

PIP

B-Component

CBPCBP

CNP

CNP

PNP

PNP

BSI (bundled) service interface

S-VLANComponent

88-a8Table 8-2

Customer’sProvider Bridge

PNP

CBP

PIP

BSI transparent service interface

CNP

CNP

BSI transparent service interface

CNP MPEP

CNP MPNP

PNP

Transparent Service Interface

Port Based Service Interface

Individual S-VLAN Service Interface

T-Component CNPPIP

BSI transparent service interface

CNP

29

PTNNetwork

Ports

ONPs are replaced by PTNPs

Page 30: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

PTN Summary

An Ethernet based PTN requires the development of a PTN Network Port (PTNP), which supports 2-stage VLAN multiplexing and transport specific Ethernet featuresA stackable VLAN Tag is required to support the single and multi-domain ETH VC/VP/VS (VLAN) hierarchy

30

Page 31: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Annex

31

Page 32: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality

Transport network specificEthernet features

Alarm suppressionAdditional Y.1731, G.8021, G.8031, G.8032 Ethernet OAM framesG.8031 VLAN linear protection (ETH SNC protection) G.8032 VLAN ring protectionVLAN IDs have a link local scope and VID Translation is used to map the local VID on each link onto the Relay VID inside a node

Number of FIDs is equipment specific and not limited to 4094 (as specified in 8.8.8/802.1Q); e.g. could also be 16k, 32k, 64k, 128k,...VLAN connection management with network management or GMPLS control plane

without spanning tree protocol (MSTP) and without VLAN registration protocol (MVRP)

32