[DNSOP] Re: (Concluded) RE: Moving DNS64 (RFC6147) to Internet Standard

[Philipp Tiesel <[e-mail]>]

Hi Jordi,

We might take that chance to include a proper description of local synthesis into the -bis
As it is mostly the same algorithm ad DNS64 without the undesired side effects. 
That way, we get a proper reference for Happy Eyeballs instead writing “similar to bump in the stack”.

Happy to contribute text if there is something to merge it into.

AVE!
   Philipp

> On 24. Apr 2026, at 12:44, [e-mail] <jordi.palet=[e-mail]> wrote:
> 
> Hi Med,
> 
> We are already working in an update of the -bis that we have prepared, having in mind the recent discussions.
> 
> Regards,
> Jordi
> 
> @jordipalet
> 
> 
>> El 24 abr 2026, a las 12:26, [e-mail] escribió:
>> 
>> Hi all,
>>  
>> Thank you all for the constructive comments and feedback.
>>  
>> There is no consensus to proceed with an administrative status change. There are some contentious points and other aspects that are better addressed/clarified by having a bis document. If the original authors or any other volunteers are interested in that work, note that this is not covered by V6OPS charter and that work is to be brought to DNSOP like any other DNS-related individual contribution.
>>  
>> Cheers,
>> Med
>>  
>> De : [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>
>> Envoyé : jeudi 9 avril 2026 18:19
>> À : IPv6 Operations <[e-mail] <mailto:[e-mail]>>; dnsop <[e-mail] <mailto:[e-mail]>>; Brian E Carpenter <[e-mail] <mailto:[e-mail]>>
>> Objet : [v6ops] Moving DNS64 (RFC6147) to Internet Standard
>>  
>> Hi DNSOP/V6OPS, 
>>  
>> V6OPS is in the process of progressing several widely deployed IPv6-related features into Internet Standard (e.g., [1]). There is an ongoing WGLC for NAT64 (RFC6146) to move it to IS. Although there is no strong dependency between NAT64 and DNS64 (RFC6147), DNS64 is usually deployed in networks that host NAT64.
>>  
>> Brian raised a question about the plan for RFC 6147 [2]. Given that DNS64 is also widely implemented and deployed and that there is only one minor erratum that does not impact interop [3], I think that we can proceed with a status change for RFC6147 and progress NAT64/DNS64 as a set this round as well.
>>  
>> Please share you thoughts on this plan by 23/04/2026.
>>  
>> Cheers,
>> Med
>>  
>> [1] https://mailarchive.ietf.org/arch/msg/v6ops/x1UNhtW1qkMpBh_27a1G_4JctHU/
>>  
>> [2] https://mailarchive.ietf.org/arch/msg/v6ops/G35ha3lL_tK2hSWVATiTnPXLaKc/
>>  
>> [3] https://www.rfc-editor.org/errata/eid2975
>>  
>> ____________________________________________________________________________________________________________
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>  
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>> ____________________________________________________________________________________________________________
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>> 
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>> _______________________________________________
>> DNSOP mailing list -- [e-mail] <mailto:[e-mail]>
>> To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
> 
> **********************************************
> 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.
> 
> _______________________________________________
> DNSOP mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]