Re: [v6ops] reclassify 464XLAT as standard instead of info

[Alexandre Petrescu <[e-mail]>]

Sounds as trying to impose 464xlat to everyone else?

My little IoT IPv6 cellular device does not run 464xlat and neither 
IPv4.  If 464xlat becomes Stds Track does it mean that it MUST run 
464xlat?  I would disagree with that.

Alex

Le 19/09/2017 à 14:23, JORDI PALET MARTINEZ a écrit :
> Hi all,
> 
> RFC6877 (464XLAT) is an informational document.
> 
> However, this transition mechanism is the one that has a bigger deployment in terms of number of subscribers using it (hundreds of millions), which I think is even more than ALL the other transition mechanism together.
> 
> Doesn’t make any sense, in my opinion to keep it as an informational document, while we have many others that are standards track and don’t have such level of deployment.
> 
> I was commenting this last week with a couple of the co-authors of this document, and they have the same opinion.
> 
> So, should we aim to do this?
> 
> Can we even consider moving it to STD?
> 
> Regards,
> Jordi
>   
> 
> 
> 
> **********************************************
> 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
>