Re: [v6ops] [*SPAM* Score/Req: 3.9/3.3] Re: [*SPAM* Score/Req: 3.9/3.3] Re: reclassify 464XLAT as standard instead of info

[Owen DeLong <[e-mail]>]

> Here, in this operations group, there is need that Android accepts these
> RFCs.

I’m not sure that we want to take on the role of RFC Enforcement Police in this group.

> And we need that before we even talk moving an Android-only CLAT from
> INFORMATIONAL to something else.

First, I don’t accept your idea that CLAT is “Android-only”. While Android may be the most prolific example of CLAT implementation, it is certainly not the only implementation, nor is there anything preventing CLAT from being deployed in other devices beyond those where it is currently implemented.

It seems clear at this point that your intent is to try and hijack this thread to apply pressure to Android developers to implement DHCPv6 on Android. Regardless of the worthiness (or not) of that goal, the simple reality is that it is a completely orthogonal issue unrelated to 464XLAT or CLAT in any meaningful way and there’s simply no validity to your argument.

Jordi, Ole, Cameron, and myself, have all made it clear to you that the claims you have made in an attempt to tie the issues together are not supported by the facts. CLAT and DHCP can co-exist on the same network. CLAT and IPv6-in-GTP can co-exist as well.

DHCP is an address and/or prefix assignment mechanism.
IPv6-in-GTP is a tunneling mechanism for moving IPv6 packets through an IPv4 mobile network.
CLAT and/or 464XLAT are an IPv6 transition mechanism allowing an IPv6-only client to connect to IPv4 servers via an IPv6-only network with appropriate PLAT support.

They are three completely separate solution spaces and all three can co-exist.

> Alex
> PS: to support the claim that Android explicitely blocks DHCPv6, I can
> provide pointers to public Google pages, numerous requests of DHCPv6
> integration in Android (to avoid need of 'rooting' the devices), the
> availability of DHCPv6 app in Android store that runs only on WiFi and
> must 'root', invitations from competitor OSs to bring DHCPv6 there
> instead of Android, and more.

We get it… Android doesn’t support DHCPv6 and you don’t like that.

However, this isn’t about Android, it’s about 464XLAT and CLAT. These are protocols, not vendors.

Take your Android issues up with the Android developers. They are unrelated to this thread.

Owen