IEPL vs IPLC: the site definitions

The definitions

An international private leased circuit (IPLC) is the SDH/OTN-era private line: time-division capacity between two countries, sold at fixed rates such as E1, STM-1, STM-4 or STM-16. It behaves like a transparent pipe. The customer hands off a framed signal at each end, and the provider carries the bits without interpreting the Layer 2 protocol inside. An international Ethernet private line (IEPL) carries Ethernet frames privately instead, with a port-based service (EPL) or a VLAN-based service (EVPL) as defined in ITU-T G.8011. The customer hands off an Ethernet interface, usually 1000BASE-LX or 10GBASE-LR, and the provider forwards frames between the two sites.

The practical difference is where the provider's responsibility ends. With IPLC, the demarcation is a time-division interface and the customer's router owns everything above it. With IEPL, the demarcation is an Ethernet port and the provider is already forwarding frames, so VLAN handling, MTU and Ethernet OAM become part of the service conversation. Neither term says anything about the underlying fiber; both can run over the same optical network.

Choosing

Greenfield designs take IEPL. Ethernet is what applications and routers speak natively, the port rates scale in useful steps, and the service is easier to integrate with a modern WAN. Installed IPLC bases stay until their contracts and hardware cycles end, because replacing a working circuit has a migration cost that the acronym does not capture. The decision point is usually the contract renewal or the end of support for the SDH equipment, not a preference for newer technology. When a site already has an E1 router and a working circuit, the cheapest next step may be to keep it for another term.

Some requirements still favor a TDM handoff: an application that needs a deterministic fixed-rate pipe, an installed PBX or legacy device with an E1 interface, or a contract that specifies a traditional private line. Those are exceptions. For most data traffic between offices, plants and data centers, Ethernet is the better fit.

What the handoff looks like

At the customer end, IPLC usually arrives as an E1 (2.048 Mbps) or an STM-N interface, terminated on a router or a multiplexer. IEPL usually arrives as an Ethernet port on a switch or router, with a copper or optical interface and a defined speed. In both cases there is a demarcation point, often a network terminating unit provided by the carrier at its point of presence, and the customer is responsible for the cabling and equipment beyond it. Ask which side owns the NTU, what the connector type is, and whether a cross-connect inside the building is included.

The handoff decides more than the cable. An E1 handoff caps the circuit at 2 Mbps per port, so growth means adding ports or moving to a higher TDM rate. An Ethernet handoff can be 10 Mbps, 100 Mbps, 1 Gbps or 10 Gbps on the same fiber, which makes upgrades simpler. It also changes the failure diagnosis: with Ethernet you can test frames, VLANs and OAM; with TDM you test the framed signal and the bit errors.

Why the words matter

The two terms are often used as if they were synonyms, and that causes real procurement mistakes. A quote that says private line without saying which one can be quoted against a different handoff, a different protection level or a different port speed. A customer expecting an Ethernet port may receive an E1 interface and need a new router. A customer expecting a transparent Layer 1 pipe may receive an EVPL service that polices VLANs.

The site uses IPLC for the legacy TDM circuit and IEPL for the Ethernet service, and a quote should do the same. If a provider uses the words differently, ask for the handoff and the service definition in writing. That written definition matters more than the label. The China connectivity explainer compares private lines with transit and access, and the premium vs standard comparison covers the transit side.

Common mistakes

The first mistake is treating IEPL as an internet service. It is point-to-point capacity, not an on-ramp. The second is confusing EPL and EVPL and assuming the provider will carry any VLAN you send. The third is ignoring MTU: a circuit that passes 1500-byte frames may drop jumbo frames, and the application sees it as intermittent loss. The fourth is assuming protection is included when the quote only has a single path. The fifth is comparing a 100 Mbps committed rate with a 1 Gbps port speed. The sixth is assuming private means encrypted; if the data needs encryption, run it end to end. The seventh is forgetting the local loop, which can be the longest lead time in the order.