Feature request: ND Proxy (RFC 4389)

When a host has more than one address, to my knowledge, most hosts that have a direct presence/address-assignment within the same prefix as the destination they are trying to reach will properly source from the address they possess within that same subnet/prefix. So, trying to talk to link-local will result in your host sourcing from its link-local. If all of your LAN hosts in the same broadcast domain / VLAN have ULA from the same prefix, they’ll all source from their ULA address when talking to somebody else on the LAN at its ULA address. Et cetera.

The ambiguity with sourcing when a host has multiple addresses tends to arise when something between your host and the destination has to gateway your traffic. For most residential/SMB network, this is not going to be an issue. I could see how this could get sticky, though, for larger LANs with multiple segments or VLANs.

The other thing that occurs to me about this whole topic is that, even if the whole “graceful prefix transition” bit of IPv6 could actually be depended upon for most changes, it still isn’t really that helpful. What if you are in the middle of a transfer of an extremely large file that is going to take multiple hours to complete? It is no comfort that you have, say, a 2-hour grace period before you have to vacate the old prefix if you still have 8 hours remaining on this transmission. And that doesn’t change regardless of whether that transfer is between you and another host on the internet, or between two hosts on your LAN. So, another argument in favor of not relying on GUAs (at least PA ones) for intra-LAN comms…


That’s a tangentially-related-but-different subject. (Though not one that is any less important, to be sure.) We were talking about source address selection, but you suddenly shifted gears to destination address selection, which also includes the additional spin of protocol selection if you are in a dual-stacked environment. The whole matter of which destination address to use can only come into play if the host making the connection even knows that there are multiple possibilities in the first place, which in turn implies some sort of directory lookup / abstraction system (DNS) that is being used which can inform the host about those different options. So we are suddenly talking about a lot of different things!

The context up to this point also (at least as I took it) included the implication that whatever hypothetical intra-LAN session we are talking about is explicitly an IPv6 exchange. If it is explicitly IPv6, then how certain IPv6 prefix classes are prioritized relative to other IPv4 prefix classes when a host is trying to choose what destination to talk to doesn’t factor in…that decision already got made a long time ago (either someone typed in a raw address, which locks the protocol in, or the protocol choice got made when the answer to the DNS query was returned). On the sourcing side, it’s kind of a non-sequitur to talk about…you could theoretically have one host with multiple IPv6 addresses source its traffic from any of them when talking to another IPv6 host, but a dual-stacked host is obviously not going to source from any of its IPv4 addresses when trying to talk IPv6 to another host.


Sounds like you’re saying they want to have it both ways: it’s “their problem” (or at least they consider it “their business”) that your network only work the One True Way™, but not “their problem” that their product becomes useless on anybody’s networks who won’t comply with their demands. Got it.

I don’t think the Android guys are coming at this from a position of strength here, myself. IT departments typically have a lot of say in what devices can or cannot be used on the networks they support. On top of that, when it comes to mobile platforms, Apple (as much as it pains me) IS in a position of strength and are much harder for IT to say “no” to, due especially to their popularity in the C-suite. So if iPhone has DHCPv6 support, Android doesn’t, IT isn’t going to budge on their position that it’s DHCPv6 or take a hike, and everybody at the company wants corporate to issue iPhones ANYWAY…

…then it sounds like Android deployments at corporations and universities are going to be few and far between. And if Android doesn’t work well on their network, that’s “not their problem” & door’s to the left. Cuts both ways.


I…have no idea what you’re talking about here? Now you’ve completely lost me.