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

[JORDI PALET MARTINEZ <[e-mail]>]

If you do "manual" EAM configurations at each side, it is fully solved, but is this useful in a generic case.

So what I'm trying to do with the optimization is that the EAM creation is "automated".

Regards,
Jordi
@jordipalet
 
 

El 9/7/19 22:13, "ipv6 en nombre de Mudric, Dusan (Dusan)" <[e-mail] en nombre de [e-mail]> escribió:

    Thanks Jen. 
    
    In your example " IPv4-only client needs to talk to the Ipv6-only server". If IPv4-only client needs to talk to the Ipv6-only client, the call flow will be the same? In the other direction, IPv6-only client calling IPv4-only client needs to use DNS64/NAT64, as in your previous example (attached). This means, for bi-directional communication NAT46/DNS46 and NAT64/DNS64 need to be used (may be my terminology is not quite correct). 
    
    However, Jordi said that the problem is not fully solved yet ("the *actual* implementation of 464XLAT/NAT64 doesn't allow IPv4-only hosts to connect to IPv6-only hosts.") and he is writing draft-palet-v6ops-464xlat-opt-cdn-caches. What is in the current technology that prevents bi-directional call flow between IPv4-ony and IPv6-only hosts?
    
    Dusan
    
    > -----Original Message-----
    > From: Jen Linkova <[e-mail]>
    > Sent: Monday, July 8, 2019 9:34 PM
    > To: Mudric, Dusan (Dusan) <[e-mail]>
    > Cc: Manfredi (US), Albert E <[e-mail]>; IPv6
    > Operations <[e-mail]>; 6man <[e-mail]>
    > Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
    > 
    > On Tue, Jul 9, 2019 at 1:50 AM Mudric, Dusan (Dusan) <[e-mail]>
    > wrote:
    > > [Dusan] What if IPv4only client needs to initiate the session to IPv6only
    > client? What is the solution for that use case?
    > 
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__tools.ietf.org_html_rfc7755&d=DwIBaQ&c=BFpWQw8bsuKpl1SgiZH64Q
    > &r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=_cWRsdzof5dXI
    > 9yTQH51H_KHtcSRcMAtARArKVcdnWM&s=wDxWEwS-e-N-I0oAfcdi-
    > 5GucNiCQpR32t9Rw4RZyn0&e= mentioned before.
    > 
    > IPv4-only client -- IPv4-enabled network--- SIIT translator ---- IPv6-only LAN -
    > -- IPv6-only server.
    > 
    > Let's say  your IPv4-only client needs to talk to the Ipv6-only server, ipv6-
    > only.example.net.
    > For this to happen the owner of the Ipv6-only server needs to configure the
    > translator (SIIT box in the diagram above).
    > The owner would create a DNS A RR for  ipv6-only.example.net. - let's say,
    > 192.0.2.2 Ipv6-only server would have an IPv6 address which has that IPv4
    > address encoded - for example, 2001:db8:1::192.0.2.2 That IPv4 address (or
    > the prefix most likely) will be routed to the translator.
    > 
    > So your Ipv4-only client sends a DNS request to resolve ipv6-
    > only.example.net, gets 192.0.2.2 back, sends a packet to 192.0.2.2.
    > The packet reaches the translator. The translator translates IPv4 packet to
    > IPv6 packet and sends it to the server (note that the destination IPv6 address
    > can be easily constructed as the translator knows the prefix and just adds the
    > IPv4 address - 192.0.2.2 - to that prefix to get the destination IPv6 address.
    > IPv6 source address is synthesised in the same way from the client IPv4
    > address).
    > 
    > Here is a nice talk Tore Anderson gave at RIPE 7 years ago:
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__ripe64.ripe.net_presentations_67-2D20120417-2DRIPE64-2DThe-
    > 5FCase-5Ffor-5FIPv6-5FOnly-5FData-
    > 5FCentres.pdf&d=DwIBaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJ
    > xhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=_cWRsdzof5dXI9yTQH51H_KHtcS
    > RcMAtARArKVcdnWM&s=GsPTdPr_ZwWYK13LIrhTv9rYM6dYJfgbT8HtLwVRk
    > Zo&e=
    > 
    > 
    > 
    > > > For IPv4 to IPv6, if you must allow the IPv4 client to initiate the
    > > > session, you'd have to have preconfigure something.
    > > [Dusan] Where and how is this configuration done?
    > 
    > On the translator which connects IPv6-only network to dual-stack/IPv4-only
    > one.
    > In general, when you need to let one protocol talk to another, you'd have a
    > point (or the edge) where those two networks meet each other.
    > Usually you'd have a box (or boxes) interconnecting them - quite often it's
    > exactly the box you'd need to configure ;)
    > 
    > --
    > SY, Jen Linkova aka Furry
    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    [e-mail]
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------
    



**********************************************
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.