RFC 5171: Cisco Systems UniDirectional Link Detection (UDLD) Protocol
In plain English — editorial summary, not part of the RFC
This document describes a Cisco Systems protocol that can be used to detect and disable unidirectional Ethernet fiber or copper links caused, for instance, by mis-wiring of fiber strands, interface malfunctions, media converters' faults, etc. It operates at Layer 2 in conjunction with IEEE 802.3's existing Layer 1 fault detection mechanisms. This document explains the protocol objectives and applications, illustrates the specific premises the protocol was based upon, and describes the protocol architecture and related deployment issues to serve as a possible base for future standardization. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5171
- Published
- April 2008
- Authors
- M. Foschiano
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5342IANA Considerations and IETF Protocol Usage for IEEE 802 ParametersObsoleted
September 2008
- RFC 7042IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 ParametersObsoleted
October 2013
- RFC 7043Resource Records for EUI-48 and EUI-64 Addresses in the DNSCurrent
October 2013
- RFC 7448MIB Transfer from the IETF to the IEEE 802.3 WGCurrent
February 2015
- RFC 2816A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN TechnologiesCurrent
May 2000
- RFC 1390Transmission of IP and ARP over FDDI NetworksCurrent
January 1993
- RFC 9542IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 ParametersCurrent
April 2024
- RFC 4562MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access NetworkCurrent
June 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?