Posted by: Margaret Rouse
|One of the earliest drivers for pseudowire standards came from the need to run virtual circuit services such as frame relay and ATM over IP.Tom Nolle, Pseudowires: Reality vs. Hype|
I need to read more about how pseudowires fit into Cisco’s AToM (Any Transport over MPLS.) Luca Martini is now an exec at Cisco. Here’s more about ”Dry Martini.”
Where the original Martini pseudowire work was intended primarily for transparent LAN services and virtual LAN services over the WAN, Dry Martini was expected to map Layer 2 services over optical wavelengths, ATM virtual circuits, Sonet cross-connects or other transport options, without requiring MPLS going out to endpoints. Ironically enough, although the work was an extension to MPLS, it eliminated the need to use Layer 3 MPLS to the client. As a result, Dry Martini became known as Transport MPLS.