While I believe that relying on DNS64 is not a good long-term direction,
and I’m uncertain what practical impact changing its standard status
would have, I would still support such a change given that DNS64 is
already widely used in operational networks.
Chenhao
On 2026/4/10 00:18, 【外部账号】 wrote:
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.
_______________________________________________
v6ops mailing list [email protected]
To unsubscribe send an email [email protected]
--
————————————
马晨昊/Chenhao Ma
网络技术研究所
中国电信股份有限公司研究院
13366626492/(010)50902575
[email protected]
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
