RFC 2991: Multipath Issues in Unicast and Multicast Next-Hop Selection
In plain English — editorial summary, not part of the RFC
The effect of multipath routing on a forwarder is that the forwarder potentially has several next-hops for any given destination and must use some method to choose which next-hop should be used for a given data packet. This memo summarizes current practices, problems, and solutions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2991
- Published
- November 2000
- Authors
- D. Thaler; C. Hopps
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2992Analysis of an Equal-Cost Multi-Path AlgorithmCurrent
November 2000
- RFC 9262Tree Engineering for Bit Index Explicit Replication (BIER-TE)Current
October 2022
- RFC 7325MPLS Forwarding Compliance and Performance RequirementsCurrent
August 2014
- RFC 3052Service Management Architectures Issues and ReviewCurrent
January 2001
- RFC 2901Guide to Administrative Procedures of the Internet InfrastructureCurrent
August 2000
- RFC 2859A Time Sliding Window Three Colour Marker (TSWTCM)Current
June 2000
- RFC 3167Request to Move RFC 1745 to Historic StatusCurrent
August 2001
- RFC 2682Performance Issues in VC-Merge Capable ATM LSRsCurrent
September 1999
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?