RFC 8475: Using Conditional Router Advertisements for Enterprise Multihoming
In plain English — editorial summary, not part of the RFC
This document discusses the most common scenarios of connecting an enterprise network to multiple ISPs using an address space assigned by an ISP and how the approach proposed in "Enterprise Multihoming using Provider-Assigned Addresses without Network Prefix Translation: Requirements and Solution" could be applied in those scenarios. The problem of enterprise multihoming without address translation of any form has not been solved yet as it requires both the network to select the correct egress ISP based on the packet source address and hosts to select the correct source address based on the desired egress ISP for that traffic. The aforementioned document proposes a solution to this problem by introducing a new routing functionality (Source Address Dependent Routing) to solve the uplink selection issue. It also proposes using Router Advertisements to influence the host source address selection. It focuses on solving the general problem and covering various complex use cases, and this document adopts its proposed approach to provide a solution for a limited number of common use cases. In particular, the focus of this document is on scenarios in which an enterprise network has two Internet uplinks used either in primary/backup mode or simultaneously and hosts in that network might not yet properly support multihoming as described in RFC 8028.
Document record
- Document ID
- RFC8475
- Published
- October 2018
- Authors
- J. Linkova; M. Stucchi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8501Reverse DNS in IPv6 for Internet Service ProvidersCurrent
November 2018
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 8683Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise NetworksCurrent
November 2019
- RFC 8161Benchmarking the Neighbor Discovery ProtocolCurrent
May 2017
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 9096Improving the Reaction of Customer Edge Routers to IPv6 Renumbering EventsCurrent
August 2021
- RFC 9099Operational Security Considerations for IPv6 NetworksCurrent
August 2021
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?