RFC 8611: Label Switched Path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) Interfaces
In plain English — editorial summary, not part of the RFC
This document defines extensions to the MPLS Label Switched Path (LSP) Ping and Traceroute mechanisms as specified in RFC 8029. The extensions allow the MPLS LSP Ping and Traceroute mechanisms to discover and exercise specific paths of Layer 2 (L2) Equal-Cost Multipath (ECMP) over Link Aggregation Group (LAG) interfaces. Additionally, a mechanism is defined to enable the determination of the capabilities supported by a Label Switching Router (LSR). This document updates RFC 8029.
Document record
- Document ID
- RFC8611
- Published
- June 2019
- Authors
- N. Akiya; G. Swallow; S. Litkowski; B. Decraene; J. Drake; M. Chen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 29
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8287Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data PlanesUpdated
December 2017
- RFC 8012Label Switched Path (LSP) and Pseudowire (PW) Ping/Trace over MPLS Networks Using Entropy Labels (ELs)Current
November 2016
- RFC 7737Label Switched Path (LSP) Ping and Traceroute Reply Mode SimplificationCurrent
January 2016
- RFC 8595An MPLS-Based Forwarding Plane for Service Function ChainingCurrent
June 2019
- RFC 8665OSPF Extensions for Segment RoutingCurrent
December 2019
- RFC 8666OSPFv3 Extensions for Segment RoutingCurrent
December 2019
- RFC 8667IS-IS Extensions for Segment RoutingCurrent
December 2019
- RFC 8669Segment Routing Prefix Segment Identifier Extensions for BGPCurrent
December 2019
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?