[DNSOP] (Concluded) RE: Moving DNS64 (RFC6147) to In ternet Standard
[email protected] Fri, 24 Apr 2026 10:26:10 +0000
| Newsgroups | gmane.ietf.dnsop,gmane.ietf.v6ops |
|---|---|
| Message-ID | <PATP264MB6765DF96FD91CD7DA986159E882B2@PATP264MB6765.FRAP264.PROD.OUTLOOK.COM> |
--===============2856592920887283266== Content-Language: fr-FR Content-Type: multipart/alternative; boundary="_000_PATP264MB6765DF96FD91CD7DA986159E882B2PATP264MB6765FRAP_" --_000_PATP264MB6765DF96FD91CD7DA986159E882B2PATP264MB6765FRAP_ Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi all, Thank you all for the constructive comments and feedback. There is no consensus to proceed with an administrative status change. Ther= e are some contentious points and other aspects that are better addressed/c= larified by having a bis document. If the original authors or any other vol= unteers 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 : [email protected] <[email protected]> Envoy=E9 : jeudi 9 avril 2026 18:19 =C0 : IPv6 Operations <[email protected]>; dnsop <[email protected]>; Brian E Car= penter <[email protected]> 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 be= tween 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 i= s also widely implemented and deployed and that there is only one minor err= atum that does not impact interop [3], I think that we can proceed with a s= tatus change for RFC6147 and progress NAT64/DNS64 as a set this round as we= ll. 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 confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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 confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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. --_000_PATP264MB6765DF96FD91CD7DA986159E882B2PATP264MB6765FRAP_ Content-Type: text/html; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:11.0pt; font-family:"Aptos",sans-serif; mso-ligatures:standardcontextual; mso-fareast-language:EN-US;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#467886; text-decoration:underline;} pre {mso-style-priority:99; mso-style-link:"Pr=E9format=E9 HTML Car"; margin:0cm; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New";} span.PrformatHTMLCar {mso-style-name:"Pr=E9format=E9 HTML Car"; mso-style-priority:99; mso-style-link:"Pr=E9format=E9 HTML"; font-family:Consolas; mso-ligatures:standardcontextual; mso-fareast-language:EN-US;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Courier New"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:612.0pt 792.0pt; margin:70.85pt 70.85pt 70.85pt 70.85pt;} div.WordSection1 {page:WordSection1;} --></style> </head> <body lang=3D"FR" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:bre= ak-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= Hi all,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= <o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Thank you all for the constructive comments and feedback.<o:= p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">There is no consensus to proceed with an administrative stat= us change. There are some contentious points and other aspects that are bet= ter addressed/clarified by having a bis document. If the original authors or any other volunteers are interested in that wor= k, note that this is not covered by V6OPS charter and that work is to be br= ought to DNSOP like any other DNS-related individual contribution.<o:p></o:= p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Cheers,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Med<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm = 4.0pt"> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span style=3D"font-family:"Calibri",sa= ns-serif;mso-ligatures:none;mso-fareast-language:FR">De :</span></b><s= pan style=3D"font-family:"Calibri",sans-serif;mso-ligatures:none;= mso-fareast-language:FR"> [email protected] <mohamed.boucadai= [email protected]> <br> <b>Envoy=E9 :</b> jeudi 9 avril 2026 18:19<br> <b>=C0 :</b> IPv6 Operations <[email protected]>; dnsop <dnsop@i= etf.org>; Brian E Carpenter <[email protected]><br> <b>Objet :</b> [v6ops] Moving DNS64 (RFC6147) to Internet Standard<o:p= ></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= Hi DNSOP/V6OPS, <o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= <o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">V6OPS is in the process of progressing several widely deploy= ed IPv6-related features into Internet Standard (e.g., [1]). There is an on= going 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.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Brian raised a question about the plan for RFC 6147 [2]. Giv= en that DNS64 is also widely implemented and deployed and that there is onl= y one minor erratum that does not impact interop [3], I think that we can proceed with a status change for RFC6147 and prog= ress NAT64/DNS64 as a set this round as well.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Please share you thoughts on this plan by 23/04/2026.<o:p></= o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Cheers,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">Med<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">[1] <a href=3D"https://mailarchive.ietf.org/arch/msg/v6ops/x= 1UNhtW1qkMpBh_27a1G_4JctHU/"> https://mailarchive.ietf.org/arch/msg/v6ops/x1UNhtW1qkMpBh_27a1G_4JctHU/</a= > <o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">[2] <a href=3D"https://mailarchive.ietf.org/arch/msg/v6ops/G= 35ha3lL_tK2hSWVATiTnPXLaKc/"> https://mailarchive.ietf.org/arch/msg/v6ops/G35ha3lL_tK2hSWVATiTnPXLaKc/</a= > <o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New"">[3] <a href=3D"https://www.rfc-editor.org/errata/eid2975"> https://www.rfc-editor.org/errata/eid2975</a> <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour= ier New""><o:p> </o:p></span></p> <pre>______________________________________________________________________= ______________________________________<o:p></o:p></pre> <pre>Ce message et ses pieces jointes peuvent contenir des informations con= fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre> <pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez= recu ce message par erreur, veuillez le signaler<o:p></o:p></pre> <pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag= es electroniques etant susceptibles d'alteration,<o:p></o:p></pre> <pre>Orange decline toute responsabilite si ce message a ete altere, deform= e ou falsifie. Merci.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>This message and its attachments may contain confidential or privilege= d information that may be protected by law;<o:p></o:p></pre> <pre>they should not be distributed, used or copied without authorisation.<= o:p></o:p></pre> <pre>If you have received this email in error, please notify the sender and= delete this message and its attachments.<o:p></o:p></pre> <pre>As emails may be altered, Orange is not liable for messages that have = been modified, changed or falsified.<o:p></o:p></pre> <pre>Thank you.<o:p></o:p></pre> </div> </div> <pre>_________________<wbr>______________________________<wbr>_____________= _________________<wbr>______________________________<wbr>_ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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.</pre></body> </html> --_000_PATP264MB6765DF96FD91CD7DA986159E882B2PATP264MB6765FRAP_-- --===============2856592920887283266== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRE5TT1AgbWFp bGluZyBsaXN0IC0tIGRuc29wQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg dG8gZG5zb3AtbGVhdmVAaWV0Zi5vcmcK --===============2856592920887283266==--