On Thu, Jun 11, 2015 at 12:35 AM, Tore Anderson <t...@fud.no> wrote: > > And that's not counting future applications that can take > > advantage of multiple IP addresses that we haven't thought of yet, and > that > > we will have if we get stuck with > > > there-are-more-IPv6-addresses-in-this-subnet-than-grains-of-sand-but-you-only-get-one-because-that's-how-we-did-it-in-IPv4 > > networks. > > Of course. Hard to argue against imaginary things. :-) >
I think "imaginary" is the wrong word here. There's a difference between imaginary things and leaving room for for future innovation. Phone network model vs. Internet model is the usual example that comes to mind. > On the other hand, there exist applications *today* that do require > DHCPv6. One such example would be MAP, which IMHO is superior to > 464XLAT both for the network operator (statlessness ftw) as well as for > the end user (unsolicited inbound packets work, no NAT traversal > required). MAP is provisioned with DHCPv6 (I-D.ietf-softwire-map-dhcp), > so without DHCPv6 support in Android, MAP support in Android is a > non-starter. > Support for the DHCPv6 protocol, or support for assigning addresses from IA_NA?