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

Jen Linkova <furry13@gmail.com> Fri, 05 July 2019 02:21 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 3A682120179; Thu, 4 Jul 2019 19:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 adL2_0vAM1bF; Thu, 4 Jul 2019 19:21:38 -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 B648912010F; Thu, 4 Jul 2019 19:21:38 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id a15so9730129qtn.7; Thu, 04 Jul 2019 19:21:38 -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=M/RFvdlV8rwPFY+uY1mVOPKUNPAWi9Cx1t2FCJgNPi8=; b=AbOz+2bpfMpujMR3vUGvx+jqo6UPinBKY537ZlG3vAPxtlDNgIoe9RugSxC7NaKaR6 2FmGifz+bOkLmfAL/gh2nw4j92e6kl9ImI+GN81f4pogp8wUxIYmp2SBUEhdrQnTYaws h+rRx5fBw+doNH4jcNaxsgpYbOEY0nQ/aKEnfqpbjUAMXhV0xs3gi5aiQbZ6R6h8ZawX hZ0Ui/2WVzRQgw0BuxUf1iHClUkbGauQ9XolAxEoYUYC88yVzbCjthwO+nda6T4nbjkC rXRczx2fRtm+4iym/Pr9eXp+HMfdE0riltZfGHtg5OPFCoJYeJcVmDwmILzFr7pqtPwe hE7A==
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=M/RFvdlV8rwPFY+uY1mVOPKUNPAWi9Cx1t2FCJgNPi8=; b=OJM2j5Xe5eBNEwwFtP11FlWRq19cMArsPiaGI4nfhQN/GkMlMa/jifQRBSOWU5oQ0C rSbrehqAhbUKwxu/2i+RDlojUCcMgBJyMyfHGepWD32WmVtujK+OJ1cvH38t0Ic9zHGu 4YShtyncFpfAV5IN1fkqJ6v64Pq3Hjf8OW0Pwy8XDFW7NN9Yf1HmBf9UW8xgFXDEhF0w 2fk4xxJrNfHhzaH3Os9Jn7rET2Fi1yurUJQ/+4FEHfnLIu3S1nkwZd/mC1oCbDykS2RE fcfULj2RgG0pNUynKRiUID6ax0ViC9EbimvHh8/R9LNO8eXgJlxtlNxK847o/rONUX5D EzZA==
X-Gm-Message-State: APjAAAWv+9CstOAxakOwNzezoW0LuiBBWHg3bpB6ouIAA6R9+P0XveFi QQD6suMxjzp8DFn5h+VjQIkN8lK8qZBLTMcJpBE=
X-Google-Smtp-Source: APXvYqyOF2sU2QmURyLULvpTRc/rPdaF616fyl4XrIhJeFvsSep8vggvyXeyY0wxaN3pdY6OHCp/w3/tluf/6npZ+Fs=
X-Received: by 2002:ac8:2e59:: with SMTP id s25mr731474qta.94.1562293297445; Thu, 04 Jul 2019 19:21:37 -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>
In-Reply-To: <DM6PR15MB250640D3141DCB2C64789B95BBFA0@DM6PR15MB2506.namprd15.prod.outlook.com>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 05 Jul 2019 12:21:25 +1000
Message-ID: <CAFU7BAROif-44uFy1+oiutsQLiFOa09jM1Ve_8qaqpr1TPLGyQ@mail.gmail.com>
Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
Cc: Fred Baker <fredbaker.ietf@gmail.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/eqBtVKuJrIKhEnKmp8hIAVQVLJM>
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: Fri, 05 Jul 2019 02:21:40 -0000

Hi Dusan,

On Fri, Jul 5, 2019 at 6:19 AM Mudric, Dusan (Dusan) <dmudric@avaya.com> wrote:
> What is the best reference document for a Translator that facilitates:
>
> - IPv4only - to - IPv6only, and

https://tools.ietf.org/html/rfc7755

> - IPv6only - to - IPv4Only

https://tools.ietf.org/html/rfc6146

> 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://tools.ietf.org/html/rfc6052.


> > -----Original Message-----
> > From: Fred Baker <fredbaker.ietf@gmail.com>
> > Sent: Wednesday, July 3, 2019 3:32 PM
> > To: Mudric, Dusan (Dusan) <dmudric@avaya.com>
> > Cc: 6man <6man@ietf.org>; IPv6 Operations <v6ops@ietf.org>
> > Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
> >
> >
> >
> > > On Jul 3, 2019, at 12:01 PM, Mudric, Dusan (Dusan) <dmudric@avaya.com>
> > 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
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



-- 
SY, Jen Linkova aka Furry