Skip to main content

Cisco Systems UniDirectional Link Detection (UDLD) Protocol
RFC 5171

Revision differences

Document history

Date Rev. By Action
2018-12-20
03 (System)
Received changes through RFC Editor sync (changed abstract to 'This document describes a Cisco Systems protocol that can be used to detect and disable unidirectional …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
03 (System) Notify list changed from foschia@cisco.com to (None)
2012-08-22
03 (System) post-migration administrative database adjustment to the No Objection position for Dan Romascanu
2008-04-24
03 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2008-04-24
03 Amy Vezza [Note]: 'RFC 5171' added by Amy Vezza
2008-04-23
03 (System) RFC published
2008-03-24
03 (System) IANA Action state changed to No IC from In Progress
2008-03-24
03 (System) IANA Action state changed to In Progress
2007-08-14
03 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2007-07-23
03 Amy Vezza IESG state changed to Approved-announcement sent
2007-07-23
03 Amy Vezza IESG has approved the document
2007-07-23
03 Amy Vezza Closed "Approve" ballot
2007-07-20
03 (System) Removed from agenda for telechat - 2007-07-19
2007-07-19
03 Amy Vezza State Changes to Approved-announcement to be sent from IESG Evaluation by Amy Vezza
2007-07-19
03 Dan Romascanu [Ballot Position Update] Position for Dan Romascanu has been changed to No Objection from Discuss by Dan Romascanu
2007-07-19
03 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded by Jari Arkko
2007-07-19
03 Chris Newman [Ballot Position Update] New position, No Objection, has been recorded by Chris Newman
2007-07-18
03 Ross Callon [Ballot Position Update] New position, No Objection, has been recorded by Ross Callon
2007-07-18
03 Yoshiko Fong
IANA Additional Comments:

Marco replied our qustion.

No, I don't wish IANA to keep track of the opcodes, flags and options
in section 6.

Thus …
IANA Additional Comments:

Marco replied our qustion.

No, I don't wish IANA to keep track of the opcodes, flags and options
in section 6.

Thus IANA has NO ACTION for this document.
2007-07-18
03 Dan Romascanu
[Ballot discuss]
This document is documenting a Ethernet OAM function that has little if nothing to do with the IETF scope. Moreover, there is at …
[Ballot discuss]
This document is documenting a Ethernet OAM function that has little if nothing to do with the IETF scope. Moreover, there is at least one standard method that I am aware about which can provide similar functionality in the Ethernet OAM developped for Ethernet First Mile, as per clause 57 of IEEE 802.3. The MIB modules that cover these functions were developped in the IETF hubmib Working Group, which is now close to being concluded. I would like to ask whether the RFC Editor is aware of these issues and if the document underwent an appropriate IEEE 802 expert review. At a least I would suggest that a mention is made in the text of the document about the existence of standards methods to detect mis-configuration of physical cabling.
2007-07-18
03 Dan Romascanu
[Ballot discuss]
This document is documenting a Ethernet OAM function that has little if nothing to do with the IETF scope. Moreover, there is at …
[Ballot discuss]
This document is documenting a Ethernet OAM function that has little if nothing to do with the IETF scope. Moreover, there is at least one standard method that I am aware about which can provide similar functionality in the Ethernet OAM developped for Ethernet First Mile, as per clause 57 of IEEE 802.3. The MIB modules that cover these functions were developped in the IETF hubmib Working Group, which is now close to being concluded. I would like to ask whether the RFC Editor is aware of these issues and if the document underwent an appropriate IEEE 802 expert review. At a least I would suggest that a mention is made in the text of the document about the existence of standards methods to detect mis-configuration of physical cabling.
2007-07-18
03 Dan Romascanu [Ballot Position Update] New position, Discuss, has been recorded by Dan Romascanu
2007-07-18
03 Cullen Jennings [Ballot Position Update] New position, No Objection, has been recorded by Cullen Jennings
2007-07-18
03 Ron Bonica [Ballot Position Update] New position, No Objection, has been recorded by Ron Bonica
2007-07-17
03 Tim Polk [Ballot Position Update] New position, No Objection, has been recorded by Tim Polk
2007-07-17
03 David Ward [Ballot Position Update] New position, No Objection, has been recorded by David Ward
2007-07-16
03 Lars Eggert [Ballot Position Update] New position, No Objection, has been recorded by Lars Eggert
2007-07-13
03 Russ Housley Ballot has been issued by Russ Housley
2007-07-13
03 Yoshiko Fong
IANA Evaluation Comments:

The document says in IANA consideration section that
it has no IANA considerations.

In the main text it defines a packet format …
IANA Evaluation Comments:

The document says in IANA consideration section that
it has no IANA considerations.

In the main text it defines a packet format and values
for that packet header some of the values are reserved.

Please confirm if you would like IANA to keep track of
these opcodes, Flags and Options, from section 6.
2007-07-09
03 Russ Housley Placed on agenda for telechat - 2007-07-19 by Russ Housley
2007-07-09
03 Russ Housley [Ballot Position Update] New position, Yes, has been recorded for Russ Housley
2007-07-09
03 Russ Housley Ballot has been issued by Russ Housley
2007-07-09
03 Russ Housley Created "Approve" ballot
2007-07-09
03 (System) Ballot writeup text was added
2007-07-09
03 (System) Last call text was added
2007-07-09
03 (System) Ballot approval text was added
2007-07-09
03 Russ Housley State Changes to IESG Evaluation from Publication Requested by Russ Housley
2007-07-09
03 Russ Housley Draft Added by Russ Housley in state Publication Requested
2007-04-09
03 (System) New version available: draft-foschiano-udld-03.txt
2006-08-28
02 (System) New version available: draft-foschiano-udld-02.txt
2006-02-14
01 (System) New version available: draft-foschiano-udld-01.txt
2005-09-26
(System) Posted related IPR disclosure: Cisco's Statement about  IPR claimed in draft-foschiano-udld-00.txt
2005-08-03
00 (System) New version available: draft-foschiano-udld-00.txt