RFC 6438: Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels
In plain English — editorial summary, not part of the RFC
The IPv6 flow label has certain restrictions on its use. This document describes how those restrictions apply when using the flow label for load balancing by equal cost multipath routing and for link aggregation, particularly for IP-in-IPv6 tunneled traffic. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6438
- Published
- November 2011
- Authors
- B. Carpenter; S. Amante
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6436Rationale for Update to the IPv6 Flow Label SpecificationCurrent
November 2011
- RFC 7098Using the IPv6 Flow Label for Load Balancing in Server FarmsCurrent
January 2014
- RFC 6790The Use of Entropy Labels in MPLS ForwardingUpdated
November 2012
- RFC 7190Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)Current
March 2014
- RFC 7226Requirements for Advanced Multipath in MPLS NetworksCurrent
May 2014
- RFC 7325MPLS Forwarding Compliance and Performance RequirementsCurrent
August 2014
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 7938Use of BGP for Routing in Large-Scale Data CentersCurrent
August 2016
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?