Carrier Ethernet

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Carrier Ethernet is a marketing term for extensions to Ethernet to enable telecommunications network providers ("common carriers" in US industry jargon) to provide Ethernet services to customers and to utilize Ethernet technology in their networks.

Background[edit]

Ethernet has a long history. It has become dominant in enterprise networks. This dominance has led to high production-volume components, which in turn have allowed extremely low cost per bit. Likewise Ethernet has a long history of re-inventing itself. From the original copper coaxial cable format ("thicknet") it has extended its scope to nearly all copper, optical fiber and wireless physical media. Bit rates have continued to increase, traditionally growing tenfold each time a new rate is defined. Gigabit Ethernet interfaces are widely deployed in PCs and servers, and 10 Gbit/s in local area network (LAN) backbones. Rates up to 100 Gigabit Ethernet were standardized in 2010 and 2011.[1][2][3]

Ethernet's dominance is partly attributed to the simple advantages for the industry of adopting a single standard to drive up volumes and drive down prices. In part, it is also due to ease of deployment, using its ability to self-configure based on the key concepts of “learning bridge” (flooding, and associating learned destination addresses with bridge ports) and "spanning tree protocol" (the protocol used for avoiding bridging loops).

Historically, competing protocols and cabling have been created in order to access higher speed devices than contemporary Ethernet-connected devices handled at an affordable price. Examples include FireWire and Light Peak. One motive to create competing standards has been to drive down the price of comparable-speed Ethernet devices. Once this purpose is achieved, competing standards tend to disappear or be confined to very specialized niches.

Ethernet is a fairly simple protocol which has scaled to hundreds of thousands of times faster speeds and consistently been able to adapt to meet the needs and demands of new markets. For example, time domain capabilities are being added to IEEE 802.3 Ethernet to support IEEE 802.1 Audio Video Bridging (AVB),[4] and these capabilities will be applicable to time sensitive carrier applications likewise IEEE 1588.

Customer LAN networks are increasingly connected to wide-area telecommunications networks over Ethernet interfaces or to devices that bridge digital subscriber line (DSL) or wireless to these. Moreover, customers are familiar with the capabilities of Ethernet networks, and would like to extend these capabilities to multi-site networks. Meanwhile the needs of such networks have expanded to include many services previously handled only on the LAN or by specialized connections, notably video and backup. It is not practical to expand most small networks beyond 1G or at most 2G (dual teaming gigabit) capacity per segment, since the bottleneck remains in the wide area links to other offices and online services.

Carrier constraints[edit]

Thus wide area network (WAN) and metropolitan area network (MAN) providers find themselves with three needs:

  1. To provide their customers with Ethernet services
  2. To make use of the volume and cost advantages of Ethernet technologies in their networks
  3. To replace non-Ethernet technologies with Ethernet competitors that have sufficient capacity for storage, backup and HD video and guarantee features (transfer certainty, low latency) needed to support these services

They are also constrained as services cannot be migrated from local to wide area services too fast lest they exceed the total provisioning available and result in unacceptable quality. Services that try to expand too fast lose money while those that wait too long lose customers. Accordingly carriers must expand their services conservatively and pay close attention to Quality of Service (QoS).

The Beginning: Metro Ethernet[edit]

The Metro Ethernet Forum (MEF)[1] was formed in 2001 in order to develop ubiquitous business services for Enterprise users principally accessed over optical metropolitan networks in order to connect their Enterprise LANs. The principal concept was to bring the simplicity and cost model of Ethernet to the wide area network.[5]

Expansion to Carrier Ethernet[edit]

The success of Metro Ethernet Services caught the imagination of the world when the concept expanded to include worldwide services traversing national and global networks:[5]

  • Access networks to provide availability to a much wider class of user over fiber, copper, cable, passive optical network (PON), and wireless
  • Economy of scale from the resulting converged business, residential and wireless networks sharing the same infrastructure and services
  • Scalability & rapid deployment of business applications
  • Adoption of the certification program
  • All while retaining the cost model and simplicity of Ethernet

Carrier Ethernet services[edit]

To create a market in Ethernet services, it is necessary to clarify and standardise the services to be provided. Recognising this, the industry created the Metro Ethernet Forum. This played a key role in defining:

  • E-Line: a service connecting two customer Ethernet ports over a WAN.
  • E-LAN: a multipoint service connecting a set of customer endpoints, giving the appearance to the customer of a bridged Ethernet network connecting the sites.
  • E-Tree: a multipoint service connecting one or more roots and a set of leaves, but preventing inter-leaf communication.

All these services provide standard definitions of such characteristics as bandwidth, resilience and service multiplexing, allowing customers to compare service offerings and facilitating service level agreements (SLAs). Analogous definitions for wireless networks are defined in IEEE 802.21 and IEEE 802.11u, though these are intended for much shorter time commitments and services appropriate for mobile users only.

Transport of Ethernet services[edit]

The Metro Ethernet Forum does not specify how Ethernet services are to be provided in a carrier network. Despite the advantages described above, Ethernet has traditionally had a number of limitations in the WAN application. The "bridge" and "spanning tree" concepts described above do not scale to large international networks. Moreover, Ethernet has lacked some of the dependability features necessary in this application (in particular, mechanisms to isolate one customer's traffic from another, to measure performance of a customer service instance, and to rapidly detect and repair failures in large networks).[citation needed] Because of these limitations, and because of the need to make use of pre-existing equipment, Ethernet services have been carried across wide area networks using other technologies. Two types of technology have been widely used, while a third (Carrier-Ethernet transport) is rapidly emerging as a viable and logical option for Carrier-Ethernet services.

Ethernet over SDH/SONET[edit]

Point-to-point Ethernet links are carried over SDH/SONET networks, making use of virtual concatenation (ITU-T G.707) and LCAS (Link Capacity Adjustment Scheme - ITU-T G.7042) to create an appropriate size carrier bundle, of the Generic Framing Procedure of SDH equipment, and takes advantage of the management and recovery features of SDH to provide high availability and resilience to failures.

Ethernet over MPLS[edit]

Ethernet services are carried over IP/MPLS networks making use of a wide range of IP-related protocols (see IETF pseudowire standards, e.g. RFC 3985, RFC 4448). Ethernet links are transported as “pseudowires” using MPLS label switched paths (LSPs) inside an outer MPLS “tunnel”. This strategy can support both point-to-point (Virtual Private Wire Service - VPWS) and multipoint (Virtual Private LAN service - VPLS) services, and has recently achieved significant deployment in routed networks. It makes use of a number of basic transport protocols, including SDH and (increasingly) Ethernet.

Ethernet over Carrier-Ethernet Transport (CET)[edit]

Proponents of Carrier-Class Ethernet argue Ethernet is the best for Metro Area Networks because all data traffic originates as Ethernet. Ethernet’s ubiquitous presence in the LANs worldwide drives down the cost of Ethernet as a technology. Thus, the use of Ethernet in a metro network allows service providers to take advantage of volumes that a much larger enterprise segment commands. Carrier-Ethernet Transport (CET) usually involves an evolution of conventional Ethernet and comprises multiple technology components. Provider Backbone Bridges (PBB) provides the scalability and a secure demarcation, while Provider Backbone Bridge Traffic Engineering (PBB-TE, commonly called PBT) provides for traffic-engineering and an effective transport for protected Ethernet services. Connectivity-Fault Management (CFM-OAM) provides the much-required OAM that makes Ethernet carrier grade.

Carrier Ethernet demarcation[edit]

Carrier Ethernet demarcation is a key element in Carrier Ethernet services and transport networks for business, wholesale and mobile backhaul applications, as it enables service providers to extend their control over the entire service path, starting from the hand off points. This is achieved by connecting customer premises equipment (CPE) to the network with provider-owned demarcation devices that are deployed at customer locations, thereby enabling a clear separation between the user and provider networks.

Carrier Ethernet demarcation devices are required to support services, such as Ethernet Private Line (EPL), Ethernet Virtual Private Line (EVPL or E-LAN), and Ethernet Virtual Private Tree (E-Tree), as specified by the MEF (Metro Ethernet Forum). Such support needs to include service level agreement (SLA) management capabilities, with consistent performance over fiber, DSL, bonded PDH, and SDH/SONET access lines. As a result, must-have Carrier Ethernet demarcation features include sophisticated traffic management and hierarchical quality of service (QoS) mechanisms, standard end-to-end operations, administration and maintenance (OAM) and performance monitoring, extensive fault management and diagnostics, and SDH/SONET-like resiliency to reduce service provider operating costs and capital expenses.[6]

Carrier Ethernet technologies[edit]

The industry has made a concerted effort to resolve the limitations of Ethernet in the WAN described above, so as to allow the use of "native" Ethernet technologies by network providers.[citation needed] The key roles have been played by the Institute of Electrical and Electronic Engineers (IEEE) 802.1 and 802.3 standards committees. IEEE 802.1 has addressed the scalability and management issues in the standards for Provider Bridges (802.1ad) and Provider Backbone Bridges (802.1ah). These standards allow for Ethernet networks of planetary scale.[citation needed] Associated standards (IEEE 802.1ag, and related ITU-T standard Y.1731) provide Operations and Maintenance (OAM) capabilities allowing connectivity verification, rapid recovery, and performance measurement. Current work on PBB-TE (802.1Qay: Provider Backbone Bridging-Traffic Engineering) is allowing such an Ethernet to be controlled by an external control or management application (for example, a network management application or a transport control plane such as GMPLS (IETF RFC 3945)), so as to allow the full range of traffic engineering policies and strategies to a network provider.[citation needed]

The IEEE 802.3 Working Group in close cooperation with the ITU have been working to simplify the transport of 40G and 100G technologies being developed by both bodies: 802.3 for LAN and ITU for the OTN. The OIF and the Ethernet Alliance have also been working cooperatively with their members to enable future enhancements to Ethernet for the WAN while looking to the future speed of Ethernet technologies and services.

See also[edit]

References[edit]

  1. ^ "IEEE P802.3ba 40Gb/s and 100Gb/s Ethernet Task Force". official web site. IEEE 802. June 19, 2010. Retrieved August 6, 2011. 
  2. ^ IEEE P802.3ba 40Gb/s and 100Gb/s Ethernet Task Force : http://ieee802.org/3/ba/
  3. ^ IEEE P802.3bg 40G SMF PMD for Carrier Client Task Force : http://www.ieee802.org/3/40GSMF/
  4. ^ IEEE 802.1 Audio/Video Bridging
  5. ^ a b "Metro Ethernet Forum". MEF. Retrieved 30 May 2011. 
  6. ^ "Carrier Ethernet and CE 2.0 | CE-Services". 

External links[edit]