Hi Brandon, This may help: https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/
It is in last call right now, I need to send a new version today/tomorrow, as the IESG review had some inputs, but nothing that change the document as you can read it now. Regards, Jordi -----Mensaje original----- De: NANOG <[email protected]> en nombre de Brandon Martin <[email protected]> Fecha: viernes, 14 de diciembre de 2018, 17:20 Para: "[email protected]" <[email protected]> Asunto: Auto-configuring IPv6 transition mechanisms on customer devices Are there any (draft, standard, or otherwise) defined mechanisms for indicating to customer-provided devices that they should configure IPv6 to IPv4 transition mechanisms such as MAP, 4rd, 464XLAT, etc. and providing the configuration details thereof? I'm not aware of any. It seems like this is something that, if defined, would make deployment of such mechanisms a lot easier even if SPs provide the customer edge router that implements said mechanisms. I guess they'd probably be implemented as extensions to DHCPv6 or similar or embedded in RAs (the latter seems ugly). -- Brandon Martin ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com 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.
