RE: NAT64 in RA, draft-ietf-6man-ra-pref64

["Mudric, Dusan (Dusan)" <[e-mail]>]

Hi Jen,

If IPv4only - to - IPv6only client initiated communication needs SIIT-DC (rfc7755), and IPv6only - to - IPv4Only client initiated communication needs Stateful NAT64 (rfc6146), can the two protocols be combined in two device (DNS and  translator) and used at the same time for bidirectional communication? Is it called NAT64-NAT46 or something similar?

- How can DNS64 tell IPv6 only client the IP of IPv4 only client, and vice versa? Is DNS64 server returning IPv4ony client address to IPv6only client, using the A RR? 
- How can IPv4only client get the address of IPv6only client (or, it is impossible for IPv4only client to get IPv6 address of IPv6only client)? 
- Do these IPv4 and IPv6 client addresses need to be pre-configured on the translator and/or DNS64?

Thanks,
Dusan.

> -----Original Message-----
> From: Jen Linkova <[e-mail]>
> Sent: Thursday, July 4, 2019 10:21 PM
> To: Mudric, Dusan (Dusan) <[e-mail]>
> Cc: Fred Baker <[e-mail]>; IPv6 Operations
> <[e-mail]>; 6man <[e-mail]>
> Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
> 
> Hi Dusan,
> 
> On Fri, Jul 5, 2019 at 6:19 AM Mudric, Dusan (Dusan) <[e-mail]>
> wrote:
> > What is the best reference document for a Translator that facilitates:
> >
> > - IPv4only - to - IPv6only, and
> 
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_html_rfc7755&d=DwIBaQ&c=BFpWQw8bsuKpl1SgiZH64Q
> &r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=rXn-
> qcfSIhjB1FVZq9fT0HWKIE4FsVW55Pw4ufcd4Qc&s=6jgy81ePeiWaBFML3XwP
> C3wDxGkyDrvzWG0Jg9Oog_w&e=
> 
> > - IPv6only - to - IPv4Only
> 
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_html_rfc6146&d=DwIBaQ&c=BFpWQw8bsuKpl1SgiZH64Q
> &r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=rXn-
> qcfSIhjB1FVZq9fT0HWKIE4FsVW55Pw4ufcd4Qc&s=SobSFuvzPm9XQ3bWhSEL
> bnhk4KtAaYJ7yB5QWf70A6A&e=
> 
> > clients message exchanges?
> >
> > Is this communication bidirectional or works only from IPv6only-to-IPv4only
> client (meaning IPv6only client has to initiate the communication)?
> >
> > How can Translator or DNS64 tell IPv6 only client the IP of IPv4 only client,
> and vice versa?
> 
> In a nutshell:
> 
> IPv6-only client asks DNS64 server for AAAA for, let's say,
> ipv4only.example.net As that server is IPv4-onl, does not have AAAA RR, the
> DNS64 server synthesise a new AAAA using an IPv6 prefix (usually /96 - the
> Well-Known Prefix is 64:ff9b::/96) and IPv4 address from the A RR. The
> algorithm described in rfc6147
> 
> So if ipv4only.example.net has an IPv4 address 192.0.2.2, then DNS64 will
> return 64:ff9b::192.0.2.2 as AAAA RR.
> The ipv6-only client would initiate a connection to that address . As
> NAT64 prefix is supposed to be routed to the NAT64 device, that device
> would translate IPv6 packet to IPv4 packet using the algorithm described in
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_html_rfc6052&d=DwIBaQ&c=BFpWQw8bsuKpl1SgiZH64Q
> &r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=rXn-
> qcfSIhjB1FVZq9fT0HWKIE4FsVW55Pw4ufcd4Qc&s=XTCYMjY3HOKEx535PU_I
> Ora8JAiRD_Uayt1SwrJnWv8&e=.
> 
> 
> > > -----Original Message-----
> > > From: Fred Baker <[e-mail]>
> > > Sent: Wednesday, July 3, 2019 3:32 PM
> > > To: Mudric, Dusan (Dusan) <[e-mail]>
> > > Cc: 6man <[e-mail]>; IPv6 Operations <[e-mail]>
> > > Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
> > >
> > >
> > >
> > > > On Jul 3, 2019, at 12:01 PM, Mudric, Dusan (Dusan)
> > > > <[e-mail]>
> > > wrote:
> > > >
> > > > [Dusan] Please clarify how IPv4-only host can reach IPv6 only
> > > > host, and vice
> > > versa. Also, how IPv6 only host can know IPv4 address of IPv4 only
> > > host, assuming IPv4 only host is in a public domain?
> > >
> > > Simple. Using a Translator, either at layer 3 or above it. Any other
> > > way doesn't work.
> > > --------------------------------------------------------------------
> > > ------------ The fact that there is a highway to hell and a stairway
> > > to heaven is an interesting comment on projected traffic volume...
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > [e-mail]
> > Administrative Requests:
> > https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mail
> >
> man_listinfo_ipv6&d=DwIBaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbL
> eaJxhf3
> > iCrhIoUWB8YLZU23029sMQGQ2kY&m=rXn-
> qcfSIhjB1FVZq9fT0HWKIE4FsVW55Pw4ufcd
> > 4Qc&s=GHcNdEhtOVJ_cLvOIIb6oNNDJIgpb8m_oqHiePqYicg&e=
> > --------------------------------------------------------------------
> 
> 
> 
> --
> SY, Jen Linkova aka Furry