IPv6 Host-to-Router Load Sharing (RFC4311)
Original Publication Date: 2005-Nov-01
Included in the Prior Art Database: 2005-Dec-01
Internet Society Requests For Comment (RFCs)
R. Hinden: AUTHOR [+2]
The original IPv6 conceptual sending algorithm does not do load sharing among equivalent IPv6 routers, and suggests schemes that can be problematic in practice. This document updates the conceptual sending algorithm in RFC 2461 so that traffic to different destinations can be distributed among routers in an efficient fashion.
Network Working Group R.
Request for Comments: 4311 Nokia
Updates: 2461 D. Thaler
Category: Standards Track Microsoft
IPv6 Host-to-Router Load Sharing
Status of This Memo
specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2005).
IPv6 conceptual sending algorithm does not do load
sharing among equivalent IPv6 routers, and suggests schemes that can
be problematic in practice. This document updates the conceptual
sending algorithm in RFC 2461 so that traffic to different
destinations can be distributed among routers in an efficient
conceptual sending algorithm in [ND] and in the optional
extension in [ROUTERSEL], a next hop is chosen when no destination
cache entry exists for an off-link destination or when communication
through an existing router is failing. Normally, a router is
selected the first time traffic is sent to a specific destination IP
address. Subsequent traffic to the same destination address
continues to use the same router unless there is some reason to
change to a different router (e.g., a redirect message is received,
or the router is found to be unreachable).
In addition, as
described in [ADDRSEL], the choice of next hop may
also affect the choice of source address, and hence indirectly (and
to a lesser extent) may affect the router used for inbound traffic as
Hinden & Thaler Standards Track [Page 1]
RFC 4311 IPv6 Host-to-Router Load Sharing November 2005
In both the base sending algorithm and in the optional extension,
sometimes a host has a choice of multiple equivalent routers for a
destination. That is, all other factors are equal and a host must
break a tie via some implementation-specific means.
It is often
desirable when there is more than one equivalent router
that hosts distribute their outgoing traffic among these routers.
This shares the load among multiple...