© UNIVERSITY of NEW HAMPSHIRE INTEROPERABILITY LABORATORY IEEE 802.1ad Provider Bridges Henry He UNH-IOL Bridge Functions Consortium

© UNIVERSITY of NEW HAMPSHIRE INTEROPERABILITY LABORATORY

IEEE 802.1ad Provider BridgesIEEE 802.1ad Provider Bridges

Henry HeUNH-IOL Bridge Functions

Consortium

UNIVERSITY of NEW HAMPSHIRE

INTEROPERABILITY LABORATORY

Carrier Ethernet Summit – San Diego, CA

Presentation goalsPresentation goalsPresentation goalsPresentation goals

•High level understanding

•What it can do for the customer

•What it can do for the Service Provider

•Pros and cons

•Speak intelligently about it…

•High level understanding

•What it can do for the customer

•What it can do for the Service Provider

•Pros and cons

•Speak intelligently about it…




What is needed?What is needed?What is needed?What is needed?

• Extending Bridged LANs

• Preserve Bridged LAN properties

• Quality of Service

• Sum it up: Something that acts like a Bridged LAN

• Extending Bridged LANs

• Preserve Bridged LAN properties

• Quality of Service

• Sum it up: Something that acts like a Bridged LAN

Lancast Corp.San Francisco, CA

Lancast Corp.Durham, NH

Lancast Corp.San Diego, CA




Why Provider Bridges?Why Provider Bridges?Why Provider Bridges?Why Provider Bridges?

•Provider Bridges are Bridges

•Provider Bridges inherit Bridge properties

•Provider Bridged Network not only acts like a Bridged LAN, it is a Bridged LAN

•“Bridges” are simple

•Lower CAPEX and OPEX than routers in general

•Provider Bridges are Bridges

•Provider Bridges inherit Bridge properties

•Provider Bridged Network not only acts like a Bridged LAN, it is a Bridged LAN

•“Bridges” are simple

•Lower CAPEX and OPEX than routers in general




Who standardizes it?Who standardizes it?Who standardizes it?Who standardizes it?

•IEEE 802.1 Working Group•Amendment to IEEE Std. 802.1Q•Incorporated into IEEE Std. 802.1Q-2005•Similar: Q-in-Q, VLAN Stacking, 802.1Q tunneling

•IEEE 802.1 Working Group•Amendment to IEEE Std. 802.1Q•Incorporated into IEEE Std. 802.1Q-2005•Similar: Q-in-Q, VLAN Stacking, 802.1Q tunneling




What is it trying to do?What is it trying to do?What is it trying to do?What is it trying to do?

• Private Ethernet connectivity over a shared Bridged LAN

• Private Ethernet connectivity over a shared Bridged LAN

Lancast CorpLancast Corp

Pacific NetPacific Net SE TelcoSE Telco




What is the scope?What is the scope?What is the scope?What is the scope?

• Functionality wise…– Transparency

– Traffic segregation

– Service identification

– Customer interfacing

– Priority selection

– Access protection

• Demarcation wise…– from UNI to UNI

• Functionality wise…– Transparency

– Traffic segregation

– Service identification

– Customer interfacing

– Priority selection

– Access protection

• Demarcation wise…– from UNI to UNI




The equipmentsThe equipmentsThe equipmentsThe equipments

Provider Bridged Network

S-VLANBridge

S-VLANBridge

S-VLANBridge

S-VLANBridge

S-VLANBridge

ProviderEdge

Bridge

ProviderEdge

Bridge

ProviderEdge

Bridge

Lancast Corp.Equipment

orLAN


orLAN


orLAN

Pacific NetEquipment

orLAN

Pacific NetEquipment

orLAN

SE TelcoEquipment

orLAN

SE TelcoEquipment

orLAN

SE TelcoEquipment

orLAN




The customer’s viewThe customer’s viewThe customer’s viewThe customer’s view

Lancast CorpLancast Corp

Pacific NetPacific Net SE TelcoSE Telco




The provider’s viewThe provider’s viewThe provider’s viewThe provider’s view

S-VLANBridge

S-VLANBridge

ProviderEdge

Bridge

ProviderEdge

Bridge

ProviderEdge

Bridge

S-VLANBridge

S-VLANBridge

S-VLANBridge




How does it work?How does it work?How does it work?How does it work?

SMAC = PC

DMAC = RTR1

SIP = PC

DIP = Server

SMAC = PC

DMAC = RTR1

SIP = PC

DIP = Server

SMAC = RTR1

DMAC = RTR2

SIP = PC

DIP = Server

VID = 100

SMAC = RTR1

DMAC = RTR2

SIP = PC

DIP = Server

VID = 100

SMAC = RTR2

DMAC = Server

SIP = PC

DIP = Server

Server

PC




How does the PBN do that?How does the PBN do that?How does the PBN do that?How does the PBN do that?

S-VLANBridge

S-VLANBridge

ProviderEdge

Bridge

ProviderEdge

Bridge

ProviderEdge

Bridge

S-VLANBridge

S-VLANBridge

S-VLANBridge

SMAC = RTR1

DMAC = RTR2

SIP = PC

DIP = Server

VID = 100

SMAC = RTR1

DMAC = RTR2

SIP = PC

DIP = Server

VID = 100

SVID = 1000

FCS

SMAC = RTR1

DMAC = RTR2

SIP = PC

DIP = Server

VID = 100




Inside the PBN…Inside the PBN…Inside the PBN…Inside the PBN…

S-VLANBridge

SMAC = RTR1

DMAC = RTR2

SIP = PC

DIP = Server

VID = 100

Port 2Port 2Port 2Port 2



FID Destination MAC SVID Port

111 00 AC F1 DE 28 C1

1

112 2

:

:

:

:

:

:

999 00 2A 1C 9D A0 EE

3

RTR2

Filtering DatabaseFiltering DatabaseFiltering DatabaseFiltering Database

S-VLANBridge Port 2Port 2Port 2Port 2



FID Destination MAC SVID Port

111 00 FE A1 22 31 D2

2000 2

112 1000 2

:

:

:

:

:

:

999 00 E1 FA E8 41 C2

1000 3

RTR2

Filtering DatabaseFiltering DatabaseFiltering DatabaseFiltering Database




Noteworthy detailsNoteworthy detailsNoteworthy detailsNoteworthy details

•New Ethertype

•Reserved MAC address for PBN Spanning Tree

•PCP and Drop Eligible

•Frame expansion needed (802.3as)

•New Ethertype

•Reserved MAC address for PBN Spanning Tree

•PCP and Drop Eligible

•Frame expansion needed (802.3as)




Port-based Service InterfacePort-based Service InterfacePort-based Service InterfacePort-based Service Interface

S-VLAN Bridge

Untagged

C-VLAN 10C-VLAN 20

Untagged

C-VLAN 50

C-VLAN 60

Untagged

C-VLAN 50

C-VLAN 60

Provider BridgedNetwork

Service Instance determinedby physical port




C-tagged Service InterfaceC-tagged Service InterfaceC-tagged Service InterfaceC-tagged Service Interface

Provider Edge Bridge

Untagged

C-VLAN 10C-VLAN 20


Service Instance determinedby C-VLAN ID




S-tagged Service InterfaceS-tagged Service InterfaceS-tagged Service InterfaceS-tagged Service Interface

S-VLAN Bridge

Untagged

S-VLAN 1000S-VLAN 2000


Service Instance determinedby S-VLAN ID




Deployment scenariosDeployment scenariosDeployment scenariosDeployment scenarios


4094 Service Instances4094 Service Instances4094 Service Instances4094 Service Instances







4094 Service Instances4094 Service Instances4094 Service Instances4094 Service Instances







Provider BackboneNetwork

(IEEE P802.1ah)







IETF L2VPN




Pros and ConsPros and ConsPros and ConsPros and Cons

•Pros– A true Bridged LAN service (as opposed to

emulated LAN)

– Based on well standardized and well deployed technologies (namely, .1Q)

•Cons– 4094 service instances are not enough

– Managing 4094 service instances

•Pros– A true Bridged LAN service (as opposed to

emulated LAN)

– Based on well standardized and well deployed technologies (namely, .1Q)

•Cons– 4094 service instances are not enough

– Managing 4094 service instances




SummarySummarySummarySummary

•It is a Bridged LAN (not emulated)

•Based on simple and well established technologies (.1Q)

•Inherits Bridging characteristics

•IEEE Std. 802.1ad

•Limited to 4094 service instances

•Not an encapsulation protocol

•It is a Bridged LAN (not emulated)

•Based on simple and well established technologies (.1Q)

•Inherits Bridging characteristics

•IEEE Std. 802.1ad

•Limited to 4094 service instances

•Not an encapsulation protocol




Q&AQ&AQ&AQ&A

Documents

© UNIVERSITY of NEW HAMPSHIRE INTEROPERABILITY LABORATORY IEEE 802.1ad Provider Bridges Henry He UNH-IOL Bridge Functions Consortium