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

2 What Problem are We Trying to Solve? Q-in-Q Network Mac-in-Mac Network Ethernet VLAN Circuits (solid red lines) PBB Tunnels (green tubes) Ethernet Circuits in Mac-in-Mac Encapsulation (dotted red lines) Conditions: A ll-Ethernet network The access/aggregation net’s are Q-in-Q The core is PBB-based How to aggregate Ethernet flows into PBB tunnels?  Aggregator

3 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…

4 What does the header look like? C-SA = Customer Source MAC address C-DA = Customer Destination MAC address VID = VLAN ID C-VID = Customer VID (12 bits) S-VID = Service VID (12 bits) I-SID = Service ID (24 bits) B-VID = Backbone VID (12 bits) B-DA = Backbone DA B-SA = Backbone SA C-DA C-SA Payload B-DA B-SA B-VID I-SID C-DA C-SA Payload Ethertype 802.1Q C-DA C-SA Payload C-VID Ethertype C-DA C-SA Payload S-VID C-VID Ethertype S-VID C-VID Ethertype Customer frames 802.1ad 802.1ah Provider Bridge (PB) frame format Provider Backbone Bridge (PBB) frame format Same format and Ethertype as an S-Tag S-Tag C-Tag Mac-in-Mac Header

5 Our Proposal Q-in-Q Network Mac-in-Mac Network Ethernet VLAN Circuits PBB Tunnels Ethernet Circuits in Mac-in-Mac Encapsulation Aggregator Target LDP (RFC4447) FEC 129 Encode Mac-in-Mac data in AII and AGI

6 Operation Overview Q-in-Q Network Mac-in-Mac Network Aggregator A B IP-A MAC-A I-SID-A B-VID-A IP-B MAC-B I-SID-B 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

7 What to be standardized? New AII Type A new AII format

8 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