IETF 70 Vancouver: draft-dolganow-ospf-pw3-ms-pw-ext-01 authors: Alex Zinin, Andrew Dolganow, Dimitri Papadimitriou, Matthew Bocci, Mustapha Aissaoui – Alcatel-Lucent Luca Martini – Cisco Systems Frederic Jounay – France Telecom Yuji Kamite – NTT

draft-dolganow-ospf-pw3-ms-pw-ext-01 Motivation/Problem recap: Need a method to dynamically establish MS-PW inside provider’s access, metro network MP-BGP may not be deployed due to Opex/Capex constraints Single OSPF AS in most cases Draft so far: First presented at IETF 68 in Prague Comments received and incorporated in a new version New co-authors added (Luca Martini)

draft-dolganow-ospf-pw3-ms-pw-ext-01 Changes from version 1.0 Priority given to define consensus parts required for basic functionality: Advertise AIIs required for placement of MS-PW using OSPF Router does not necessarily need to have T-LDP or Tunnel to advertise PW Switching LSA Opaque LSA mechanism used to flood the advertisements (both Area and AS scope are allowed) Pseudo Wire switching LSAs carry AIIs attached at T-PEs / routable through S-PE using Exterior AII TLV. Routers learn which AIIs to advertise through: Configuration Advertisement Interaction with exterior gateway protocols (BGP) Full alignment with Dynamic Placement of Multi Segment Pseudo Wires

draft-dolganow-ospf-pw3-ms-pw-ext-01 Area 1 S-PE C Area 10 Area 0 T-PE 2 Segment 2 Segment 1 Segment 3 S-PE B T-PE 1 S-PE A Example: Each S-PE and T-PE have their own L2 address (Global Id + prefix). T-PE1 advertises its AIIs using an Exterior AII TLV in PW switching Opaque LSA flooded as per Opaque LSA procedures S-PEs inject non-backbone AIIs into their backbone AII advertisement and vice-versa Advertisements installed and used in PW routing DB at T-PE 2, which can now place Multi-Segment Pseudo Wires to T-PE 1’s AIIs

draft-dolganow-ospf-pw3-ms-pw-ext-01 Next steps Adopt this draft as PWE3 WG draft (continue to work closely with OSPF group on any OSPF related topics) Create an ISIS version