1. Introduction

A single fiber pair between two metro sites can carry a hyperscaler's data-center-interconnect traffic, a mobile operator's 5G backhaul, a bank's low-latency trading circuit, and a utility's control channel at the same time. Historically those tenants were separated by buying more fiber, more wavelengths, or more transponder shelves. Optical network slicing replaces that capital-heavy separation with a software construct: a set of network resources carved out of a shared optical substrate, bound to one customer or service, and held to explicit performance commitments. The slice looks and behaves like a private network to its tenant while riding the same amplifiers, wavelength-selective switches, and fibers as every other slice.

The term arrived in transport from the mobile world. The Internet Engineering Task Force gave it a formal frame in RFC 9543, A Framework for Network Slices in Networks Built from IETF Technologies (standard-specified, March 2024), which defines a network slice as connectivity between endpoints delivered with specific Service Level Objectives (SLOs) and Service Level Expectations (SLEs) over a common underlay. That definition is technology-agnostic on purpose. It is realized differently at each layer: as a VPN and queue policy in IP/MPLS, as a container in Optical Transport Network (OTN), and as a block of spectrum on a flexible-grid line system. This article is about the last two of those, the transport layers that a packet slice finally rides on, and about the seam where a 5G slice's latency and isolation promise becomes a real allocation of wavelengths, time slots, and switch ports.

Three things make optical slicing a 2026 topic rather than a research curiosity. The flexible grid standardized in ITU-T G.694.1 turned fixed 50 GHz lanes into arbitrary-width spectrum blocks that can be handed out per tenant. Coherent digital signal processing made each of those blocks independently measurable and tunable, so a slice's health can be observed without demultiplexing the whole comb. And the control plane matured: RFC 9543's Network Resource Partition, the CCAMP working group's OTN-slicing YANG model (a standards-track draft that expires in September 2026), and SDN controllers with path-computation engines now let an operator request a slice through a northbound interface and have it instantiated across the optical domain without touching a single patch panel. The rest of this deep dive works through the definition, the spectrum mechanics, the isolation taxonomy, the control plane, the 5G SLA mapping, the math, and the hardware, and ends where every honest slicing discussion ends: the trade-off between how strongly you isolate a slice and how much of the fiber you waste doing it.

2. What an Optical Slice Actually Is

Start with the object, not the abstraction. An optical slice is a bounded set of physical-layer resources reserved for a tenant: some spectrum, on some set of fibers, through some sequence of ROADM degrees, carried in some set of OTN containers, with a control-plane identity that ties them together and a performance contract attached. Strip away any one of those and it stops being a slice and becomes something weaker, a wavelength service, a leased lambda, a best-effort VPN.

RFC 9543 gives the abstraction a clean vocabulary that transport engineers should adopt because it removes ambiguity across layers. The customer buys an IETF Network Slice Service, expressed as connectivity between Service Demarcation Points (SDPs) with SLOs and SLEs. The provider realizes it inside the network as an IETF Network Slice, and the pool of underlay resources allocated to carry that slice's traffic is the Network Resource Partition (NRP). The NRP is the concept that maps most directly onto optics: it is the spectrum, the time slots, the buffer share, the wavelengths that belong to this slice and no other. A slice can be sliced again, hierarchically, and slices from different domains can be stitched end to end, which is exactly what a 5G end-to-end slice does when it crosses the Radio Access Network, the Transport Network, and the Core Network.

2.1 The three planes a slice touches

An optical slice is defined simultaneously in three planes, and confusion usually comes from collapsing them. In the data plane, the slice is the actual signal energy: a frequency slot on the fiber, or an ODU container in a time-division multiplex, carrying the tenant's bits. In the control plane, the slice is a set of forwarding and switching states with a slice identifier, computed and installed by GMPLS signaling or an SDN controller. In the management plane, the slice is a lifecycle object with a service model, an SLA, telemetry streams, and a northbound handle the tenant or an orchestrator can call. A well-built slice keeps these three consistent: the identifier in the control plane maps to the spectrum in the data plane and to the SLA object in the management plane, so a fault on one is observable on the others.

2.2 Why the optical layer is where isolation gets real

Packet-layer slicing can promise isolation, but it delivers it statistically, through queues, policers, and resource-partition markings that hold only as long as the scheduler behaves and the links are not oversubscribed past their design point. The optical layer can offer something packet layers cannot: a slice whose resources are physically disjoint from every other slice's, where one tenant's congestion, misconfiguration, or attack has no path to another tenant's signal. That is the property enterprises pay for and regulators sometimes mandate, and it is why the transport layers sit at the bottom of every serious end-to-end slice. For the packet side of the same story, the walkthrough on IP over DWDM architecture shows how a coherent router hands its wavelength to the very line system that a slice partitions.