1

Supporting VUNI in DRNI

Maarten Vissers2011-10-26

v00

2

Introduction

The following slides analyse the ENNI DRNI within a Virtual UNI (V-UNI) scenario.

The ENNI with V-UNI application is defined in MEF28, and relevant text from MEF28 is copied in slide 3.

An ENNI with V-UNI example scenario is presented in slides 4 and 5, illustrating its data plane model with 802.1Q components. The example includes a Network Operator network deploying PBN and a VUNI Operator network deploying either PBN (slide 4) or PBBN (slide 5).

A ENNI with V-UNI application deploys the RCSI specified in 802.1Qbc. This service interface also supports non V-UNI ENNI applications. An example is presented in slide 6,

The data plane model of an ENNI DRNI with V-UNI example is presented in slide 7. The ENNI DRNI contains 2 x 2 nodes with 2 ENNI links. The associated layer stacks are presented in slide 8. Slides 7 and 8 identify the scope of the DRNI to be the S-VLAN Components attached to the E-NNI links. This scope is not aligned with the DRNI scope in axbq-haddock-multiple-drni-support-1011-v01.pdf.

3

Virtual UNIText from MEF 28, clause 3 “Scope and Key Concepts”

R-UNI aware of very basic service attributes, not aware of service details, e.g. # EVCs.

R-UNI maps all (C-Tagged, Prio-C-Tagged, Untagged) service frames to single OVC end point supporting UTA.Single BW profile & CoS

ENNI: an S-VID is used to map ENNI frames to the OVC end point supporting UTA.

Network Operator provides Port-based Service at R-UNI

Single BW profile & CoS

Network Operator provides S-Tagged Service at ENNI

NOTE: Virtual UNI has no Hairpin requirement

4

Virtual UNIin terms of 802.1Q

S CNPPNPCNPPNP

CNP PNPCNP PNPCNP PNP

S CNPPNPCNPPNPPNP PNP

PNP PNPPNP PNP

(R)UNI

Network Operator(e.g. PBN)

PAP

PAP

RCAP

PNP

CEPPEPPEPPEP

CNP

PIP

CNP

PIP

CNP

PIP

CNP

VUNI Operator(e.g. PBN, PBBN)

S SS

C

SPAPCEP

PEPPEPPEP

CNPCNPCNP

C

PAPCEPPEPPEPPEP

CNPCNPCNP

CPNPPNPPNP

PNP

CBP

PNP

CBP

PNP

CBP

BPort-based

Service Interface

S-Tagged Service

Interface

C-Tagged Service

InterfaceV-UNI-N

Port-based Service

Interface

CBPCBPCBP

xxP C

S-EC1S-EC2S-EC3

707 4 0433 O-EC(3)SP-EC(4)

UNI-EC(0)

7

6

Link-EC(7)Link-EC(7)

7777

4

Link-EC(7)

77

3 3 34 37 7 C

C

c6.9c8.5

SP-EC(7)

SP-EC(7)7 7

Link-EC(7)

7 S

c6.9c8.5

Example 1 with 3 C-VLAN EVCs (S-EC1..3) between UNI ports and 1 port-based EVC (S-EC4) between RUNI and VUNI

Alternative network technologies are: PBB(TE),

MPLS-TP, SDH, OTN

6

Link EC

Link-EC

(7)

S-EC4

VUNI

ENNI

PNP

with or without B-VLAN

S-VLAN ECs

C-VLAN ECswithout B-VLAN

Link ECs

77

7C-VLAN ECs

S-VLAN/Link EC

xxP C

C

c6.9c8.5

CVID Forwarding

Alternative network technologies are: PBB-TE,

MPLS-TP, SDH, OTN

Alternatives for this B- Component are LSP-, VCn-,

and ODUk-ComponentsEC: Ethernet Connection, O: Operator,

S: Subscriber, SP: Service Provider, (7): MA level 7

5

Virtual UNIin terms of 802.1Q

S CNPPNPCNPPNP

CNP PNPCNP PNPCNP PNP

S CNPPNPCNPPNPPNP PNP

PNP PNPPNP PNP

(R)UNI

Network Operator(e.g. PBN)

PAP

PAP

RCAP

PNP

CEPPEPPEPPEP

CNP

PIP

CNP

PIP

CNP

PIP

CNP

S SS

C

SPAPCEP

PEPPEPPEP

CNPCNPCNP

C

PAPCEPPEPPEPPEP

CNPCNPCNP

CPNPPNPPNP

PNP

CBP

PNP

CBP

PNP

CBP

BPort-based

Service Interface

S-Tagged Service

Interface

C-Tagged Service

InterfaceV-UNI-N

Port-based Service

Interface

CBPCBPCBP

xxP C

S-EC1S-EC2S-EC3

LinkEC s

707 4 0433 O-EC(3)SP-EC(4)

UNI-EC(0)

77

7

7

6

Link-EC(7)Link-EC(7)

7777

4

Link-EC(7)

77

3 3 34 37 7 C

C

c6.9c8.5

SP-EC(7)

SP-EC(7)7 7

S

c6.9c8.5

Example 1 with 3 C-VLAN EVCs (S-EC1..3) between UNI ports and 1 port-based EVC (S-EC4) between RUNI and VUNI

Alternative network technologies are: PBB(TE),

MPLS-TP, SDH, OTN

6

C-VLAN ECs

S-VLAN ECs

B-VLAN ECs

Link-EC

(7)

S-EC4

VUNI

ENNI

PNP

with or without B-VLAN

Link-EC(7)

7 B

c6.9c8.5

SO-EC(7) 7

c6.10c6.11Link EC

C-VLAN ECswith B-VLAN

S-VLAN/Link EC

I

O-EC(7) 7

DA

/SA

xxP C

C

c6.9c8.5

CVID Forwarding

VUNI Operator(e.g. PBN, PBB)

Alternative network technologies are: PBB-TE,

MPLS-TP, SDH, OTN

Alternatives for this B- Component are LSP-, VCn-,

and ODUk-ComponentsEC: Ethernet Connection, O: Operator,

S: Subscriber, SP: Service Provider, (7): MA level 7

6

Multi-operator Port-based Servicein terms of 802.1Q

S CNPPNPCNPPNP

CNP PNPCNP PNPCNP PNP

S CNPPNPCNPPNPPNP PNP

PNP PNPPNP PNP

(R)UNI

Network Operator(e.g. PBN)

PAP

PAP

RCAP

PNP

CEPPEPPEPPEP

CNP

PIP

CNP

PIP

CNP

PIP

CNP

S SS

C

SPAPCEP

PEPPEPPEP

CNPCNPCNP

C

PAPCEPPEPPEPPEP

CNPCNPCNP

CPNPPNPPNP

PNP

CBP

PNP

CBP

PNP

CBP

BPort-based

Service Interface

S-Tagged Service

Interface

ENNI-N

Port-based Service

Interface

CBPCBPCBP

xxP C

Link-EC

(7)

700433 O-EC(3)SP-EC(4)

UNI-EC(0)

7

Link-EC(7)Link-EC(7)

7777

4

Link-EC(7)

77

3 3 34 37 3O-EC(3)

Example 2 with 1 multi-operator port-based EVC between UNI portsThis (non-Virtual UNI) multi-operator port-based EVC and the RUNI-VUNI port

based EVC in example 1 can both be supported on the ENNI.

Alternative network technologies are: PBB(TE),

MPLS-TP, SDH, OTN

xxP C

6

S-VLAN

LinkLink-EC(7)

7 S

c6.9c8.5

PNP

VUNI

ENNI

Normal ENNI path

with or without B-VLAN

Link

77

7C-VLAN

S-VLAN/Link

7 7

without B-VLAN

VUNI Operator(e.g. PBN, PBB)

Alternative network technologies are: PBB-TE,

MPLS-TP, SDH, OTN

Alternatives for this B- Component are LSP-, VCn-,

and ODUk-ComponentsEC: Ethernet Connection, O: Operator,

S: Subscriber, SP: Service Provider, (7): MA level 7

7

Virtual UNI plus ENNI DRNI

S CNPPNPCNPPNP

CNP PNPPNP

CNP PNP

S CNPPNPCNPPNP

PNP PNPPNP PNPPNP PNP

(R)UNI

Network Operator(e.g. PBN)

PAP

PAP

RCAP

PNP

CEPPEPPEPPEP

CNPPIPCNPPIPCNPPIPCNPPNP

VUNI Operator

SS

S

C

SPAPCEP

PEPPEPPEP

CNPCNPCNP

C

PAPCEPPEPPEPPEP

CNPCNPCNP

CPNPPNPPNP

PNP

CBP

PNP

CBP

PNP

CBP

B

S-Tagged Service

Interface

CBPCBPCBP

xxP C

CNP PNPPNP

CNP PNPS

PAP

PAP

RCAP

PNP

CEPPEPPEPPEP

CNPPIP

CNPPIP

CNPPIP

CNPPNP

S

C

SPAPCEP

PEPPEPPEP

CNPCNPCNP

C

PAPCEPPEPPEPPEP

CNPCNPCNP

CPNPPNPPNP

PNP

CBP

PNP

CBP

PNP

CBP

BCBPCBPCBP

PNP PNPPNP PNPPNP PNP

SCNP

CNPPNP

PNP

PNPPNP PNPPNP PNPPNP PNP

SB

Intr

a-D

AS

(a)

ENNI 1

ENNI 2

Intra-DA

S

Intra-Netw

ork

Intra-Network (A)

Intr

a-N

etw

ork

(B)

Intra-Network C)

Intra-Network C)

Intra-DAS (b)

Intra-DAS (b)

Intra-DAS (b)

Intra-DAS (b)

Hal

f DA

SH

alf D

AS

Supports DRNI protected &

unprotected ECs

Half D

AS

Half D

AS

ENNI DRNI between Network Operator and VUNI Operator networks should operate at the ENNI’s S-VLAN EC level. This implies that the DRNI is between the S-VLAN Components connected to the ENNI links.It also implies that there are Virtual V-UNI-N ports, consisting of two V-UNI-N ports as illustrated. Compare the Virtual V-UNI-N port with the Virtual CBP Port in an IB-BEB; functionality is the same.

Network side DRNI domain Network side

VUNI

ENNI

VUNI

Intra-DAS links may be supported via 802.3 link (Intra-DAS(a)) or via virtual link in the network (Intra-DAS(b)).

V-UNI-N:LAN with

N x C-VLANmapped intoM x S-VLAN

CBPLAN withN x BSI

mapped intoM x B-VLAN

Virtual V-UNI-N Port(same functionality as Virtual CBP Port)

Virtual PNP-PNP Port

xxP C

8

Link

Link

Link

S-VLAN Link

S-VLAN

DRNI location within Layer Stacks

C-VLAN

Link S-VLAN Link

Link Link Link

CNP PNPCNP PNPCNP PNP

S CNPPNPCNPPNP

PNP PNPPNP PNPPNP PNP

(R)UNI

RCAPPIP

S SSS PAPCEPPEPPEPPEP

CNPCNPCNP

CPNP

PNP

CBPPNPPNP

B

xxP C

ENNI

CBPCBP

Link Link

DRNI scope A

B-VLAN

Link

Alternative network layer technologies are: PBB-TE

ESP/TESI, MPLS-TP Transport-LSP, SDH VC-n, OTN ODUk

B-VLAN

Link

Exam

ple

1Ex

ampl

e 2

VUNI

PNP PNP

animated slide

Common S-VLAN ECs at both ends of DRNI

9

Link

Link

Link

S-VLAN Link

S-VLAN

DRNI location within axbq-haddock-multiple-drni-support-1011-v01.pdf

C-VLAN

Link S-VLAN Link

Link Link Link

CNP PNPCNP PNPCNP PNP

S CNPPNPCNPPNP

PNP PNPPNP PNPPNP PNP

(R)UNI

RCAPPIP

S SSS PAPCEPPEPPEPPEP

CNPCNPCNP

CPNP

PNP

CBPPNPPNP

B

xxP C

ENNI

CBPCBP

Link Link

DRNI scope B

B-VLAN

Link

Alternative network layer technologies are: PBB-TE

ESP/TESI, MPLS-TP Transport-LSP, SDH VC-n, OTN ODUk

B-VLAN

Link

Exam

ple

1Ex

ampl

e 2

VUNI

PNP PNP

animated slide

DifferentS-VLAN ECs at both ends of DRNI

10

DRNI scope discussion

axbq-haddock-multiple-drni-support-1011-v01.pdf (slide 9) and this presentation (slides 7/8) assume that the DRNI includes different sets of 802.1Q Components as illustrated in slides 7/8 (scope A) and 9 (scope B)

To be discussed is the right DRNI scope: A, B or other

11

Backup

12

CNP PNPCNP PNPCNP PNP

S CNPPNPCNPPNP

PNP PNPPNP PNPPNP PNP

(R)UNI

CNPPNP

S SSB

PIPPNP xxP C

Functionality commonality between PEB/VUNI and IB-BEB

CNP PNPCNP PNPCNP PNP

S CNPPNPCNPPNP

PNP PNPPNP PNPPNP PNP

(R)UNI

RCAPPIP

S SSS PAPCEPPEPPEPPEP

CNPCNPCNP

CPNP

PNP

CBPPNPPNP

B

xxP C

ENNI

CBPCBP

VUNI

PNP PNP

ISID based distribution

I

c6.11

BVLAN MEP

CVID based distribution

c6.9c8.5

c6.9c8.5SVLAN MEP

B-Component

I-Component

S-VLAN-Component

S-VLAN-/I- ComponentB-Component

DRNICBPCBP

PNP

Similar functionality in PEB/VUNI and IB-BEB following the component connected to the E-NNI

links

CBP

V-UNI-N:LAN with N x C-VLAN

mapped into M x S-VLAN

CBPLAN with N x BSI

mapped into M x B-VLANanimated slide