IETF Logo Mail Archive

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

Fred Baker <fredbaker.ietf@gmail.com> Wed, 03 July 2019 19:32 UTC

Return-Path: <fredbaker.ietf@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 D579A1203F6; Wed, 3 Jul 2019 12:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 GNrIZHMVMFOA; Wed, 3 Jul 2019 12:32:16 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 9650E12016E; Wed, 3 Jul 2019 12:32:16 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id z23so3547336ote.13; Wed, 03 Jul 2019 12:32:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+Q9kwFBgNBkS5yOd2f9M8yVd2uEf72PFor1cKIb72w8=; b=HmUngBuhkjyrokd/FjlFXDRTMTONOttCr0y8zdSnNo8dlsop1dZVVIMGSEbEFKXL2B sVjj6omVnCjXFL70j4p/pJsIiOQKscqyzDuHFRcHijug7wnzs8Fze7vBxk5BAXQnNeGk UG35w6PvFERK+Z0Elf1AMuuUQv4jxvOBpbTRuztq07//n1WKRdkracOb0nAiUdMPHwoB lzGVHbVHjbObLcvQVfoC2hu3WnwLII56IJtso4+1VQGE8hSlYSHKbvafHM2SUgzNUV44 xG/2DQbCFdODCkb5Unfzqz2zSz/ZktU9ouNM0YAOYeomkNvx8LjtSBXvRbtXgdS24bJi 1YtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+Q9kwFBgNBkS5yOd2f9M8yVd2uEf72PFor1cKIb72w8=; b=mpttBQ27jTwfwQlkl2SHd+nfP4YQT5Kt0IYUYhHsxLiMgA1Q0WvthHJhlNRF2fCMlg 8yjtDBZWNh0ho7qyXWVYoWL/xXWAg91KSnM+zOkbIH5UgfRvsRySstL6MxUapswu9gsm SJymywlvHs00vnVgfNtIt8394lP8IFwiCIMkhTvs0bQG8CDJtVF6eK8q8HKkCe1MgAg7 /mHcB4L7lEUaJ+L3MBxcoCo+45MnNGNgtrBdCuhH1nHJ7x82habEwhoL1MCroMaHwZPj Aw1DjXPDdEIvbfDI/cDUvmNSCeF82LBZvvB1TxRyhRfYEdJr3nBTJWDJP1d/8rabAjhX YwTg==
X-Gm-Message-State: APjAAAUw5ayiXnisujKaG9RMAprAQy6zS9FbqxqPg6HtHIM9KhrosAcG wzV0dzzargZ53tJcImup2cE17xVG
X-Google-Smtp-Source: APXvYqzfqEB9Ig59zx5Cm0o3xrDUN0ismkgPCuhA8euUi7OiI2JssAcrp8p2QFLEBANyviHW6C0iow==
X-Received: by 2002:a9d:d87:: with SMTP id 7mr29375988ots.263.1562182336026; Wed, 03 Jul 2019 12:32:16 -0700 (PDT)
Received: from ?IPv6:2600:8802:5903:df16::1006? ([2600:8802:5903:df16::1006]) by smtp.gmail.com with ESMTPSA id j8sm1051202otl.9.2019.07.03.12.32.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jul 2019 12:32:15 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3560.7\))
Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <DM6PR15MB2506C03D1D88F2785B5016C1BBFB0@DM6PR15MB2506.namprd15.prod.outlook.com>
Date: Wed, 03 Jul 2019 12:32:14 -0700
Cc: 6man <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <675D1F10-02FF-4AB4-88E3-5A0D95A34ABF@gmail.com>
References: <DM6PR15MB2506C03D1D88F2785B5016C1BBFB0@DM6PR15MB2506.namprd15.prod.outlook.com>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
X-Mailer: Apple Mail (2.3560.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/JRveOU-GMSLY4uDxkNw3VVKNKxc>
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: Wed, 03 Jul 2019 19:32:18 -0000


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

v2.23.0 | Report a Bug | By Email