Setup and Manage PBB-based Tunnels with

PWE3 Mechanism

Ping Pan (Hammerhead Systems)

Shane Amante (Level 3)
Nasser El-Aawar (Level 3)

Chicago, IETF 69
 What Problem are We Trying to Solve?

Aggregator

Q-in-Q Network
Q-in-Q Network

Mac-in-Mac Network

PBB Tunnels Ethernet Circuits in

Ethernet VLAN Circuits Mac-in-Mac Encapsulation
(solid red lines) (green tubes)
(dotted red lines)

Conditions:
• All-Ethernet network How to aggregate Ethernet flows
• The access/aggregation net’s are Q-in-Q  into PBB tunnels?
• The core is PBB-based 2
 Observation
• Due to operational reasons, the carriers have a good
reason in deploying MAC-in-MAC Ethernet core
– Interconnecting Q-in-Q access networks with MAC-in-MAC core
• Due to operational reasons, MPLS LER’s may not be
desirable to be used at the edge right now
– Network operation may take a while to migrate… baby steps!
• There are ways to setup edge-to-edge tunnels
– Existing practice: static configuration
– Other proposals: dynamic signaling protocols etc.
– Outside of the scope of our proposal
• The scenario is almost identical to that PWE3 has a
solution for
– Aggregating AC’s through PSN tunnels
– Instead of PW header with label, it’s Mac-in-Mac header…

3
 What does the header look like?
Provider
Provider Backbone
Bridge (PB) Bridge (PBB)
Customer frames frame format frame format

Payload Payload Payload Payload

Ethertype Ethertype Ethertype Ethertype

C-SA C-VID C-VID C-VID C-Tag
Ethertype Ethertype Ethertype
C-DA
C-SA S-VID S-VID S-Tag
802.1 Ethertype Ethertype
C-DA
C-SA C-SA
802.1Q C-DA C-DA
802.1ad I-SID
Ethertype
Same format
C-SA = Customer Source MAC address B-VID and Ethertype
C-DA = Customer Destination MAC address Ethertype as an S-Tag
VID = VLAN ID B-SA
C-VID = Customer VID (12 bits)
S-VID = Service VID (12 bits) B-DA
I-SID = Service ID (24 bits) 802.1ah
B-VID = Backbone VID (12 bits)
B-DA = Backbone DA
B-SA = Backbone SA Mac-in-Mac Header 4
 Our Proposal

Target LDP (RFC4447)

• FEC 129
• Encode Mac-in-Mac
data in AII and AGI

Aggregator

Q-in-Q Network
Q-in-Q Network

Mac-in-Mac Network

PBB Tunnels Ethernet Circuits in

Ethernet VLAN Circuits Mac-in-Mac Encapsulation
5
 Operation Overview

Aggregator

Q-in-Q Network
Q-in-Q Network
A
B
Mac-in-Mac Network

IP-A IP-B
MAC-A MAC-B
I-SID-A I-SID-B
B-VID-A B-VID-B

1. There are PSN tunnels interconnecting node A and B

2. Operators configure IP, I-SID and B-VID etc. at edge
3. From node A, send Label Mapping message to node B with
• SAII = {MAC-A, I-SID-A, B-VID-A}
• TAII = { MAC-B, I-SID-B, B-VID-B}
4. Upon reception, run the standard RFC4447 on Node B, then A…
5. Program the data path for encapsulation and aggregation
6. Ethernet flows will go through the PBB networks 6
What to be standardized?

• New AII Type

• A new AII format

7
 In Conclusion…

• PBB is a viable option for Ethernet deployment

at core
• Aggregating Ethernet VLAN circuits over the
core is important
• PWE3 has defined a simple mechanism for data
aggregation at network edge
– “Simple” means that there is no need for extensive IP
routing etc.
• By allocating a new AII Type (and associated
format), we can achieve Ethernet circuit
aggregation over PBB networks
• Please consider this as a WG document