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

[JORDI PALET MARTINEZ <[e-mail]>]

Why you try to mix things?

CLAT is a transition mechanism. SLAAC or DHCPv6 (-PD) is a way to provision addresses/prefixes.

No sense to mix all them.

Many other transition mechanisms don’t state if SLAAC or DHCPv6 is used or not, and I think is perfectly correct.

Regarsd,
Jordi
 

-----Mensaje original-----
De: v6ops <[e-mail]> en nombre de Alexandre Petrescu <[e-mail]>
Responder a: <[e-mail]>
Fecha: miércoles, 20 de septiembre de 2017, 10:28
Para: <[e-mail]>
Asunto: Re: [v6ops] [*SPAM* Score/Req: 3.9/3.3] Re: reclassify 464XLAT as standard instead of info

    
    
    Le 20/09/2017 à 15:19, JORDI PALET MARTINEZ a écrit :
    > Google is your friend:
    > 
    > https://android.googlesource.com/platform/external/android-clat/
    
    Google is my friend.
    
    Ctrl-F also, and that page does not seem to display any correction that 
    says "DHCP" in the last 3 and a half years.
    
    But I think CLAT should run DHCP somehow, otherwise it's a non standard 
    way to get Prefix Delegation.  Does it?  (I may download it later and 
    look at it).
    
    As long as these two things stay distinct they are in competition.
    
    Once you make 464XLAT StdsTrack you cant also keep DHCPv6-PD as 
    StdsTrack - they are on the same layer.
    
    But yes, you can keep XMPP on the StdsTrack, because it's on another layer.
    
    Alex
    
    > 
    > Same for other questions that you asked before … you can find it also for OpenWRT.
    > 
    > Regards,
    > Jordi
    >   
    > 
    > -----Mensaje original-----
    > De: v6ops <[e-mail]> en nombre de Alexandre Petrescu <[e-mail]>
    > Responder a: <[e-mail]>
    > Fecha: miércoles, 20 de septiembre de 2017, 9:55
    > Para: Erik Kline <[e-mail]>
    > CC: "[e-mail]" <[e-mail]>
    > Asunto: Re: [v6ops] reclassify 464XLAT as standard instead of info
    > 
    >      No need to stress terms like billions; that's what modem manufacturers
    >      put on the market too routinely.  Maybe we can talk trillions of IoT
    >      devices.  Maybe we can use the SI prefixes, like exa, or peta.
    >      
    >      That aside, I would like to ask you whether the CLAT src on Android is
    >      something I could look at?
    >      
    >      Alex
    >      
    >      Le 20/09/2017 à 08:03, Erik Kline a écrit :
    >      > There seem to be some misconceptions flying around here.
    >      >
    >      >> Well, I dont think 464XLAT is deployed anywhere else than on cellular. These
    >      >> are the big numbers that the Original Poster talked about: miliions of users
    >      >> - they are on cellular.
    >      >
    >      > 464xlat is a client-side bit of code (the NAT64+DNS64 in the network
    >      > is the "other half").  It is primarily implemented in mobile devices,
    >      > and primarily in Android, to be more specific.
    >      >
    >      > As such, the number of 464xlat capable nodes is numbered in the /billions/.
    >      >
    >      > There are also some wifi (and wired) networks that are IPv6-only with
    >      > NAT64+DNS64; mobile networks aren't the only ones.
    >      >
    >      > NAT64+DNS64 is easily the single most successful IPv6 transition
    >      > technology on the planet ([a] if one excludes "dualstack", [b] queue
    >      > the Sean Spicer jokes).  464xlat can help ease things on the client
    >      > side, but it's not the only way to do it (cf. iOS).
    >      >
    >      
    >      _______________________________________________
    >      v6ops mailing list
    >      [e-mail]
    >      https://www.ietf.org/mailman/listinfo/v6ops
    >      
    > 
    > 
    > 
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    > 
    > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
    > 
    > 
    > 
    > _______________________________________________
    > v6ops mailing list
    > [e-mail]
    > https://www.ietf.org/mailman/listinfo/v6ops
    > 
    
    _______________________________________________
    v6ops mailing list
    [e-mail]
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.