This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| LDP | |
|---|---|
| Name | LDP |
| Abbreviation | LDP |
| Type | Protocol |
| First | 1997 |
| Developer | Internet Engineering Task Force |
| Status | Active |
| Domain | Computer networking |
LDP
LDP is a label-distribution protocol used to establish label-switched paths across packet-switched networks. It coordinates label bindings between peers to enable traffic forwarding by label rather than by native packet header lookup, and it interoperates with protocols and systems such as Multiprotocol Label Switching, Border Gateway Protocol, Resource Reservation Protocol, Interior Gateway Protocol, and various Routing Information Protocols. LDP implementations are found in commercial and open-source platforms developed by vendors and projects including Cisco Systems, Juniper Networks, Arista Networks, Huawei, Cumulus Networks, FRRouting, Quagga, and OpenBSD.
LDP is a control-plane protocol that distributes labels used by Multiprotocol Label Switching to create label-switched paths between Label Switch Routers. It uses TCP sessions between peers and a session discovery mechanism to advertise label mappings for prefixes learned from routing protocols like Open Shortest Path First and Border Gateway Protocol. The protocol defines message types such as Notification, Label Mapping, Label Request, Label Withdraw, and Initialization; these messages are exchanged over TCP and rely on Transmission Control Protocol semantics. LDP supports both downstream unsolicited label advertisement and downstream-on-demand models, and it interacts with mechanisms like Penultimate Hop Popping and Fast Reroute.
LDP was specified in the late 1990s by working groups within the Internet Engineering Task Force as part of efforts to operationalize Multiprotocol Label Switching in carrier networks. Early experimental deployments and vendor lab work at companies such as Cisco Systems and Nortel Networks informed the draft specifications that led to standardized protocol documents. Subsequent revisions and operational experience incorporated lessons from large-scale networks operated by carriers including AT&T, Verizon, Deutsche Telekom, NTT, and research networks such as SURFnet and GÉANT. LDP evolved alongside complementary control-plane work like Label Distribution Protocol for ATM experiments and the development of Resource Reservation Protocol extensions.
There are several LDP variants and extensions standardized or implemented in practice. Basic LDP as described in core documents supports IPv4 and IPv6 via address families and interacts with Multiprotocol BGP when labels are used across administrative domains. Extensions include targeted LDP (tLDP) for non-directly connected peer signaling, LDP for downstream-on-demand behavior, and extensions for support of Label Switched Path protection and Graceful Restart procedures. Vendors have produced proprietary extensions to integrate with features like Virtual Private LAN Service and Layer 2 VPN offerings that build on LDP semantics. Alternate label-distribution approaches in the same problem space include Resource Reservation Protocol-based signaling and Border Gateway Protocol label exchange mechanisms used in some multi-domain architectures.
LDP is widely used in service provider backbones for traffic engineering, VPN services, and fast packet forwarding. Operators deploy LDP to instantiate point-to-point and point-to-multipoint Label Switched Paths that carry services such as Layer 3 VPNs, Layer 2 VPNs, and carrier-grade tunneling for mobile backhaul used by vendors serving Verizon Wireless, Vodafone, China Mobile, and T-Mobile. Data center fabrics offered by companies like Cisco Systems, Arista Networks, and Juniper Networks may use LDP for simplifying forwarding tables and accelerating convergence. Research and academic testbeds such as Internet2 and GLIF have used LDP to prototype inter-domain label operations and to compare with alternatives like Segment Routing.
LDP operates by establishing TCP sessions between LDP peers and exchanging TLV-encoded messages that carry label bindings mapped to network layer FECs learned from routing protocols such as Open Shortest Path First and Border Gateway Protocol. The protocol supports discovery via multicast or targeted sessions, label mapping and withdrawal, and a label retention mode that drives label allocation behavior. Key methodological concepts include downstream unsolicited distribution, downstream-on-demand distribution, and label merging for efficient multipoint delivery. LDP relies on routing-plane information from systems like Interior Gateway Protocol deployments to derive the topology and reachability used for label assignment; it also integrates with techniques such as Penultimate Hop Popping and Equal-Cost Multi-Path to optimize forwarding.
LDP sessions inherit transport security limitations of TCP; therefore, deployments consider authentication and integrity protections such as TCP-AO, IPsec, or control-plane filtering. Threats include session spoofing, label-hijacking, and misuse of label bindings to redirect traffic toward adversarial nodes potentially affecting large-scale providers such as CenturyLink or Orange S.A. Mitigations include strict peer ACLs on interface or VRF levels, use of IPsec tunnels between peers in hostile environments, and control-plane monitoring with tools from vendors like SolarWinds and projects like Nagios and Prometheus to detect anomalous label advertisements. Privacy concerns are limited because LDP distributes label information rather than payloads, but misconfiguration can expose topology or service mappings across peering relationships.
Multiple software and hardware implementations exist. Commercial router platforms from Cisco Systems (IOS, IOS-XR), Juniper Networks (JunOS), Huawei (VRP), and Nokia (SR OS) include production-grade LDP. Open-source implementations include FRRouting, Quagga, Bird Internet Routing Daemon, and the LDP daemon in OpenBSD, enabling lab and production use in white-box environments provided by vendors like Cumulus Networks and Mellanox Technologies. Network management and orchestration tools from Ansible, OpenDaylight, Netconf-based toolchains, and Yang models facilitate automated LDP configuration, while observability integrations into ELK Stack and Grafana support operational telemetry and troubleshooting.
Category:Internet protocols