| Newsgroups |
gmane.ietf.apps-discuss,gmane.ietf.v6ops |
| Message-ID |
<[email protected]> |
--===============5684357807284632303==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_68D568AE-7F89-43DC-93AF-C569FE6A2315"
--Apple-Mail=_68D568AE-7F89-43DC-93AF-C569FE6A2315
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
Hi John,
There are many deployments choices for NAT64 and DNS64. I=E2=80=99ve depict=
ed them in https://datatracker.ietf.org/doc/rfc8683/.
Basically, yes both the DNS64 and the NAT64 should be able to be reachable =
from the IPv6-only network and (typically) in a different interface to the =
IPv4-only.
The one you=E2=80=99re suggesting is very close to the one I=E2=80=99ve pre=
pared, however Med suggested avoiding such changes as it was well understoo=
d in the original RFC6146:
+--------------+ +--------------+
| IPv6-only | | IPv4-only |
| network | +--------+ | network |
| | | DNS + | | |
| | --| DNS64 |-- | +----+ |
| +----+ | | +--------+ | | | H2 | |
| | H1 | |--| |--| +----+ |
| +----+ | | +--------+ | | 192.0.2.1 |
| 2001:db8::1 | --|stateful|-- | |
| | | NAT64 | | |
| | +--------+ | |
+--------------+ +--------------+
Regards,
Jordi
@jordipalet
> El 9 jul 2026, a las 19:00, John R Levine <[email protected]> escribi=C3=B3=
:
>=20
>>=20
>> A you know that figure is inherited from RFC6146, which is meant to prov=
ide a "simple example".
>> Jordi did actually proposed a revised version that I found confusing. I =
asked him to revert the change and leave 6146.
>=20
> My impression is that the DNS and NAT talk to both hosts on both networks=
so the figure would look something like this:
>=20
>=20
> +----------------+ +---------------+
> | IPv6 network | | IPv4 |
> | | +-------------+ | network |
> | |---+--| Name server |--+--| |
> | | | | with DNS64 | | | +----+ |
> | +----+ | | +-------------+ | |--| H2 | |
> | | H1 |----| | | | +----+ |
> | +----+ | | +-------+ | | 192.0.2.1 |
> |2001:db8::1 |---+------| NAT64 |----+--| |
> | | +-------+ | |
> | | | |
> +----------------+ +---------------+
>=20
>=20
>>> -----Message d'origine-----
>>> De : John Levine via Datatracker <[email protected]>
>>> Envoy=C3=A9 : jeudi 9 juillet 2026 00:04
>>> =C3=80 : [email protected]
>>> Cc : [email protected]; last-
>>> [email protected]; [email protected]
>>> Objet : draft-ietf-v6ops-rfc6146-bis-10 telechat Artart review
>>>=20
>>>=20
>>> Document: draft-ietf-v6ops-rfc6146-bis
>>> Title: Stateful NAT64: Network Address and Protocol Translation
>>> from IPv6 Clients to IPv4 Servers Reviewer: John Levine Review
>>> result: Ready with Issues
>>>=20
>>> ARTART last call review of draft-ietf-v6ops-rfc6146-bis
>>>=20
>>> Reviewer: John Levine
>>>=20
>>> Overall: Still ready with Issues
>>>=20
>>> In the previous review I called out two issues, the confusing
>>> Figure one, and the lack of DNSSEC concerns in the security
>>> section. The second issue is fixed with a short addition, the
>>> first unfortunately is not.
>>>=20
>>> While the authors removed a few line segments from Figure 1, it
>>> doesn't help since all of the same issues remain. Rather than
>>> trying to tweak it, the authors could start over on a piece of
>>> paper with a sketch of the actual topology, then transcribe it
>>> preferably into SVG or if need be ASCII art.
>>>=20
>>=20
>> ________________________________________________________________________=
____________________________________
>> Ce message et ses pieces jointes peuvent contenir des informations confi=
dentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu 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.
>>=20
>> 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 d=
elete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have be=
en modified, changed or falsified.
>> Thank you.
>>=20
>=20
> Regards,
> John Levine, [email protected], Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>=20
> _______________________________________________
> art mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
**********************************************
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 con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.
--Apple-Mail=_68D568AE-7F89-43DC-93AF-C569FE6A2315
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" c=
ontent=3D"text/html; charset=3Dutf-8"></head><body style=3D"overflow-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Jo=
hn,<div><br></div><div>There are many deployments choices for NAT64 and DNS=
64. I=E2=80=99ve depicted them in <a href=3D"https://datatracker.ietf.=
org/doc/rfc8683/">https://datatracker.ietf.org/doc/rfc8683/</a>.</div><div>=
<div><br></div><div>Basically, yes both the DNS64 and the NAT64 should be a=
ble to be reachable from the IPv6-only network and (typically) in a differe=
nt interface to the IPv4-only.</div><div><br></div></div><div>The one you=
=E2=80=99re suggesting is very close to the one I=E2=80=99ve prepared, howe=
ver Med suggested avoiding such changes as it was well understood in the or=
iginal RFC6146:</div><div><br></div><div><p style=3D"margin: 0px; font-styl=
e: normal; font-variant-caps: normal; font-width: normal; font-size: 16px; =
line-height: normal; font-family: Menlo; font-size-adjust: none; font-kerni=
ng: auto; font-variant-alternates: normal; font-variant-ligatures: normal; =
font-variant-numeric: normal; font-variant-east-asian: normal; font-variant=
-position: normal; font-variant-emoji: normal; font-feature-settings: norma=
l; font-optical-sizing: auto; font-variation-settings: normal; color: rgba(=
0, 0, 0, 0.85); background-color: rgb(255, 255, 255);">+--------------+&nbs=
p; +--------------+=
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| IPv6-only | =
| IPv4-only |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| network | +--------+ =
| network |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| | &nb=
sp; | DNS + | | =
|</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| | --|=
DNS64 |-- | +----+ |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| +----+ | | +--------+ |&nbs=
p; | | H2 | |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| | H1 | |--| &=
nbsp; |--| +----+ |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| +----+ | | +--------+ |&nbs=
p; | 192.0.2.1 |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| 2001:db8::1 | --|stateful|-- | &nbs=
p; |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| | &nb=
sp; | NAT64 | | =
|</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">| | &nb=
sp; +--------+ | &nbs=
p; |</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; fon=
t-width: normal; font-size: 16px; line-height: normal; font-family: Menlo; =
font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal=
; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-variant-emoji: no=
rmal; font-feature-settings: normal; font-optical-sizing: auto; font-variat=
ion-settings: normal; color: rgba(0, 0, 0, 0.85); background-color: rgb(255=
, 255, 255);">+--------------+ &nb=
sp; +--------------+</p></div><div><br></div><div>Regards,</d=
iv><div><div><div>Jordi<br><br>@jordipalet<br></div>
</div>
<div><br><blockquote type=3D"cite"><div>El 9 jul 2026, a las 19:00, John R =
Levine <[email protected]> escribi=C3=B3:</div><br class=3D"Apple-inter=
change-newline"><div><div><blockquote type=3D"cite"><br>A you know that fig=
ure is inherited from RFC6146, which is meant to provide a "simple example"=
.<br>Jordi did actually proposed a revised version that I found confusing. =
I asked him to revert the change and leave 6146.<br></blockquote><br>My imp=
ression is that the DNS and NAT talk to both hosts on both networks so the =
figure would look something like this:<br><br><br> =
+----------------+ &n=
bsp;  =
; +---------------+<br> &nbs=
p; | IPv6 network | &n=
bsp;  =
; | IPv4 &=
nbsp; |<br> &nbs=
p; |  =
; | +-------------+ | =
network |<br> &=
nbsp; | &n=
bsp; |---+--| Name server |--+--| =
|<br> &nb=
sp; | &nbs=
p; | | | w=
ith DNS64 | | | +----+ |<br> &nbs=
p; |  =
;+----+ | | +-------------+ | &nb=
sp;|--| H2 | |<br> &n=
bsp; | | H1 |----| | &=
nbsp; &nbs=
p; | | +----+ |<br> &n=
bsp; | &nb=
sp;+----+ | | +=
-------+ | | 192.0.2.1 |<br> &nbs=
p; |2001:db8::1 |---+-=
-----| NAT64 |----+--| &nbs=
p; |<br> &=
nbsp; | &n=
bsp; | +-------+=
| =
|<br> &nb=
sp; | &nbs=
p; |  =
; &n=
bsp; | &nb=
sp; |<br> =
+----------------+ &n=
bsp;  =
;+---------------+<br><br><br><blockquote type=3D"cite"><blockquote type=3D=
"cite">-----Message d'origine-----<br>De : John Levine via Datatracker=
<[email protected]><br>Envoy=C3=A9 : jeudi 9 juillet 2026 00:04<=
br>=C3=80 : [email protected]<br>Cc : draft-ietf-v6ops-rfc6146-bis.all=
@ietf.org; last-<br>[email protected]; [email protected]<br>Objet : draft-iet=
f-v6ops-rfc6146-bis-10 telechat Artart review<br><br><br>Document: draft-ie=
tf-v6ops-rfc6146-bis<br>Title: Stateful NAT64: Network Address and Protocol=
Translation<br>from IPv6 Clients to IPv4 Servers Reviewer: John Levine Review<br>result: Ready with Issues<br><br>ARTART last call review=
of draft-ietf-v6ops-rfc6146-bis<br><br>Reviewer: John Levine<br><br>Overal=
l: Still ready with Issues<br><br>In the previous review I called out two i=
ssues, the confusing<br>Figure one, and the lack of DNSSEC concerns in the =
security<br>section. The second issue is fixed with a short addition,=
the<br>first unfortunately is not.<br><br>While the authors removed a few =
line segments from Figure 1, it<br>doesn't help since all of the same issue=
s remain. Rather than<br>trying to tweak it, the authors could start over o=
n a piece of<br>paper with a sketch of the actual topology, then transcribe=
it<br>preferably into SVG or if need be ASCII art.<br><br></blockquote><br=
>__________________________________________________________________________=
__________________________________<br>Ce message et ses pieces jointes peuv=
ent contenir des informations confidentielles ou privilegiees et ne doivent=
donc<br>pas etre diffuses, exploites ou copies sans autorisation. Si vous =
avez recu ce message par erreur, veuillez le signaler<br>a l'expediteur et =
le detruire ainsi que les pieces jointes. Les messages electroniques etant =
susceptibles d'alteration,<br>Orange decline toute responsabilite si ce mes=
sage a ete altere, deforme ou falsifie. Merci.<br><br>This message and its =
attachments may contain confidential or privileged information that may be =
protected by law;<br>they should not be distributed, used or copied without=
authorisation.<br>If you have received this email in error, please notify =
the sender and delete this message and its attachments.<br>As emails may be=
altered, Orange is not liable for messages that have been modified, change=
d or falsified.<br>Thank you.<br><br></blockquote><br>Regards,<br>John Levi=
ne, [email protected], Taughannock Networks, Trumansburg NY<br>Please conside=
r the environment before reading this e-mail. https://jl.ly<br><br>________=
_______________________________________<br>art mailing list -- [email protected]=
<br>To unsubscribe send an email to [email protected]<br></div></div></blo=
ckquote></div><br></div><br>**********************************************<=
br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.<br>
<br>
</body></html>
--Apple-Mail=_68D568AE-7F89-43DC-93AF-C569FE6A2315--
--===============5684357807284632303==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KYXJ0IG1haWxp
bmcgbGlzdCAtLSBhcnRAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBh
cnQtbGVhdmVAaWV0Zi5vcmcK
--===============5684357807284632303==--