IETF Logo Mail Archive

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

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Fri, 05 July 2019 20:11 UTC

Return-Path: <albert.e.manfredi@boeing.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 437E1120118; Fri, 5 Jul 2019 13:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 RX6qQUbslr-a; Fri, 5 Jul 2019 13:11:22 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEEEB1200EF; Fri, 5 Jul 2019 13:11:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id x65KBHck010679; Fri, 5 Jul 2019 16:11:17 -0400
Received: from XCH16-01-11.nos.boeing.com (xch16-01-11.nos.boeing.com [144.115.66.39]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id x65KBC78010646 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 5 Jul 2019 16:11:12 -0400
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-11.nos.boeing.com (144.115.66.39) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1713.5; Fri, 5 Jul 2019 13:11:11 -0700
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.1713.004; Fri, 5 Jul 2019 13:11:11 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
CC: IPv6 Operations <v6ops@ietf.org>, 6man <6man@ietf.org>
Subject: RE: NAT64 in RA, draft-ietf-6man-ra-pref64
Thread-Topic: NAT64 in RA, draft-ietf-6man-ra-pref64
Thread-Index: AdUx0cT0siGdnGcqO0Oy0E0RKZ7PVQAPuuUAADPtxoAADKc3gAAjb/oAAA0OlrA=
Date: Fri, 05 Jul 2019 20:11:11 +0000
Message-ID: <d4d2f637b80544708def95dd77af4d81@boeing.com>
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>
In-Reply-To: <DM6PR15MB2506ABCBD8457003114E60EBBBF50@DM6PR15MB2506.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 6D89DBE17893F652DAA7855B1855B9483489F02EA855E84D4311BAB3873358512000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_Ba7hGMeVjlJOozI7TE2WN8v1Cg>
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 20:11:24 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Mudric, Dusan (Dusan)

> - How can DNS64 tell IPv6 only client the IP of IPv4 only client, and vice versa?

IPv6 to IPv4 should be straightforward, because it's a one-to-one relationship. The other way around would normally not work, but everyone has been accustomed to that with IPv4 NAPT already. The client behind the NAPT initiates.

> Is DNS64 server returning IPv4ony client address to IPv6only client, using the A RR?

The DNS synthesizes the IPv6 address, which has the IPv4 address embedded in it.

> - How can IPv4only client get the address of IPv6only client (or, it is impossible for IPv4only client to get IPv6 address of IPv6only client)?

That's clearly more difficult, which is why the normal course of action is for the IPv6 client to initiate the session.

> - Do these IPv4 and IPv6 client addresses need to be pre-configured on the translator and/or DNS64?

For IPv4 to IPv6, if you must allow the IPv4 client to initiate the session, you'd have to have preconfigure something.

Bert

v2.23.0 | Report a Bug | By Email