Subject: [Softwires] no need to update RFC8026 in draft-ietf-v6ops-transition-ipv4aas

From: JORDI PALET MARTINEZ <[email-masked]>
Date: Thu, 14 Jun 2018 18:21:43 +0200

Hi all,

After a long chat with the authors of RFC8026, we have found an alternative solution which avoids updating RFC8026 and also avoids requiring a new option code for 464XLAT, as there is already one that we can use, which is related to NAT64, so still can use RFC8026 for our original intend of prioritizing and managing the available mechanism from the operator network.

Consequently, we are working in a new version of draft-ietf-v6ops-transition-ipv4aas, which will be posted ASAP in v6ops.

Anyway, we had lot of fun in v6ops because this, and I think every comment has been very useful!

Thanks!

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.