In order to support increasing data traffic levels, equipment developers must build systems that map Ethernet packets over Sonet/SDH links. In this two-part series we'll lay out the encapsulation techniques required to make Ethernet-over-Sonet come to life.
Today's incumbent service providers are seeking to accommodate increasing demands for bandwidth, security and service level management resulting from the proliferation of LAN-based applications. According to RHK, 2.4 million metro Ethernet ports distributed among 10/100/1000 Mbps rates are expected to be deployed by 2006. These Ethernet ports will primarily be used to support these emerging applications: • Broadband Internet access for e-mail and web-based content • Packet-based video conferencing • Tunneled virtual private networks (VPNs) • E-commerce hosting for outsourced applications services such as customer relationship management (CRM)
Storage area networking (SAN) for outsourced access/management of server content including disaster recovery services
The big issue carriers face is how to handle Ethernet traffic. Depending on the cost, distance, bandwidth, and traffic management requirements of the WAN/MAN application, several metro approaches may be used to transport Ethernet data traffic. These include direct mapping of Ethernet over wavelengths (EoW), Ethernet over Sonet/SDH (EoS), optical Ethernet (i.e. native Ethernet over fiber for long haul, 1000BaseLX), or implementing an Ethernet in the first mile (EFM) solution over copper or fiber. Of all these solutions, EoS is the one gaining the most ground with today's developers.
In this two-part series, we'll lay out some of the key requirements for mapping Ethernet frames over Sonet/SDH links. In part 1, we'll look at the advantages EoS brings to an equipment designer. We'll also begin a discussion on encapsulation techniques, looking at virtual concatenation and the link capacity adjustment scheme