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

Jen Linkova <furry13@gmail.com> Tue, 09 July 2019 01:34 UTC

Return-Path: <furry13@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492E71203CE; Mon, 8 Jul 2019 18:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.453
X-Spam-Level:
X-Spam-Status: No, score=-0.453 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyPvVt8OEYtM; Mon, 8 Jul 2019 18:34:08 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CDD312030F; Mon, 8 Jul 2019 18:34:08 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id h18so12633139qtm.9; Mon, 08 Jul 2019 18:34:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IWLOcMYgLdYzJFpA6aiNMUlE224uHjnnzUJKO+MdkpY=; b=bNYo6EgR+3H6Tzy60EytwN+V/Q23t1p2IEMEkNa+aVTrulBu9bMWYmngBiadSRDjrY vsEVddh72kku4UlxxoD0Jr1dugUsqCjIKF+wNbjjqYfT0RzrFqliOuSJwz/F367Ys1CU 6C7W5cisU2TlBiKlN5y32nNmU/BQ/OPI64qt1FrvW8i9vSEV4LYJFCp6qTrMKYuG2HqT RM9cFRdfWW8qF4X1fcIPpeW/kHmJ0PFbq80pVgJN2LAAnxSjSRF6o+zM4D2szAW1kt+O MrDQ5qAuofBjrSmJpdWNN+Y36EApRdh+5GA2C6pObRa6lErAuv63kAA2056ilTU209sM FfBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IWLOcMYgLdYzJFpA6aiNMUlE224uHjnnzUJKO+MdkpY=; b=QI3QkxTv3S7gN0RHbSGwxGa6wpOD1ujFczPSZcSxp6SZqnN71d/WA8TxybCc3RHyif Kif+wsSy8E66yjWynpn3qH4jUTQxl4/BV5uqgWsTf0ab3EIAUi4BHCEXiOjwyldJleor 9D2GukJY6kYxsNgcgKOHKLqCvveLd+2BRgh8LHrJP5WKmktFPSwYCu8IaCzVsTsr/z5S k0RtXAJZTobksH2ynMB1BnCtRI+waSl1BFlT4nBtqvaVyiDQN1qy/LoUcJ1Wdd5wuukr FTCiUc3UTFECnInXb02YQ7y/Bx0kdLAb5NOoyt9hwwu4qL9kByev2ZP5oKMzE4UmWWv3 qSFg==
X-Gm-Message-State: APjAAAWlGFU6+33yWPH2+ai506HcXjxlYNlccy7LXmMIMnBCz8NWcjAN KoPmXlJ3F38Zg3PHNbZ7bdJZ40yhrEQjVzMcjvw=
X-Google-Smtp-Source: APXvYqzXKDjPPaboyRFDGFDJ+cd3SQliAZEISSJ/gmUuAk+y87CwHp1tijLECwAtqUbVZaFypXMSiAT4PnyYbIXb75k=
X-Received: by 2002:ac8:2b90:: with SMTP id m16mr16093450qtm.384.1562636047273; Mon, 08 Jul 2019 18:34:07 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR15MB2506C03D1D88F2785B5016C1BBFB0@DM6PR15MB2506.namprd15.prod.outlook.com> <675D1F10-02FF-4AB4-88E3-5A0D95A34ABF@gmail.com> <DM6PR15MB250640D3141DCB2C64789B95BBFA0@DM6PR15MB2506.namprd15.prod.outlook.com> <CAFU7BAROif-44uFy1+oiutsQLiFOa09jM1Ve_8qaqpr1TPLGyQ@mail.gmail.com> <DM6PR15MB2506ABCBD8457003114E60EBBBF50@DM6PR15MB2506.namprd15.prod.outlook.com> <d4d2f637b80544708def95dd77af4d81@boeing.com> <DM6PR15MB2506F92308CA8DA8921BA0A5BBF60@DM6PR15MB2506.namprd15.prod.outlook.com>
In-Reply-To: <DM6PR15MB2506F92308CA8DA8921BA0A5BBF60@DM6PR15MB2506.namprd15.prod.outlook.com>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 09 Jul 2019 11:33:55 +1000
Message-ID: <CAFU7BAQSUsDWFu6QGP4K4g+XAQAO5G23F+Z7jC5f=wu-Cvj=Vw@mail.gmail.com>
Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
Cc: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, IPv6 Operations <v6ops@ietf.org>, 6man <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/XX6fwWedWjCQVyX1HqZmjBc_ouA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2019 01:34:14 -0000

On Tue, Jul 9, 2019 at 1:50 AM Mudric, Dusan (Dusan) <dmudric@avaya.com> wrote:
> [Dusan] What if IPv4only client needs to initiate the session to IPv6only client? What is the solution for that use case?

https://tools.ietf.org/html/rfc7755 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://ripe64.ripe.net/presentations/67-20120417-RIPE64-The_Case_for_IPv6_Only_Data_Centres.pdf



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