# IPv6 Support for Multiple Routers and Multiple Interfaces

DevFeed: [IPv6 Support for Multiple Routers and Multiple Interfaces](<https://devfeed.tech/articles/ipv6-support-for-multiple-routers-and-multiple-interfaces-11096.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/11/ipv6-multihoming-draft/>)

Published: 2024-11-28T10:57:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Networks](<https://devfeed.tech/topics/networks.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [ietf](<https://devfeed.tech/tags/ietf.md>), [internet](<https://devfeed.tech/tags/internet.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [nat](<https://devfeed.tech/tags/nat.md>), [networks](<https://devfeed.tech/tags/networks.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [tcp](<https://devfeed.tech/tags/tcp.md>)

## AI overview

The article comments on Fernando Gont's Individual Internet Draft about IPv6 support for multiple routers and interfaces. It argues that the draft clearly describes a long-standing multihoming problem and says current practical options are NAT or rarely implemented host-based solutions, while questioning whether an IETF working group will adopt the draft.

## Source excerpt

Fernando Gont published an Individual Internet Draft (meaning it hasn't been adopted by any IETF WG yet) describing the Problem Statement about IPv6 Support for Multiple Routers and Multiple Interfaces. It's so nice to see someone finally acknowledging the full scope of the problem and describing it succinctly. However, I cannot help but point out that: I was ranting about that problem in 2009 (15 years ago) and did a summary of older rants in 2015. It was evident to everyone but the religious zealots that the only solution we have at the moment is either NAT (because stuff simply does not work otherwise) or host-based solutions that never got implemented (apart from a few rare cases of multipath TCP). Anyway, Fernando wraps up his draft with: Read more ...