Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions
RFC 8678, “Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions”, is an Informational document published in December 2019 by F. Baker, C. Bowers, J. Linkova. The canonical text is published by the RFC Editor.
Abstract
Connecting an enterprise site to multiple ISPs over IPv6 using provider-assigned addresses is difficult without the use of some form of Network Address Translation (NAT). Much has been written on this topic over the last 10 to 15 years, but it still remains a problem without a clearly defined or widely implemented solution. Any multihoming solution without NAT requires hosts at the site to have addresses from each ISP and to select the egress ISP by selecting a source address for outgoing packets. It also requires routers at the site to take into account those source addresses when forwarding packets out towards the ISPs.
This document examines currently available mechanisms for providing a solution to this problem for a broad range of enterprise topologies. It covers the behavior of routers to forward traffic by taking into account source address, and it covers the behavior of hosts to select appropriate default source addresses. It also covers any possible role that routers might play in providing information to hosts to help them select appropriate source addresses. In the process of exploring potential solutions, this document also makes explicit requirements for how the solution would be expected to behave from the perspective of an enterprise site network administrator.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8678 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8677 Name-Based Service Function Forwarder Component within a Service Function Chaining Framework
- RFC 8679 MPLS Egress Protection Framework
- RFC 8676 YANG Modules for IPv4-in-IPv6 Address plus Port Softwires
- RFC 8675 A YANG Data Model for Tunnel Interface Types
- RFC 8674 The "safe" HTTP Preference
- RFC 8673 HTTP Random Access and Live Content
- RFC 8683 Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks
- RFC 8672 TLS Server Identity Pinning with Tickets