IETF Logo Mail Archive

Re: [IPsec] [sunset4] ietf-nat64 - Internet VPN clients

Bill Fenner <fenner@fenron.com> Mon, 12 December 2016 16:45 UTC

Return-Path: <fenner@fenron.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBB3A12944B for <ipsec@ietfa.amsl.com>; Mon, 12 Dec 2016 08:45:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level:
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fenron.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 3Mw2YTH9OFMS for <ipsec@ietfa.amsl.com>; Mon, 12 Dec 2016 08:45:17 -0800 (PST)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 8C670129DF2 for <ipsec@ietf.org>; Mon, 12 Dec 2016 08:40:52 -0800 (PST)
Received: by mail-ua0-x230.google.com with SMTP id b35so86444146uaa.3 for <ipsec@ietf.org>; Mon, 12 Dec 2016 08:40:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fenron.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jD51K4V7+bNvrWanQSCAfr4bGjD2jq8gb2p8cD7kU6k=; b=Uvu5P59M+Mnrod9XcYrfArO59W3x8xEZRR7ED2QdxAzh6Q9b0+W+qSK1Y1apjtQJRG KhfniEtD8crARlaN6qnYptFJeQ+2LZmCCOVsHaZyJwkKzOrCcufX9ugVJS9RYZ04CQSz xHSkHwLt5urODi50t1K+GwjHZQFsIbNx42zk0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jD51K4V7+bNvrWanQSCAfr4bGjD2jq8gb2p8cD7kU6k=; b=GaPmLL4lViG180G6A7HtWLcPE7Bi5fRpSlU9plsrzvDuiX1TSwlYiR9WaU9blEtvEC 5jUN1o8nosQapYfYLT223uh+nrpUSiccB+FLZM2NBxIq749+yKT7mPzV3chHExT7dRrQ RV3lnA5QG2VBxmlAl6yA6xODJBRwjUul8v1EpSkWlW/97eHkmSjFKsTxnlfsEvMPFxLt oJyXmJ5FYoIp2j5gC/vkXrN2/Gu1AxUbx8b5CvyxOM0PZah+F2DTe/9/cLONF9pWxq5+ ViUYkK1Ygq8whoL+dGEC7YrNf7cgq+sozEQeszS2onkNl8KGe2uiG40vjmK8/aJmL05h B8mQ==
X-Gm-Message-State: AKaTC02XHvuROeUlDlPUpOet4wvwFO3FOpMpkDU+RnOEb4iTcMYOmp69yRf5ugDF8PDWV0HrBk2dLIr66Wb7mg==
X-Received: by 10.176.2.167 with SMTP id 36mr58640834uah.41.1481560851638; Mon, 12 Dec 2016 08:40:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.34.168 with HTTP; Mon, 12 Dec 2016 08:40:51 -0800 (PST)
In-Reply-To: <6205.1481319551@obiwan.sandelman.ca>
References: <6536E263028723489CCD5B6821D4B2132C3DF16D@UK30S005EXS06.EEAD.EEINT.CO.UK> <D45333DE.87DB3%evyncke@cisco.com> <6536E263028723489CCD5B6821D4B2132C401D4E@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAATsVbbRWpscHdRYGDfo04JnWeHE6Fmi1vpF87ox=NnuG9iH7w@mail.gmail.com> <D52B781A-39B2-4A74-9484-43DA1C12138C@lists.zabbadoz.net> <6205.1481319551@obiwan.sandelman.ca>
From: Bill Fenner <fenner@fenron.com>
Date: Mon, 12 Dec 2016 11:40:51 -0500
Message-ID: <CAATsVbYryKN3hH0bmh1CLcD-wk9f=Ov1z_0GYaWp4WrWQQWyYw@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="001a113acf724674fc054378c466"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/aUH5U7bYcScgsm10QEorjAyDYgU>
Cc: ipsec@ietf.org, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, "sunset4@ietf.org" <sunset4@ietf.org>
Subject: Re: [IPsec] [sunset4] ietf-nat64 - Internet VPN clients
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2016 16:45:19 -0000

On Fri, Dec 9, 2016 at 4:39 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote:
>     > That’s maybe for the ipsec wg but while native IPv6 VPN has been
> working fine
>     > for me for ages, how would a NAT64 policy exchange actually look
> like (I am
>     > thinking about what is done for IPv4 NAT or double NAT within the
> same
>
> NAT64 depends upon DNS64 to provide a fake IPv6 target for the application
> to
> connect to.
>
> So, for IPsec to work over NAT64 would require:
>
> 1) IPsec able to traverse over IPv6 networks (outer IP header being IPv6).
> 2) An IKEv2 deamon that uses DNS to find it's IPv4-only gateway, so that it
>    can be lied to about the returned AAAA record.
>
> In Bill's case, he hasn't got (1), so it's not going to work.
>

Well, I was using Apple's "Cisco IPSec" client for OSX 10.11.5, and it's
the server side implementation that says that IPv6 transport is not
supported.  So, perhaps, I have a client that would support it.


> Once he has (1) (the upgrade he mentioned), if his policy lets him use DNS
> to
> find his gateway, and he doesn't do DNSSEC on that, then it ought to work.
>

That is what I have configured.

  Bill

v2.23.0 | Report a Bug | By Email